Forum Replies Created

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

    (@a3rev)

    @hensterrsa

    Please upgrade to version 5.3.16, it has the fix for this issue.

    Thank you for the bug report.

    Steve

    Plugin Author Steve Truman

    (@a3rev)

    @dimalifragis

    Please upgrade to new maintenance version 2.4.13 – it has the fix for this issue.

    Thank you for the bug report.

    Steve

    Plugin Author Steve Truman

    (@a3rev)

    @dimalifragis

    Hmm – we run this plugin on over 100 clients sites and have not seen that issue. Will try and recreate your error message. How do I do recreate that error message? I don’t see it from dev tools on the frontend.

    Are you using a plugin that is showing that, I mean I have test with Query Monitor and it is not showing it as a PHP error ?

    What version of WordPress and PHP is your site running on?

    Thank you
    Steve

    Plugin Author Steve Truman

    (@a3rev)

    Hello @funmelody

    Yes that is correct – Please understand that the counter is activated each time the url loads in the browser, regardless of how that happens (refresh) or who it is (not logged in or logged in).

    The count is for visitors to see – it is ‘social proof’ for both site visitors and site owners who don’t care to use or look at their Google Analytic tracking.

    We never set out to build a Google Analytics type tracking plugin – we set out to make a easy to use Page Views counter that shows on the page and increases by 1 each time the page is loaded.

    If you are after very accurate recording of Page Views for making marketing decisions please please use Google Analytics script or facebook pixel for that. There are many plugins for both of those things.

    Sorry I cannot help you more with your wishes.

    Thank you
    Steve

    Plugin Author Steve Truman

    (@a3rev)

    Hello @aldociana,

    Thank you for letting me know about the issue you had with the upgrade to version 2.6.0 – sorry about that. We have fixed the issue and released the patch in version 2.6.1

    Thank you
    Steve

    Plugin Author Steve Truman

    (@a3rev)

    Hello @jbromberger

    In answer to your question – we have not built an interface to see Total page views on the backend because there are very good Google Analytics plugins that do a great job of that, and I don’t want to reinvent the wheel so to speak. Page Views Count is a simple ‘Social Proof’ script that we built for use on our own client sites, and have shared it here on wordpress.org for others.

    We could add the option to ignore logged in Admin views – but have never done that as it would just add another query that must be run on each page load, so we never have added it.

    Cheers
    Steve

    Plugin Author Steve Truman

    (@a3rev)

    hello @vbenkovskyy

    That is pretty harsh! The Quick View pop up does work – I have no idea why its not working for you – When it does not work (the pop up) it is usually because there is a broken JavaScript on the site (from another plugin or the theme) that is blocking the Quick View pop up from working.

    Steve

    Plugin Author Steve Truman

    (@a3rev)

    Hi @mitfi, @pamahfoundation, @mijia99eggers, @pmsoft85, @kapman

    Version 2.4.2 is out with Compatibility with WP 5.6 – It contains the fix for this issue.

    Here is the changelog

    2.4.2 – 2020/12/08

    * This maintenance release has tweaks and bug fixes for compatibility with WordPress major version 5.6, PHP 7.4.8 and WooCommerce 4.7.1
    * Tweak – Test and Tweak for compatibility with PHP 7.4.8
    * Tweak – Test for compatibility with WordPress 5.6
    * Tweak – Test for compatibility with WooCommerce 4.7.1
    * Fix – Attached ajaxComplete to document instead of window
    * Fix – Replace old isFunction by typeof check function

    Steve

    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

    @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.

    Thread Starter Steve Truman

    (@a3rev)

    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 1 year, 3 months ago by Steve Truman.
Viewing 15 replies - 1 through 15 (of 890 total)