Now we are going to express our dissatisfaction with a tool without revealing the company that developed it.
When you work with WordPress you often want to do it without having it visible for everyone. Or you maybe want to have it as subdomain in an own folder. Later on, when the website is going to be moved to the root folder which is accessible for everyone, problems can come.
This change can be done manually or with some locally developed migration tool. We actually experienced one of them. By some reason we installed a WordPress site with the 1-click function created by a web host. The installation as subdomain was successful but migration to the root was not.
We investigated rules and limits and our WordPress site was small enough for successful migration. But unfortunately it was not successful. The 1-click function affected the website speed. It was really unbelievably slow. And the interesting moment in this case was how technicians at this web host were not able to identify the problem directly. They behaved like in some guessing game. Cache or some code in .htaccess file? Their explanation was this:
Creating a new .htaccess file, only containing the basic WP code could be a good idea.
The question is then: Why does their 1-click function for WordPress create all that code that is not needed in .htaccess file then? Who can explain that?
So we must ask ourselves: Why develop something if we are not able to handle it properly? However, this incident might have been one of some unique cases but it still feels like something developers should think about.