Wordpress 2.0 is out, and I was unable to find a version bump request, so here it is.
*** Bug 116830 has been marked as a duplicate of this bug. ***
Since my dev box is dead, due a failed motherboard, I'm going to have to find another one of the devs willing to bump this for me. It might take a little bit, but I should have this taken care of in the next day or so. Cheers.
*** Bug 116834 has been marked as a duplicate of this bug. ***
when short PHP tags are disabled in the webserver, there's a problem with /wp-admin/templates.php. i've already reported this issue upstream, but if you decide to include an ebuild based on the official WP 2.0 tarball that is served on the servers now, i thik it would be good to fix the problem. i'll attach a patch that should fix the problem.
Created attachment 75758 [details, diff] fix short PHP tags in templates.php
Hm, that patch definitely should go upstream. The upgrade from version 1.5 to 2.0 is a pretty major thing, and 2.0's turned out to be quite buggy; it might be worth waiting until a bugfix comes out from upstream.
This is what I was thinking, as well. It has been buggy for me, as well as many other users. If I put it in the tree, it's going to package.mask, due to the bugs. I think it makes more sense just to wait until a 2.0.1 or some other release is made.
*** Bug 117765 has been marked as a duplicate of this bug. ***
Good idea guys, I'm glad I saw this bug. I almost installed wordpress2 today manually (without ebuild). Didn't realize it was so buggy though!
*** Bug 119045 has been marked as a duplicate of this bug. ***
*** Bug 119495 has been marked as a duplicate of this bug. ***
A checklist of steps for the ebuild to follow when upgrading an existing installation is described here: http://codex.wordpress.org/Upgrading_WordPress
Mike, All of what is referred to in that document takes place *after* the ebuild is upgraded. That's not relevant to the Gentoo update process. I will mention again here, for anyone still following this bug, I'm not putting 2.0 into the tree. We're going to wait until another release comes out.
*** Bug 120056 has been marked as a duplicate of this bug. ***
Created attachment 77908 [details] wordpress-2.0.ebuild wordpress-2.0.ebuild. Needs work but does install wordpress-2.0 correctly.
Mark, I mean no offense, so please understand that ahead of time. Did you read the rest of the comments on this bug request? 2.0 is *not* going into the tree. I'm going to wait for at least a released 2.0.1 or newer before putting it into the tree. Cheers. Aaron Kulbe "SuperLag"
(In reply to comment #16) > Mark, > > I mean no offense, so please understand that ahead of time. Did you read the > rest of the comments on this bug request? > > 2.0 is *not* going into the tree. I'm going to wait for at least a released > 2.0.1 or newer before putting it into the tree. > > Cheers. > > Aaron Kulbe > "SuperLag" > I don't expect 2.0 to go into the tree. I posted it for people who use portage overlay to use the ebuild, since my other post was closed resolved and marked as duplicate.
*** Bug 120327 has been marked as a duplicate of this bug. ***
Version 2.0.1 was released today. I just commited that to the tree. Enjoy.
Reopen, to set proper resolution.
Bumped to 2.0.1 Closing bug RESOLVED - FIXED.
