freelance08

It was the first time. WordPress 4.6.1.
Thanks for your help!

Thanks Ben, that did the trick. That plugin’s going to come in handy elsewhere too, so double thanks for the tip! ??

I was able to get Hostgator support to fix this for my sites. They said that it was mod_security rule number 1234234 that needed to be changed:

the rule is 1234234, however, that does not mean it will always be the same issue or rule. For the safety of your site and content, replicating the issue and pulling the exact code is what we need to do in order to properly whitelist the issue.

Commenting so I can subscribe. I’m in the exact same situation.

How about now? Is there an ETA? And if not, can you suggest a band-aid solution? We’re deeply invested in the theme we’re using. Is there something I can take out of your code, or can I rename the variable or something?

Thanks in advance for any help you can provide.

Hi caimin,

Thanks for replying. No, we don’t have any plugins that appear to use custom fields other than Events Manager. And actually, the changes first started showing up when we would update an existing event. Saving the event would kill the custom attribute values (and render them “Array”).

Thanks for your thoughts!

I just went and deleted the plugin, reinstalled it, and went directly to change those values. I changed both the thumb and full size values to 100 width and 125 height.

Just as before, those new dimensions seem to be reflected in the page where it asks you to choose the crop area to use, but once I click “Crop”, the resulting image is 150 x 150, and distorted (since the original image is not 150 px wide).

Any help figuring out why this would for some reason not work as described would be much appreciated. Is there somewhere else where this might be being overridden? It’s not in my wp-config.php, and I did a search through my theme’s files for USER_AVATAR and nothing came up.

OK, as I mentioned, I had already tried editing those lines to no avail, but I’ll go through it once again. Meanwhile, if anyone has an idea why that wouldn’t work for some reason, please let me know.
Thanks again!

I tried that, and it didn’t work for me. I even took out the relevant “define” lines from your plugin, and that didn’t make a difference. For that matter, before that, I edited those lines in your plugin to have different sizes (both the thumbnail and the full size settings), and nothing seemed to change. Actually, that’s not totally true–on the crop page, it shows my image size under “Choose the part of the image you want to use as your profile image.” and under the preview, but then when I click “Crop, it warps the image and creates a 150 x 150 version.

Can you help? I’m boggled and frustrated. Thanks!

This is the biggest hole in WordPress’s development, in my opinion. It’s kind of unbelievable that there isn’t a readily-available way to use the WP visual editor in a widget.

Here’s hoping someone works it out! ??

Oh BTW, unlike Baden, we did not have this working originally. Just to clarify that. We’ve been getting various forms of fatal errors upon activation since we’ve been trying to use this plugin for the past month+. Oh, and I do have the main Mailchimp signup plugin installed, though as I mentioned, I tried activating yours first and it didn’t seem to help.

Thanks again for any help you can provide. Really looking forward to using this plugin!

Hi,

I get the same error message as Baden above (though with different amounts of bytes). It references line 1007 in functions.php as well, but oddly our functions.php only has a couple dozen lines (it just has the code for widgets in it).

I get the fatal error even if I deactivate all other plugins first, though I do get a slightly different one:
Fatal error: Out of memory (allocated 48496640) (tried to allocate 3107570 bytes) in […]/wp-includes/wp-db.php on line 849

The site is https://projectsimplify.com
hosted at Hostgator
PHP 5.2.4
WP 3.0 (now 3.01, same problem still)
Lots of other plugins are installed; I don’t have a list handy.

Thanks for your help Mark!

First, Amaury, if you’re listening, thanks so much for working on keeping Simple Tags compatible!

Just reporting in…I also got the “fatal error” message when activating it, but it appears to have activated nonetheless. I haven’t had a chance to test any of the actual functionalities yet.

FYI, this is now controllable within the core WordPress installation, via the “Screen Options” menu on the Edit Posts and Edit Pages pages. Hooray!

I do really like how you give access to all of a plugin’s files in the plugin editor. (But at the same time, you did away with the clickable list of plugins on that same page, and replaced it with a less-desirable dropdown menu.)