Page 1 of 1

Where are blog entry files stored?

Posted: Wed Dec 24, 2025 5:43 pm
by DavidC
I'd like to export all of the blog entries I've made, for backup and other usages.

They need to be in a generic .doc type format, or something else non-proprietary.

I've been looking in the various folders on my Bluehost-hosted serendipty instance and cannot find them.

I tried the Export RSS and received an error:
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at webmaster@website-4e6f3420.sun2save.com to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.
EDIT: I can get to phpMyAdmin and Exporting tables from "nevilsst_imperfect" database - but the content is jammed into the "Body" column. Is it possible to just output the plain text content of my 200+ blog posts?

Thanks

Re: Where are blog entry files stored?

Posted: Thu Dec 25, 2025 3:55 pm
by DavidC
12 views, no suggestions. Is there no way to do this, please?

Re: Where are blog entry files stored?

Posted: Thu Dec 25, 2025 6:13 pm
by DavidC
UPDATE:

I've discovered that if I select Custom and for Format: "Texy! Text" I get a flat text file.

After that I then removed all of the non-post output.

What remains is to strip-out all of the 'special characters'.
|2|What God Did & Why - (Week 2 of 2) - Thursday Devotional|1747329360|<p>What God Did & Why - Thursday Devotional (Week 2 of 2)</p>

<p>Let's explore more of the context ...</p>

<p>The Bible teaches a sequence of choices: Test - Temptation - Sin - Escalating Active Sin.</p>

Re: Where are blog entry files stored?

Posted: Fri Feb 20, 2026 4:48 pm
by onli
For the log, exporting an RSS file was a good option. One would have to check the error message that would have been logged when the 500 error occured to see what went wrong. Maybe a timeout.

And exporting the database would also work, like you tried. The text is in the body column, but you could extract it from there - for example import it all into an sqlite database and then work with that, or export the body column from there.