Francesco

Thanks for replying Brad.

That’s a great workaround and I hadn’t noticed that the option of setting custom URLs for album galleries was there.

I guess this would only work if the album(s) are actually published?

I have just updated from 1.3.29 to 1.4.8 and bumped into this very same problem with Justified Galleries on blog posts.

In my case, it seems to get sorted by:

• Disabling lazy load in the specific gallery settings (I use a3 Lazy Load site wide).
• Setting Max row height from -1 to 100%.
• Setting Last row from Center to Justify

I hope this helps you too..!

Hey Keith @kpgraham

Picking up from this topic:

1. Are you planning on releasing a new version that uses the wp_enqueue_script() function?
2. If yes would you also consider adding the option of having the JS script inlined instead of being loaded as the external file no-right-click-images.js?

Thanks for keeping this public and free, works like a charm.

You’re welcome – the script to disable the archive page should work, though

FWIW, the removed /testimonials/ archive page no returns a 404 error, so either an update of this plugin or an update of Polylang has fixed it.

Hi Emma, I have the script in functions.php and it works fine.
I remember at first the /testimonials/ archive page didn’t disappear – perhaps a caching issue?

Then it started returning a 500 error. Not it’s returning a 404 which is better.

Do you have a page with the slug testimonials in your site? I’d rename that to something like client-testimonials, then you can set a 301 redirect from /testimonials/ to the new one.

• This reply was modified 8 years, 1 month ago by Francesco.

Hey Darko, thank you so much – I didn’t know of that selector / didn’t think of looking into that, and it makes life much easier. It works ??

FYI I’ve used
.rpt_feature:last-child{border-bottom:none!important;}

What’s best, 0px dotted white or none?
I’ve added !important because otherwise my child CSS was getting overpowered by rpt_style.min.css

Thanks again.

Thank you! Much appreciated.

Of course, thank you. And just to confirm: hosting provider did recently disable exec() for security reasons. Mystery solved!

Thanks – it has to be that because I’ve just remembered of another website using EWWW on the same shared hosting now suddenly showing the message, and it was definitely not there as recently as 6 weeks ago when I first installed the plugin.

On another note (and sorry if this is not the right place to talk about this), I’m slightly confused about the pricing plans. Basically for minimal usage (let’s say about 30 images per month) how much one would spend to make API calls?

Thanks for your replies.

Cheers – I’ve asked and they say that exec() is “not supported on any of our servers”.

That’s odd as I didn’t see the EWWW notification message until just recently, and the plugin has been active for a year or so with no problem.

Has anything changed with any of the latest releases?

Just updated, thanks!

Thanks! I’m in no rush at all. Feel free to roll out the update whenever you want ?? Thanks again.

Makes sense! Thanks for replying

You’re a star! Thanks so much.