Support » Plugin: XML Sitemap & Google News » Error 500 site not working

  • Resolved euklidis

    (@euklidis)


    Parse error: syntax error, unexpected ‘&&’ (T_BOOLEAN_AND), expecting ‘)’ in

    This killed my website. I had to delete the plugin via FTP. Please fix

Viewing 15 replies - 1 through 15 (of 16 total)
  • The plugin author should remove 5.0 from the repository.

    Use version 4.9.4 if you want, since other things are wrong too in 5.0. Your error is probably this one:

    xml-sitemap-feed/xml-sitemap.php Line 238
    if ( is_array($value) && empty( $value['active'] && isset( $new[$key] ) ) ) {
    should be
    if ( is_array($value) && empty( $value['active'] ) && isset( $new[$key] ) ) {

    A good option to delete when going between versions in this SNAFU situation is
    ‘xmlsf_version’ in wp_options if you have access to PHPMyAdmin. Otherwise, you can temporarily put delete_option( 'xmlsf_version' ) in your theme’s functions.php file.

    Plugin Author RavanH

    (@ravanh)

    Hi, sorry to hear you are having trouble. Seems you are not the only one. I’m working on find out where this comes from.

    @kitchin, good spot thanks! It may well be the cause so this fix is going in right now. You have spotted more? Deleting the xmlsf_version from the DB will cause the upgrade routine to kick in again. Are you saying that solved the issue for you?

    I was just guessing what would make 4.9.4 work after 5.0 had done its upgrade stuff. I guessed rerunning the the version check would make 4.9.4 happy.

    Thanks for working on this so quickly.

    Hey @ravanh this is the same error I’m getting. I’d reply in my other thread, but seeing as it’s here, I thought I’d just point you here instead.

    Plugin Author RavanH

    (@ravanh)

    Hi @n3rdabl3 it should be fixed in version 5.0.1… Are you still getting the error? If so, can you tell me exactly when/where it occurs?

    Hey @ravanh, updated to 5.0.1 still getting white screen of death. I’m on mobile so I couldn’t check for errors.

    Plugin Author RavanH

    (@ravanh)

    OK, thanks for letting me know. Does this happens immediately after the upgrade or when visiting a certain page or sitemap?

    I too now have a site that’s crashed after updating this plugin:

    HTTP ERROR 500

    I can’t get to the admin side of the site at all. Since I’m a very basic WP user, not a programmer, can someone please point me to the steps to either roll this back to the previous version or uninstall it so I can get the site to load?

    Thanks

    Plugin Author RavanH

    (@ravanh)

    Hi @gnemes, sorry this happens to some people after the update. I can’t figure out why because I’ve not been able to reproduce this… To get back into your admin, you need to use an FTP program like FileZilla to connect to your host and then delete the folder /xml-sitemap-feed/ that you can find inside /wp-content/plugins/. Once deleted, the plugin will not be running anymore and you have access to the admin like before.

    Is there any way for you to check the host error log? If so, can you find a message about the crash?

    Hello,

    i have the same problem. I can´t save any articles since the update.

    I changed to the earlier version and there is no problem.

    Plugin Author RavanH

    (@ravanh)

    @n3rdabl3 and @gnemes can you tell me which PHP version is running on your web server?

    Hey @ravanh, we’re currently running 5.4.45 (old, I know, we’re working on updating).

    Plugin Author RavanH

    (@ravanh)

    Hmmm, that’s a problem… I’ll try to get an old 5.4 installed for testing.

    @ravanh yeah, a few plugins have caused us problems due to incompatibilities with 5.4.

    If you have any suggestions on where I can look for errors or other info, I’m happy to help out as much as I can.

    Plugin Author RavanH

    (@ravanh)

    If you can find any related and meaningful messages from when this occurred in the apache/nginx/php error log files, it’d be very helpful 🙂 do you know where to find them?

Viewing 15 replies - 1 through 15 (of 16 total)
  • The topic ‘Error 500 site not working’ is closed to new replies.