barbccfl

I sent some screen shots to your support email. In the meantime, I discovered the sitemap for the CT exists, https://barblafara.com/surname-sitemap.xml But, it is not included on the primary sitemap page, https://barblafara.com/sitemap.xml

Yes, I’d like to find a resolution, What is your support email so that I can send the screen shots? I am using 4.1.20 and still not getting a sitemap for my CT despite the fact it is listed on the settings page. BTW, the debug log is VERY large, is there a specific section you want to see?

• This reply was modified 6 months, 2 weeks ago by barbccfl. Reason: add more info

Since I did not get a reply, I disabled the Yoast sitemap and am now using a dedicated plugin for my sitemap.

I spoke to soon… version 4.1.20 did not change the result. Still no custom taxonomy list.

Thank you for the speedy reply! I’ll head over to GitHub and see if that release solves my problem. I’ll mark this resolved.

Further troubleshooting, I installed a different plug-in that makes XML sitemaps called ‘XML Sitemap Generator for Google 4.1.19’. It successfully made a post list, https://barblafara.com/post-sitemap.xml So, why isn’t Yoast able to make one?

BTW, I have other WP sites on this hosted server and they also use Yoast and all of their post XML pages are working. None have exactly the same plug-ins installed, so it could be some sort of conflict, but I disabled all the plug-ins yesterday, including Wordfence, and still had the issue. AND, if it is a conflict, wouldn’t the other XML sitemap pages fail?

I sorted through the log file and pulled some representative lines that show both myself and others trying to load the post-sitemap page. I am 71.1.237.0, you can see I accessed the sitemap index in the morning and just the posts page failed. I have not included the many times throughout the day where I was testing the post-sitemap, but I did include below where I tried loading the .xsl version. The other examples look to be bots and the validators that were visiting the page.

71.1.237.0 – – [05/May/2024:09:47:57 -0400] “GET /post-sitemap.xml HTTP/1.1” 500 2609 barblafara.com “https://barblafara.com/sitemap_index.xml” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36” “-“
71.1.237.0 – – [05/May/2024:09:48:02 -0400] “GET /post-sitemap.xml HTTP/1.1” 500 2609 barblafara.com “https://barblafara.com/sitemap_index.xml” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36” “-“
71.1.237.0 – – [05/May/2024:09:48:05 -0400] “GET /page-sitemap.xml HTTP/1.1” 200 1802 barblafara.com “https://barblafara.com/sitemap_index.xml” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36” “-“
71.1.237.0 – – [05/May/2024:09:48:33 -0400] “GET /category-sitemap.xml HTTP/1.1” 200 5695 barblafara.com “https://barblafara.com/sitemap_index.xml” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36” “-“

5.255.231.0 – – [05/May/2024:11:36:53 -0400] “GET /robots.txt HTTP/1.1” 200 262 barblafara.com “-” “Mozilla/5.0 (compatible; YandexBot/3.0; +https://yandex.com/bots)” “-“
5.255.231.0 – – [05/May/2024:11:36:55 -0400] “GET /post-sitemap.xml HTTP/1.1” 500 2609 barblafara.com “-” “Mozilla/5.0 (compatible; YandexBot/3.0; +https://yandex.com/bots)” “-“

52.167.144.0 – – [05/May/2024:11:37:39 -0400] “GET /post-sitemap.xml HTTP/1.1” 500 2609 barblafara.com “-” “Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; bingbot/2.0; +https://www.bing.com/bingbot.htm) Chrome/116.0.1938.76 Safari/537.36” “-“
52.167.144.0 – – [05/May/2024:11:37:59 -0400] “GET /post-sitemap.xml HTTP/1.1” 500 2609 barblafara.com “-” “Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; bingbot/2.0; +https://www.bing.com/bingbot.htm) Chrome/116.0.1938.76 Safari/537.36” “-“

2600:1f18:7d00:: – – [05/May/2024:13:58:03 -0400] “GET /post-sitemap.xml HTTP/1.1” 500 2609 barblafara.com “-” “W3C_Validator/1.3 libwww-perl/6.68” “-“

85.92.66.0 – – [05/May/2024:13:59:26 -0400] “GET /post-sitemap.xml HTTP/1.1” 500 2609 barblafara.com “-” “Mozilla/5.0 (compatible; XML Sitemaps Generator; https://www.xml-sitemaps.com) Gecko XML-Sitemaps/1.0” “-“

71.1.237.0 – – [05/May/2024:14:55:49 -0400] “GET /post-sitemap.xsl HTTP/1.1” 200 – barblafara.com “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36” “-“
71.1.237.0 – – [05/May/2024:14:55:50 -0400] “GET /favicon.ico HTTP/1.1” 302 – barblafara.com “https://barblafara.com/post-sitemap.xsl” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36” “-“

85.208.98.0 – – [05/May/2024:16:03:51 -0400] “GET /post-sitemap.xml HTTP/1.1” 500 169 barblafara.com “-” “Mozilla/5.0 (iPhone; CPU iPhone OS 6_0 like Mac OS X) AppleWebKit/536.26 (KHTML, like Gecko) Version/6.0 Mobile/10A5376e Safari/8536.25 (compatible; SiteAuditBot/0.97; +https://www.semrush.com/bot.html)” “-“

I have the log file, how do I attach it here or send it to you? It is .gz compressed file. I could place in Dropbox…

No, they did not… Ultimately I uninstalled your plug-in and am just using the built-in captcha feature supplied with the Divi theme.

Good suggestions, thanks! I will turn off my firewall and try again. I had thought about deleting and re-install, but was being lazy… But, based on your experience I will go ahead and do it. Thanks again.

Thank you for confirming the solution. I made the changes earlier today and have had no more login lockout alerts.

I’m having this same issue. Cannot use the editor inside the Media Library without getting the error. “Could not load the preview image. Please reload the page and try again.” If I deactivate All in One plug in the editor works, reactivate and re-install to my htaccess file and media editing returns the error when trying to make any type of edit. I’ve read it may be an issue with a closed .php file ‘?>’ or a php open with a ‘space’… I looked at a few of the .php files for the plug in but did not quickly notice any issue as described. Anyway, is there a solution? Thanks!

Many thanks for the replies… We use a child to the Divi-theme and have no plug-ins for this particular page, other than the Divi-builder. If this problem occurs on one of our other sites (once we get up the courage to update to 4.7…), we will definitely try one of the thumbnail re-generators. This has been a good reminder of regularly backing up, certainly before doing any updates.