All or nothing?

Just to let you know…the latest version (1.10, uploaded last week) will let you select multiple categories of posts to export (default is all posts). Hope that is useful to you.

If the plugin is useful to you, please add a review. If you have any other suggestions, let me know here in a new topic.

The plugin doesn’t do any ‘framey’ things. It just queries the database, then outputs each post’s title, date, and content, each in individual H-tags.

Once the file is generated, you should see a dialog box to allow you to open/save the generated content. If you select Open, it will use your default browser to open a new window. All you should see is each post, with it’s title, date, and content.

If you save the file, you can decide where to save it; the file name is a combination of the current date/time plus a few characters in front, it is an HTML file by default. Images have minimal formatting/css, and should be flush left. Each generated element (title, date, content, image) has a class attached to it so you can add your CSS (the classes used are on the Settings page).

So, unsure how you are getting a frame, and the menu/theme stuff. Have you tried saving the file to your local drive, then opening from there? Perhaps your browser is showing new/clicked links in a frame? (I use FireFox, and have new links opened in a new tab.)

If you look at the generated file’s source code, you shouldn’t see any of your theme/menu/etc.

Let me know the results of your testing.

I usually test the plugin on a smallish site of mine, and it always works well. But I can see with a ‘large’ site (lots of posts) that there might be a timeout issue.

So I tested the plugin with a ‘large’ site, and it did indeed not finish. That indicates a timeout error that is not caught. So I added the following code to the top of the blog-to-html.php file

ini_set('max_execution_time', 300); //300 seconds = 5 minutes

And ran it again on the ‘large’ site, and all worked as designed (I got the save/open dialog box at the end).

So, if you could, try adding that code line to the top of the blog-to-html.php file on your site (somewhere just before the first php code line; not in a commented area).

Let me know how it works for you. If it fixes the problem, then I’ll add it to the next version.

Thanks for your patience and help.

Perhaps your browser settings are set to automatically save the file, rather than giving you the Save As / Open dialog box? The file that is created is called blogexport*.html ; perhaps a search for that file pattern will find the file?

If you use Firefox, this article explains how to change what happens when the Save As / Open dialog box is ‘called’: https://support.mozilla.org/en-US/kb/change-firefox-behavior-when-open-file .

When the process runs, there is no visual indication that something is happening, other than a possible/probable ‘spinner’ on the browser’s tab (like you get when a page is loading). Only when the file is completed do you get the open/save as dialog box.

If your settings are set to automatically save, then you might not see that dialog box. But the blogexport*.html file should be somewhere on your computer.

After many hours of testing different things, I think that I have fixed the problem with the exported output appearing on the screen, rather than the Open/Save As dialog box. I still need to do some more testing on a few different sites, though.

And, I added a new feature that allows you to have the generated HTML file emailed. Thought that might be useful. Plus the 1.10 update that allowed selection of specific categories of posts.

So, I need to do some final testing. Have another commitment tomorrow that will take most of the day, but hope to have the 1.20 version uploaded tomorrow (Fri) evening.

Thanks for your patience.

Hmmm…possibilities include a server process timeout, or maybe a browser timeout.

Do you know the values of PHP max_execution_time and PHP Memory Limit on your server (you can find it via your php.ini file, or using the <?php phpinfo(); ?> command in a little PHP file on your server. Might also be able to find it via your site’s host CPanel.

You could also check the error_log file in the wp-content folder to see if there is an error message.

Did you try using the email function to email the file? That might give you the whole file without having to ‘bother’ the browser waiting for the SaveAs dialog.

I’ve been thinking about a date range or record count range for the next version. But the timeout and memory settings and any error message might be helpful to determine what the problem is.

Thanks for your patience.