RonBPalmer

So your solution to the problem you created is for me to add specialized programming. How about you have some basic respect and not cross certain boundaries. I have been forced to systematically remove jetpack functionality because it was causing issues elsewhere. Every feature I have to turn off lowers your value proposition and makes the arrogance of the advertising and the response more annoyance than the value you provide.

Also
Missing divi-style

The error messages for these two are incomplete so I don’t have any information to go on.

Resolved is not at all the correct term. Ignored is a better term.

You create broken links on my site and tell me to ignore them. That is NOT a satisfactory answer and I have already taken steps to resolve the issue through alternate means and I will be purchasing the pro version of that service.

The problem was caused by a content security policy on the Nginx server. The relevant error messages were found in the html page using Chrome Developer Tools.

This can easily be checked by simply turning off the CSP long enough to test the page. CSP also has a log only setting that allows you to test the configuration settings. It will log the errors but not reject the action. Once you have resolved all the errors you can then turn the csp on fully.

This page provides the best explanation I have found so far: https://scotthelme.co.uk/content-security-policy-an-introduction/

It also affects paypal exactly the same. I disabled that plugin to simplify the problem. So NO, the problem is yours.

https://github.com/RonBPalmer/woocommerce-issue/commit/d5ec6b59b32ffe5fba990c3ed8d756ab40cb015d

I have resolved the issue. There were a number of issues combined. Caching was part of it. The new wordpress default sitemap generator may have been a part of it. My lms plugin was creating sitemaps,

I disabled the wordpress default sitemap.
I turned off the aioseo sitemap.
I removed every sitemap file from my website root.
I cleared my cache.
Then I restarted the aioseo sitemap and it worked.

If sitemaps are going to be dynamic they really need to post a generated date on the display page. Requiring us to look at the source code is just asking for seo problems. I would like to see a visible log of sitemap generation in the aioseo panel as a reassurance that it is working as intended. Automation is wonderful until it turns an occasional problem into 10,000 problems per day. Sitemaps are critically important and mine has been broken for an unknown but substantial period of time even though by all appearances it was performing perfectly. The financial loss to me is impossible to measure but undoubtedly substantial.

Ideally, I would prefer static maps of my pages and my products and a dynamic map of my posts. After this experience, I will be looking into how that might be possible and will find a solution even if I have to code it myself.

and when google and bing see them as 404 errors and lower my rankings? They actually appear in the pages my site serves so, yes, they are a problem. If they don’t resolve then they can serve no valid purpose.

If these cannot be fixed, the solution is to remove the plugin that creates them. I would rather not but, broken links in today’s seo world simply aren’t tolerable.

except that the links are invalid and cause 404 errors that i cannot ignore

Andrew Nevins, I have 25 years of IT engineering, management, and consulting experience. CIOs read my books. I can fix the freaking technical problems as obviously any teenager who hasn’t figured out how to speak to other humans can if they spend enough time doing the research. I spent the last 18 years trying to teach technical people how to communicate to other human beings and I am just frustrated at the colossal waste of my time trying to accomplish the impossible. I did NOT ask you to fix my problem for me and your deep technical expertise on a single narrow technology does NOT entitle you to arrogance in your responses.

I worked Premier Support for Microsoft and my point is that this is the typical BS Microsoft answer, reboot. That answer earned Microsoft a reputation, one would think that others would not want to emulate. Every fool knows to reboot and every fool who has ever worked with wordpress knows the standard BS answer to wordpress problems.

Andrew Nevins, if you are unable to engage in basic human conversation, I suggest you buy a computer that can do a better job.

With the amazing success of wordpress, surely you realize that we are running revenue generating production websites on wordpress. Your first and default solution is to shut off our revenue generator and piss off our paying customers!

• This reply was modified 6 years, 10 months ago by RonBPalmer.