cdturri

>>So presumably WP ignores all SQL errors then?

>Nope.

The there must be a bug on the post module or it might be ignoring errors from an insert only?

At last… I fixed [hacked] the issue. I removed the NOT NULL attribute for the pinged and post_content_filtered fields on my POSTS table. Defore doing that I checked that I had this set to NULL on all my posts (SELECT distinct post_content_filtered FROM tb_posts t;) therefore I decided that changing the WP schema was safe. Could anyone check on their installations if they have these two fiels set as NOT NULL by default? I guess this was something that didn’t export correctly on the backup I did of my previous WP DB.

BTW, MySQL sucks! It should be possible to set the query logs fromt he client but you can only do it from the command line and you need to restart the server.

On the other side I would have expected WP to catch SQL errors. So presumably WP ignores all SQL errors then?

OK, I am getting close. I enabled a full query log on MySQL and got the INSERT that WP is sending and guess what, it fails if you try to run it manually. The error is:

Field ‘pinged’ doesn’t have a default value

Checking why this is failing now…

Checked the POSTS table and indeed is set to auto increment.

Trying to save a new post shows this on the Apache access log:

[03/Sep/2006:21:58:12 +0100] “GET /wp-admin/post.php?action=edit&post=460 HTTP/1.1” 200 12179

460 is the next valid new post ID on my POSTS table so nothing wrong there. HTTP code 200 is OK so no problems there either. Editing and saving an existing post works with no problems though. So the issue is with new posts. Something strange is going on here…

No, I don’t see any errors on my Apache log. My permalinks are working fine.

I am seeing the same issue after migrating my Blog to a new install running PHP 5.2.0RC3-dev and Apache 2.2.3 under Windows. I see no errors on the PHP or Apache logs. There are no errors shown on the screen either (my php.ini has the error reporting level to E_ALL). Clicking on “Save and Continue Editing” results on the following message being shown: “Filed under: Uncategorized — @”. I have verified that no records are being saved to the POSTS table.

I am currently trying with the PHP.INI settings but seeing other people having the same problems seems like it’s something else.

Any ideas?

If the date & time of the posting is in the future, it will marked as publish but it won’t be shown on your BLOG until that date and time is in the past…

TinyURL is a good alternative solution:

https://tinyurl.com/

Here is a solution for those who can’t switch to PHP4:

https://www.ads-software.com/support/topic.php?id=10957

Beyond Compare: Good soft to compare two files and see the difference. Also if you use Textpad it has a good compare files feature.

??

Don’t know those, but I use SPG and I am very happy with it.

Your page doesn’t validate on XHTML:

https://validator.w3.org/check?uri=http%3A%2F%2Fvictoria.ithium.net%2Findex.php&charset=%28detect+automatically%29&doctype=%28detect+automatically%29&verbose=1

Also, when you go to the December archive the Calendar dissapears. I like the design but fix it in FireFox, IE sucks!

Hi guys,

The problem I was having was due to other issue. After doing what this post says the issue with the comments was resolved.

Thanks!