@jbx – could you try installing the development version from http://wordpress.org/plugins/xml-sitemap-feed/developers/ (under Other Versions) and let me know if you still get the error?
@vann – it looks like the sitemap generation process is running out of memory. Please try setting the “Split by” option under the specific post type sitemap settings to “Year” or even “Month” if needed.
@ravanh – that seems to work for right now.
is the sitemap supposed to redirect to the homepage when you click on the post links???
is the sitemap supposed to redirect to the homepage when you click on the post links???
No, clicking the links in the sitemap index, you should land on the individual sitemap. Clicking on a link in a sitemap, you should land on the actual post… Can it be that your site has NO posts? WordPress is known to behave funny (in respect to feeds) when there are no posts at all. IF so, try to publish at least one post.
You also might try to resave your permalink structure, just to make sure.
@ravanh i got 6486 (including the 1s on the homepage) posts published.
so what that mean???
URL: http://www.vanndigital.com/
@vann – those are items of type Porfolio, not the normal Post. Your main blog feed http://www.vanndigital.com/feed/ returns a 404 status. Publish at least one normal post. You do not even need to include it in a sitemap…
Thread Starter
jbx
(@jbx)
In my case I also don’t have any posts. I have 6 pages (its a new site).
But I installed another plugin “Google XML Sitemaps” and it works fine.
I will try to install the dev version on my local installation this evening and see if it works.
@ravanh thats because we dont use that feed.
this the feed we use…
http://www.vanndigital.com/portfolio_category/channels/feed
but we went back to using WordPress SEO sitemap yesterday & we’re now using your plugin for Google News sitemap
Hi jbx, did you get around to testing the dev version? If so, and if still getting this warning then please tell me if the custom post type you are using has the has_archive parameter set to false by any chance.
Apparently WordPress can return a null on get_query_var('post_type') in some cases which would explain the illegal offset type warning…
