Posted 11 months ago #
If you're using WP in MultiSite mode
and wp-recaptcha 3.1.3
and contact-form-7
and this plugin (contact-form-7-recaptcha-extension)
Then you undoubtedly have issues.
Please read this post -> http://wordpress.org/support/topic/doesnt-save-keys-for-wordpress-305?replies=7#post-2193926
For how to fix it NOT saving keys, and having to be done per-site instead.
Also, note my fixes.. :)
http://wordpress.org/extend/plugins/contact-form-7-recaptcha-extension/
Posted 11 months ago #
Oh... thanks for the hint. I will have a look to the post.
Can I add your fix for the problem to my plugin according to your description? As long as the fix for the keys is not implemented in the original wp-recaptcha plugin it could be a help...
Kind regards
Andre
Posted 11 months ago #
OK OK...
I see the problem.
The ONLY problem I see is in the wp-admin/options.php. They only say update_option(...) without checking the multi-site stuff and using update_site_option(...). Otherwise the whole settings API would work.
Instead if they would use update_site_option(...) there everything would work fine. Because the function checks for multi site and uses update_option(...) if no multi site is detected.
Do you think we should file a bug? Then it could get fixed in the next WordPress version.
For the meantime I don't know if I should write a lot of code to do what the settings API does only to keep backwards compatibility... What do you think?
Kind regards
Andre
I don't think there's a bug in WordPress. It's just that WordPress hasn't implemented an interface for site-wide options that is similar to per-blog options. It's more a lack of a feature.
It looks like the author of wp-recaptcha intended to use *both* site-wide options and *per-blog* options, with per-blog options overriding any site-wide options, if any.
What this means is that it's not just a matter of detecting multisite and using update_site_option instead of update_option; it's a matter of having two sets of options pages: one in the Network Admin which uses update_site_option (if multisite) and one under the regular Settings menu which uses update_option (for both multisite and non-multisite). But update_option vs. update_site_option is only part of the story. The CGI form interface for site settings is what's really missing from WordPress.
Posted 11 months ago #
But the form interface for the settings does not depend on the options stuff. It only creates a table with the settings in it that I want to show to the customer. There are methods called that I have to implement with the code that creates the parts of the form. So there I am totally free as a developer.
The magic happens after the selected settings are committed by the customer. And I agree with you that there is a feature missing where I can tell the wp-admin/options.php that the committed stuff is for the site or the blog. That's the only missing piece, I think.
As a solution I would, in a first step, change the behavior of my settings to be saved for the blog only. In a second step I would implement a posibillity to set some site options and request a feature for the next WordPress version that would implement such a method for everyone. Something like: send the form to options.php and save it for the blog or send it to site_options.php and save it for the whole site. So you can use the the same settings api for the forms and only have to decide which kind of settings you would like to save.
If blog options override site options or the other way around depends on the developer of a plugin...
What do you think?
Kind regards.
Andre
Yeah I think that feature request as you described it would be great.
My guess is there's probably an issue on file already.
But otherwise, plugin developers definitely need this feature.
Posted 11 months ago #
ok... the fix is done...
will be up in a minute. hope it works. please report back...
Posted 9 months ago #
doesn't work for me - i get an error about neither of the dependent plugins being activated.
Running:
CF7 - 2.4.6 - Network activated
reCAPTCHA - Huyz edit - Network activated
CF7 reCAPTCHA extension - 0.0.10 - tried both network and site-based activation, both gave same error re dependencies
Posted 9 months ago #
Hi godkid,
thank you for the hint. Can you tell me which version of WordPress you are using?
Kind Regards
Andre
Posted 9 months ago #
Hi Andre - thnx for the quick response on this - for ease going to copy what I had and add the WordPress version:
Running:
WP - 3.2.1 - Multisite (folders NOT sub-domains)
CF7 - 2.4.6 - Network activated
reCAPTCHA - Huyz edit - Network activated
CF7 reCAPTCHA extension - 0.0.10 - tried both network and site-based activation, both gave same error re dependencies
** this is the setup for a site other than the one listed in my profile by the way **
Posted 9 months ago #
Hi,
thanks for the additional information.
I have some issues with the multisite stuff of wordpress. At the moment I work on a major restrukturing of the plugin what will take at least a week. With that I will setup a MS instance for myself and target the MS issues.
Is it possible for you to wait until I got this finished or do you need the plugin urgently. I would try to create an intermediate version for you.
Kind regards
Andre
Posted 9 months ago #
I can wait - thanks for the quick and warm responses
Posted 9 months ago #
You are more than welcome...
I thought about sending you a test version before the next release if it is ok. But I am not sure about that at the moment.
Posted 9 months ago #
would prefer to wait for a release candidate - but thnx for the consideration
Posted 4 months ago #
Hello Andre,I'm Hello Andre, I'm to use reCaptcha with contact form 7 on a Multi Site installation and the plugin doesn't seem to be working. I get an error that contact form 7 and Contact Form 7 reCAPTCHA Extension is not activated.
Can you offer any help?
Posted 3 months ago #
Bump. Installed it on a fresh WP3+ Network. Did Network Activate and do not see it on the individual sites.
You must log in to post.
