lightroomqueen

A “me too” here unfortunately.

Thanks, I’ve narrowed it down to the Angelleye PayPal plug-in and I’m in touch with the developer.

How did you solve this? I’m seeing unusable fields too, seems to be a conflict with the Angelleye PayPal plug-in version 2.40 and later.

> Perhaps it would be good, if you also update this to XPress support.

I don’t use Xpress (I use a custom bridge) so I doubt they’ll want to hear from me!

Glad to hear it worked for you too!

I tried it on my usual staging site, which stopped throwing errors (but has the actual sending of emails disabled, to save my customers receiving doubles) and then set up a clean install of WP&XF to test it more fully, including actually sending the emails to myself. I can’t push it to my live site this week due to other commitments, but I’m happy enough that I will at the end of the week.

Ok, everything looks ok, but do your own testing…

I went to https://github.com/MyIntervals/emogrifier/releases and scrolled down to 3.1.0 (NOT 4.0.0, as that changes filenames). Click Assets and then download the zip.

For Xenforo, navigate to /src/vendor/pelago/emogrifier, rename that emogrifier folder (in case you want to put the original back) and upload the contents of the zip into a new emogrifier folder.

For WordPress, navigate to /wp-content/plugins/woocommerce/vendor/pelago/emogrifier and again, rename the emogrifier folder and upload the contents of the zip into a new emogrifier folder.

In my testing, that appears to solve the issue, but YMMV.

I think I’ve got it. About a year ago, I ran into an issue where WordPress and Xenforo had different versions of Sodium Compat and it was causing fatal errors. I think the same thing is happening here.

I’ve just tried replacing both XF and WP’s Emogrifier files with the latest and the WordPress errors are gone. I’m not a developer, I could be way off base here, and I’ve got a load more testing to do… but if it seems to check out, I’ll post back with more specifics.

Hmmmm. I’m also hitting an error with a Xenforo integration (not Xpress) and WC 4.1 and later. Disabling the XF integration solves it, or I can work around it by setting WC to Plain Text emails instead of HTML. Neither is a great solution. Did either of you get any further on this?

That’s great, thanks. Just a typo in the error message – Week should be Weak. ??

Week Password!
Hint: To make password stronger, use upper and lower case letters, numbers, and symbols like ! ” ? $ % ^ & ).

Oh that’s wonderful news, thank you very much!

Same issue here. Please don’t make me go back to Chimpy…

Scratch that! Found it! It was a plug-in called Category Tag Page that was causing my disappearing posts. I’ll carry on testing your plug-in but it looks like it’s working great!

Where does the plug-in record the changes? Uninstalling the plug-in doesn’t undo the settings.

The sort order works great, but some of my custom pages aren’t showing up under their categories and I can’t see why. They’re categories I edited with your plug-in, so I want to remove all trace to see if that fixes it.

No, no visible error. Everything just keep redirecting back to the home page.

I’ve just asked the host for more details and they said: The LiteSpeed license didn’t carry over properly to the new hardware and after a while it reset back to Apache. There are some things LiteSpeed handles better than Apache resulting in the errors. We identified the licensing issue and restored the license but caching could cause some people to see errors for longer until they clear their browser cache or the cache expires.

It seems it may have been a hiccup with the web host. I’m not inclined to test that theory myself, but if you can’t reproduce it, you can probably ignore it.