pstew21

and after browsing through the bug track and cvs, it appears to be solved in cvs, so wait for the next nightly if you are uncomfortable with adding the field yourself

Yeah, not sure what that means…
Do you have access to phpmyadmin?
A quick workaround is to go into the users table and just add the user_description as an extra field. It seems right now in the nightlys this is missed as a new field.
Either that, or start hacking up the code to back out the new stuff regarding user_description calls… But that’s pointless.
I’m sure it’ll get fixed down the road, but simply adding this field manually solved my issue, which sounds exactly like your issue.

It looks like user_description is new, but the install / upgrade scripts aren’t adding that column to the users table.
I just went in to the table and added it, but it should be fixed in the upgrade or install scripts somewhere.

Getting same error. Ran upgrade.php, nothing…
New, fresh install of latest nightly, same problem. Seems like a bug in the sql update string…

Any way to make the backup script just backup the posts and comment data and then allow restore of it?
Reason being, doing a clean install of WP and reimporting the posts, this would be really handy for troubleshooting, cleaning, upgrades, etc.

Ok, cleared out cache on Firefox and that seemed to fix it, wierd

Ok, really odd now, it works with Internet Explorer, but not Firefox and just my site???
Wierd…

I would like to see a changed only files package at the minimium…
That way, those that have hacked those files, can apply the hacks back to those files and just upload the changed files…
If there is a need to run an upgrade.php or something like that, provide instructions to do that as well.
As for preserving hacks, that’s why there is the plugins function now… Move all the hacks to plugins, and upgrades will go much smoother…
The upgrade / changed files package should not include the index.php or at least change the name to default_index.php or something like that so it wouldn’t overwrite your index.php that may or may not be customized and then give us the ability to view any radical code / template changes, if any…
Just my two cents.
Also, I’d suggest some sort of export option for posts and comments so one can do a clean install of WP and then reimport entries… I had to do this the hard way already due to some db changes (before I realized upgrade.php took care of it) and think an export entries and import entries back in including comments would come in handy for upgrades as well as backups and site moves…

I’d like to see a export entries option as well in WP.
Not that I plan on dumping WP, but for a couple of reasons…
One, the ability to start fresh with a clean install of WP and reimport only the entries…
Two, backup. Sure I can backup my MySQL db, but having a quick backup of all my entries in a text file that is a universal would aid in the long future of my content…
Maybe the RSS import option would do what is needed, just export all the entries to an .xml file and use the RSS import to bring them back in? Would this be robust enough??? And does anyone have templates for the RSS export of all entries with comments and all meta data?

Any chance this can be mod’d to a plugin?
How does it work under 1.2?

Been active a bit on the site and added some cool features, would appreciate any feedback to make it better…

Works fine for me. Just upgraded to RC2 from RC1. FYI

I added this to the Wiki, any requests let me know…

Works great now… BTW after edditing the files before, it worked fine… This now removes the warning SID line, and I’m sure gives some sort of additional support…

I’ve mod’ed this code to add a few features such as auto centering both horizontally and vertically based on text length and font size.
Cleaned up the code a bit and added the ability to set a margin for the box and offset for the drop shadow.
You can get my code from here…
https://www.patrickstuart.com/txt-png_php.zip
Hopefully the original author doesn’t mind, the file wasn’t creditted, I’ve added my info there, but original credit goes to who wrote this first…
As always, use at own risk, your mileage may vary…