ba66e77

Thanks, Michael, but still no joy. The records are in the table (as show below) and the guid is correct. I ran REPAIR TABLE and it ran clean, but no change.

I’m using a non-standard table prefix. Is it possible that the browse script is still using the default prefix?

mysql> select id, substring(post_content,1,25),post_parent, guid, post_type from molly_posts;
+—-+——————————+————-+————————————————————————-+————+
| id | substring(post_content,1,25) | post_parent | guid | post_type |
+—-+——————————+————-+————————————————————————-+————+
| 2 | This is an example of a W | 0 | | page |
| 3 | What better way to start | 0 | https://smithweb.us/mollysBlog/?p=3 | post |
| 4 | | 3 | https://smithweb.us/mollysBlog/wp-content/uploads/2007/05/pict0038_2.jpg | attachment |
| 5 | | 3 | https://smithweb.us/mollysBlog/wp-content/uploads/2007/05/pict0038_2.jpg | attachment |
| 6 | | 3 | https://smithweb.us/mollysBlog/wp-content/uploads/2007/05/pict0038_2.jpg | attachment |
+—-+——————————+————-+————————————————————————-+————+
5 rows in set (0.00 sec)

Groovy. Thanks

Doh! It took building my own upload script to find the problem, but it turns out that while uploads were allowed, the upload_tmp_dir setting in php.ini had no value, so the process was failing. Once I set that, everything started working.

Thanks, samboll, but still no joy. There has to be some trick I’m missing, but I’m not seeing what it is.