I'm not quite sure where to start with this issue as it cropped up after the most recent update to Open Atrium (1-0 beta 8). Prior to the update, everything worked fine.
After the update, when I click on the "Add" tab or an edit link for a context, Firefox gives me a "Firefox has detected that the server is redirecting the request for this address in a way that will never complete" message. To further complicate things, when checking in Opera, it shows that, at first, it's redirecting to a path with an Organic Group of mine in the path, but when reloading, the group disappears from the path.
I've checked my .htaccess files. Everything checks out there. I've cleared the cache, both via the "Clear cache" button at Administer > Site configuration > Performance as well as manually through the database (just to make sure). I've cleared my browser cache, refreshed my db server, and even did a complete reboot just to cover all the bases here.
Just to rule out something very general, I've tested Add/Edit links on all other major components such as Views and CCK, as well as Add/Edit links to nodes and things seem to be working fine.
I'm working on a localhost development site using the following:
Windows 7
XAMPP v. 1.7.1
MySQL 5.1.33
Apache 2.2.11 (Win32)
Open Atrium 1.0 Beta 8 with Drupal 6.19 and Context 3.0 (amongst many other things)
I also use Pathauto on this site, recently updated to the most current recommended version (6.x-1.4), though I have not configured this above and beyond the default configs.
| Comment | File | Size | Author |
|---|---|---|---|
| #11 | purl-context-tab-not-redirecting-properly-900564-11.patch | 9.43 KB | tobby |
| #4 | purl_608916_20100917.patch | 11.48 KB | ranm |
Comments
Comment #1
nenad.scekic commentedSame problem. !!
Comment #2
ranm commentedSame bug for me, we'll be happy for a fix/answer...
Thanks Ahead!
Ran
Comment #3
ranm commentedJust gathered to fix Context UI by disabling jQuery update, but still, redirect loop when trying to edit/add new context occurs.
Thanks again,
Ran
Comment #4
ranm commentedHi everyone,
Found the solution to our redirect loop bug when trying to add/edit new context!!!
After doing some research and debugging I found out the redirect loop occur because when trying to add new context it goes through all groups, for example : www.example.com/group1/admin/build/context/add... www.example.com/group2/admin/build/context/add... www.example.com/group3/admin/build/context/add... etc..
Therefore the solution (-:
I found out this bug is caused by the PURL module (Persistent URL) and I found this patch (attached to post). below the things needed to do :
1. patch PURL with the attached patch
2. go to : /admin/settings/purl/disabled and add entry admin/*
That's it, all works fine for me!
Thanks,
Ran Mizrahi
Drupal Department Leader
CodeOasis.com
Comment #5
Daniel A. Beilinson commented@ranm: thanx for excellent patch! And don't forget to check group space option after adding this path.
Comment #6
ranm commentedNice to make some people happy! (-:
Comment #7
shushu commentedMoved under the PURL project for review from maintainers.
Regards,
Shushu
Comment #8
ashedryden commentedAny update on this? This seems to also be effecting the Open Atrium beta 9 installs.
Comment #9
tobby commentedI'm looking for a way to replicate the issue. I've tried fresh installs of OpenAtrium as well as installing beta-7 and updating to beta-8 and beta-9. So far, I've not been able to replicate the infinite redirect issue.
Does it do this when you try from a new install of OpenAtrium on that same environment? Which modules, besides pathauto, have you installed since the initial build?
Comment #10
ranm commentedHi Tobi,
This bug usually occurs after a specific number of groups published at the website which actually causes the redirect.
Try adding large amount of groups and I guess you will occur the context redirect.
Thanks,
Ran
Comment #11
tobby commentedI have rerolled the patch from #4 since it was made from CVS a long time ago. Can anyone with these issues please test and make sure the patch 1) applies cleanly for them using the current dev release, and 2) fixes the actual "not redirecting properly" issue?
Comment #12
muka commentedPatch works for me, thanks