Tim Carr
Forum Replies Created
-
Glad you were able to resolve.
We haven’t forgotten anything in our latest version – that error tells you that the Buffer API can’t be reached.
Confirm your server can connect to buffer.com, and liaise with your hosting provider as necessary.
No ideas at this time, we will be updating the free version to use better hooks for Post publication / updates, which should resolve some of these issues.
Please don’t hijack other threads / post the same issue across multiple threads. It makes it extremely difficult for us to best provide support in the limited free time we have for this free product.
Zach,
I acknowledge receipt of your email.
Per our readme, support for our free product is solely provided through these forums. Customers of our Premium product have access to support by email.
Turning to the issue in question, it’s clear that introducing (and then removing W3 Total Cache) has resulted in a configuration change within WordPress that has rendered our plugin unsuitable.
I cannot begin to advise what that configuration change would be (how long is a piece of string), and therefore suggest the following:
1. Enable debugging in WordPress – see how to do this at https://www.wpcube.co.uk/support
2. Retest, make a note of the precise steps you’re taking, what happens, what you expect to see. Include any error messages that appear
3. If the above doesn’t resolve, setup a clean installation without W3 Total Cache on a new subfolder / subdomain.
4. Retest, make a note of the precise steps you’re taking, what happens, what you expect to see. Include any error messages that appearAt some point in the above process you’ll either find the cause of the problem or the solution.
Feel free to post back here with the results, and we’ll go from there.
That’s not Envira’s lightbox (ours is a different design).
Check your theme and other plugins to see if one of them uses its own lightbox, as that will be the cause of the issue.
Fixing in 1.5.0.4, releasing Thursday.
https://preview.marketsoul.cz/sekvoia/references/ shows cropped images at 350 x 270 pixels
Let me know what I’m missing to reproduce this bug.
Thanks.
You’d need to implement custom CSS to achieve this. It isn’t an option in Envira.
Fixing in 1.5.0.4, releasing Thursday.
No main reason, and hard to advise without specifics.
If you have an example URL demonstrating the issue, we’d be happy to take a look.
This is by design in the new version, glad you found a solution.
I can confirm https://github.com/futtta/autoptimize/commit/1279edf0fe9d3da8f82bcdfcf8c4a531bdd9a0d8 fixes the issue in my opening bug report and with Envira Gallery.
Further to the above, this is a fault with Autoptimize’s code, and the author has been notified:
https://www.ads-software.com/support/topic/autoptimize-fails-to-aggregiate-inline-javascript-containing-srcOnce resolved, the following settings in Autoptimize will ensure correct working functionality with Envira Gallery Lite and Envira Gallery:
– Optimize Javascript Code: Yes
– Force Javascript in head: No
– Also aggregate inline JS: YesConflict has been found, Frank to receive an email advising of how to improve Autoptimize to resolve this.