Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug
Bug#: 53563
Alias:
Product:
Component:
Status: RESOLVED
Resolution: TEST-REQUEST
Assigned To: web-apps Herd <webapps-request@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Peter Westwood <peter.westwood@ftwr.co.uk>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
wordpress-1.2.ebuild The ebuild text/plain Peter Westwood 2004-06-10 12:12 0000 1.92 KB Details
wordpress-1.2.gentoo.diff The required diff for symlink fixing patch Peter Westwood 2004-06-10 12:13 0000 4.94 KB Details | Diff
postinstall-en-1.2.txt postinstall-en.txt required by ebuild text/plain Peter Westwood 2004-06-10 12:13 0000 490 bytes Details
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 53563 depends on: Show dependency tree
Bug 53563 blocks: 57395
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2004-06-10 12:10 0000
webapp aware ebuild for wordpress v1.2 includes a diff to get around problems
with symlinks.

Reproducible: Always
Steps to Reproduce:

------- Comment #1 From Peter Westwood 2004-06-10 12:12:14 0000 -------
Created an attachment (id=33041) [details]
The ebuild

ebuild for wordpress-1.2

------- Comment #2 From Peter Westwood 2004-06-10 12:13:04 0000 -------
Created an attachment (id=33042) [details]
The required diff for symlink fixing

Diff for symlink fixing

------- Comment #3 From Peter Westwood 2004-06-10 12:13:52 0000 -------
Created an attachment (id=33043) [details]
postinstall-en.txt required by ebuild

Install/Upgrade instructions

------- Comment #4 From Peter Westwood 2004-06-10 12:14:22 0000 -------
Reassigned to it's proper home

------- Comment #5 From Stuart Herbert (RETIRED) 2004-07-11 15:28:36 0000 -------
Okay, this is now in Portage.  To use this, you need to use webapp-config
1.10-r5 or later.  I had to patch the login code to make it work with my
existing wordpress upgrade, so please let me know if there's any problems with
this ebuild.

Best regards,
Stu

------- Comment #6 From Stuart Herbert (RETIRED) 2004-07-11 15:29:26 0000 -------
*** Bug 53051 has been marked as a duplicate of this bug. ***

------- Comment #7 From Stuart Herbert (RETIRED) 2004-07-11 16:05:41 0000 -------
Hrm .. I'm going to have to take another look at my login-patch when I'm a bit
more awake.

------- Comment #8 From billy 2004-07-14 14:41:52 0000 -------
Login does not seem to work on a new install of wordpress 1.2.
The default blog shows fine, and the login link from there works.
But when putting in the user "admin" and the password given on install,
it just reloads the login page asking yet again for login/pass.

I do have webapp-config 1.10-r5 installed.

------- Comment #9 From Stuart Herbert (RETIRED) 2004-07-20 15:20:53 0000 -------
I've put a new login patch in place.  It works for me on my existing install of
wordpress.

Please let me know how you get on.

Stu

------- Comment #10 From billy 2004-07-29 07:31:03 0000 -------
I unmerged wordpress 1.2 and re-emerged. Letting the app setup the database
from scratch. Unfortunately I'm still having redirect limit errors when trying
to login.
I've tried it w/ firefox .9.2 on win32 and IE 5.5.

What's weird, is I was able to login on the first try via IE, but logging out
gave me a redirect error. When I tried to login again w/ IE, I got redirect
limit errors.

I deleted all cookies, tmp files, and basically everything from both browsers
and tried again. Redirect limit errors on each.

I can unmerge and re-emerge pretty simply, so if there is anything specific
you'd like me to try, just say the word.

Thanks,
billy

------- Comment #11 From Kai Groner 2004-07-30 14:02:56 0000 -------
I tried the wordpress ebuild this afternoon with no previous wordpress install.
 I got a redirect loop when I try to load wp-login.php.

It looks like checklogin() (in wp-login.php) is returning true when no
wordpress cookie is found.

I changed line 246 of wp-login.php to test for that:
-               if ($user_pass_md5 != $userdata->user_pass) {
+               if (!$userdata || $user_pass_md5 != $userdata->user_pass) {

I can log in now, I have not checked for similar problems elsewhere in the
login patch.

------- Comment #12 From billy 2004-07-31 09:44:14 0000 -------
Kai, that change works for me as well, much appreciated.
If the login is looping because of the lack of a cookie, is the ultimate problem the fact that a cookie is not being set? My install does not attempt to set a cookie.

------- Comment #13 From Stuart Herbert (RETIRED) 2004-08-08 03:46:52 0000 -------
I've added Kai's fix as -r1.  Please test it, and let me know how you get on,
so that I can close this bug ;-)

Best regards,
Stu

------- Comment #14 From billy 2004-08-18 10:05:37 0000 -------
Just installed -r1 and it's working great.
Muchas gracias,
billy

Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug