Abland

@wongjn – thanks! Changing tru to true fixed the issue.

/wp-content/plugins/duplicate-post-page-menu-custom-post-type/duplicate-post-page-menu-cpt.php on line 144

• This reply was modified 2 months, 1 week ago by Abland.

Hi @hjogiupdraftplus

You are correct that the sites were copies of an original site on the same hosting. I won’t be doing any further investigation though as the site owners are switching a lot of things up, but thanks for your help nonetheless.

@hjogiupdraftplus

I tried commenting out that line but still received the same error. I cleared the server caches and tried again and got the same error again.

@wendool

Thanks for the feedback. I tried the same steps but no joy in my case. I also have other sites on the hosting that updated properly but two of them have run into this error.

@tonyzeoli @majick
Thank you. I just updated and all is working as it should.

@tonyzeoli, that link you posted goes 404.

• This reply was modified 3 years ago by Abland.

@sounds

Thank you for the follow up. I went to install the updated version manually but noticed the conflict errors no longer show. I was able to set the schedule correctly without issue.

Hi, @majick

I’m also experiencing this issue, and it only occurs on the current day. If a show starts at 12:00am on Thursday, it’s only on Thursday that it conflicts with a show ending at 12:00am Wednesday. Come Friday it no longer conflicts.
My initial assumption was the upcoming change to Daylight Savings here in Canada but now that it’s changed the issue still exists. The server time is set correctly.

Hi, Srinath @zmintegration

I have not heard anything further regarding this issue. On digging deeper I see that the ZeptoMail plugin does not recognize breaks in code generated email notices:

\r\n\\

Plugins that use those breaks get sent as all one continuous line rather than new sentences or paragraphs.

As far as the initial issue of html, I added the following to the theme’s functions.php which appears to work by making html the default mail setting for the sites:

/* DEFAULT MAIL AS HTML */
function wpcs_set_email_content_type() {
    return 'text/html';
}
add_filter( 'wp_mail_content_type', 'wpcs_set_email_content_type' );

Hi, Srinath @zmintegration

Thank you for following up. I have sent off an email to support.

Hi, @mainwp

Thank you for your follow up. I haven’t had time to pursue this further until today, and I have found what the issue was. I’ll post in case it helps anyone else.

My install of the MainWP Dashboard might be unusual. I have it installed on a multisite on three different subsites. It’s NOT network activated, just activated singularly on site 2, site 3, and site 4. Each of those three subsites are for individual client groups. Each group is a web development company with their own clients whom I white label development and maintenance for.

This latest update (4.1.7) only worked for subsite 4 while subsites 2 and 3 “lost” all sites. I tried uploading a csv backup to those sites and they failed, saying the sites already existed. So I checked the database and a couple different fields were missing on subsites 2 and 3, but both were missing sync_id as a Primary field. I added the fields manually and the dashboard updated without an issue. So all is good now.

I did check the error logs and apparently they reported database errors for unknown field health_value for subsite 3 since September 2020.

I’ll mark this resolved and thanks again.

@wpdogger

This might be the issue you’re experiencing:
https://www.ads-software.com/support/topic/server-500-on-godaddy-shared/

There’s a closing </IfModule> that wasn’t opened in the .htaccess. Resave the firewall rules in the plugin then edit the .htaccess as indicated by @mbrsolution

@mbrsolution

Thank you for the follow up. Oddly enough, on the GoDaddy sites the [USER AGENTS] rule was missing so there was no opening IfModule. I resaved the Firewall rules in your plugin which restored the [USER AGENTS] rule, then moved the closing IfModule as you indicated. All is working as normal.

Hi, @arabianmido

Thank you for your quick response. We’ve just updated the plugin this morning and all is working correctly.

@designful

A quick update: the issue was with the Alt Manager plugin. I rolled back the entire site in sandbox then updated each plugin until the issue happened. Your plugin is working fine at the latest version.

Thanks anyway. We rolled back the plugin from a backup and all is working. I suspect a conflict from another plugin but will need to sandbox and test.

Is it possible to send the link privately?