rustindy

Stupidly, perhaps, I was under the impression that run /wp-admin/upgrade.php was actually in the readme.html file included with WordPress…. lemme check… yup! There it is! It’s step number 3 under the “Upgrading” heading 🙂

So, let me ask. How many people actually skim the readme.html file for instructions on installation and upgrading before coming to the support forum and complaining about how WP1.5 broke their damn blog? Are the 4 upgrade steps maybe 2 too many for some people?

Why should 1 line of upgrade instructions be in bold? Obviously nobody reads the damn things – maybe ALL the lines should be in bold! I’ll bet that more than half the people who skipped reading (and performing) that 1 little line would not have come here for help if the forum address hadn’t been a link. It would have been too much effort to actually copy & paste or, heavens forbid, type, the address into their address bar.

Thanks for passing on your mood Bernardy 🙁

*bump* anyone? i’ve got 3 blogs with the same problem 🙁

yup, that’s the code i’m working on right now too – but in ASP, not PHP.

innereyes.com right now just queries all the blogs’ RSS feeds each time the page loads. of course, that’s the dumb way to do it, and i’ll be fixing it later tonite.

the easiest way to handle it is to control the schedule on your own end – just store an entry in a database or text file with the last time the feeds were queried. then decide whether it should have a 60 minute refresh, or daily, or 5 minutes, or whatever. compare the current time against the stored time, and if more than X minutes have passed, re-query the feeds.

alternatively, figure out how “pingbacks” work and use that 🙂 it’s the hard way, but it’s probably the best way

Yup, there should definitely be a “draft” option for pages as well as posts I think.

There’s actually an updated Exhibit 1.0d on the website – you have to dig for it though. The file name (doing a Search on the guy’s site should turn this up) is identical to the original archive name, but with a “2” added to it. So if the regular download name is exhibit10d.zip then the updated, 1.5 version would be exhibit10d2.zip. At least, that’s what I remember seeing there….

With the exception that my server is Apache 2.0.52 still, I have the identical setup and no problems whatsoever. PHP5 includes the newer authentication schemes for MySQL 4.1 (where PHP4 breaks with anything higher than MySQL 4.0 unless you either compile mysqli into it or change some 4.1 settings – or don’t put a password on your database account).

As far as I know, you shouldn’t have had to change anything at all if your setup was previously working.

As for the MySQL interface, nothing that WP uses has changed (to my knowledge). The main change is the MySQL client authentication library, and if you’re using PHP5, it should work just fine.