Adam

@paradore,

You lost me at “within your SCIG param/setting,” but if you and @realtm can figure this out, I salute you.

Hi again, Thomas, I just made the site above private. If you’re willing to look into it, let me know where to send you admin credentials.

Hi @realtm,

I did the full plugin/theme test, as I detailed here. I’m happy to give you admin access to the staging site I linked to in that support post, where the problem is most definitely not caused by a plugin or theme conflict.

It seems to me that because you can’t replicate an issue that a lot of your users are experiencing, an opportunity to investigate it where it is replicable would be really valuable for everyone.

Thanks!

Hi @conniegoh,

I’m sorry to tell you I’m not a MailPoet tech, so I couldn’t tell you. I suggest you ask in the plugin forums, or email them directly.

In that spirit, I’ll put in a plug for you with Organic Themes. I’ve come to use them exclusively. ??

@jmstudio, so glad that helped. ??

Personally, I dread doing a plugin conflict test. I wish there were a master database of all plugin conflicts you could query. Talk about a timesaver.

Right on, Rob! Thank you!

Thanks. OT seems to be understandably slow to move all their themes to the Customizer. They’re about 40% converted right now, I think.

Update: it looks like OF may have been baked into the theme. When I reinstalled/updated by x.x.2, OF appears to be back in working order.

Hi @nsp-code, I’m afraid the solution your describing falls beyond my abilities. Thanks for the reply, though!

Thanks, @mattburns_uk!

And @adamjedgar, I’m working in a child theme. Always. ??

@esmi, the behavior I was referring to just popped up on my staging site, after saving Widget options.

Screenshot of problem (on staging site).

Screenshot of how it should look (on live site).

Thanks, @wakapedia! Great idea. Looks like some substantial changes in Galleries.

Actually, not any more. I just moved a copy of the live site (without the problem) to a local staging server, and updated. No apparent problem.

The issue was that the front page truncated .entry-content‘s width to about 480px, where it should have been closer to 780px.

If it comes back I’ll make an effort to document it.

Because when I updated on my staging site I saw strange behavior I couldn’t account for in my child theme’s CSS, nor could I roll back by restoring a backup of the site (though keeping the theme at 1.1).

And for general clarity/transparency. ??