Forum Replies Created

Viewing 15 replies - 76 through 90 (of 256 total)
  • Problem is now how to delete che cached links, where are they stored? I can’t see new links yet

    Maybe I found the fix.

    file:

    \amazon-associates-link-builder\rendering\xml_manipulator.php

    line 202

    change $3 to $2, so that it becomes:

    return preg_replace( "((tag=)[^&]+(&))", "$1" . $store_id . "$2", $response );

    I confirm this bug, my links are borken too and I’m not getting clicks after upgrading to 1.9.1

    Trying to investigate on a manual fix, but it’s hard to dig in the code.

    • This reply was modified 7 years, 3 months ago by DrLightman.

    => WP Dashboard -> Settings -> WP Super Cache -> WP Super Cache Settings -> Advanced tab -> Miscellaneous -> UNCHECK the little box in front of “Make known users anonymous so they’re served supercached static files.” because if CHECKED it’s FULLY INCOMPATIBLE with at least WP 4.9.x.

    This worked for me, thanks.

    ok maybe because filters have already run

    Yes, it looks like it’s not working, not always at least.

    I’m doing this in a widget output code to inject the a3-notlazy class and it’s not working:

    $htmlimg = get_the_post_thumbnail(get_the_ID(), 'my-theme-slider');
    echo str_replace('class="', 'class="a3-notlazy ', $htmlimg);

    The resulting image has these classes in the final html of the page but I think it gets lazied anyway:

    class="a3-notlazy lazy lazy-hidden attachment-my-theme-slider size-my-theme-slider wp-post-image"

    • This reply was modified 7 years, 8 months ago by DrLightman.
    • This reply was modified 7 years, 8 months ago by DrLightman.
    • This reply was modified 7 years, 8 months ago by DrLightman.
    • This reply was modified 7 years, 8 months ago by DrLightman.
    Thread Starter DrLightman

    (@drlightman)

    Thanks!

    Thread Starter DrLightman

    (@drlightman)

    Is there a place to download older versions? I need the 2.1.3

    Thread Starter DrLightman

    (@drlightman)

    nvm I guess I found the answer here https://wordpress.org/support/topic/disable-lazyload-on-page-template/

    but it still loads assets though (js, css)

    At that stage (before content on a page) is too late, the pugin has already been activated.

    You should put that code in functions.php and modify it by putting the condition by which you want the disable to take effect, inside the skip_a3_lazy_load_for_this_page function.

    So,

    1) put the code in functions.php

    2) add the condition, for instance if you want to disable on post ID 123:

    add_filter( 'a3_lazy_load_run_filter', 'skip_a3_lazy_load_for_this_page', 11 );
    function skip_a3_lazy_load_for_this_page( $apply_lazyload ) {
      if(is_single(123)){
        $apply_lazyload = false;
      }
      return $apply_lazyload;
    }
    Thread Starter DrLightman

    (@drlightman)

    Maybe you don’t look closely enough. If you take a closer look to your plugin’s style.css:

    /seo-redirection-premium/cf/css/style.css

    You can see the rules that override properties in the whole html doc, such as:

    body { background-color: transparent; font-family: “Open Sans”,sans-serif; font-size: 13px; }

    ^ this will change the whole font family to “Open Sans”, sans-serif overriding the WP defaults of “-apple-system,BlinkMacSystemFont,”Segoe UI”,Roboto,Oxygen-Sans,Ubuntu,Cantarell,”Helvetica Neue”,sans-serif;” in my wp 4.6.11

    unfortunately most of classes in your style are generic or single classes that may conflict with other styles because doesn’t targtet your elements only exactly by being more specific, such as:

    .seo-redirection .mytable …
    .seo-redirection .myform …
    et cetera

    I’m having same doubt. I’m using another cache plugin that produces static html files, and I found this inside a cached html page:

    <script type='text/javascript'>
    /* <![CDATA[ */
    var cnArgs = {
    "ajaxurl":"https:\/\/www.XXXXXX.it\/wp-admin\/admin-ajax.php",
    "hideEffect":"fade",
    "onScroll":"yes",
    "onScrollOffset":"100",
    "cookieName":"cookie_notice_accepted", // <--- ???
    "cookieValue":"true", // <--- ???
    "cookieTime":"15811200",
    "cookiePath":"\/","cookieDomain":"XXXXXX.it",
    "redirection":"",
    "cache":"1",
    "refuse":"no",
    "revoke_cookies":"0",
    "revoke_cookies_opt":"automatic",
    "secure":"1"
    };
    /* ]]> */
    </script>

    If that is a cookie saved as “true” aka accepted, it’s now been served to all clients requesting that cached page for as long the cache lives as if they had accepted? That is WRONG.

    • This reply was modified 7 years, 11 months ago by DrLightman.
    • This reply was modified 7 years, 11 months ago by DrLightman.
    • This reply was modified 7 years, 11 months ago by DrLightman.
    Thread Starter DrLightman

    (@drlightman)

    If I fix it by replacing $ with jQuery, it works sometimes. Other times another error popups instead:

    Uncaught TypeError: Cannot read property 'focus' of undefined    proofreading-ajax.js?ver=1.0:194
        at tmce_setSelection (proofreading-ajax.js?ver=1.0:194)
        at HTMLButtonElement.click (proofreading-ajax.js?ver=1.0:76)
        at HTMLButtonElement.dispatch (load-scripts.php?c=...)
        at HTMLButtonElement.r.handle (load-scripts.php?c=...)
    • This reply was modified 8 years ago by DrLightman.
    Thread Starter DrLightman

    (@drlightman)

    I made a mistake in the code above with the closing body tag, this is the correct test code to use:

    <!--
         This is the minimum valid AMP HTML document. Type away
         here and the AMP Validator will re-check your document on the fly.
    -->
    <!doctype html>
    <html ⚡>
    <head>
      <meta charset="utf-8">
      <link rel="canonical" href="self.html" />
      <meta name="viewport" content="width=device-width,minimum-scale=1">
      <style amp-boilerplate>body{-webkit-animation:-amp-start 8s steps(1,end) 0s 1 normal both;-moz-animation:-amp-start 8s steps(1,end) 0s 1 normal both;-ms-animation:-amp-start 8s steps(1,end) 0s 1 normal both;animation:-amp-start 8s steps(1,end) 0s 1 normal both}@-webkit-keyframes -amp-start{from{visibility:hidden}to{visibility:visible}}@-moz-keyframes -amp-start{from{visibility:hidden}to{visibility:visible}}@-ms-keyframes -amp-start{from{visibility:hidden}to{visibility:visible}}@-o-keyframes -amp-start{from{visibility:hidden}to{visibility:visible}}@keyframes -amp-start{from{visibility:hidden}to{visibility:visible}}</style><noscript><style amp-boilerplate>body{-webkit-animation:none;-moz-animation:none;-ms-animation:none;animation:none}</style></noscript>
      <script async src="https://cdn.ampproject.org/v0.js"></script>
    </head>
    <body>Hello, AMP world.
      <a href="http://example.org" alt="some alt text">hello</a>
    </body></html>
    Thread Starter DrLightman

    (@drlightman)

    It wouldn’t bother me, but AMP complains about that tag in AMP pages therefore they don’t validate as valid AMP code and that’s bad for Google.

    You can see it here by yourself:

    https://validator.ampproject.org/

    By entering this test code:

    <!--
         This is the minimum valid AMP HTML document. Type away
         here and the AMP Validator will re-check your document on the fly.
    -->
    <!doctype html>
    <html ⚡>
    <head>
      <meta charset="utf-8">
      <link rel="canonical" href="self.html" />
      <meta name="viewport" content="width=device-width,minimum-scale=1">
      <style amp-boilerplate>body{-webkit-animation:-amp-start 8s steps(1,end) 0s 1 normal both;-moz-animation:-amp-start 8s steps(1,end) 0s 1 normal both;-ms-animation:-amp-start 8s steps(1,end) 0s 1 normal both;animation:-amp-start 8s steps(1,end) 0s 1 normal both}@-webkit-keyframes -amp-start{from{visibility:hidden}to{visibility:visible}}@-moz-keyframes -amp-start{from{visibility:hidden}to{visibility:visible}}@-ms-keyframes -amp-start{from{visibility:hidden}to{visibility:visible}}@-o-keyframes -amp-start{from{visibility:hidden}to{visibility:visible}}@keyframes -amp-start{from{visibility:hidden}to{visibility:visible}}</style><noscript><style amp-boilerplate>body{-webkit-animation:none;-moz-animation:none;-ms-animation:none;animation:none}</style></noscript>
      <script async src="https://cdn.ampproject.org/v0.js"></script>
    </head>
    <body>Hello, AMP world.</body>
      <a href="http://example.org" alt="some alt text">hello</a>
    </html>

    More on AMP and Google:
    https://support.google.com/webmasters/answer/6340290?hl=en

    For example if a site has an article at this url:
    http://site.com/article/
    if the site supports AMP, it will deliver the AMP version of that article at the url:
    http://site.com/article/amp/

Viewing 15 replies - 76 through 90 (of 256 total)