| Post |
|
Member | aidan 8:14 am May 27, 2009
posts 8 |
|
|
Hi Oliver,
First let me thank you for cforms, I'm a long time user of this amazing plugin!
Now I'm having a problem at the moment with a form I've set up as a secure form with https. I'm getting the non-secure content warning from the browsers because the includes for cforms files (javascript, css) are using http:
I am using the https for Wordpress plugin which converts siteurl and other options to https when the page is accessed by https but yet the files included by cforms are still using http.
I have read othe topics on this issue but didn't find any solutions there (already tried reactivation).
Any help would be greatly appreciated.
Thanks,
Aidan
|
|
|
Admin
| Oliver Munich, Germany 7:27 pm May 27, 2009
posts 6001 |
|
|
have you tried the forums at wordpress.org , I think I remember seeing one or two threads there about what you need to do to make cforms https compliant.
|
|
|
|
|
Member | aidan 11:05 pm May 27, 2009
posts 8 |
|
|
Just tried searching for cforms https there but nothing uselful.
The https-for-wordpress plugin is just a very simple plugin that converts the following variables to https when the page is requested by HTTPS:
option_siteurl option_home option_url option_wpurl option_stylesheet_url option_template_url
The readme states:
This plugin will make sure that all elements on a page are SSL if the page is being accessed via HTTPS. For this to happen you must have used correct programming practices and use siteurl, wpurl, url etc where all the locations are supposed to be.
Some plugins do not correctly use this, I have already notified a few of them, but you may find some other issues, if you do, please contact me and I will research and attempt to notify the developers of the other plugins.
Is cforms using some other variables other than those listed above that would cause the http to appear, or is it hardcoded somewhere?
|
|
|
Member | aidan 12:12 am May 28, 2009
posts 8 |
|
|
I nearly lost this post because 'the answer to the math question was incorrect' – I think the question changed on me. I almost didn't notice the warning but happened to double check to see if my post was there. Managed to retrieve it with the backbutton.
I've done some digging in the code and I believe the problem comes from the way cforms stores it's own version of the root directory. I made a change on line 95 of cforms.php:
$cforms_root = $cformsSettings['global']['cforms_root'];
first I changed it to:
$cforms_root = get_bloginfo('wpurl') . "/wp-content/plugins/cforms";
However this did NOT work and I'm baffeled as to why because I expected the https-for-wordpress filter to turn the result of get_bloginfo('wpurl') into its https version. Maybe someone with more understanding can illuminate me.
So then I changed it to the relative path:
$cforms_root = "/wp-content/plugins/cforms";
and this works for me. (only works if WP is in the root, if not in the root need to modify path accordingly)
So maybe in future release of cforms this can be addressed. Why does cforms need its own setting for cforms_root when it can be derived from wpurl? Howabout just using a relative path? One thing that bugs me a bit about WP in general is the heavy reliance on full paths in URLs instead of relative paths – it becomes a major pain when one needs to move a site and requires workarounds such as https-for-wordpress when working with https.
|
|
|
Guest
| security_man 8:43 am September 22, 2009
|
|
|
i was having a similar problem, but after looking at the code you suggested changing i see that it is handled differently than you are assuming. I made sure the wordpress address in the general settings had the https:// and then reactivated the cforms plugin and clicked update settings in the admin actions menu (on the top right of all cforms pages) and that solved the problem.
hope that helps :)
|
|
|
Guest
| dndco 6:34 am September 24, 2009
|
|
|
I am in the same boat as Aidin. I would like for cforms to work with the HTTPS For WordPress plugin.
The solution provided by secure_man is the same I found on the WP forums, set the URL in the General Settning of WP to https:// However, this makes the whole site secure.
I don't want that, I only have one page that needs to be secure a checkout page, which doen't even use cforms but falls victim to security error because of the cform .js links in the header.
It sounds like if cforms did use siteurl, wpurl or url it would work or at least that is what I am gleening from the HTTPS For WordPress plugin page;
http://wordpress.org/extend/pl…..-wordpress
Thanks!
p.s.
Oliver, if you can tell me how to make the change so I can implement it in my install of cforms 11 that would work too. Unfortunatley, this not working has thrown a wrench in my project.
|
|
|
Guest
| paulsane 4:28 pm December 10, 2009
|
|
|
Has there been any movement on this as it stands its not possible to use cforms on a secure page
|
|
|
Guest
| Carl Chapman 8:25 pm January 30, 2010
|
|
|
I'm having the same kind of problem posed by needing to use HTTPS calls on only one page (credit card update) of my membership blog.
cForms is using the http call and even though I'm not using cForms on the check out page, we all know that it puts it's javascript call on every page.
I love the plugin, it is fantastic, but there has to be a work-around. Either to only call it conditionally on pages where you are using a form, or to ahve it call itself in a way that would allow for using HTTPS correctly.
Anyon find a solution?
|
|
|
Guest
| bgeissler 8:07 pm February 20, 2010
|
|
|
I made a change on line 99 of cforms.php (Version: 11.3):
//$cforms_root = $cformsSettings['global']['cforms_root']; $cforms_root = WP_SITEURL . "/wp-content/plugins/cforms";
it runs on my Site.
|
|
|
Guest
| bgeissler 8:07 pm February 20, 2010
|
|
|
I made a change on line 99 of cforms.php (Version: 11.3):
//$cforms_root = $cformsSettings['global']['cforms_root']; $cforms_root = WP_SITEURL . "/wp-content/plugins/cforms";
it runs on my Site.
|
|