why something would need a tweak?
because it isn’t good, there is no other reason, short version: read this, write it down as emergency survival instruction
it is already a shame that wordpress starts it’s installation with http:// and not by default or even forced with https://
time to wake up depps! sorry, I meant devs . . . take a strong coffe or something and get yourselves back on track, you’re still in the 90’s, or hand your cepter over, you’re too old or just not fit anymore?
finding AFTER installation the site and home url in settings is just hilarious, no explanation and no highlighting of it’s importance, anyway, it doesn’t solve the problem
this tweakdefine('WP_HOME','https://ensaios.studio-one.art.br');
define('WP_SITEURL','https://ensaios.studio-one.art.br');
after instalalation doesn’t solve it, solves partially the outcome, but not the problem, some try with tweaking it in .htaccess with#Force https
RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule ^ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
#
but is the same thing, just a workaround, in order to solve the problem people have to fix the database with UPDATE wp_posts SET guid = REPLACE(guid, 'http:', 'https:');
UPDATE wp_posts SET post_content = REPLACE(post_content, 'http:', 'https:');
nobody cares until been bitten by the beast, some call us, others keep suffering, don’t know how the wp staff can sleep with their incompetence, are they mean? smiling about people getting hit by their traps?
fix it!
you guys look stupid when releasing such crap of code, you’re embarrising yourselves . . .
tweaks are confessions
hakka quote … Focused on usability and not on RTFM theories or get-yourself-programming-skills advices.

Leave a Reply