Impedisci a WordPress di usare HTTPS e usa semplicemente HTTP

Ci sono 2 cose che devifare.

Se stai utilizzandoil server Apache,vai su .htaccesse cambiailmotore Rewrite and RewriteBasein

 RewriteEngine On

RewriteCond %{SERVER_PORT} ^443$
RewriteRule ^(.*)$ http://%{HTTP_HOST}/$1 [R=301,L]

RewriteBase /
RewriteRule ^index.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
 

Se stai usando Nginx,qualcosa di simile dovrebbefunzionare

 server {
   listen 80 443;
   server_name example.com;
   # add ssl settings
   return 301 https://example.com$request_uri;
}
 

Questo reindirizzerebbe https a http

e vai al databasetramitephpmyadmin o qualunque cosatu usi vai a wp_optionse trovae modificai valori siteurle home da https://example.com a http://example.com

Pulisci la cachee riprova. Dovrebbefunzionare senzaproblemi. Seil sito richiede ancora SSL,controllailtuofile wp-config.phpper vedere se ha questo codice

 define('FORCE_SSL_ADMIN', true);
 

quindi cambiail "vero"in "falso"

Spero che questoti aiuti.

There are 2 things you must do.

If you are using Apache server go to .htaccess and change the Rewrite and RewriteBase engine to

RewriteEngine On

RewriteCond %{SERVER_PORT} ^443$
RewriteRule ^(.*)$ http://%{HTTP_HOST}/$1 [R=301,L]

RewriteBase /
RewriteRule ^index.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]

If you are using Nginx something like this should work

server {
   listen 80 443;
   server_name example.com;
   # add ssl settings
   return 301 https://example.com$request_uri;
}

This would redirect the https to http

and go to the database through phpmyadmin or whatever you use go to wp_options and find and change the siteurl and home values from https://example.com to http://example.com

Clean your cache and try again. It should work without problem. If the site still asks for SSL check your wp-config.php file to see if it has this code

define('FORCE_SSL_ADMIN', true);

then change the 'true' to 'false'

Hope this helps you.

Ci sono unpaio difattori qui.

Prima ditutto,potresti voler controllare leimpostazioni del sitoin wp_options (o wp_X_options seti troviin ​​una configurazionemultisito),in particolareil valore di:

• home
• siteurl

Le altretabelle che desideri controllare sono:

• wp_blogs
• wp_domain_mapping
• wp_options
• wp_site
• wp_sitemeta

Non so chetipo di sistema usateper sincronizzareil vostro DB di sviluppo conprod,ma abbiamo uno script SQL cheeseguiamo dopo aver clonato un sottoinsieme del database diprod.

 UPDATE wp_dev.wp_blogs SET domain = REPLACE(domain, "https://produrl.com", "http://devurl.com");
UPDATE wp_dev.wp_domain_mapping SET domain = REPLACE(domain, "https://produrl.com", "http://devurl.com");
UPDATE wp_dev.wp_options SET option_value = REPLACE(option_value, "https://produrl.com", "http://devurl.com");
UPDATE wp_dev.wp_site SET domain = REPLACE(domain, "https://produrl.com", "http://devurl.com");
UPDATE wp_dev.wp_sitemeta SET meta_value = REPLACE(meta_value, "https://produrl.com", "http://devurl.com");
 

Sostituisci wp_dev coniltuo database localee produrl.come devurl.com secondonecessità. Notareperò che questo cambiagli URLinterni da HTTPS a HTTP.

Infine,potrebbeesserenecessariomodificare la configurazione WP localee aggiornare queste dueimpostazioni:

 define('FORCE_SSL_LOGIN', false);
define('FORCE_SSL_ADMIN', false);
 

There's a couple of factors here.

First of all, you might want to check the site settings in wp_options (or wp_X_options if you're in a multisite setup), especially the value of:

• home
• siteurl

The other tables you want to check are:

• wp_blogs
• wp_domain_mapping
• wp_options
• wp_site
• wp_sitemeta

I don't know what sort of system you guys use to sync your dev DB with prod, but we have an SQL script we run after we clone a subset of the prod database.

UPDATE wp_dev.wp_blogs SET domain = REPLACE(domain, "https://produrl.com", "http://devurl.com");
UPDATE wp_dev.wp_domain_mapping SET domain = REPLACE(domain, "https://produrl.com", "http://devurl.com");
UPDATE wp_dev.wp_options SET option_value = REPLACE(option_value, "https://produrl.com", "http://devurl.com");
UPDATE wp_dev.wp_site SET domain = REPLACE(domain, "https://produrl.com", "http://devurl.com");
UPDATE wp_dev.wp_sitemeta SET meta_value = REPLACE(meta_value, "https://produrl.com", "http://devurl.com");

Replace wp_dev with your local database, and produrl.com and devurl.com as necessary. But notice that this changes the internal URLs from HTTPS to HTTP.

Finally, you may need to change your local WP config, and update these two settings:

define('FORCE_SSL_LOGIN', false);
define('FORCE_SSL_ADMIN', false);

Grazie Loic. Sto usando BackupBuddyper copiarei miei siti web attivie ripristinarli su WAMP. Uno dei siti ha continuato aprovare a utilizzare HTTPS.Hoprovato ainstallare un certificato su wamp locale senzafortuna.

Hoesaminato la directory delmio sito ripristinato localmentee ho rimosso la semplice cartella ssl.

Boom.Orafunzionae rimane su HTTP

Amico,eratroppofacile.Grazie ancora.

Thank you Loic. Im using BackupBuddy to copy my active websites and restore on WAMP. One of the sites kept trying to use HTTPS. Ive been trying to install a cert on local wamp without any luck.

I did look at the directory of my locally restored site and removed the simple ssl folder.

Boom. It works now and stays on HTTP

Man that that was too easy. Thanks again.

Iltuo ambiente di sviluppoe messain scena dovrebbe sempre corrispondereilpiùpossibile all'ambiente diproduzione.Non utilizzare lo stessoprotocollo è una deviazionemoltogrande chenon ènemmenogiustificatain alcunmodo.

Poiché sitratta dellatua organizzazione,installa semplicemente lo stesso certificatoneltuo ambiente di sviluppo o,seper qualchemotivo è associato a un IP specifico,generane unonuovoperiltuo ambiente di sviluppo.

Your development and staging enviroment should always match as much as possible the production enviroment. Not using the same protocol is a very big deviation which is not even justified in any way.

Since it is your organization, just install the same certificate on your dev enviroment, or if it is bound to a specific IP for some reason, generate a new one for your dev enviroment.