wp-sqlsrv

Hello, We have issues with removing or otherwise editing sample content (The Hello world post ect) We can change them in the dashboard without getting any sort of error but when we check, the posts stand unmodified. Just as we can't delete them. Dashboard reports they have been placed in the trash, but they remain on the frontpage. As far as we could test, content we made ourselves has not been affected by this problem. Wordpress is running on a Windows 2008 server with IIS 7 and SQL server 2005. Thanks in advance.

I have this same issue. The post can be removed by editing the SQL DB directly, but that is obviously not the way we want to go. I tested making another post and then comparing them in the SQL DB and I can't see any difference that would cause the Hello World post to be safe from edits and deletes. Chris

curious... are either of you using any kind of caching (apc, wincache, wp caching, a cache plugin, etc) ?

Our latest attempts were on a fresh install with no plugins activated.

we are having the same problem. wordpress 2.9.2 works, but neither 3.0 nor 3.0.1 let you edit your posts. it doesn't even let you edit pages. at times it will let you edit them with something short, like dddd or test, but you it is very random. and it won't let me add copy/paste text. it doesn't give me any errors, it just refreshes the page when you click update, and does not save the change. We need a fix soon. Did about 10 clean installs on different servers, different databases, different names, even different IPs

I wonder if anyone is even reading this? I mean, Anyone in the development team? Very frustrating. Is there an ETA on 3.0.2? or when a patch will come up that will fix the problem editing pages/posts on 3.0.1 ?

Yes, we are reading this and are looking into it. We will release a patch for the bug as soon as possible.

Ok ... so here seems to be the problem. In lines 268-270 of wp-includes/wp-db/translations/sqlsrv/translations.php You will see a function call to verify_update() after translations for the query have been ran. This method is the culprit for the problems you guys are experiencing. Commenting out: $query = $this->verify_update($query); should fix what you guys are experiencing. Now let me explain a little further about the verify_update() method and what it does and why it is broken. It is possible that an UPDATE query would have its SET values changed during the translation process if that value contained SQL... for example: UPDATE wp_posts SET post_title = 'SELECT * FROM wp_posts LIMIT 1' WHERE post_id = 1; The translations may change the value data to SELECT TOP 1 FROM wp_posts...in UPDATE/INSERT case we don't want that to happen...as in these cases the user is wanting literal SQL to be shown in the blog post... so verify_update() and verify_insert() were created to check that the values of the query pre and post translation are the same. Currently the implementation for this method, as you have experienced, is broken and it is doing a poor job of parsing out those values correctly. In the Hello World post it happened because of the comma in the post content which verify_update() ended up parsing as two different values. More than likely you guys are not writing literal SQL in your post content or titles ... but if you are, you may see some breakage until I get this fixed, otherwise commenting out the verify_update() call should suffice. Sorry for the issue and thank you for reporting it. We do appreciate it and we are trying to make the patch as robust as possible.

I performed the edit just a while ago by commenting out the suggested line. I was then able to make edits to existing posts as well as delete the "Hello World" post. Thank you for the workaround! Updating my other posts.

Thank you so much for the workaround. that fixed the problem for us.