Hi, Im using amember with wp and the amember wp plugin. When I set the site up, it took a while to get the softwares working nicely together, so I'd like to check before hand if anyone else has managed to upgrade the two without anything breaking? Currently using WP2.5, aMember Pro 3.0.9 and the aMember WP Plugin (no idea on version) The site's setup so that aMember logs users into WP, and then premium posts are protected using a Hidepost plugin (hides content to users not logged in). This IS NOT the 'walled' type setup. Cheers
Hi Wordpress 2.6 uses an entirely different way fo handling cookies to 2.5 It is a pain. The owner of amember sent me a plugin for wordpress 2.5 and it works well. Evenb the wordpress guys say their own forum (BBPress) does not wintegrate with wp 2.6 and advises people to carry on using 2.5. So I would do as they say.
Do not upgrade to WP 2.6 yet if using the WordPress plugin - the Amember wordpress plugin will break completely.
Just got a copy of the new version of the plugin and its working on 2.6. You need to add some more info (AUTH_KEY, SECURE_AUTH_KEY, LOGGED_IN_KEY) to your wp-config file and match it with the amember plugin screen. David
You have to request it from Amember support. Why they don't just update the download link in the members area to always provide the latest plugin is beyond me. Surely it would save on a huge number of support requests. Sigh.
Yep, but this way not everyone gets it before its fully tested- there were a few bugs in it, but think they've been worked out. They should though have a clearer method to this, explain its a beta, and here's the old one just in case etc.. David
I agree - a clearer description of the plugins with version numbers would be great. A couple of weeks back I was pulling my hair out trying to get WP2.5.1 to integrate with Amember using the WP plugin. I trefused to work even though the plugin claimed compatiblity with WP2.5.1. Turns out that it was broken. There was a new version of the plugin which I had to request that added support for WP2.5.1. So not only did the original plugin not have any version number to indicate if it was the latest version of the plugin, it also incorrectly stated that it worked with WP2.5.1 when it didn't. Very frustrating and a lot of time wasted when it would be **so** simple to stick CVS revision control numbers into the code header for each plugin php file just as they do for the amember script itself. And yes, identifying beta versions would be a huge help as well.
Please update YES this would've been nice to know BEFORE I did a fresh install on a new server... ./gripe