Not found – Sorry, but you are looking for something that isn't here.

Synology CS407 is a network attached storage (NAS) device, i.e. a hard drive, so I’m not sure how updating the firmware for the disks would kill your posts but not the WordPress installation/admin panel – since you would expect a problem with the hard drive to kill everything or nothing, not half and half.

Joe

Correct the CS407 is a NAS device. And the device is working fine in other areas (File sharing, Synology admin pages, fotostation etc.).

The question is: What could make the WordPress behave like this, and how can it be fixed?

Is it:
1. File failure
2. Missing PHP extension
3. Missing SQL connection
4. Error in SQL database
5. Other?

I have read some other posts regarding the same behaviour, but there is no real conclusion. Some are caused bad programming, but this is not the case here as the WordPress was running smothly before upgrading the CS407 firmware.

If I was in your position, the first thing I would do is to use a tool like PhpMyAdmin, check your WordPress database and look inside the wp_posts table to see how many records it contains and if your actual posts are still there.

If your posts are still present, you should be able to see multiple records under the post_content field, containing your blog article content.

If the posts are not there, then something has corrupted your WordPress database and you will need to restore it from a backup – you have a database backup right?

If the posts are there but the control panel is not seeing them, then we’ve eliminated the possibility that it is a missing database data problem but an issue with reading the data or something else. In technical issues like this, troubleshooting is essentially an exercise and process of elimination – you rule out all possibilities until you find the source of the problem.

Ideally if you can find someone you trust to go into your blog directory and take a proper look at the database and wordpress script.. at the moment it is like a car mechanic telling the customer to check here and there blindly over the telephone when the mechanic could probably spot the likely problem by taking a brief look under the hood.

First step should be to check your database and ensure the actual posts are there or if they have been corrupted/wiped for some reason – the next step will be determined according to what you find in this first check.

Joe

Thank you for using time on this Joe.

I am not so familiar with what is under the hood of WordPress, so I appreciate your time spend here. I am a programmer myself, mainly in “C” and some Javascript. I have made a few changes to the mainpage in my blog by own hand.

1. My posts are present in SQL wp_posts ??
2. SQL post_content has my actual written text ??

From my point of view I wonder what could have happened when updating the CS407 firmware, causing this error.

Btw. After checking the SQL, I updated WordPress to 3.0.2., in case any files were corrupted, but that did not help.

I hope that you will continue your guidance.

Regards
FlummerDK

It’s good to know that your posts have not actually been lost – that would have been a much worse situation, so that’s a positive on that front.. though it does deepen the mystery of why WordPress is not detecting the posts.

Are you using a custom theme? If so, try reverting to the default WordPress theme and then check your site again.

If that doesn’t make any differences or provide any clues: then de-activate all your installed plugins, and check your site again if it makes any difference or throws any different errors.

While we are at it, could you provide some hosting information, such as if you are on Windows or Linux based OS, the type of web server setup you have and if you’re using any ‘seo’ type plugins or doing any url rewriting (to make index.php?xyz look more like /blog/xyz/).

If you can include a link here to your website, that might also help provide a clue.

Joe

Once again thank you for using time on this Joe. ??

I am also very puzzled with this..

1. I have tried running the default theme, and the error is still present.
2. By testing my used plugins, I found that “Yet Another Photoblog” version 1.9.12 triggered the error. When updating to version 1.9.24, my site works again.

Excellent!! (Yes I am jumping up and down of joy)

What have I learned here:
I still wonder how and update of my CS407 (Linux), could cause this error.
Next time I need to search for errors in a WordPress installation I will start with disabling Theme and Plugins (I had already tried changing to the default theme at the beginning..).

Joe: Thank you from my heart (and my wife!).

Regards
FlummerDK

That’s okay, you’re welcome – just glad to hear everything is resolved. ??

Joe