balex66

Following as I’m seeing this same issue on a new client’s CPanel

Here is the full code in the channel section at the top of the feed the frequency looks to be set hourly but the build date doesn’t seem to refresh:

<channel> <title>Schwartzreport</title> <atom:link  rel="self" type="application/rss+xml" /> <link>https://www.schwartzreport.net/</link> <description>Trends That Will Affect Your Future</description> <lastBuildDate>Fri, 29 Sep 2023 05:23:14 +0000</lastBuildDate> <language>en-US</language> <sy:updatePeriod> hourly </sy:updatePeriod> <sy:updateFrequency> 1 </sy:updateFrequency>

Scratch that part about MailerLite. It was showing the published date of the items in preview as 2023-09-28, but when I sent out a test email the date was correct. So I still can’t figure out why MailChimp is a day behind when it looks at the feed. Even when I create a whole new campaign.

Here is a screen recording of the issue.

What is stranger still is sometimes we can’t even go back to a revision to get the field data restored, it’s like it was never entered even though multiple saves are being done while editing.

I have found a way to replicate the issue. I’ve only been able to trigger it by editing a scheduled post, then click the preview button at the top of the editor window, click preview in new tab none of the custom fields will show but any changes to the main content area will show in the preview. If a user then goes out of that window to posting a new post or back to the “All Posts” page in the dashboard, all of the ACF field data will be lost.

However, if edits are made to a schduled post and then the blue “Schedule” button is clicked to save the edits and the “View Post” link that appears briefly at the bottom of the window is clicked all the content and changes are visible. If the changes are saved and then you go back out to All posts without previewing first, and then click “preview” under the scheduled post all the ACF fields and changes are saved.

I’ve also verified that I have at least two sites so far where I can replicate this behavior. Both sites have custom field groups created with ACF Pro attached to the post type “Posts”

• This reply was modified 1 year, 2 months ago by balex66.

I’m wondering if I should try disabling wp-cron in wp-config and run a cron job from my Bluehost Control Panel instead.

• This reply was modified 1 year, 2 months ago by balex66.

I don’t see an available update. Do we need to uninstall and reinstall to get the new version? Our site shows:

However, when I click view details in the dashboard it shows Post Grid Combo:

• Version: 2.2.54
• Author: PickPlugins
• Last Updated: 3 days ago
• Requires WordPress Version: 5.0.0 or higher
• Compatible up to: 6.3.1

We use a site builder does the new version still support shortcodes?

It get’s weirder. I was also seeing the same error on the root domain. I restored the wordfence-waf.php file from a backup and now the site is back up. Is there anything we should do for the addon domain. Currently wordfence is not installed on the domain but clearly it is affected by the WF install on the root level domain.

• This reply was modified 1 year, 3 months ago by balex66.

I put Wordfence in learning mode on the main domain and was then able to whitelist the action it flagged and blocked on the subdomain. I will install it on the subdomain next and reach out to their support if further issues arise. Thank you for helping me narrow down what was causing the problem.

That’s helpful. It’s coming from Wordfence, which is installed on the main hosting domain, and is not installed on this addon domain.

I disabled the only two plugins installed: Akismet and Limit Login Attempts Reloaded. I also tried switching to different themes: Twenty Twenty-Three and Twenty Twenty-Two. The behavior persists.

I can change a post from draft to published and back again from the post editor but not from the “All Posts” > Quick edit function. I tried reinstalling WordPress. This is a new bare bones install.

Same error filling up my error log after the latest update. Caching is currently disable on the site.

PHP Warning: Cannot modify header information – headers already sent in /home2/stephaz0/public_html/schwartzreport/wp-content/plugins/wpdiscuz/utils/class.WpdiscuzHelper.php on line 162

I’ve seen this on 3 sites this morning after updating to 7.5.2.

Example 1: [09-Jul-2019 15:03:36 UTC] PHP Fatal error: Class ‘Jetpack_Sync_Sender’ not found in /public_html/wp-content/plugins/jetpack/sync/class.jetpack-sync-actions.php on line 323

Example 2: [09-Jul-2019 15:03:33 UTC] PHP Fatal error: Class ‘Jetpack_Sync_Sender’ not found in /public_html/<domain redacted>/wp-content/plugins/jetpack/sync/class.jetpack-sync-actions.php on line 323

• This reply was modified 5 years, 4 months ago by balex66.

That worked. Thanks!