Jeff Rose

In theory, hosting the files on S3 or similar with restrictive IAM permissions would prevent direct access.

My approach is to have 2 versions. 1 watermarked/lower quality for preview and 1 full quality, not watermarked for download when offered.

But I’d love to simplify this.

3 – This would be in your browser developer console. Right-click and choose “inspect”

I’m not the developer, but I’d say “Yes and no”. I’m running this on one site I’m developing (4.6.2) and it works perfectly. The last update was only a month ago so the developer is probably still working on things or no change is needed.

“Not tested” is simply a flag. The developer could update that with a new version, and not make any actual changes.

My opinion only.

The src=”book.jpg” needs to be the full (or maybe relative) path to the file:

[pixobecoloringbook src = "https://www.google.com/somepicture.jpg"]

If you just do book.jpg, it’ll look for the image within the plugin’s files and it won’t be there.

I apologize for the title. I wrote it when I was having trouble when it didn’t work. That was because the media in the shortcode was set incorrectly.

Your plugin works, I’d just love to see the changes I mentioned.

Ugh. Thanks for the reply. I suppose I could update the database so that all posts are “old”.

Having the same problem here. WordPress 5.1.1, Folders 2.0.4 (Free). Screenshot below.

WordPress Folders Bug

Actually, looking at the code, the function deleteAllOptions is attached to the deactivation hook.

So everything was deleted, including accounts.

I’m not sure about the other guys, but it seems like deactivating the plugin – which happens during an update – clears many of the settings.

For example, I had excluded hundreds of posts, and after the upgrade, everything was active.

I just tested again by excluding a few posts, confirming they were excluded and then deactivating the plugin. When I reactivated, all of my posts were still included.

The plugin inserts a shortcode, and then draws the content directly from Amazon it appears, so that prices and descriptions are always current and correct.

Yep, dozens upon dozens. In another thread here, I think someone said it won’t affect anything except prevent proper use of GeoTargeting, but it’s definitely something that shouldn’t happen.

I’ve gone so far as to set the entire path to 777 temporarily, but it still throws the errors (I set the permissions back to standard after the test).

Love to see this fixed!

As mentioned, I filed a support request (7899) also.

Never mind.

Thanks for the reply, this does seem to work properly!

I really want to use your plugin, but these errors make it impossible.