Tyler Tork

I will not open a support thread. I’m just switching to a different plugin. The email report in this case does show there was a problem. It’s simply that the SUBJECT LINE of the email doesn’t show there was a problem.

I wouldn’t say the issue has been resolved. After your last message I expected to hear more. You don’t need more information from me, do you?

I also had this problem. You message “explaining” this issue blames the theme or plugins (“PHP is NOT allowed in your code (disabled by your theme or a plugin)”). This had me running down a rabbit hole for HOURS trying to figure out which plugin was the problem, when YOUR plugin was the problem. Even if the update had worked perfectly, this is really obnoxious. Please take the trouble to write clear messages.

When you mention that Local Broken Link is deactivated, do you mean deactivating it from the Plugin page or just switching from Local to Cloud

The plugin is active and in cloud mode. https://prnt.sc/I2X1hV_VQ4t5

Are you still receiving the email notifications periodically of was it a one time instance?

I have only received one such notice that I’m aware of while the plugin was in cloud mode. It occurred after editing a page that already contained those links.

It could be possible the cron job that triggers the notification was delayed and still in queue even after the plugin was deactivated.

I haven’t had any problems with other cron processes, such as plugin updates and newsletter mailings. Moreover, the email was apparently triggered by my editing the containing page after the plugin was already in cloud mode. I should note that I’d already responded to your plugin’s complaints about these particular URLs when I created the page.

Could you also share the info about the current version used? And also let us know if you have the plugin installed in other sites and if they are presenting the same issue?

Version 2.2.0, last updated 2 weeks ago. I do use the plugin elsewhere. I haven’t observed this particular issue elsewhere yet, but I don’t often go in and edit existing pages, which seems to be the trigger for this issue.

I am interested. Let’s talk. At tylertork.com, I’m tyler.

It is in a reusable block, in fact.

If I add a Gallery, your lightbox effect works with both the Gallery and the Image block.
I assume this is for diagnosis, not because you’re going to recommend that I have a Gallery in every post.

It sounds like you have no intention of doing anything to make this less of a problem in the future. Can your program not write the .htaccess rules to exempt certain folders of plugins known to securely use PHP files, so we can have the benefits of PHP-execution protection generally while still allowing it where needed?

I have documented the solution here: https://torknado.com/2022/12/ithemes-security-incompatibility-with-matomo/ in hopes others having the same problem will find it when they search.

I confirm unchecking “Disable PHP in Plugins” was enough to get it working. I ask again that iThemes just make this work for Matomo and maybe a few other popular plugins that have a legitimate need for this.

The Blog page is set to “inherit”. New screenshot: https://prnt.sc/l9sQOlrrlAF7
The Home page is also set to “inherit”, and I’ve tried switching it to show a sidebar.

Fix confirmed. Thank you!

I appreciate the importance of SEO, yet also I notice that all the most popular plugins have titles much shorter than yours, most only 2 or 3 words. Yet they have achieved great popularity. I think having a useful, admin-friendly, and well-documented plugin is far more important than any SEO considerations. Because a good plugin will be reviewed and linked to — as I have reviewed and linked to yours from my website — and that does much more toward SEO than a long title.

Some suggestions follow:

• I dislike the note suggesting people not watermark the “full” size image. As that’s the original, highest-quality image, of course they want to watermark that one if they do any of them. Instead, how about adding a note next to “full” that says, “Original image; if you watermark this you will not be able to remove watermark unless you enable backup images on the ‘image protection & backup’ tab.”
• For deciding which sizes need to be watermarked, it would be helpful if you display the pixel dimensions associated with each size. Themes and plugins will often add entries to this list and the user won’t necessarily know how big they are.
• In addition to selecting which size names have watermarks applied, it would be helpful to have a number field, “Don’t automatically watermark images unless they are at least ___ pixels in both dimensions” with default value maybe 500. If the original is a 64-pixel square icon, they almost certainly don’t want to add a watermark.
• Add an option to tile the watermark.
• I’d like the documentation to state where the backup images are stored.
• Some plugins have an checkbox option to remove all data associated with the plugin when it’s deactivated. Since your plugin has a lot of associated data (the backed up original images), I’d like either a checkbox like this, or some reassurance that the backup images are stored in a way that they will be gone if the plugin is deleted.
• I don’t know whether this is possible, and I haven’t tested how it works now, but I suspect that if I use the Recalculate Thumbnails plugin or similar and the “full” image is watermarked, this will result in having watermarks on all the sizes, including those I didn’t select. It would be nice to make this bulletproof if possible — for instance, if there’s a backup of the full image, that you could use some hook in the WordPress code to substitute that as the ogiginal image for resizing purposes. Interactions with other plugins are complex, I know.
• Likewise, when the user asks to edit an image in WordPress, if the full has a watermark and you have a backup, could you supply the backup image for editing?
• If the image is watermarked, and the image is edited in WordPress, can you intercept the save event and reapply the watermark as appropriate?
• When an image is watermarked (or the watermark is removed) and my browser has a cached version of the image, when I view the image in the media library, I can’t see the change until I refresh the cache (Ctrl+F5). Not sure there’s anything you can do about this.
• I’m getting more impractical as I go along. If the admin chooses to watermark the full image and doesn’t enable backup, if they have to edit the image they would do it on their PC and then re-upload it. But there’s no way in WordPress to re-upload an image and replace the original image. They might update it in the back end using FTP. But if they do that, your code has it flagged as watermarked when it is no longer watermarked. I fear that will prevent them from reapplying the watermark. Is there some way you can tell that the image was modified after you marked it? By size or timestamp for instance?

And make sure there’s not a browser cache or CDN cache of the old scaled images.

I don’t think this plugin does what you want — you need to search for something like “fixup media” or “restore media database”. This one just operates on images already in the database to create updated scaled versions.