John

Thank You @mej @marketingfire for fixing the issue. Would love to know why a moderator would have chosen to delete our comments. We were all civil in raising the issue, so I don’t think we broke any WordPress forum rules.

I can confirm my comment was deleted. Not impressed.

My question exactly. My images are being shrunk down to fill the lightbox, which is what I want, but I’d like to get the little arrow at the bottom which opens the carousel to not be sitting on top my images. I figure I need to add some margin to separate the image from the arrow. Have lightbox padding set to 0. Captions and carousel set to not display initially.

The latest version seems to have fixed it. Thank You.

Thanks for continuing to address this issue. Auto Update for this plugin is different from all other plugins I’ve encountered. Guess which one of these is Docket Cache?

https://northumberlandstudiotour.ca/wp-content/uploads/Auto-Update-Enabled.jpeg

My only problem now is that I’ve installed the plugin on nearly 100 websites and I don’t know which ones need to be updated to auto update. I will eventually get to them all as I visit them, but it will take some time.

Here’s a screen shot of the plugins page on one of my sites.

https://northumberlandstudiotour.ca/wp-content/uploads/Auto-updates-enabled-scaled.jpeg

I found my problem. Although the plugin states Auto Updates Enabled on the plugin page, when I manually update the plugin, a link appears under the Auto Updates Enabled saying Configure auto updates. Clicking on that takes me to the configuration tab of the plugin. Scrolling down to Plugin Options, I find Docket Cache Auto-Updates disabled. So although the plugin tells WordPress it is set for auto-updates, it actually isn’t until that configuration is made in the plugin options. A bit confusing to be sure.

Thanks for your response. What is strange is that auto-updates usually indicate when they will happen, usually next day, once an update appears. Your plugin does not seem to do that.

If you’re using the free version of Yoast SEO, and you don’t want any Yoast-related information to appear in the sidebar, you can disable the pre-publish checks as shown in the screenshot.

Where is this in the free plugin? How do I find this switch?

No I don’t want you putting ads in with my Publish settings box or anywhere in my sidebar.

What a stupid thing to do.

Thank You Rory. That solved it.

The UI on that notice really doesn’t work. You need to indicate to people that they have to scroll down past the large empty section of the page to see anything. Even then, it makes no reasonable sense to downgrade to a free account and then click Pay. Some additional instruction there would have solved it. I’m a little surprised because your plugin and website are usually so intuitive. Anyways, thank you again for your help.

I also now know not to ask for support through your contact page as 4 days has passed without no reply there.

This is why we have a love/hate relationship with WordPress. If they didn’t ram these things through like this, I might be more tempted to explore them instead of just reacting negatively when I find my sites highjacked. Now I have over a hundred websites I have to install this plugin on. Thanks for nothing WordPress.

I am also seeing this error which only shows when WP Simple Paypal Shopping cart Version 4.5.2 is activated. I have WordPress 5.6.1 installed.

Server architecture Linux 3.10.0-962.3.2.lve1.5.42.el7.x86_64 x86_64
Web server Apache
PHP version 7.4.14 (Supports 64bit values)
PHP SAPI cgi-fcgi
PHP max input variables 3000
PHP time limit 90
PHP memory limit 512M
Max input time -1
Upload max filesize 32M
PHP post max size 32M
cURL version 7.71.0 OpenSSL/1.1.1d

Excellent. That works just fine and also, good to know.

Thank you for the speedy reply!

I agree Neil Murray, which is why I use
From: [your-name] <[email protected]>
but I still get that error message on the Additional Headers.

Perhaps I need to start a new thread as my issue may be different from bowqtr’s issue.

Following as I’m having similar problems with the latest validator.

Cc: [email protected]
Reply-To: [your-email]

Warning: Invalid mailbox syntax is used in the Reply-To field.

Strange, because Reply-To: validates on other forms on the same site using the same code. Never been a problem in the past.