-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Documentation needs some more updates before I roll up the release packages, particularly the release notes and the upgrade information, but I've gone ahead and branched 1.9 off from trunk to make sure it doesn't get hit by another ten regressions by morning. ;)
The 1.9 release branch can be checked out via Subversion at: http://svn.wikimedia.org/svnroot/mediawiki/branches/REL1_9/phase3
A few more testers to confirm that installation and upgrade work on configurations other than developers' own machines before we make a wider release would be welcome, so don't be shy about testing it. :)
- -- brion vibber (brion @ pobox.com / brion @ wikimedia.org)
Brion Vibber a écrit :
A few more testers to confirm that installation and upgrade work on configurations other than developers' own machines before we make a wider release would be welcome, so don't be shy about testing it. :)
Standard installation tested on a wamp (XP+php 5.1.6+ MySQL 5.0.24), no apparent problem :-) , seems to be working properly (edit, image/thumbnails, login).
Is there anything in particular we should pay attention to ?
Brion wrote:
[snip]
A few more testers to confirm that installation and upgrade work on configurations other than developers' own machines before we make a wider release would be welcome, so don't be shy about testing it. :)
Sure, no problem, creating a backup of my current system now..... ;-)
What is the (required) upgrade path from 1.6? Can I immediately upgrade to 1.9, or do I have to touch 1.8 first?
[snip]
On 08/01/07, Hans Voss hans.voss@gmail.com wrote:
What is the (required) upgrade path from 1.6? Can I immediately upgrade to 1.9, or do I have to touch 1.8 first?
Direct upgrade should be fine; run the maintenance/update.php script as usual.
Rob Church
I'd love to test/try it now since it's soon to be released, but, I'd really hate to put all my trust into it, and it'd turn out to be like last time.. 12 FRESH installs, straight out of the box, only to get multiple redirecting loops..
Part of email I sent a few good weeks ago, and that subdomain isn't up any more..
"By the way, after the downloading, and doing a *fresh* install of the trunk/phase3, then going to index page, it's spitting out redirecting loops.. this url is what got below sigh :( spencerp.net/index.php/Index.php/Index.php/Index.php/Index.php/Index.php/Index.php/Index.php/Index.php/Index.php/Index.php/Index.php/Index.php/Index.php/Index.php/Index.php/Index.php/Index.php/Index.php/Index.php/Index.php"
And being that NO ONE really replied to me on this issue, or said anything about this issue.. I just don't have any clue of what to except ...
Ah, the downfalls of a list of people here to help, but don't anyway.. Well, they do, they just picky on who they want to talk too.. Oops..
Either way, I'm learning her myself though.. Besides being busy working with WordPress 2.1, theme customizing, and the bbPress forum software.. I might get some more time into learning it..
By the way, here's my notes on what I had done.. I hope it helps others! http://www.mwusers.com/forums/showthread.php?t=3348 http://bbpress.org/forums/topic/486?replies=9
-- spencerp http://spencerp.net
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
spencerp wrote:
I'd love to test/try it now since it's soon to be released, but, I'd really hate to put all my trust into it, and it'd turn out to be like last time.. 12 FRESH installs, straight out of the box, only to get multiple redirecting loops..
Part of email I sent a few good weeks ago, and that subdomain isn't up any more..
"By the way, after the downloading, and doing a *fresh* install of the trunk/phase3, then going to index page, it's spitting out redirecting loops.. this url is what got below sigh :( spencerp.net/index.php/Index.php/Index.php/Index.php/Index.php/Index.php/Index.php/Index.php/Index.php/Index.php/Index.php/Index.php/Index.php/Index.php/Index.php/Index.php/Index.php/Index.php/Index.php/Index.php/Index.php"
Well, I'd certainly recommend trying 1.9 then; it should work more consistently and/or provide better error messages for this case.
- -- brion vibber (brion @ pobox.com)
[Brion Wrote Before> Well, I'd certainly recommend trying 1.9 then; it should work more consistently and/or provide better error messages for this case.~~~]
YES!! I just upgraded to the Latest - 1.10alpha copy.. I know, I know, haha.. but, figured out how to do the line command now, on over-writing the files in the codex's root directory. I did make a database backup first though, saved the extension to computer, same goes for original LocalSettings.php file, and some others in which I did core file edits..
At first though, for some odd reason.. I couldn't get the "php update.php" command line to work on "maintenance/", gave me a message saying, it couldn't work because of running php 4.X.X, but if you're sure php5 is running, check the path to it, or whatever.. But, I AM running the MediaWiki on PHP 5.1.2 though.. so.. not sure what's up with that. I'm on Dreamhost.com by the way..
(I'm not sure on the AdminSettings.php file deal, I put in there my user and pass that's actually for the Database user and pass.. and it's different of course, to my Administrator account for the Codex itself..) Do I have to manually create that user's table first, or something.. ?
Anyway, I chmodded the config/ folder 777, renamed my LocalSettings.php file to LocalSettings.php.old.. and went through normal browser install stuff, it upgraded the database like supposed too..
Then saved the NEWLY made LocalSettings.php file as LocalSettings.php.newest, and then moved it to root/ of the codex.. however, I'm using the original one instead..Re-chmodded the config/ 644
I didn't try the BBPress_Auth extension yet, but will here soon. I want to make sure that's still going to work with it, which I'm sure it will..
All that customized work is and was saved.. I went around here and there on the Codex.. and haven't recieved any errors.. so, to me looks like she's working great! Awesome!! Thanks for your time .. ;) :)
-- spencerp http://spencerp.net
On 10/01/07, spencerp spencerp1@gmail.com wrote:
YES!! I just upgraded to the Latest - 1.10alpha copy.. I know, I know, haha.. but, figured out how to do the line command now, on over-writing the files in the codex's root directory. I did make a database backup first though, saved the extension to computer, same goes for original LocalSettings.php file, and some others in which I did core file edits..
If running the bleeding-edge of MediaWiki, you MUST be prepared to keep updating the files to follow any fixes that are applied to it. If someone adds a feature and a security vulnerability, and we notice and fix the latter before it's release time, we won't generally issue another release, since it's in the unstable branch.
At first though, for some odd reason.. I couldn't get the "php update.php" command line to work on "maintenance/", gave me a message saying, it couldn't work because of running php 4.X.X, but if you're sure php5 is running, check the path to it, or whatever.. But, I AM running the MediaWiki on PHP 5.1.2 though.. so.. not sure what's up with that. I'm on Dreamhost.com by the way..
The version of PHP running at the command line (the CLI) is often different to that running in a web browser; these goddamn stupid modern shared hosts. You can often find the real path to the PHP 5 CLI and use that, otherwise, use the "re-run the installer" or "phpShell" methods mentioned in the upgrade pages on the MediaWiki site.
(I'm not sure on the AdminSettings.php file deal, I put in there my user and pass that's actually for the Database user and pass.. and it's different of course, to my Administrator account for the Codex itself..) Do I have to manually create that user's table first, or something.. ?
There's another, recent thread on this mailing list where I explained the whole "AdminSettings.php file deal" in great length, but the gist of it is that AdminSettings.php is for providing the credentials of a MySQL user with permission to perform maintenance operations on the database.
Anyway, I chmodded the config/ folder 777, renamed my LocalSettings.php file to LocalSettings.php.old.. and went through normal browser install stuff, it upgraded the database like supposed too..
Then saved the NEWLY made LocalSettings.php file as LocalSettings.php.newest, and then moved it to root/ of the codex.. however, I'm using the original one instead..Re-chmodded the config/ 644
Ack! *Never* rename the LocalSettings.php file such that it no longer ends in ".php" - stuff like ".old" etc. will cause Apache to serve it as a plain text file, which will expose database connection information.
When renaming, stick to a scheme such as "LocalSettings.old.php" and "LocalSettings.new.php" - different files, safer extensions.
I didn't try the BBPress_Auth extension yet, but will here soon. I want to make sure that's still going to work with it, which I'm sure it will..
No experience using it, don't know.
All that customized work is and was saved.. I went around here and there on the Codex.. and haven't recieved any errors.. so, to me looks like she's working great! Awesome!! Thanks for your time .. ;) :)
Generally, one of the benefits of going down the Subversion route for upgrades is that Subversion itself handles merging of file changes, so local hacks are easier to preserve. Extensions, when well authored (ahem) are completely pluggable and provided you're sensible about keeping the extension up to date, won't fsck up MediaWiki when it's time to go to the next point release.
Rob Church
[Rob wrote> If running the bleeding-edge of MediaWiki, you MUST be prepared to keep updating the files to follow any fixes that are applied to it. If someone adds a feature and a security vulnerability, and we notice and fix the latter before it's release time, we won't generally issue another release, since it's in the unstable branch.~~]
Yep, will do. However, that was a mistake on my part, I didn't use the right svn co url.. =( I forgot to use the one Brion posted a few emails back sigh. Dang.. Well, I'll keep updating as needed though.. ;) :)
[Rob wrote> The version of PHP running at the command line (the CLI) is often different to that running in a web browser; these goddamn stupid modern shared hosts. You can often find the real path to the PHP 5 CLI and use that, otherwise, use the "re-run the installer" or "phpShell" methods mentioned in the upgrade pages on the MediaWiki site.~~~]
Hahaha, yeah.. stupid hosts. >_< Oh well, I'll just use the "web installer method" then.. ;) :) If for some reason I feel "daring" and what not, I'll find the real path to the PHP 5 CLI then.. ;) :)
[Rob wrote> There's another, recent thread on this mailing list where I explained the whole "AdminSettings.php file deal" in great length, but the gist of it is that AdminSettings.php is for providing the credentials of a MySQL user with permission to perform maintenance operations on the database.~~~]
Oh okay, I think I remember your's coming through the list, but it was deleted though sigh. I'll go back through the archives then, but, I probably won't worry about this too much, though. I still have TONS of other things going on sigh.. But, I'll find your post then. ;) :)
[Rob Wrote> Ack! *Never* rename the LocalSettings.php file such that it no longer ends in ".php" - stuff like ".old" etc. will cause Apache to serve it as a plain text file, which will expose database connection information.
When renaming, stick to a scheme such as LocalSettings.old.php" and "LocalSettings.new.php" - different files, safer extensions.~~]
Slaps self, Okay.. I'll remember that for later. :) ;) I'm not sure if this makes a difference though, but I manually chmodded those files 644, and folders 755.. Well, always do, for everything except images.. ;) :) But, anyway.. I'll remember that next time. ;)
[Rob wrote> Generally, one of the benefits of going down the Subversion route for upgrades is that Subversion itself handles merging of file changes, so local hacks are easier to preserve. Extensions, when well authored (ahem) are completely pluggable and provided you're sensible about keeping the extension up to date, won't fsck up MediaWiki when it's time to go to the next point release.~~]
You have a good point there.. ;) :) Well, like I said above, I'll check that extension out then, and see if it's all good yet. If it's not. I'll let the author know of it. ;) :) Thanks so much Rob for your tips, suggestions, comments, and what not.. ;) :)
By the way, the Extension's URL for whoever wants to read up on it: http://codex.wordpress.org/User:RobLa/bbPress_Auth_for_MediaWiki http://comox.textdrive.com/pipermail/wiki-tech/2005-August/000028.html
-- spencerp http://spencerp.net
Dear Brion,
I installed updated from 1.9-branch:
Great! The blank-page-issue has been solved. Nice work :-)
Now I only get an error-message above the wiki; but I will try out this tomorrorw ... install fresh and deactivate extensions (now: need sleep ;).
FYI, the error: Warning: is_file() [function.is-file]: open_basedir restriction in effect. File(/lock_yBgMBwiR) is not within the allowed path(s): (...mypath.../subdomains/mwbeta/httpdocs:/tmp) in ...mypath.../subdomains/mwbeta/httpdocs/includes/GlobalFunctions.php on line 256
Regards, Jan
Brion Vibber schrieb:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Documentation needs some more updates before I roll up the release packages, particularly the release notes and the upgrade information, but I've gone ahead and branched 1.9 off from trunk to make sure it doesn't get hit by another ten regressions by morning. ;)
The 1.9 release branch can be checked out via Subversion at: http://svn.wikimedia.org/svnroot/mediawiki/branches/REL1_9/phase3
A few more testers to confirm that installation and upgrade work on configurations other than developers' own machines before we make a wider release would be welcome, so don't be shy about testing it. :)
- -- brion vibber (brion @ pobox.com / brion @ wikimedia.org)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFFojUowRnhpk1wk44RAgnCAJ9JJAfc2WuUSoQ2LZIfb3dcX+L1rQCglt9H T/vOy3I/zwZ5eLa1u62NVZU= =mnri -----END PGP SIGNATURE-----
MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org http://lists.wikimedia.org/mailman/listinfo/mediawiki-l
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Jan wrote:
Dear Brion,
I installed updated from 1.9-branch:
Great! The blank-page-issue has been solved. Nice work :-)
Now I only get an error-message above the wiki; but I will try out this tomorrorw ... install fresh and deactivate extensions (now: need sleep ;).
FYI, the error: Warning: is_file() [function.is-file]: open_basedir restriction in effect. File(/lock_yBgMBwiR) is not within the allowed path(s): (...mypath.../subdomains/mwbeta/httpdocs:/tmp) in ...mypath.../subdomains/mwbeta/httpdocs/includes/GlobalFunctions.php on line 256
Fixed: http://svn.wikimedia.org/viewvc/mediawiki?view=rev&revision=19012
- -- brion vibber (brion @ pobox.com)
Dear Brion,
"open_basedir"-fix works fine :) Updated to r19016, I found no more warnings/bugs :)
Excellent, fast work!
Regards, Jan Toelstede
Brion Vibber schrieb:
Fixed: http://svn.wikimedia.org/viewvc/mediawiki?view=rev&revision=19012
mediawiki-l@lists.wikimedia.org