Este plugin no se ha probado con las últimas 3 versiones mayores de WordPress. Puede que ya no tenga soporte ni lo mantenga nadie, o puede que tenga problemas de compatibilidad cuando se usa con las versiones más recientes de WordPress.

Mavis HTTPS to HTTP Redirection


This plugin was developed to solve a redirection issue when navigating from a secured checkout page back to
a non-secured page (or page that you need to have as non-secured—possibly because of non-secured
external links, etc.)

For example, a user comes to your wordpress e-commerce site, locates an item, then navigates to your
secured checkout page. Now the customer, realizes there is something else they need, and instead of clicking
a Continue Shopping link, then click a top category link. Since the customer is in a secured session, wordpress
put the secured protocol on all the links including that category. Now the customer navigates to that
category, but they are still in a secured page session. Now this category page is displaying improperly because
of some external links that did not translate properly into the secured session. Customer is now upset, thinking
that the site design demonstrates the level of incompetence of the shop owner and questions the shop owner’s
integrity to fulfill the customer’s order, so the customer in a behavior of discuss, rapidly leaves the
shop owner’s site and that customer becomes a non-customer!

This plugin resolves this issue by redirecting all non specified checkout (and other non-secured pages)
back to a non-secured page counterpart.


We make honorable mention to anyone who helps make Mavis HTTPS to HTTP Redirect a better plugin!


Support is provided at You will require a free account on

Please contact or visit the above forum with questions, comments, or requests.



To instal this plugin, follow these steps:

  1. Download the plugin
  2. Extract the single file mavis.php
  3. Extract mavis plugin to the /wp-content/plugins/ directory as new directory will be created identified as ‘mavis-https-to-http-redirect’
  4. Activate the plugin through the ‘Plugins’ menu in WordPress, identified by ‘Mavis HTTPS to HTTP Redirection’
  5. Change your site to use pretty permalinks from the ‘Permalinks’ menu in WordPress
  6. Set your secured page on the ‘Mavis HTTPS/HTTP Redirection’ admin page from the ‘Settings’ menu in WordPress
  7. If you have more than one secured page, separate each page name using commas (e.g. checkout,confirm)


Please do not be afraid of asking questions?

(There are no stupid or dumb questions!)


24 de febrero de 2017
If you had only 1 page that needed to be redirected to non-https, as I read the instructions, you have enter in all of the pages that are to remain https: That's backwards.
3 de septiembre de 2016
I installed and in few minutes it was working exactly the way it should be and the way i wanted. All you ned to read carefully the instruction.. Thats it.
3 de septiembre de 2016
I tried so hard to do this for several days before finding this plugin. It is amazing and exactly what I needed! Thanks to the developers for making it happen. And I hope you guys come back to the plugin so it won't go out of date!
3 de septiembre de 2016
Thanks you so much! I just needed my checkout pages secured with my SSL's, but then all of the other pages would want to be https as well, all of them with that annoying yellow triangle. This plugin fixed it all with magic! Thanks!
Leer todas las 6 reseñas

Colaboradores y desarrolladores

«Mavis HTTPS to HTTP Redirection» es un software de código abierto. Las siguientes personas han colaborado con este plugin.


Traduce «Mavis HTTPS to HTTP Redirection» a tu idioma.

¿Interesado en el desarrollo?

Revisa el código , echa un vistazo al repositorio SVN o suscríbete al registro de desarrollo por RSS.

Registro de cambios


  • fixed Deprecated: has_cap
  • switch from separate database table to wp option variable of


  • updates for wp version 4.3


  • Fix a bug that prevented displaying secured page list in text field properly


  • Fix a bug that prevented plugin from being activated when php short definition is not defined.


  • Filtered code from NOT being executed during an admin session. Apparently, one user reported that it does?


  • Added support for multiple secured page checking
  • Forced redirect of secure page tags back to a secured page session if session is unsecured


  • Created