Forum Replies Created

Viewing 15 replies - 1 through 15 (of 883 total)
  • Plugin Author Steve Truman

    (@a3rev)

    Hello @dsouzaj86

    I am sorry that the February 2020 release broke your custom code.

    Re this:

    there seems to be a recent code refactor that has changed namespaces and class names causing code errors where custom code has referenced this plugin.

    A quick look at the Changelog will show you that the change in the namespaces was done over a 2 month period between December 2019 and February 2020. There have been 5 maintenance releases since then, none of which changed namespaces. These where changed as part of upgrading the plugin to use PHP Composer.

    The first release for this was done in December 2019 as a major version release upgrading the plugin PHP to Composer Dependency manger.

    2.4.0 – 2019/12/16
    This feature release is a major refactor of the plugins PHP to Composer PHP Dependency Manager, a Sparkpost bug fix and compatibility with WordPress 5.3.1 and WooCommerce 3.8.1
    * Feature – Plugin fully refactored to Composer for cleaner and faster PHP code

    The second stage of this release was done in February 2020 and Sure if you had used the old namespaces in custom code they would break.

    2.4.1 – 2020/02/15
    * This maintenance release includes the completion of conversion to PHP composer, a fix for smpt api custom header, a security upgrade for a dependency script and compatibility with WordPress 5.3.2 and WooCommerce 3.9.2

    There have been 5 Maintenance releases since that release.

    It would appear that you have only recently upgraded the plugin and it has broken your custom code. At that time we also upgraded all of our plugins to PHP Composer – yours is the only report we have had of it breaking developers custom code and I am sorry that it happened to you.

    We do not set out to break out users code or sites and in fact spend a lot of time trying to ensure it never happens – but of course it is not possible in all cases, all of the time.

    Steve

    • This reply was modified 1 day, 3 hours ago by Steve Truman.

    @garyhawkins Yes I ran the latest version 5.2.1 this morning and it fixed nothing – the PHP Warnings, the Notice where still logged in the browser inspector , and the LayBuy did not show on the frontend , on products or the cart.

    Backporting to v 5.1.11 and everything works fine.

    Steve

    Had the same issue and posted about it here

    No response so also had to roll back to version 5.1.11 so that the plugin can work on the frontend and the PHP warnings and Notices don’t show.

    Have turned OFF auto updates on this plugin.

    Ok sorry – could not wait any longer for a response and there has been another version release since I posted this and no fix.

    Have rolled the version back to 5.1.11 – and the notices are gone and the frontend can work again.

    Have turned off auto updates and will wait for advise that the issue is fixed before updating.

    Steve

    Plugin Author Steve Truman

    (@a3rev)

    @bobsled

    It would appear that the scripts are cached in your browser – it has been removed from the plugin so it is impossible that it is still logging that depreciated script.

    Please clear the scripts from your browser cache or check it in another browser or on another machine.

    Steve

    Plugin Author Steve Truman

    (@a3rev)

    Hello @bobsled @umairsahb

    We have released version 2.4.1 which has a fix for that jQuery Migrate Helper issue.

    Steve

    Plugin Author Steve Truman

    (@a3rev)

    @michaelxxx

    Hi Micheal,

    Thanks for your question. In the latest a3 Lazy Load version 2.4.0 which is the WordPress 5.5.0 compatibility version, this is what we did to try and let our users know how the compatibility with WordPress 5.5.0 core lazy load works.

    1. Changelog – we put this in the changelog and as the update message

    This feature release has full compatibility with WP 5.5 core image lazy loading. Just Update and a3 Lazy Load will work side-by-side with the WP core image lazy load. No settings to update and a3 lazy load will enhance it by lazy loading images the new core feature misses and on older browsers that do not support the new feature.

    2. Update plugins readme file and the description with these notes about WP 5.5 compatibility

    100% COMPATIBLE WITH WORDPRESS 5.5
    WordPress 5.5 introduced lazy loading for all images uploaded to a site’s media library. a3 Lazy Load Image options work side-by-side with this, but then enhances it by lazy loading all the images loaded from outside of the media library or on older browsers that do not support the new WP attribute.

    3. For those that already have the plugin installed we also Update plugins Image Options help text about WP 5.5 compatibility.

    So the answer is you do not need to do anything. WordPress will lazy load images from the Media Library and a3 Lazy Load will lazy load any images outside of the media library (plugins etc) and from 3rd part sources, plus in older browsers that don’t support the new WordPress lazy Load feature.

    Steve

    • This reply was modified 3 months, 1 week ago by Steve Truman.
    Plugin Author Steve Truman

    (@a3rev)

    @dan14 @bjrnet21

    Hello – we have test again with WordPress 5.5 on there are no issues.

    Since last release 6 days ago, there have been 50,000 + downloads and no issues except your 2 reported.

    My though is that upgrading to WordPress 5.5 has broken another plugins (or the themes) JavaScript loaded on the wp-admin dashboard on your sites. This broken JS will be blocking any JS that loads after it.

    That would be why you don’t see the content load in the a3 Lazy Load plugins admin pages. This would also be breaking any other JS that loads after the broken JS so it would need to be found and removed or fixed.

    To see what is causing that open the admin panel and check for JS errors with your favorite browser inspector eg Chrome Deve Tools.

    Steve

    Plugin Author Steve Truman

    (@a3rev)

    Hello @elevas33

    You do not need any of that.

    With the Gutenberg editor just use the core WordPress YouTube block – copy and paste the video URL into the block.

    Responsive YouTube video that is lazy loaded.

    Side Note! With classic editor just copy and paste the URL into the editor – it’s only not responsive if you use the embed code which contains width and height attributes – those make it fixed size in all browsers.

    Hope that helps.

    Steve

    Plugin Author Steve Truman

    (@a3rev)

    Hi Charlotte

    Very strange – Look at this – I download the image and try to edit it with Photoshop – and it can’t open with this error message

    Cannot complete your request because an unknown or invalid JPEG marker type is found.

    See screenshot

    I Googled ‘unknown or invalid JPEG marker type’ and found this post which explains the issue and how you can resolve it.

    Hope that helps you a bit

    Steve

    Plugin Author Steve Truman

    (@a3rev)

    Hi Charlotte

    Thanks for the link. The issue is something to do with the images – I mean if you just run the images in a Safari mobile browser they also can’t load (no Lazy Load involved)

    For example in a mobile click on this image

    https://www.charlotteplansatrip.com/wp-content/uploads/2020/03/Budget-Sri-Lanka.jpg

    If you try in Chrome browser on mobile it is the same.

    Run that url in a Laptop Chrome, Firefox or Edge browser and it shows fine.

    The image is there but it is just a tiny thumbnail that is impossible to see.

    Just a question? are you using Jetpack Plugin Image Enhancer (Photon) or something similar?

    Are you seeing the same issue with a3 Lazy Load deactivated – you should be because the raw image url that pulls the image straight from the server has the same issues in mobile browsers.

    Plugin Author Steve Truman

    (@a3rev)

    Hi Charlotte

    Have tested and there is no issue with the latest or recent Safari browser. Also I think if there was we would have many reports of that and yours is the only one.

    I think that it is an issue with your browser cache. You would just need to clear it. If you have had the plugin deactivated for a week it has probably cleared itself.

    Try reactivating it and see how it is. If you still see the issue then clear your safari cache.

    If the issue still persists then please post an link to the site so that I can check it for you (a3 Lazy load would have to be activated of course).

    Steve

    Plugin Author Steve Truman

    (@a3rev)

    Filters are already defined, you don’t need to define again.

    Try using

    add_filter

    Example

    add_filter( 'a3_lazy_load_placeholder_url', function( $image_url ) {
     $image_url = 'your_new_image_url'; // put your new image url here
     return $image_url;
    } );

    Change your_new_image_url to your real image url or image data

    Steve

    Forum: Plugins
    In reply to: [a3 Lazy Load] hidden tab
    Plugin Author Steve Truman

    (@a3rev)

    Hello @aga2442

    I have never heard of Chromes Hidden tab’ feature – so just do some research on Google. Seems it is brand new and only supported from chrome Version 77 tp current.

    It is a touted replacement for Google Synch (apparently it is faster). Also seems that the feature is still buggy – you should check this checklist – it suggests 5 things to check and do to fix bugs

    https://www.guidingtech.com/fixes-chrome-send-your-devices-missing-not-working-issue/

    Chrome sync works fine with a3 Lazy Load so it should with this new feature – but Chrome may continue with it or maybe not – before we go spending time digging into it and debugging it – I’d like to see it become a lot more ‘mainstream’

    Please let me know what you find once you have been through the post 5 things to check.

    Steve

    Plugin Author Steve Truman

    (@a3rev)

    Hi @jinsley8
    Thanks for letting me know what you have done – much appreciated.

Viewing 15 replies - 1 through 15 (of 883 total)