DOMDocument::Save() Error

New home Forums Basic Version Troubleshooting DOMDocument::Save() Error

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • #21212
    jtresponse
    Member

    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
    JohnT

    #21224
    jtresponse
    Member

    Hi,

    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
    JohnT

    #21230
    SupportTeam
    Moderator

    Hi 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?

    #21235
    jtresponse
    Member

    Hi 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
    JohnT

    #21254
    SupportTeam
    Moderator

    Hi John

    Just to confirm, has this been resolved then? Was it related to your hosting?

    #21255
    jtresponse
    Member

    Hi,

    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
    JohnT

    #21345
    SupportTeam
    Moderator

    Hi JohnT

    So glad to hear it’s now working as expected. My apologies for the inconvenience caused.

Viewing 7 posts - 1 through 7 (of 7 total)
  • You must be logged in to reply to this topic.