Title: J.Smith's Replies | WordPress.org --- # J.Smith [ ](https://wordpress.org/support/users/jsmith-1/) * [Profile](https://wordpress.org/support/users/jsmith-1/) * [Topics Started](https://wordpress.org/support/users/jsmith-1/topics/) * [Replies Created](https://wordpress.org/support/users/jsmith-1/replies/) * [Reviews Written](https://wordpress.org/support/users/jsmith-1/reviews/) * [Topics Replied To](https://wordpress.org/support/users/jsmith-1/replied-to/) * [Engagements](https://wordpress.org/support/users/jsmith-1/engagements/) * [Favorites](https://wordpress.org/support/users/jsmith-1/favorites/) Search replies: ## Forum Replies Created Viewing 3 replies - 1 through 3 (of 3 total) * Forum: [Themes and Templates](https://wordpress.org/support/forum/themes-and-templates/) In reply to: [[Twenty Eleven] [Theme: Twenty Eleven] Bug Report: Custom Link Colour – garbage in HTML](https://wordpress.org/support/topic/theme-twenty-eleven-bug-report-custom-link-colour-garbage-in-html/) * Thread Starter [J.Smith](https://wordpress.org/support/users/jsmith-1/) * (@jsmith-1) * [14 years ago](https://wordpress.org/support/topic/theme-twenty-eleven-bug-report-custom-link-colour-garbage-in-html/#post-2682453) * I’ve realised that the garbage css code in HTML was exactly what I wanted my links to look like. * I’ve added the above css code to style.css in my child theme, and voila! It worked! * This definitely looks like a bug to me. Not sure if it has been taken care of in WP 3.3.2. No desire to dig throught the code either – sorry about that! * Best regards, John Smith * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[qTranslate] [Plugin: qTranslate] Warnings about data loss](https://wordpress.org/support/topic/plugin-qtranslate-warnings-about-data-loosing/) * [J.Smith](https://wordpress.org/support/users/jsmith-1/) * (@jsmith-1) * [14 years ago](https://wordpress.org/support/topic/plugin-qtranslate-warnings-about-data-loosing/#post-2705237) * Dear andrelopes, * Please, have a look at my hack at [Qian Qin’s forums](http://www.qianqin.de/qtranslate/forum/viewtopic.php?f=3&t=3240&p=10666#p10666). * Best regards, John Smith * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[WordPress HTTPS (SSL)] [Plugin: WordPress HTTPS (SSL)] Cannot Log into Wp-Admin](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-cannot-log-into-wp-admin/) * [J.Smith](https://wordpress.org/support/users/jsmith-1/) * (@jsmith-1) * [14 years, 1 month ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-cannot-log-into-wp-admin/page/2/#post-2380526) * Hello, * I just wasted quite a few hours of my life by trying to make wordpress-https work for shared SSL scenario. * As metakong’s mentioned, the key word is: the lack of documentation. * Removing the plugin from the file system doesn’t clean up WordPress installation: * ``` mysql> select * from wp_options where option_name like 'wordpress-https%'; +-----------+---------+----------------------------------------+--------------+----------+ | option_id | blog_id | option_name | option_value | autoload | +-----------+---------+----------------------------------------+--------------+----------+ | 599 | 0 | wordpress-https_exclusive_https | 0 | yes | | 594 | 0 | wordpress-https_external_urls | | yes | | 600 | 0 | wordpress-https_frontpage | 0 | yes | | 601 | 0 | wordpress-https_ssl_admin | 0 | yes | | 596 | 0 | wordpress-https_ssl_host | | yes | | 598 | 0 | wordpress-https_ssl_host_subdomain | 1 | yes | | 597 | 0 | wordpress-https_ssl_port | 443 | yes | | 595 | 0 | wordpress-https_unsecure_external_urls | | yes | | 602 | 0 | wordpress-https_version | 2.0.4 | yes | +-----------+---------+----------------------------------------+--------------+----------+ 9 rows in set (0.00 sec) ``` * vs. * ``` $ grep delete_option plugins/wordpress-https/uninstall.php delete_option('wordpress-https_external_urls'); delete_option('wordpress-https_unsecure_external_urls'); delete_option('wordpress-https_ssl_host'); delete_option('wordpress-https_ssl_port'); delete_option('wordpress-https_exclusive_https'); delete_option('wordpress-https_frontpage'); delete_option('wordpress-https_ssl_admin'); delete_option('wordpress-https_ssl_host_subdomain'); ``` * I wish [those simple instructions from the parallel thread](http://wordpress.org/support/topic/plugin-wordpress-https-ssl-cant-log-in-to-wordpress-after-enabling-force-ssl-administration) could have been published as part of documentation: `DELETE FROM wp_options WHERE option_name LIKE 'wordpress-https%';` Somehow WPHTTPS_RESET leaves the garbage as per above select query :o(. * I have a feeling that in order to make this particular plugin to work, quite a few unstated conditions have to be met. * I am mostly into a scenario, where WordPress Address (URL) and Site Address ( URL) point at the same insecure virtual host, while shared SSL access is provided via alternative URL. * Most likely, in these circumstances, WordPress has to be deployed with multisite option, and WordPress Address (URL) should point at the shared SSL access via alternative URL. * Would it be a correct assumption?! * Back to the lack of the documentation, how option wordpress-https_ssl_host relates to WordPress Address (URL) and Site Address (URL)? * Oh, well, it could be a repeat of the previous question, sorry! * Cheers, John Smith Viewing 3 replies - 1 through 3 (of 3 total)