apcpub

I was trying to add a page ID under “Excluded Pages” in the settings. The results of that test in a nutshell were:

With dynamic sitemap generation checked:
Would not save new page ID (already some there from before upgrade)
https://example.com/sitemap.xml styled OK
https://example.com/sitemap.xml styled OK

With dynamic sitemap generation un-checked:
Saves new page ID OK
https://example.com/sitemap.xml blank page style missing
https://example.com/sitemap.xml styled OK

I was unaware of the checkbox feature to exclude on each page. So, I did some testing of that too because if that worked, and also didn’t ping search engines, that would be really cool. Unfortunately, that gave me problems too. Here are the results of that test:

As Administrator, with dynamic sitemap gen:
Checkbox saved OK
looked at https://example.com/sitemap.xml
styled OK
page excluded OK

As Administrator, with static sitemap gen:
Checkbox saved OK
looked at https://example.com/sitemap.xml
blank page NOT styled
page NOT excluded (looking at page source)
ls -la /public_html reveals sitemap.xml not regenerated

As Editor, with dynamic sitemap gen:
Checkbox NOT saved
looked at https://example.com/sitemap.xml
styled OK
page NOT excluded

As Editor, with static sitemap gen:
Checkbox NOT saved
looked at https://example.com/sitemap.xml
blank page NOT styled
page NOT excluded (looking at page source)
ls -la /public_html reveals sitemap.xml not regenerated

If you aren’t seeing this, I can try to look for conflicts. I don’t think its the caching because its configured to not cache the sitemap. I know its not the firewall because I have been watching the logs during my tests.

A couple more things I noticed. First, I tried using the latest version of IE in wp-admin. That did not help.

Second, when I add the exclude ID and turn off dynamic sitemap and click update that seems to work. (save for the stylesheet problem above)

However, as soon as I turn dynamic sitemap back on and click update sitemap, I tell it to delete the static .xml and .gz and reload the sitemap and notice that excluded page is back. If I navigate away and back to the xml sitemap settings again, I notice that the excluded ID is again missing from the excluded pages field. I hope that helps you, but I am going to stick with the unstyled static until webmaster tools says its a problem.

I looked into it further and even when disabling the plugin and submitting a blank comment form WordPress returns web server error 500.

Then I found some talk about it here:
https://www.ads-software.com/support/topic/wp-comments-postphp-500-internal-server-error-1
But, I will not hack the wordpress core to address this.

I will have to see if I can make a policy in OSSIM to filter out these particular 500 events or find another solution. I hope this helps someone else save time.

Thanks for the quick response I am marking this resolved.

OK, thanks.

One piece of information that may help ??

This error occurs right when trying to activate it. I had all my plugins deactivated for maintenance and this was the first plugin I tried to reactivate then saw the error.

I hope this helps.

I just updated the plugin to the latest version and I am having the same problem with WP v3.8.3. I upgraded to WP v3.9 and have the same problem.

I will look to see if there is a quick fix, but will probably just revert to the old version of the plugin until fixed.

BTW, GREAT PLUGIN!!! Will be looking for donation button and will gladly buy you lunch man!

I found a patch that works for me for now.

I replaced line 939 in aioseop_sitemap.php.

Was:
echo '<?xml-stylesheet type="text/xsl" href="' . $plugin_path . 'sitemap.xsl"?>' . "\r\n";

replaced with:
echo '<?xml-stylesheet type="text/xsl" href="' . str_replace("https","http",$plugin_path) . 'sitemap.xsl"?>' . "\r\n";

Seems like it could work as a permanent fix. In the case that someone is logged in via http it still works. And, I can’t see why someone would want to use an ssl link to their sitemap or the .xsl stylesheet in the sitemap anyway, though I guess there could be a special case.

This plugin is great. Just what web masters need!

YouTube recently started supporting an iframe embed code and I recently started using it so my videos are all compatible with iPhone / iPad and other HTML 5 video.

Despite <iframe> </iframe> tag having a YouTube link in it this plugin isn’t seeing them ??

Please update! Also, I second K4TAY in putting the file in the right place if your blog is hosted in a sub-folder (not root).

Thanks!

I don’t seem to be having the rebuild problem with wp 2.9.1 and v3.2.2 of the plugin.

I do have a problem with trying to exclude individual posts and pages that I don’t want to be indexed by the search engines.

Excluding entire categories does seem to work though.