EntBuddha
Forum Replies Created
-
Since day one after signing up with SG. Like I said the full delete and reinstall seems to have corrected the response time issues. Thank you.
The delete and re-install seems to have worked, may want to let other users know that they have to fully delete it for the patch to come in unless your pumping down 5.0.9.
I can only report what I experienced. With the plugin activated at 5.0.8, the site would respond much slower than usual and had the notice error which it didn’t before. With the plugin deactivated, the site speed returned to normal. The site was fine at 5.0.7. I know not all sites are the same, but I can tell you in my case, the site functions better with it disabled at 5.0.8. It’s a night and day experience with it enabled and disabled at this version, so that is why I think there may be deeper issues than the notice. Just my opinion.
I’m just waiting for the inevitable 5.0.9 update at this point. This plugin, while awesome, has been revised many times over since the 5.0 update, these incremental changes are becoming untrustworthy.
Hello,
I don’t see an update to 5.0.9, so upon reactivation the plugin exhibits the same issues as stated in this thread.
Forum: Plugins
In reply to: [PowerPress Podcasting plugin by Blubrry] New Setup not saving Feed changesDid some more testing, I think this simply may be a browser cache issue, but if anyone can confirm that’d be great.
Alright, so after resubmitting after dropping the URL count to 250 per index, here are the new errors with as much detail as Search Console offers. Please note, error lines will probably change a bit since the site posts new posts daily:
1. http://www.entertainmentbuddha.com/sitemap_post_10.xml sitemap will open, but has the This tag was not recognized. Please fix it and resubmit.
Parent tag: caption
Tag: aError is on line 2. Unfortunately, when I view the source code, the entire XML is coded on line 2, so somewhere in there this invalid tag issue is happening.
2. http://www.entertainmentbuddha.com/sitemap_post_15.xml this one will open eventually in browser, but it has the Parsing issue error – We were unable to read your Sitemap. It may contain an entry we are unable to recognize. Please validate your Sitemap before resubmitting. The error is on line 2284.
3. http://www.entertainmentbuddha.com/sitemap_post_19.xml this will open eventually in a browser, but has the same issue as above, but the error is on line 7161.
4. http://www.entertainmentbuddha.com/sitemap_post_2.xml this will open eventually in a browser, but has the same issue as above, but the error is on line 2.
5. http://www.entertainmentbuddha.com/sitemap_post_20.xml this will open eventually in a browser, but has the This tag was not recognized. Please fix it and resubmit.
Parent tag: caption
Tag: aError is on line 2. Unfortunately, when I view the source code, the entire XML is coded on line 2, so somewhere in there this invalid tag issue is happening.
6. http://www.entertainmentbuddha.com/sitemap_post_27.xml this will open eventually in a browser, but has the parsing error issue like others above, it’s on line 12090.
7. http://www.entertainmentbuddha.com/sitemap_post_28.xml this will open eventually in a browser, but has the parsing error issue like others above, it’s on line 1013.
8. http://www.entertainmentbuddha.com/sitemap_post_3.xml no reported errors, just bombs out on load. Not sure how many others are like this, not going to test all.
9. http://www.entertainmentbuddha.com/sitemap_post_29.xml this one bombs out in a browser like above, but also has the parsing error issue like others above, it’s on line 4688.
10. http://www.entertainmentbuddha.com/sitemap_post_36.xml this will open eventually in a browser, but has the parsing error issue like others above, it’s on line 3877.
11. http://www.entertainmentbuddha.com/sitemap_post_55.xml this one bombs out in a browser like above, but also has the parsing error issue like others above, it’s on line 2.
12. http://www.entertainmentbuddha.com/sitemap_post_58.xml this one bombs out in a browser like above, but also has the parsing error issue like others above, it’s on line 2.
13. http://www.entertainmentbuddha.com/sitemap_post_72.xml this one bombs out in a browser like above, but also has the parsing error issue like others above, it’s on line 2.
There definitely appears to be a pattern with the bomb outs and errors on line 2, so hopefully you all can find the bug.
If it won’t affect duplicate content or anything like that then I don’t have an issue with it. I’ll be on the lookout for any parsing issue fixes. Thanks again for diving in.
This is somewhat unrelated, but why does the sitemap have the addl entry with just the homepage and blog page, but then again those are listed under the page sitemap entry in the sitemap index?
Michael,
I’ve replied to the contact form, but my issue is like Bobsled’s now. The sitemap will render with the indexing option toggled and 5000 per index, but google has parsing issues with it. Based on the other support requests coming in it appears that this is a glitch after all. I’ve updated my original thread, but I’m getting posts from others with the same issue, so that’s why I’m replying here. My post https://ww.wp.xz.cn/support/topic/version-2-4-broke-sitemap/
Alright it’s back on. The site is in the midst of a massive traffic decline anyway, so doesn’t matter I guess if this is broken now or not. I haven’t resubmitted to Search Console yet.
Just as an FYI I’ve disabled the sitemap feature again for the time being until the above issue can be looked at. I will be using the Google XML Sitemap Generator plugin for the time being. Thanks for taking the time to dive into this.
That worked, but now Search Console reports most of the sitemaps as having parsing errors. Upon looking at the line of code that was flagged, it appears Google doesn’t like reading in images from an amazon ad. Validation error
That’s just one, there are many others that don’t parse.
Yeah it’s your plugin, so rather than break my site to verify it for you I’ll just disable the sitemap feature and use another plugin. It clearly broke on the update, so I’m not going to spend the few hours needed to break down my site by toggling off plugins, themes, cache, etc to prove it to you, so don’t worry about it.