1.2 Beta errors

options does not save on one of my blogs. ??

On the post.php page I’m getting this error:

Database error: [You have an error in your SQL syntax. Check the manual that corresponds to your MySQL server version for the right syntax to use near ‘ORDER BY meta_key,meta_id’ at line 4]
SELECT meta_key, meta_value, meta_id, post_id FROM wp_postmeta WHERE post_id = ORDER BY meta_key,meta_id

WHERE post_id = … ORDER BY
… no post_id?

any one solved this?

i get an error on 1.2 beta when i press the back button in the browser coming from the rss 2.0 feed as displayed in the browser – for the entire site.
mod_rewrite is enabled and using the back button from the rss feed link from the archives menu, for example, is fine.
it appears to try to go back to https://www.example.com/index.php instead of just https://www.example.com when pressing back and causes what looks like a strange apache error followed by a bunch of whacky characters. (from the rss link found on the homepage https://www.example.com/)
any ideas?
also i have the date problem in RSS too – and i ran both of those scripts listed in the Wiki … still i get a very strange pubdate – something from 1969. both scripts ran successfully, and at least said “done”

My default post category has also been changed upon running the update.

I can’t goto the “uploads” section in the admin. Says the wp-content file isn’t set correctly permission wise, but it is.

Not sure what the deal on this is but when I click publish it just hangs … I don’t believe it is a server issue because when i pull the blog up in a seperate window the post is actually on the page, but it still is hanging in the other window.
Just an FYI in case it is an error with others.

Are you pinging any sites?

yes but i was before with 1.02 and didnt have similar problems.

i get the same error as atmasphere
Fatal error: Call to a member function on a non-object in /usr/www/users/jgreene/wp/wp-includes/class-xmlrpc.php on line 760
when posting or editing (nightly build 29-04). all the edits are saved though despite the error. strangely enough it only happens with 1 blog, not with the other.
both blogs are pinging

https://rpc.weblogs.com/RPC2
https://rpc.technorati.com/rpc/ping
https://ping.blo.gs/
https://rpc.blogrolling.com/pinger/
https://ping.rootblog.com/rpc.php
https://api.my.yahoo.com/RPC2

additionally the blog with the error does not display edit/delete option for the default links (no tickbox either).

Definitely strange … no new nightly for 5/1 yet so I guess we just wait it out for now.

it only seems to happen with edit.php.
i just posted something and it was fine.

I posted about this in a different thread, but probably should have posted it here:
In admin-functions.php (file date 4/30/04 9:37 p.m.)
Line 211:
WHERE post_id = $postid
maybe should be
WHERE post_id = ‘$postid’
I was getting the same SQL error warning that’s mentioned in the first few posts in this thread. This fix made it go away, but I don’t know if it’s a correct fix.

When a nightly comes out, do we just upgrade our current versions? If so, how so?