Matthew Denton

Mike,

I’m going to add additional error display to the validation screen in the upcoming version so we can see the exact reason your validation is failing.

Working on support for locales and looking to have it available by end of week.

Hi Sorry, I’ve been tied down with work and personal matters that haven’t allowed me to stay up-to-date on the plugin. The issue is simply that # needs to be removed from the color options for it to work correctly. I’ll have this updated in the new version i’m trying to wrap up.

Matthew

Hi, I’ve done some initial review and the issue does not appear to be related to the API. As i see the same version of the plugin working across multiple sites but not on some. Upon review it appears that in most cases the issue is that the server time is off causing the request to error out with RequestExpired exception from Amazon. I am working on a fix to check for this error and resubmit the request based on lookup of gmt time from a time server which is working but I need to do some follow up to make sure there is not going to be excessive calls to the Time Servers which would cause a denial of service to future requests for the time from your host and would end you back in the same situation currently being faced.

If you have access to your server I would suggest verifying the gmtdate time returns the current time correctly. I noticed on my web host it is off by 20 minutes.

Hopefully further updates soon,

Matthew

Cary:

Can you provide a link to your site so i can view what is getting rendered? also can you provide the current settings you set on the Omakase widget, does the preview of the widget function?

Thanks,
Matthew

Hi, the purpose of the Admin Localization is so that when logged in as an admin you can view your website content as viewed by different locales. E.g. if you are from US locale and want to confirm that UK users see UK versions of the products you can switch the admin locale to UK and verify the content is for that locale.

There is one caveat with this and that is for some reason on some installations of WordPress user capabilities do not get initialized properly prior to plugins executing (details here). In these cases the admin localization does not function as I put a check in to disable the code if the functions called don’t exist.

HI,

1) to modify the target simply set it to a different value in your ShortCode. e.g: [amazon_link target="_self"]...[/amazon_link]

2) Not currently. I have the masking capability as a very low priority item for a future enhancement. In my opinion there is no reason to mask urls to other websites as it is misleading to visitors. Depending on how other plugins work if they have set their filter to run after the shortcode has been parsed then they could mask the outputted links.

Mark:

The plugin was updated to a new version and uses a passive statistical tracking of version installations. Please review and re-instate the plugin in the directory.

Mark:

Where is this outlined? WordPress has no support for tracking the actual number of installed plugins or active versions (beyond the pie chart that is known to be misleading as from day to day versions shown will not be inclusive. Using the blog url you are able to know the active number of sites currently using the plugin as well as which versions of the plugin need to be supported including upgrade logic.

Kindly please specify where this is outlined. As previously stated my intentions are to know actual figures on usage of the plugin for support and enhancements. If there is another unique identifier that can be used please specify as if it is not unique then there is no way to know actual statistics on plugin usage.

Hi I wanted to know actual stats on how many sites are using the plugin, no other purpose. The website url is the unique identifier for making it so there is no repeated counts when users update to a new version of the plugin.

If you have any reservations about using the plugin then please do not use it however upon reviewing the logic of the methods you will see that all it sends is as stated website url + plugin version.

If you look at the code the information sent is strictly the version of WPAA (WordPress-Amazon-Associated) installed and the website url as that is a unique id for tracking if it gets deactivated/upgraded.

WordPress is great at telling plugin authors how many downloads there has been and percentage of sites using each version however it doesn’t give details on actual number of sites using the plugin so I built that capability into the plugin, hence the activation/deactivation functions.

Hi, the above issue is covered in other forum posts. Details…

Fix :

You open capablities.php and add require_once(‘pluggable.php’);
(but you need to change those quotes to single quotes) right after the opening <?php tag at the top of the file.

As described in following Post

Hi, what is your website address? You can send it to my email address matt(at)mdbitz.com and I will have a look at it. Are the widgets you utilize active in the WP – Amazon > Widgets Page?

Hi, it appears this is occurring for a few users. I’m trying to track down why but so far have not been able to duplicate the issue.

Hi Everyone, sorry for the problems this caused. It appears that the issue is hit or miss for different users and I can’t pin down what is different for everyone’s installs.

I have just released version 1.7.1 in it I do a manual check for if the wp_get_current_user function exists and if not then the Admin Localization (logged in administrators can view site as a selected locale) will not function.

Again sorry for the issues this caused!

> Matthew

Yes, a strange issue as it is not present for all users. I am releasing a bug fix (1.7.1) to put in a check for if the wp_get_current_user function exists and if not the Admin Localization (to view content as a locale for logged in administrator) will be disabled.

Sorry for any problems this caused.