I have come to really not like WP, which should be renamed "Whatta Pain".
Editorial aside, I did some minor updates to my home page (added spaces, uploaded two pictures), clicked preview (they looked about right) and then clicked on the UPDATE button--and the nice little circle has been circling for about an hour now.
Last time this happened, it turned out the system froze or whatever, and all my edits were lost.
Hence the phrase, "Whatta Pain"--I had to redo them all again.
Any ideas as to what is causing this? These were minor changes in the HTML folder. Do I have to save everything/update everything every time I make every little change because this program can't handle more than one change at a time.
This really shouldn't be this complicated.
Gabriel Reguly answers:
Your prize is very low, I don't think you will get any useful answer.
What do you mean by minor changes to HTML folder?
Either you would be editing a page or a post, not editing any server folders with WordPress.
That is a FTP feature, IMHO.
Maybe you should raise the prize and rephrase your question.
Luke America answers:
Two key questions are: (1) could you access other pages on the site (and other web sites) during that timeout episode, and (2) are you on a shared, VPS, or dedicated server
If you are on a shared server, this issue may well have been caused by another site hogging CPU usage ... if it was not your own ISP.
WP is database intensive which can cause issues sometimes, particularly with shared servers. Nonetheless, it is a powerful and highly extensible development platform, CMS platform, and blogging platform.
If there's a potential pblm with it, however, I've probably experienced it at least once. Here are a few things I recommend.
1. Regularly clean and optimize your database
2. Use a site caching plugin (or at least gzip page load compression)
3. minify your css, js, and html
4. choose the right web host for WordPress
5. get a VPS or dedicated server
6. delete plugins that you are not using
7. avoid process-intensive plugins and themes
8. turn off the pingback feature to see if that helps
9. if you have access rights, set PHP's memory_limit to 128M
10. if you have access rights, use fastcgi as the PHP processor
You can research these items online for further details.
That's it for a buck.