Ruty, et al.,
It was suggested by the Beavers that this problem was a local problem that was difficult to solve without access to it. That is too true. Furthermore, that it might be a problem with the server, and not with Beaver creations, also, as it turns out, true. Beaver support was good.
Here is what I sent to Ben this morning. Like with there being no one cause for a headache, this may or may not be of help.
—–
Localhost issue understood. I was curious if anyone had a similar issue in WAMP.
So after that post (the one made yesterday by me), and from Billy’s prior email, I put the site live (it’s only a blank WP test). That would totally eliminate WAMP as a cause, and also discount some other possible causes. Please understand that WAMP was a straight out of the box install specifically for WP. Save for increasing file sizes allowed it was not modified at all.
When put online, the issues went away, and this pointed the finger back to us. It was also notable that the issue was not present on the LAN server, which is where WAMP was installed. While it still could be other issues, WAMP was becoming the prime suspect.
Per Billy, I installed DeskTopServer. Gotta tell ya, I hated that one. Billy liked it, but to me it was somehow too “easy”, or something to that effect. Past experiences with “too easy” most often meant that it was great for novices, but when you wanted to hack a difficult problem there were roadblocks. So DeskTopServer went away, and XAMPP appeared in its wake.
There were, up until now, no problems with XAMPP, and that makes WAMP the villain in this little story.
One last thing on that, Ben.
You may not like making recommendations as to a localhost product, but I would bet you that many, perhaps most, of your users are not experts in configuring a localhost, and certainly not up to extensive troubleshooting of an issue such as we were having, and that would include yours truly. Since we did not wanker with it, a cold, unmodified WAMP install should have been just fine on a Win 7 host and network. That it failed is not good at all, and I would bet you a cup of coffee, and your choice of a roll, that this is not unique to us. As the acknowledged experts it might be great if you could do some testing of localhost programs and eliminate bad ones from the get-go. This could save users a lot of time, eliminate some support tickets, and make your product sing a happy song, which can’t be bad for sales.
—–
My final take is that a good localhosting program will work out of the box without any modifications, and WAMP did not pass that test.
Sorry for being verbose,
Nga
