Después de unas cuantas experiencias agridulces, finalmente me decidí por moverme definitivamente a WP Super Cache. Para dejar atrás definitivamente a mi solución anterior: W3 Total Cache.
Estas son mis razones.
Etiqueta: hosting
Virtualmin es un panel de control que permite administrar un servidor. Tener uno que fuera eficiente era importante, ya que era parte del plan al moverse a Digital Ocean. Así es como me fue en esta odisea.
El Mejorar WordPress con W3 Total Cache es una de las cosas que hay que hacer en toda instalación nueva. En este caso, yo elegí este plugin tras probar varios otros. Este fue el que mejor me funciono, debido a la forma en el cual tengo instalado WordPress. Es por ello que comparto ahora parte de mis configuraciones.
I used to be loyal to EasyPHP, but that changed once I come across XAMPP.
And all of that because I wanted to run WordPress locally. This, because I would need more computing power than I could get from a regular hosting account.
The more I work with WordPress, the more I like it. Specially because it is much more easy to set up websites and other stuff with it. Something that was not that easy with Drupal.
I was completely unaware of a feature that has been around for quite a while… one that is key for everyone and that is present in cPanel… it is the ability to have Secure Websites easily.
Back at the day when I was much more active web-wisely, having SSL or HTTPs was… painful at best, if not really expensive.
Today, while I was lurking and figuring out how to implement a nice online poll for something that is going on… I stumbled upon that.
Making a really long history short, I basically was messing up with a service called » Let’s Encrypt™» that comes embedded with cPanel. It was interesting that I could now offer secure content quite easily and without having to spend a bunch of extra bucks… what is good.
Of course, this only means that the communications between this server and you are secure… but is a nice step forward. Eventually, maybe I’ll have my hands over a private key or something, but that is a tale for another day.
Sadly for me, not all was that easy to set up in what seemed easy: Just change http to https.
Given the setup I have set here (Internet -> Cloudflare -> Private Server), WordPress started to fall into an «infinite redirection loop», and I pretty much clueless about it.
If I visited the website, without changing WP to use https instead of http, I saw half the stuff… but if I told WP to use https… it did fall into an infinite loop.
Of course, I was looking into websites like this one for answers… somewhere «promising», but at the end, only one thing or another worked out.
I was almost to give up when I finally found some light at the official WP codex, and I was surprised how much little I needed to add to fix such thing.
For the looks of it… apparently, my WP install got confused when I changed the settings and saw CloudFlare and kept trying to fix the issue, just making it worst…
But now things are much better, and kind of force SSL one way or another. What I have implemented in the other project I was messing with… and as long I do not have some kind of weird «warning», I will be a happy skonk (yeah, guess that one why).
