persian cat
Forum Replies Created
-
Forum: Fixing WordPress
In reply to: Export generates "Error 500 – Internal server error"Hi, I”d like to add to my recent post an important update: Just by chance, I was offered today a migration “to a new server platform”, when I logged into my web-hoster (STRATO). I agreed and after a single mouse-klick and virtually 4 seconds time the migration was completed by STRATO (sorry, hope nobody blames me for making advertisement for them: I”m sure there are many others and equally good hosters around).
When I again used the Tools/Export command from my WP blog, the transfer was suddenly about 4 times faster than before. Before this migration, transfer always started with 16kb/s and continiously went down during the process to 4kb/s, before it stopped and produced the truncated XML-files mentioned in my post before. The total download time for the truncated files (ranging between ~ 200kb and ~900kb) was around 1min 40sec.
Now, it transfered a 992kb XML file (complete blog with all posts and with the final </rss> tag at the end) within 20 sec.So for now, the problem with truncated exports seem to be solved. I don”t know, however, what happens if in the future my blog size will be larger, a couple of Mb or so. It might be, that even with this higher transfer rate I will run into the same problem again, as soon as the total download time exceeds 1min 40 secs.
Forum: Fixing WordPress
In reply to: Export is not exporting entire blogI”d like to add to my recent post an important update: Just by chance, I was offered today a migration “to a new server platform”, when I logged into my web-hoster (STRATO). I agreed and after a single mouse-klick and virtually 4 seconds time the migration was confirmed by STRATO (sorry, hope nobody blames me for making advertisement for them: I”m sure there are many others and equally good hosters around).
When I again used the Tools/Export command from my WP blog, the transfer was suddenly about 4 times faster. Before the transfer started with 16kb/s and continiously went down to 4kb/s before it stopped and produced the truncated XML-files mentioned in my post before. The total download time for the truncated files (ranging between ~ 200kb and ~900kb) was 1min 40sec.
Now, it transfered a 992kb XML file (complete blog with all posts and with the final </rss> tag at the end) within 20 sec.So for now, the problem with truncated exports seem to be solved. I don”t know, however, what happens if in the future my blog export increases further to a couple of Mb. It might be, that even with this higher transfer rate I have now the same situation comes back as soon as the total download time exceeds 1min 40 secs.
Forum: Fixing WordPress
In reply to: Major Export problemsI”d like to add to my recent post an important update: Just by chance, I was offered today a migration “to a new server platform”, when I logged into my web-hoster (STRATO). I agreed and after a single mouse-klick and virtually 4 seconds time the migration was confirmed by STRATO (sorry, hope nobody blames me for making advertisement for them: I”m sure there are many others and equally good hosters around).
When I again used the Tools/Export command from my WP blog, the transfer was suddenly about 4 times faster. Before the transfer started with 16kb/s and continiously went down to 4kb/s before it stopped and produced the truncated XML-files mentioned in my post before. The total download time for the truncated files (ranging between ~ 200kb and ~900kb) was 1min 40sec.
Now, it transfered a 992kb XML file (complete blog with all posts and with the final </rss> tag at the end) within 20 sec.So for now, the problem with truncated exports seem to be solved. I don”t know, however, what happens if in the future my blog export increases further to a couple of Mb. It might be, that even with this higher transfer rate I have now the same situation comes back as soon as the total download time exceeds 1min 40 secs.
Forum: Fixing WordPress
In reply to: Export generates "Error 500 – Internal server error"I recognised same problem and therefore I would not rely on the XML backup generated with the Tools/Export command. I now use to test first by repeating the Export several times and then compare the sizes of the XML-files generated.
With a 110 post WordPress blog (+ about 200 kbp images) the xml file-sizes varied between 271kb up to 908kb. The 908kb variant was generated 3 times (out of 23).
When I opened this 908kb file (using WordPad, that shows it in a nicely structured manner), I found that only those few ones had the correct </rss> tag at the end and also contained all posts.
All the other XML files (with smaller file sizes) appeared to be truncated, contained only the earlier posts and did not had the </rss> tag at the end. This indicates to me that it is a problem appearing randomly during download of the XML-export file, but not a systematic disability of WordPress to export XML-backups above a certain size. I guess that the larger the blog is, the more likely it is that the XML-backup will be truncated.
Somebody sugegsted that the transfer from the server is timed out. I also recognised in the Download-Window, that the transfer rate dropps before transfer ended of the truncated files.Therefore, the only advice I can give is to repeat the export as often as possible, than use keep the XML-file of the largest size.
This one will have the largest part of your blog. To make sure if it has indeed the complete blog, open it in wordpad and check if it contains the </rss> tag at the very end.Forum: Fixing WordPress
In reply to: Major Export problemsI recognised same problem and therefore I would not rely on the XML backup generated with the Tools/Export command. I first used to test repeated Exports and compare their files-size. With a 110 post WordPress blog (+ about 200 kbp images) the xml file-size vbaried between 271kb up to 908kb. 908kb was generated 3 times (out of 15).
When I opened the 908kb file (using WordPad, that shows it in a structured manner)just word or any other editor), I found that only those few ones had the correct </rss> tag at the end and also contained all posts.
All the other XML files (with smaller file sizes) appeared to be truncated, contained only the earlier posts and did not had the </rss> tag at the end. This indicates to me that it is a problem appearing randomly during download of the XML-export file. Could indeed be that the transfer is timed out. I also recognised in the Download-Window, that the transfer rate dropped before transfer ended of the truncated files.