I hate to admit but all my attempts to upgrade to 1.0 and now to 1.0.1 keep failing.
I can easily install 0.34 once again ( I did it already couple times ) so I, technically speaking, can't miss or typo something crucial such as database connection info, the web path to the base of lyceum, domain name of the server and uncomment in private.php otherwise I am blind :)
Anyway, my server doesn't see wp-config.php :
"There doesn't seem to be a wp-config.php file. Double check that you updated wp-config-sample.php with the proper database connection information and renamed it to wp-config.php."
When I perform a fresh install ( 1.0 as well as 1.0.1 ), there comes some errors, related to wp-config.php Everything is fine when I return to 0.34 and installs perfect.
I don't have enough information to help you. Where do you start having problems? You will have to update your wp-config.php, there are several new / different configuration options in 1.0.
Yeah, john, meantime I was trying to install 1.0.1 on another web host and got the same message about wp-config.php It seems that I repeat something wrong...
Look, in the very beginning I put /src/lib, /src/config, and /src/installation to within src/lyceum, and then placed them in the root, also uncommented define('PRIVATE_REL_PATH', './') in private,php
It was quite enough to successfully installed 0.34
Now we get close to my mistake which I yet can't figure...
During upgrade I put everything again together - /src/lib, /src/config, (but there is no such a file - /src/installation in 1.0 and 1.0.1) and installed the new code over the old code and created a new wp-config.php file from the new wp-config-sample.php I didn't edit a new private.php, there is uncommented line already.
So, in a new wp-config.php I reapplied only:
1. I keep the same MySQL settings, ( just copied and pasted 4 lines from the previous settings )
2. keep define('WEBROOT', ' '); as before
3. keep define('MAINDOMAIN', 'unlimitedwisdom.info'); as before
No more, no less. Yet I don't see where I did a mistake.
mikhail and ialexs-- can one of you file a ticket describing your problem and how you fixed it? tell us what your maindomain and webroot settings where, and any other details you can think of . Then report back here with the ticket so that we don't make 2 tickets for the same problem
I'm having some problems upgrading from Lyceum 0.33 to 1.03. The instructions are, umm, sketchy. Like they say "install the new version over the old." Well, what files/directories do I overwrite, exactly? Are there changes to the database schema or not?
On my first attempt, after installing the new version over the old as best I could figure, all I got were blank pages.
In my second attempt, I figured I'd try to set up a parallel Lyceum system, so I just did a new install of v 1.03 in a different directory, then overwrote its wp-content directory with the stuff from my old install. Had to tweak my .htaccess file to refer to the new directory name, etc. It seemed to work. So then I renamed my original directory, and renamed the new directory to the original, and retweaked the .htaccess. Then some things worked but others didn't - I kept finding links that pointed to the new directory name (and thus led to nonexistant pages) even though I had changed the .htaccess to eliminate all references to it.
Anyway, I'm frustrated and wishing there were more complete instructions about how to go about upgrading.
(Guess I'm spoiled by the Windows software installations where you just click "Install" and it all happens magically...)
Sorry... 0.33 to 1.0.x wasn't the smoothest (or i should say, most obvious to execute) upgrade.
to answer your question-- almost all of the files are changed, and/or in a new place in the file tree.
the very first thing to do, is make complete database and file backups of your existing installation, and put them in a safe place.
then, do you have any changes to your 0.33? the rest of these instructions assume that you do not.
then-- what plugins and themes have you installed? you'll be putting these back after upgrading.
now-- put the new software in place of the old software. it doesn't matter where you put it, as long as apache is pointing at the /src/lyceum directory as the web root.
next-- make a new wp-config.php file. look carefully at the entire file and make sure everything is set like it should be. it should be quite clear what to do, just make sure to look at the whole file, until you get to the debug options. leave all those as they are.
next-- move in your plugins and themes
next-- run the upgrader, as the documentation describes.
Finally had time to retry the upgrade today, and it went better. It was a little more complicated than the previous note suggests, so I'll document exactly what I did - possibly for the benefit of other users, and maybe also so John can give me help with remaining issues.
At our web site (http://watershedhs.org) we have a traditional set of web pages that you see when you go to our home page, and Lyceum blogs that you get to from various links. In order to make the regular web site work, we can't have Lyceum take over the web root directory. Instead, we have Lyceum installed at http://watershedhs.org/currents/lyceum. Internally, we have a public_html directory that is the web root, and it holds our regular HTML files as well as the "currents" directory.
So here's what I did:
1. Saved a copy of the Lyceum database offline. 2. Copied the entire currents directory hierarchy to currents-save (cp currents currents-save -r ) 3. Copied the "src" directory from the distibution over the "currents" directory (cp lyceum103/src currents -r) 4. Copied the saved wp-content directory back to its original location (wp currents-save/lyceum/wp-content currents/lyceum -r) 5. At this point one of our previously installed plugins was apparently incompatible, and prevented accessing the blogs, so I disabled them by renaming the directories currents/lyceum/wp-content/plugins and currents/lyceum/wp-content/systemplugins. 6. In my web browser, visited currents/lyceum/wp-admin/upgrade.php. (Apparently there ARE database schema changes going from Lyceum .33 to 1.03. -- this wasn't clear from the documentation. Anyway, the upgrader seemed to take care of it.) 7. Saved the text from the upgrader's report, in case I'd need to refer back to it. 8. At this point, the blogs seemed to be mostly working. I needed to edit the htaccess file (currents/lyceum/.htaccess) to reinstall a custom redirect I had done some time in the past when we needed to rename a blog.
Now the blogs are working pretty well. I have not yet re-installed the plugins we had before; that might take further work because there do seem to be some incompatibilities.
Now, here's a problem from the upgrade I haven't resolved yet.
Somehow the "admin" userid has gotten tangled up with another pre-existing userid named "arobinson" - which (perhaps no coincidence) is alphabetically the first in our list of users. The problem shows up when I'm logged in as admin and write a post: the post then shows up as having been written by arobinson. Yet when I go to the Profile/Personal Options page for admin, the name appears as "admin" like it should. And when logged in as arobinson, I have only the permissions that arobinson should have.
I have thought about deleting the arobinson account (the person it was created for has never used it) but I'm nervous about doing so in case it would somehow mess with the admin account.
Why did these accounts get entangled and how do I untangle them?