Support » Plugin: Amazon Associates Link Builder » Corrupted links automaticly created

Viewing 15 replies - 1 through 15 (of 17 total)
  • 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 months, 1 week ago by  DrLightman.

    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 );

    Problem is now how to delete che cached links, where are they stored? I can’t see new links yet

    Oh, what a nice bug. Not only the links somehow are not always shown, now they are not right.

    Thank you very much DrLightman for the fix, I already applied it and as you said, it seems to work in some links but some others still are the same, I guess because they are cached.

    And yeah,we have no control over the cache at all. Maybe a “clear cache” button at least would be nice to have.

    Also I have still no solution neither an answer for my problem, and joined with that it is difficult that I get to make more revenue when the links didn’t even work. And maybe the API is overloaded and they prioritize based on revenue, more even than they said in the guidelines?

    • This reply was modified 7 months, 1 week ago by  taisa1984.

    By studying the code, cached links should expire in 30 minutes or so:

    define( ‘AALB_CACHE_FOR_ASIN_ADUNIT_TTL’, 30 * MINUTE_IN_SECONDS );

    Thank you DrLightman for the fix! I noticed over the last 2 days that my click count was considerably less than it should be. I dread to think how much revenue I have missed out on 🙁

    Having changed that, none of my pages are loading, I get this:
    Fatal error: Namespace declaration statement has to be the very first statement or after any declare call in the script in /home/xxxx/public_html/xxx/wp-content/plugins/amazon-associates-link-builder/rendering/xml_manipulator.php on line 15

    I have rolled back the change from a backup of the file, so at the moment I am losing affiliate sales 🙁

    Come on Amazon sort this out, please.

    • This reply was modified 7 months, 1 week ago by  neildb.

    @neildb

    your editor may have messed up the php file. ensure that /xml_manipulator.php starts this way:

    <?php
    
    /*
    Copyright 2016-2018 Amazon.com, Inc. or its affiliates. All Rights Reserved.
    
    Licensed under the GNU General Public License as published by the Free Software Foundation,
    Version 2.0 (the "License"). You may not use this file except in compliance with the License.
    A copy of the License is located in the "license" file accompanying this file.
    
    This file is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND,
    either express or implied. See the License for the specific language governing permissions
    and limitations under the License.
    */
    
    namespace AmazonAssociatesLinkBuilder\rendering;
    
    use AmazonAssociatesLinkBuilder\constants\Paapi_Constants;
    use AmazonAssociatesLinkBuilder\helper\Xml_Helper;
    use AmazonAssociatesLinkBuilder\constants\XML_Constants;
    

    make sure you save it using UTF8 encoding (not UTF8+BOM).

    if you don’t know what I’m talking about, better leave the way you are with the working version 1.8.0 of the plugin and wait for an official fixed release by Amazon.

    • This reply was modified 7 months, 1 week ago by  DrLightman.
    • This reply was modified 7 months, 1 week ago by  DrLightman.
    Plugin Author Amazon Associates Link Builder

    (@amazonlinkbuilder)

    Dear all,

    Sincere apologies for this, We are working on to fix this issue.
    You can use wp-rollback to rollback to v1.8.0 till we fix this.

    Thanks for letting us known.
    Hope you guys find a fix and update the plugin soon.
    May The Force Be With You!

    Plugin Author Amazon Associates Link Builder

    (@amazonlinkbuilder)

    Dear all,

    We have fixed this issue and released v1.9.2. Very sincere apologies for this inconvenience.

    So did we just lose all amazon commissions since this problem started?
    I was affected by this since Jan 29. My Amazon report shows traffic dropped to “zero” since Jan 29.

    So what now? Do you guys have a way to backtrack the sold items via our efforts?

    @drlightman thanks! Was just about to test this when the new version was released, which I have tested now and the links are showing as they should be.

    @amazonlinkbuilder I am also keen to know the answer to @salesprodomains question above. Thanks for the quick turnaround too!

    • This reply was modified 7 months, 1 week ago by  neildb.

    @amazonlinkbuilder besides my question above…I also have 2 more questions:

    1)I have updated to the new version, should I now purge/clear cache on my page cache + browser cache + hosting cache + CDN cache so I can quickly get my links out on the internet to re-indexed by Google so the new links can start earing again?

    2) Basically, any links since Jan 29 that have been indexed are not earing us any affiliate profit right?

    Plugin Author Amazon Associates Link Builder

    (@amazonlinkbuilder)

    Dear @salesprodomains,

    We are doing analysis to see if it is possible to assign those incorrect tag attribution(with ‘amp;’) with correct ones.

    Regarding the release on January 29, it was rolled back within 6 hours and was informed on release post to rollback to 1.8.0 v1-9-0-of-plugin-released (Replies got removed by one moderator after 5 days).

Viewing 15 replies - 1 through 15 (of 17 total)
  • The topic ‘Corrupted links automaticly created’ is closed to new replies.