Hi everyone.

I'm having a javascript error in internet explorer 8 at this line.

The product works fine but I hate to see javascript errors in explorer status bar.

Are you guys having the same problem? I'm running 3.8.5 and the latest ame 2.5.6

Edit:

If I disable this plugin the error goes away.

Does anyone know what this plugin does?

I'm pretty sure that plugin "Hides" (or disables) AME for usergroups who aren't allowed to use it- if for some reason you disabled it for some users. I know one site for example where they disable it for guests.

I wonder if it would be possible to make a definition that would work for any web site and pull the "title" of the site and put it as the link, so instead of:
https://vborg.vbsupport.ru/index.php
you'd get
vBulletin.org Forum

Otherwise is there some way to make this work nicely with this existing mod?
https://vborg.vbsupport.ru/showthread.php?t=189658

It works but the titles on youtube videos become full URL's instead of titles with both mods enabled.

Okay I think I have found the problem. If you take a shortened Amazon link, like those you get from a Google search, it works just fine. The syntax is usually http://www.amazon.com/product-name-here/dp/JDISHIOEHO and AME turns it into http://www.amazon.com/product-name-h...filiatecode-20 . This validates using Amazon link checker just fine.

The problem arises if you use a longer Amazon link, like the ones you get when you search for an item at Amazon.com. These URLs already have a question mark in them, like ?ie=UTF8&blahblah . If you copy that, the AME appends ?tag=youraffilaitecode-20 to the end of the URL. This will not validate using the Amazon link checker, presumably because two question marks appear in the URL.

You can make it validate by appending &tag=youraffiliatecode-20 to the end of the URL instead. The problem is this syntax will not validate with the shorter URL format you might copy off Google.

All is fine if you are the only one putting Amazon links on your forum, but of course you want it to automatically append the right tag for whatever type of Amazon link a user might post.

Anyone handy with definitions have an idea on how to use ?tag= for shorter Amazon links and &tag= for the longer types that have a ? in the URL already? Maybe two separate ones?

One possible idea is that you append this to the end of any url ?tag=youraffiliatecode-20&tag=youraffiliatecode-20 . This seems like it works in limited testing, but I'm not all that familiar with AME definitions and Amazon URL formats to say for sure. Sometimes redundancy is good, sometimes it is not...

If what you say is true I would make the replacement link always have an ?= even if it's a dummy value it should just be ignored, ?dummy=5... then the &tag=affiliatecode should always work. I don't know if this would pass the amazon link checker but it should work in practice.

A number of these previous questions, which I would specify if I had a little more time today, are somewhat rectified if you use the up-to-date definitions in the add-on thread. The default definitions for AME have not been valid or updated in quite some time. I try my best to keep mine up to date, even though that tough in all cases.

I wanted to comment on this one real quick. Actually, yes, there's a big difference. BBCode uses more resources when a page is generated than AME does. This is explained somewhat in the description, but simplistically, this is less server intensive.

From my testing today, the combined tag I posted works best. It validated in every case that I tried, including some links that get passed to the redirected mobile Amazon site on phones. That's not conclusive, but so far, so good.

I think the definition BirdOfPrey posted back a page or two was the one from your definitions and it was far superior to the default one if I recall correctly (thanks!). Of course, if you updated it recently, perhaps your most current one solves the issue another way?

This worked for me for a while and now has stopped working? I'm using 2.5.6

Edit: I cleared cache and now it works

Any issues with that, please direct towards my thread and I'll try to address them.