Version 5.0 Error

  • Good morning. Updating to 5.0, unfortunately, kills our website with a 500 error. We’ve rolled-back to the previous version until new version becomes available.

Viewing 9 replies - 1 through 9 (of 9 total)

  • The plugin author should remove 5.0 from the repository.

    I looked at the upgrade code and the main thing 5.0 did there was delete the ‘gn-genre’ taxonomy terms and replace it with a new taxonomy ‘xmlsf_taxonomies’.

    Probably 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.

    Also, flush rewrite rules by visiting Dashboard / Settings / Permalinks. Just visiting that admin page flushes the rules.

    • This reply was modified 6 years, 2 months ago by kitchin.

    Hi, there was a weird situation during the push to SVN where some files where rejected (seems XML source was perceived by a commit hook as PHP and thus caused a parse error) so I fear some people have received in incomplete upgrade package.

    Is there a more specific error in your server log files that could tell what has gone wrong?

    What I see for xml-sitemap-feed/languages/ now is:

    Version 4.9.4: 19 files
    Version 5.0: 19 files
    Version 5.0.1: folder missing

    Yes, translations are now on https://translate.www.ads-software.com/projects/wp-plugins/xml-sitemap-feed

    Hi?Aaron, please let me know if you find anything in the error log file. I really cannot seem to figure this remaining issue with PHP 5.4 out…

    UPDATE: Think I found them all. 5.0.2 should be PHP 5.4 compatible. If you find any more issues, please let me know ??

    I still can’t see the category options either in composition or quick edit.

    Thread Starter Aaron Richardson

    (@n3rdabl3)

    @ravanh sorry for the late reply. I couldn’t find anything in our error logs, however updating to 5.0.2 I can confirm that you have fixed it!

    One thing I did notice however is that the plugin flagged our static robots.txt for deletion, not sure if that’s a bug or intentional, just thought I’d give you a heads up.

    Looking forward to exploring the new features/settings area.

    Thanks for the feedback ??

    The static robots.txt warning can be ignored if you wish to keep your static robots.txt file. But you may also decide to delete the file and let WordPress generate a dynamic robots.txt for you. In that case, you can add your custom robots rules in the field “Additional robots.txt rules” on Settings > Reading.

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘Version 5.0 Error’ is closed to new replies.