Sitemap error with geodir_location_manager

This topic contains 3 replies, has 3 voices, and was last updated by  Kiran 7 years, 3 months ago.

We have moved to a support ticketing system and our forums are now closed.

Open Support Ticket

Tagged: 

  • Author
    Posts
  • February 4, 2017 at 4:29 pm #354897

    P O
    Expired Member
    Post count: 501

    Google says bad format file when sending sitemap.
    Trying to load the sitemap file, I get this instead of the actual sitemap:
    —————–
    This page contains the following errors:

    error on line 2 at column 1: Extra content at the end of the document
    Below is a rendering of the page up to the first error.
    —————–

    If I open the sitemap. the fist 18 lines have this:
    —————–
    <br />
    <b>Warning</b>: htmlspecialchars() expects parameter 1 to be string, object given in <b>/home/site/public_html/wp-content/plugins/geodir_location_manager/geodir_location_functions.php</b> on line <b>3659</b><br />
    <br />
    <b>Warning</b>: htmlspecialchars() expects parameter 1 to be string, object given in <b>/home/site/public_html/wp-content/plugins/geodir_location_manager/geodir_location_functions.php</b> on line <b>3659</b><br />
    <br />
    <b>Warning</b>: htmlspecialchars() expects parameter 1 to be string, object given in <b>/home/site/public_html/wp-content/plugins/geodir_location_manager/geodir_location_functions.php</b> on line <b>3659</b><br />
    <br />
    <b>Warning</b>: htmlspecialchars() expects parameter 1 to be string, object given in <b>/home/site/public_html/wp-content/plugins/geodir_location_manager/geodir_location_functions.php</b> on line <b>3891</b><br />
    <br />
    <b>Warning</b>: htmlspecialchars() expects parameter 1 to be string, object given in <b>/home/site/public_html/wp-content/plugins/geodir_location_manager/geodir_location_functions.php</b> on line <b>3911</b><br />
    <br />
    <b>Warning</b>: htmlspecialchars() expects parameter 1 to be string, object given in <b>/home/site/public_html/wp-content/plugins/geodir_location_manager/geodir_location_functions.php</b> on line <b>3891</b><br />
    <br />
    <b>Warning</b>: htmlspecialchars() expects parameter 1 to be string, object given in <b>/home/site/public_html/wp-content/plugins/geodir_location_manager/geodir_location_functions.php</b> on line <b>3911</b><br />
    <br />
    <b>Warning</b>: htmlspecialchars() expects parameter 1 to be string, object given in <b>/home/site/public_html/wp-content/plugins/geodir_location_manager/geodir_location_functions.php</b> on line <b>3891</b><br />
    <br />
    <b>Warning</b>: htmlspecialchars() expects parameter 1 to be string, object given in <b>/home/site/public_html/wp-content/plugins/geodir_location_manager/geodir_location_functions.php</b> on line <b>3911</b><br />
    —————–

    So the sitemap is not working because of this.

    How can I fix it ?

    Thank you.

    February 4, 2017 at 6:12 pm #354947

    Paolo
    Site Admin
    Post count: 31206

    Hi,

    those are not errors, they are just warnings.

    You can suppress them with this: https://wpgeodirectory.com/docs/faqs/help-i-get-a-php-warning-on-my-pages/

    If you provide a link and admin credentials, we will make sure to clear them in next release too.

    Thanks

    February 4, 2017 at 6:21 pm #354953

    P O
    Expired Member
    Post count: 501

    The problem is that you are injecting warnings into the sitemap, making it unusable and with errors for submitting it. (It is not hiding a warning in the site itself)

    I added the line to functions and it seems it is working.

    Thank you.

    February 7, 2017 at 4:49 am #356213

    Kiran
    Moderator
    Post count: 7069

    Hi P O,

    I can’t recreate these errors in my local site as well on our test sites. Can you provide your site FTP or details how to recreate these errors?

    This will help us to find problem and to fix it.

    Thanks,
    Kiran

  • Author
    Posts
Viewing 4 posts - 1 through 4 (of 4 total)

We have moved to a support ticketing system and our forums are now closed.

Open Support Ticket