New home › Forums › Basic Version › Troubleshooting › DOMDocument::Save() Error
Tagged: DOMDocument::save() XML
- This topic has 6 replies, 2 voices, and was last updated 4 years, 4 months ago by SupportTeam.
-
AuthorPosts
-
September 28, 2016 at 2:44 pm #21212jtresponseMember
Hi,
We have been using this plugin without any issues for many months, but have recently started getting the following error:
Warning: DOMDocument::save(): bad type specifier while parsing parameters in /homepages/0/d276782107/htdocs/MySite/wp-content/plugins/wp-google-maps/wpGoogleMaps.php on line 1902 Could not save XML file
And
Could not save marker XML file (/homepages/0/d276782107/htdocs/MySite/wp-content/uploads/wp-google-maps/1markers.xml) for Map ID 1
Does anyone know how we resolve this ?
Thanks
JohnTSeptember 29, 2016 at 11:29 am #21224jtresponseMemberHi,
Just to add:
If I google for the error message, I see lots of other sites that have the same issue, so it is not just me having the issue.Thanks
JohnTSeptember 29, 2016 at 12:14 pm #21230SupportTeamModeratorHi John
Please login to your site via FTP, go to wp-content/uploads/ and ensure that the wp-google-maps file is writable?
Does this help at all?
September 29, 2016 at 5:13 pm #21235jtresponseMemberHi Jarryd,
I’ve checked the permissions on wp-content/uploads/ AND wp-content/uploads/1markers.xml.
Both are writeable, and the error_log.txt in that folder is still being updated OK.
However,I had some other issues with the hosting package while investigating this.
Suddenly started getting 500 errors on the whole site.
Whatever 1 and 1 did to fix this, also fixed the XML save error.Regards
JohnTSeptember 30, 2016 at 2:39 pm #21254SupportTeamModeratorHi John
Just to confirm, has this been resolved then? Was it related to your hosting?
September 30, 2016 at 2:42 pm #21255jtresponseMemberHi,
Yes, it has been resolved.
It seemed to be to do with some resource issue on the hosting package.
It is with 1 and 1, and they were not too forthcoming about the details.Regards
JohnTOctober 5, 2016 at 2:41 pm #21345SupportTeamModeratorHi JohnT
So glad to hear it’s now working as expected. My apologies for the inconvenience caused.
-
AuthorPosts
- You must be logged in to reply to this topic.