rustindy

PHP4 has issues with MySQL 4.1 related to authentication, but that doesn’t sound like the problem here. I use Apache 2 with PHP5 and MySQL 4.1 no problem for the 1.5 blogs, and IIS with PHP4 and MySQL 4.0 for the 1.2 blogs (though I had to get 3rd party poopware to get permalinks working on IIS).

You might want to check your “php.ini” file and make sure that your wordpress site has the necessary override permissions regarding what can appear in the htaccess file, and that mod_rewrite is indeed enabled and configured correctly (I don’t remember offhand if it has any specific configuration settings, but it might).

The file that tells WordPress where to store your posts is /wp-config.php – it should contain the name of the database you want to use, it’s location or IP address, the login name and password for it, and the prefix WP should use on the tables it creates.

If your database has been munched up, then restoring the old WP files will not bring it back. However, if the reason you can’t see any posts now has to do with WordPress having a goofed up /wp-config.php file, just double-check your information and see if it works 🙂

i live life on the edge, but even i took the couple minutes to make a db backup before starting to migrate my hosted blogs to 1.5 😉

I guess this means I’m qualified to write a book about WP then, yes? 😀

Seriously, whatever. I’m not in the demographic for an introductory-level WordPress book, “WordPress for Dummies” kinda thang, so that makes me qualified to write it. Don’t get mad, it’s true. I have the necessary amount of PHP, *NIX, Windows, Apache/IIS, and MySQL knowledge/experience to cover 99% of the bases when it comes to installing and using WP at a beginner level.

On the other hand, I don’t see any point in doing so. How hard is WP to install? Not very. Odd server configurations can make it more difficult, but all of the common problems are well documented already. How hard is WP to actually use? Not very. Click Write, then write. Easy easy. Again, the features are well documented already.

But on the other other hand, this information is NOT all gathered in one spot. It’s spread and sprinkled over blogs, wikis, forums and brains. Someone should collect this information into a single, highly searchable and accesible location. The Codex comes to mind, though it doesn’t necessarily need to be the place.

Yes, everyone says “someone should…” and no one does it. I am, unfortunately, no exception this time. I don’t have the time, but I definitely would if I did. Actually, I will have the time in a few weeks or so, but hey – changing the world is hard work and takes a surprising amount of paperwork 😉

So Larry, I can’t say I see any real market for a printed WP book. Some people would buy it, most wouldn’t. If profits went to support WP itself, though, that might be different 🙂 It would be smart to gain the support and input of the community instead of alienating them in that case, though.

Podz, I haven’t bothered reading this whole thread, but I did get the picture. I am one of the hundreds who never read the posts here before just now, and I am saying something. I love WordPress, end of story. I don’t care if Cybil (or Sybil… or Truddi Chase for that matter) writes the thing. NuclearMoose could be a 300 pound sumo wrestler from Sweden for all I know, and it wouldn’t matter. You guys have done a spectacular job here.

Shallow folk care about image – “oh, this dev’s a trans-gendered cross-dressing homophobic midget with herpes” is a deal-killer for them (I’m not calling anyone a herpes-riddled trans-gendered cross-dressing homophobic midget, it’s just an example off the top of my head), but many of us don’t. Shallow folk care about a buck more than they care about “right,” but many of us don’t. Shallow folk resort to personal attacks when they have nothing stronger to make their points with, but many of us don’t.

Am I coming through? I wrote too much….

In short, I say let Larry write his book and keep the money. If he can write a decent WP book after such short experience, power to him. I won’t buy it. If he violates copyrights, bend him over and do him dry (sorry, crude analogy there, but apt given the legal system these days). If he decides to do the smart thing (in my humble opinion) and write the book with the profits donated to WP (or even other F/OSS projects related to it), then I’ll buy the thing whether I need it or not.

In closing (the length, sorry, I can’t help it), I don’t need any flak for this post. Don’t like my opinion? Fine 🙂 I suspect I’ll be happier if I ignore what remains of life in this thread, at least until certain folk start acting their ages instead of their shoe sizes (nope, not going to be more specific than that – if this sentence insulted you, then you’re probably one of those folk, and you know it; don’t get mad at me for pointing it out).

Did anyone count how many grammar rules I’ve senselessly broken here?

The main reason that the instructions on the codex page will not work as expected when “upgrading” to 1.5 from 1.2.2 (or any version previous to that) is because the templates that worked in 1.2 are rarely directly transferrable to 1.5 without edits. So, following the instructions on that codex page will destroy your 1.2 template, even though the rest of the instructions are applicable to a 1.5 “upgrade”.

If you’re just using an unmodified default WP 1.2 template though, no worries at all – after 1.5 is installed, just change your theme to “Classic” and all will be well 🙂

NOTE: I haven’t personally tried the upgrade instructions to get from 1.2 to 1.5, so I cannot say for sure that it will work. In theory, it should (except for the templates, as noted above). But hey, that’s why you backed up your database before you started, right? 😉

I can’t speak for anyone else, but my way works fine for me 🙂 I use a program called WinMerge to find out what files have changed, then I post them on my page on the codex, along with any notes (like occasionally running “upgrade.php” to update the database structure, or logging out and in to update the cookies used, obvious bugs or problems with that particular build, etc.).

In other words, use it if you like, there’s no worries about re-uploading all of the files every night (unless you’ve done some custom modifications to the WP sources like I have) – pick a method that works for you 🙂