xmlsitemapgenerator

possibly. can you share more details about your website/sitemap so I can take a look?

if you prefer you can email me. support at xmlsitemapgenerator dot org.

Hello. This is not a feature at present, but I can add it as a feature request.

If you have the skills you could hack the plugin to make it work. This isn’t something I support directly, but if you have the knowledge / skills it would not be hard to work out and test.

As a pointer in the right direction, you would need to edit the Term Provider : TermsProvider.php and change the INNER JOINS to the correct outer join. I think it would be LEFT, but check this. You would need to do this for the count and get page functions.

Note that any changes would be overwritten if you updated to a new version.

Sorry for the delay.

It would be unusual for your sitemap alone to cause a significant drop for a temporary problem.

You can include/exclude individual tags / categories when you add / edit them. There will be sitemap options on each individual category.

I wonder if the error you showed me is from an older version. are you now on 2.0.7 and is the error still there?

I should forewarn you WordPress has been going after plugins. It will likely become a commercial marketplace. This was never the intent for my plugin.

If it disappears from here, I will make sure it is available on my website.

support at xmlsitemapgenerator.org

Hello. I’m not able to delete your post (or if you can), but you can edit it.

Instead of selecting view source, you select developer tools, then on the console it will usually display errors.

If you could create a test category that would help eliminate it being a more general problem.

If it would be easier, drop me an email via the support form on the website and I can respond to you that way. xmlsitemapgenerator.org/contact.aspx

Okay thanks, so the problem is likely with saving settings.

Do you have any tags / categories you could try editing the sitemap values for, then recheck the table to see if there are entries? That way I can determine if it is a post specific issue or more general.

Also, in your browser, are you able to open developer tools and see if you can spot anything in there, perhaps a javascript error.

It’s possibly a bug in the plugin or perhaps something went wrong during setup.
Are you using a single site install or a Network/multi-site install?

Are you able to access your wordpress database?

If so, can you see if you have a table “xsg_sitemap_meta” (it will have your standard wordpress table prefix).

If you do are there any records in it?

Did you press the update button on the page? They do not autosave.

great. glad you could get it sorted.
I need to do a bit more testing and will issue an update later today to ensure everyone gets the hot fixes.

2.0.5 was still using the old date format which was working.
can you share your sitemap?

I think a number of things might be being mixed up here …..

Firstly I think when you refer to “advanced settings” you might be referring to one of my other solutions that is not wordpress.

For wordpress settings in our plugin all the setting are in the main settings page, or you can edit them per tag, category, page or post.

Go to the wordpress admin area. Select settings > XML Sitemap. That is our settings page. You can also click the settings link on the plugins list.

Next, I think there is a conflict between another plugin. Ours should install , uninstall, reinstall without any issues. It’s pretty basic.

I think the problem is that you have another plugin interfering with ours coming from the fact they are sharing a filename “xmlsitemap.xml”.

If you go to the settings for our plugin and change the sitemap file name to something else e.g. “xmlsitemap2.xml” , then see if it works.

I think I found the issue. It seems PHP ISO format isn’t the same as google requires. Google is rejecting the timezone.

I just pushed an update to 2.0.7.

Could you try and reinstall 2.0.7 and see if this fixes it?

Can you send me a link to your sitemap or a screenshot of the modified dates please?

We changed to use the default PHP DateTime::ISO8601 date format, but this should be compatible.

I added a change to add the blog timezone.
I believe this is now working.

duplicate post.