WordPress.com Forums » Topic: Other problems related to widget page problem http://en.forums.wordpress.com/topic/other-problems-related-to-widget-page-problem WordPress.com Forums » Topic: Other problems related to widget page problem en Tue, 21 May 2013 06:40:26 +0000 http://bbpress.org/?v=1.1-alpha-2539 timethief on "Other problems related to widget page problem" http://en.forums.wordpress.com/topic/other-problems-related-to-widget-page-problem#post-847221 Thu, 22 Mar 2012 22:20:15 +0000 timethief 847221@http://en.forums.wordpress.com/ It seems you have already posted into the Staff questions forum on this issue > http://en.forums.wordpress.com/topic/various-problems-related-to-https-widget-page-workaround?replies=1

]]> henkvansetten on "Other problems related to widget page problem" http://en.forums.wordpress.com/topic/other-problems-related-to-widget-page-problem#post-846832 Thu, 22 Mar 2012 14:40:44 +0000 henkvansetten 846832@http://en.forums.wordpress.com/ The "solved" widget page problem, with an improvised workaround using HTTPS instead of HTTP, has left several other problems open. I'd like to get some attention for this. I feel that instead of this workaround, WordPress should implement a more structural solution asap. If only because otherwise, new users will keep running into the same old broken widget page problem and lose a lot of time before finding the workaround.

Indications there are still unsolved structural problems:

(1) Since using the HTTPS workaround for the WordPress admin pages, all my browsers on all my devices flooding me with warning screens about non-matching WordPress certificates. This happens for example when from a post edit page I try to open a post preview page.
(2) Since using the HTTPS workaround, most WordPress admin pages work painstakingly slow. Just now (on my fast desktop PC with a fast DSL line) on my main Dashboard page clicking a menu item took a full eight seconds to get any reaction at all, and several more seconds for the new page to render completely.
(3) My WordPress login page works, but still looks very weird and messed-up (will post a screenshot if you need one). I guess this is because the HTTPS workaround works only after login, so it won't work for the login page itself.

I think all these things are related, and I want to (kindly) ask the WordPress people to find and install a real solution for all this, instead of the improvised HTTPS workaround. Thanks!

]]>