webapp aware ebuild for wordpress v1.2 includes a diff to get around problems with symlinks. Reproducible: Always Steps to Reproduce:
Created attachment 33041 [details] The ebuild ebuild for wordpress-1.2
Created attachment 33042 [details, diff] The required diff for symlink fixing Diff for symlink fixing
Created attachment 33043 [details] postinstall-en.txt required by ebuild Install/Upgrade instructions
Reassigned to it's proper home
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
*** Bug 53051 has been marked as a duplicate of this bug. ***
Hrm .. I'm going to have to take another look at my login-patch when I'm a bit more awake.
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.
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
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
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.
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.
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
Just installed -r1 and it's working great. Muchas gracias, billy
