Daniel J. Lewis

I run into this, too. It’s 100% repeatable when I duplicate an item that already has a split-test on it.

I’d forgotten that this was still an issue and I had re-enabled the plugin on my site just recently. Then, with Health Check’s help, I found it was Publish To Apple News again.

Here’s the error text it gives me when I visit a post editor (page editor is fine) and click “Copy error”:

Invariant Violation: Minified React error #31; visit https://reactjs.org/docs/error-decoder.html?invariant=31&args%5B%5D=object%20with%20keys%20%7Btype%2C%20key%2C%20ref%2C%20_owner%2C%20_context%2C%20props%7D&args%5B%5D= for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
at pb (https://MY-DOMAIN-HERE/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.8.4:12:454)
at n (https://MY-DOMAIN-HERE/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.8.4:13:221)
at Ac (https://MY-DOMAIN-HERE/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.8.4:70:369)
at Ff (https://MY-DOMAIN-HERE/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.8.4:74:34)
at u (https://MY-DOMAIN-HERE/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.8.4:76:145)
at https://MY-DOMAIN-HERE/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.8.4:80:149
at N (https://MY-DOMAIN-HERE/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.8.4:90:3)
at ce (https://MY-DOMAIN-HERE/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.8.4:98:226)
at qg (https://MY-DOMAIN-HERE/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.8.4:97:440)
at hi (https://MY-DOMAIN-HERE/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.8.4:104:285)

My site is running on Liquid Web’s managed WordPress hosting.

Well, I was stupid.

It turns out the passwords I was importing were not the passwords I thought they were.

However, it does seem that the email notifications still contain the wrong password, but that’s not necessary for my needs.

How about this? https://gist.github.com/theDanielJLewis/149ce2363d0c37cf39983b79038297a4

The URL where it was happening was https://theaudacitytopodcast.com/pm19, but I’ve since switched to a different email-address-encoding plugin.

At this time, I can’t. But there were no console errors.

I tried other email-address-encryption plugins and saw even worse problems, sometimes without Social Warfare.

I also tried different settings through all of CryptX and couldn’t make it stop breaking the page, except for that “Content” setting which, of course, means it’s not processing any of the content.

Oops, I spoke too soon. This is _still_ broken. I even tried in an incognito window to ensure it wasn’t a caching issue.

I had mistakenly been editing a page and thus thought things were working. But when I went to edit a post, it was still broken. I’ll have to downgrade back to 2.0.1 or deactivate for now.

I can also confirm 2.0.3 resolved the problem.

Thank you!

I answered my own question. Yes, it works, but it declares class ActiveCampaign, which conflicts with other plugins. That class should be a unique name.

I also had the same problem and going to Settings ? Permalinks and resaving the permalinks fixed the problem.

Would it be possible for you to build the permalink-cache-flush into the plugin activation?

What’s the update on this? And what was the bug you figured out, @storyman?

It does seem post types still update, despite the message.

Downgrading to 1.3 worked for me: https://downloads.www.ads-software.com/plugin/publish-to-apple-news.1.3.0.zip

I, too, get this message updating I think any kind of post type on my site (pages, posts, products, etc.). It started with 1.4.0.

I tried this on both PHP 7.2 and PHP 5.6 and get the same results.

It even happens if I disable all</em other plugins. It’s 100% reproducible.

Please try again.
`

• This reply was modified 6 years, 5 months ago by Daniel J. Lewis.

Nuts. This means we can’t combine this plugin with any easy-to-use, efficient, whole-page caching plugins like WP Rocket or WP Super Cache.

Then I think that should be communicated more, because many people would call those automatic updates comparing them to manually re-uploading new files via FTP.