aMember does not pass log-in information to Wordpress 2.5.1

Hi all. I've successfully gotten the aMember and WordPress installations up and running. I'm using the latest WordPress plugin, along with the ViewLevel2 plugin. I can log-in to WordPress fine, as well as aMember. However, when I log into aMember, the log-in info isn't passed to WordPress so that I can view the protected posts.

Now, if I log into WordPress, I can view the protected posts just fine.

Any thoughts on how to get the two talking (I've followed the instructions that came with aMember and looked at numerous threads here...nothing has worked).

I've got aMember in the directory of /amember/ and WordPress in the directory of /blog/.

When a new user signs up through aMember, they are successfully created in WordPress. Both themes are the default themes of the installations and I have made no modifications to the core.

Thanks for all your help.

ask the support for updated wordpress plugin for wp2.5.1, that should solve your problem

I do have the latest plugin for Wordpress 2.5.1 Still didn't solve my problem.

Send a tech support ticket to make sure you got the latest plugin. (sometimes the download isnt the latest.....)

Is your secret key setup properly?

David

David - I did request a support ticket for the latest wordpress plugin and received it. That didn't seem to help. I believe I've set up my secret key correctly (place the phrase in the wp-config.php file and then replicate it in the aMember administration back-end, correct?).

Thanks for your help.

I've done a few setups with 2.5.1 - it does work, so it must be something in your setup. Hard to diagnose without seeing what you've done.


David

I'm having the exact same problem. Can't seem to figure it out. Did you ever make headway on this?

I've got aMember 3.1.0 in the /members/ folder and the blog is in the root. Users are created and everything, but the login doesn't seem to be linked properly.

David, I'm also a member of your Membership Academy.

Contact me directly then, I'll take a look at your setup- use my contact form.

David

Here's what I've been experiencing all of a sundden. My main page is at www.DoctorFloyd.com. It's a wordpress site running 2.5.1.

I have Membership Academy aMember Widget - 0.1.0 - installed. After upgrading to 2.5.1. I rebuilt the database.

If someone logs in with the widget on the main page, it says 'You'll now be redirected to the password protected area.' and goes to the main page like normal, but the person is not logged in and cannot acces all the Premium Subscriber content.

If I go to www.DoctorFloyd.com/wp-admin and type in any member's info it logs them in correctly like it should and they can access all the protected posts.

I have a ticket in to request the latest edition of the plugin (if there is one higher than 0.1.0). I'm just flummoxed as to what else to do.

Things to check
1) Wp 2.5+ uses a secret key in the wp-config and amember uses this too.
This key should be a phrase- not encrypted code.
2) do you have a $table_prefix set in wp-config? amember seems to require it.

David

1) Yep It's there. Unless this changes with each incremental version, it's the same as it was before.

2) Yep. It's the same as it was before and the location didn't change or anything.

As I said, when I enter a username or password, it logs in because I get the 'You will be redirected' amember page, but then when it cycles back to the WP page that the login box was on, the blank login fields are still there instead of the Member info (Member page, logout, etc) stuff that's there when you do login and it's not logged in and none of the protected content can be accessed.

The only thing that changed was my upgrading to 2.5.1. Before that things were working fine. I even reinstalled the 0.1.0 Widget and rebuilt the database and it didn't do anything.

Also, if someone goes to doctorfloyd.com/wp-admin and logs in, it works perfectly (Member info displayed, protected content available) It just doesn't work in the loging box on the widget.

Have you gotten an updated plugin from amember? Make sure you tell them what member of amember your using and wordpress.

Its sounds like a plugin issue.

David

THanks David. I do have a ticket in. We'll see what they say. In the amember CP=>Setup/Config->wordpress version I can only select up to 2.5, not 2.5.1. I wonder if that could be the problem?

status... log-in issue here too..

After following David's instructions... the users still aren't passed to each other when the database is rebuilt

Hi Darryl,

Edit your index.php in your wordpress directory and add the line:

PHP:

session_start();

.. directly after the <?php

Tell me if that works.

I've just had the same problem and solved it by adding the session_start(); into index.php.

This appears to be something that should be in the wordpress plugin documentation but isn't.

Or are other people here getting it to work without adding session_start() to their wordpress index page?

I think he's having a problem of users not being added to the wordpress database. I have a feeling this has to do with a new version of the plugin. They recently updated it to include a default role setting and there may be a new bug.

darryl_p: Did you hear back from amember on it?

David

Actually, I'll bet $5 that the users are being added to the WordPress database just fine but they're just not being logged in automatically.

That's the exact problem I've had with two WordPress 2.5.1 and Amember 3.1.2 sites in the last week which required session_start() to be added to the WordPress index.php to fix the problem.

So David - you're not having to add session_start() and everything's working perfectly?

One possibility is that I don't have the latest WordPress plugin, but how the heck can you tell? It's very annoying not to have version numbers on some of these plugins and a page that indicates the latest version / change log.

I stick session_start(); in the start of the wp-config.php file.

David

Ah, right. Probably a better place for it.

So the problem appears to be that the Amember WordPress plugin docs don't include this important step...

session_start(); is only needed for the amember sidebar plugins (mine or skippy's), not the amember wordpress plugin that goes in the amember plugin directory.

David