I have tried a wide variety of approaches to upgrading a set of sites from the 6.x-1.x branch to the 6.x-2.x branch. I am also preparing documentation to submit once I get this done effectively, because I suspect others may have trouble with this. Currently I am stuck and need some help. I can get the 2.x branch to receive a login from a slave. In other words, the slave sends the credentials to the master. The master establishes the session with the UID in the session table on the master. I noticed there was no bakery_user entry created for the account, so I added it myself, entering the master and slave UIDs and the slave URL (just the root URL - tried both with and without trailing slash - no difference). All of what I am describing is only happening after adding the bakery_user table entry. Now, it redirects back to the slave but I notice very briefly on the slave that the URL cycles through a double slash bakery/login during the process (//bakery/login) and resolves to Access Denied. The slave session table shows only a UID 0 entry. What is most interesting is that when I return to the master site, the welcome message is queued in the session table and shows, and I am logged in. So, I am able to login to the master from the slave, but the session is not passing back to the slave. Thoughts? (The system works on 6.x-1.x.)

Comments

greggles’s picture

My general advice is two-part: 1) be sure to clear all cookies and follow the advice in the README.txt about cookie domains. 2) Be sure to visit the admin/settings/bakery and re-save the settings to make sure they are as the 6.x-2.x branch expects.

I noticed there was no bakery_user entry created for the account

Were there any mysql errors in watchdog?

Is the problem only about registering on the slave or are their other bugs after the upgrade?

dominict’s picture

No specific MySQL errors. I should note I have one site running drupal 6.20 pressflow and the other running 6.20 commons with pressflow core swapped in. I have turned off caching in both for testing since that may cause trouble with the 6.x-2.x branch. I have cleared the caches several different ways to check this issue (directly through the database, through admin/settings/performance, etc.) I have also been checking directly in the dblog for indications. I do not see any clear signs as to why this problem is happening. I am still working on it.

dominict’s picture

I just went through the steps again, and I am having no luck. The bakery_user table is not populating itself.

coltrane’s picture

Status: Active » Postponed (maintainer needs more info)

Is that table still not being populated? It could be an issue separate from the upgrade. I'm of the mind that upgrade from 1.x to 2.x is not supported.

drumm’s picture

Issue summary: View changes
Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)

Closing due to lack of response.