anyone care to comment on my (closed-invalid) ticket 592?
http://trac.mu.wordpress.org/ticket/592
i've seen a few others being told "this should be a plugin" too but in this case i just can't agree.
how can it be right to have a site with hard-coded "http://" strings in the source and then require a second layer of http redirects (on top of the existing one for site/blog/user urls) plus some link rewriting "output handler" (apache module?) to change them all again. that just sounds Wrong.
surely, also Wrong (TM) is that this isn't how regular wordpress works. you just put it on a https web server and it works.
what do you think?
Chris - you should look at the secure admin plugin I linked to in that bug report and see how it does things. It would be really easy to expand it to replace http links in your theme with https ones without having to modify core files.
hi again donncha,
yes, i've looked at the code in the plugin and in a few others too. i understand what it's doing and i agree that it could be used to work around the problem.
however, i'm more interested in solving the root cause (as i see it) and doing things 'Right' (as i interpret it! ;-)). doing so should make the code easier to maintain, easier to update (when regular wordpress gets updated) and easier to debug when there's problems - i had a heck of a time tracking all the possible apache rewrites and http redirects already in the code!
oyvinds
Member
Posted 16 years ago #
chriseveleigh is entirely correct.
donncha wants a really bad technical solution because a good solution involves "modify core files".
That "reson" is just silly.
Heh, if you had to modify core files as many times as I have had too you wouldn't be saying that.
Stay true to the core Luke!
