Google sitemap issues after moving blog to root

  • yumadoug

    (@yumadoug)


    17 years, 1 month ago

    Help! I moved my blog from a subdirectory to the root and now my Google Sitemap Generator plugin has problems.

    I followed the WordPress move doc (including the doc to update the addresses in my database) and everything else works great, including all plugins, all images appear, all posts, etc. However, when I click on the admin page link to activate the sitemaps plugin, I get these errors:

    Warning: Invalid argument supplied for foreach() in /home/content/y/u/m/myid/html/wp-content/plugins/sitemap/sitemap.php on line 347

    Warning: Cannot modify header information – headers already sent by (output started at /home/content/y/u/m/myid/html/wp-content/plugins/sitemap/sitemap.php:347) in /home/content/y/u/m/yumadoug/html/wp-includes/pluggable-functions.php on line 270

    I downloaded a new copy of the plugin and saved new, blank sitemap.xml and sitemap.xml.gz files with 777 permissions to the root directory, but still get the same errors.

    I emailed the plug-in provider but he won’t respond. Even offered to pay for support. ;-p

    Any ideas?

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter yumadoug

    (@yumadoug)

    17 years, 1 month ago

    Arne Brachhold got back to me on this issue, with:

    “…try if the latest beta version solves your problem? There have been many improvements since the stable release.”

    Not sure which change would help in this situation (moving the blog to the root), but he was right. The latest beta version works just fine. I created the sitemap files in advance, which may or may not have been needed, and then uploaded and activated the latest beta. No more errors upon activation, and the xml files are correct.

    vkaryl

    (@vkaryl)

    17 years, 1 month ago

    So how about marking BOTH of your posts about this as resolved?

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Google sitemap issues after moving blog to root’ is closed to new replies.