David LeBlanc

Hello, I had this same problem. I fixed it by going to Settings > Page Builder > and selected the content tab.

Unclick Copy Content if the box has a check mark in it. Copy Content should not be enabled.

This fixed the issue for me.

Amboutwe

Thank you for the reply. The meta box was there prior to the latest release, wasn’t it?

I went to bed using it, updated come the morning and it was no longer there. Just for my own sanity, mind you.

It was convenient for tweaking the url, if needed.

@gemmaevans,
Hello. Posted to GitHub. Hope that helps solve the issue.

Md Mazedul Islam Khan

Sorry for the late reply. Thanks for the suggestion.

I should also note that the site’s favicon shows up again in a Chrome tab if WP Super Cache is deactivated.

Mazedul
Thanks for the reply. Good news and bad news.

Bad News. I entered the string just as described in the article and that did not fix the problem. The parsing error was still there.

Good News. I then disabled WP SuperCache and that is the problem. With WP Super Cache disabled, the XML site map shows up just as it should. And forget about me disabling all of the plugins. I guess I missed the one that counted.

Just for the record, the string I entered is
sitemap(_index)?\.xml(\.gz)?
([a-z0-9_\-]+)?sitemap\.xsl
[a-z0-9_\-]+-sitemap([0-9]+)?\.xml(\.gz)?

Is that correct? I did keep in the default entries:
wp-.*\.php
index\.php

Thanks for you help. A bit closer to resolving the problem.

mbrsolution,

How is Mike doing on the updated version? Happy to make a donation if that is what is needed.

Hello again Benjamin,

I found the problem and it is a conflict with SiteOrgin Page Builder.

Thanks for your help.

Benjamin

Okay, that turned out to be easier than I thought, sadly.

I deactivated all of the plugins and still got the problem. Switched theme to 2016 and still got the problem with plugins still deactiveted and still got the problem.

So, whatever the problem, it’s probably somewhere with the calendar plugin.

Benjamin,
Thanks for the reply. I will do this.

One question. Assuming this is the problem, if I disable all of the plugins, do i have to create an event for each plugin deactivated and then reactivated until the culprit is found?

Thanks again for any help you can offer.

Yes, here it is. https://ism.theafabgroup.com/events/.

The site is still in development, a work in progress and no matter how I fiddle with it, I get the home page in the description.

Thanks for looking at it, appreciate the help.

Dave LeBlanc

Never mind, found it. It’s all good.

Riann, thanks for the reply.

Yes, I cleared the cache. That is the first thing I thought of and did and problem remained.

I did not deactivate the plugin, if that helps.

I did notice that both the PHP version and MySQL version GoDaddy uses are below the minimums recommended. From past experience, out of date PHP can cause an issue with WooCommerce. It is possible that one or both those things is the cause of the problem.

Sadly, GoDaddy does not offer more current versions and seems to have no plans to do so.

• This reply was modified 7 years, 11 months ago by David LeBlanc.

Thanks, Ahmed, for the reply.

Got it. Thanks.