Group of dots (g?o?d)

You’re welcome Todd,

I’m happy to hear it is working now ??

With programming and WordPress I find the saying “A problem shared is a problem halved” is so true! You sometimes just need a second set of eyes on the problem.

Message me anytime you get any issues or feel free to skype message: groupofdots

Good luck with finishing the project.

Rog.

Hi Todd,

We use another css file so that the changes are not overwritten if you upgrade etc.

Anyway, it does not look like the addition of input[type=”tel”] is getting through but input[type=”email”] is.

Can you check the following:

1.
Are you sure the changes are uploaded to the server for input[type=”tel”] – login via FTP and download the file and check the change is in that file.

I am guite sure this is the issue as I have loaded your file general.css in my browser and looked at the code and input[type=”tel”] is not in the code.

Either you have not uploaded the updated version or there is a caching issue.

Let me know how you get on.

Rog.

Hi Todd,

The issue is this…

You’re adding the themes custom style sheet and not creating a file called ‘custom.css’ as I described so your style is not getting processed to the final page.

I opened the page in Firefox and used Firebug and I could see:

textarea, input[type="text"], input[type="email"], input[type="password"], select {
    background: none repeat scroll 0 0 #F6F6F6;
    border: 1px solid #CFCFCF;
    color: #626262;
}

I changed in Firebug to:

textarea, input[type="text"], input[type="tel"], input[type="email"], input[type="password"], select {
    background: none repeat scroll 0 0 #F6F6F6;
    border: 1px solid #CFCFCF;
    color: #626262;
}

..and it worked perfectly.

Please go through the other post referenced and try making the changes in a dedicated file called ‘custom.css’ and add as I detailed to header.php – even if your themes custom css is being processed it is being over written on file output.

Let me know how it goes or if you need any help.

Rog.

Hi Todd,

I suggested adding to custom.css not style.css, anyway – feel free to send me some code or a link and I will take a look for you.

Cheers,

Rog.

Ps. A link so I can see what is happening would be really useful.

Do you mean you are trying to make it work across multiple domains or on one domain?

If subdomains etc when you generate keys here:

https://www.google.com/recaptcha/admin/create

make sure you select “Enable this key on all domains (global key)”.

If this does not work check out my reply here:

https://www.ads-software.com/support/topic/doesnt-work-in-36

The first two steps (‘a’ & ‘b’) might be your solution.

Hi,

Contact Form 7 BWP reCAPTCHA Extension does work with WP 3.6, I think the problem is this…

a.
Click on ‘BWP reCAPT’ on the left of your Dashboard and then go to ‘General’ (or paste this into your URL: wp-admin/admin.php?page=bwp_capt_general).

b.
Make sure under the settings for ‘Hide the CAPTCHA for’ you have nothing selected. It has probably reset itself on the upgrade.

If anyone else has issues please check above and also these steps:

1.
Ensure you have installed:
– Contact Form 7
– Better WordPress reCAPTCHA
– Contact Form 7 Better WordPress reCAPTCHA

2.
For Better WordPress reCAPTCHA / BWP reCAPT make sure you have set the correct keys that can be quickly created here:

https://www.google.com/recaptcha/admin/create

3.
Disable any other CAPTCHA applications.

Overall I have noticed most errors are either caused by ‘a’ or ‘3’ listed above.

All posts here address the issue but are not consistent, for example many users will have different style.css files the line #’s will not match.

I’ll quickly post a how-to’ below, if you have any questions message back…

Basically in your style.css file find:

input[type="text"], textarea {

and change to:

input[type="text"], input[type="email"], textarea {

if you have problems with other fields you can (as discussed above) add them here like this (using password as the example):

input[type="text"], input[type="email"], input[type="password"], textarea {

The advice above to use a child theme or theme’s custom css is best as you’ll lose all changes if you update the plugin – this is useful to understand as it will help with other CSS/plugin changes ??

Your themes custom css is usually located here:
Dashboard/Appearance/Theme Options/General -> Custom CSS

I prefer to use a child/additional CSS file (custom.css) as this is easier to manage and also can be compressed.

I place mine in my themes header.php file like this:

<!-- Custom CSS -->
<link rel="stylesheet" type="text/css" media="all" href="<?php bloginfo( 'template_url' ); ?>/css/custom.css" />

*First check that you have the directory ‘css’ within the root ./ of your themes directory, if not create a directory called ‘css’ inside this directory upload your ‘custom.css’ file.*

If you are using a default/basic theme such as ‘twentyeleven’ you can create the ‘css’ directory and upload your custom.css file into it. Then it can be referenced in your themes header.php file like this:

<link rel="stylesheet" type="text/css" media="all" href="<?php bloginfo( 'template_url' ); ?>/css/custom.css" />

Place this directly below the default themes css file so it will look like this:

<link rel="stylesheet" type="text/css" media="all" href="<?php bloginfo( 'stylesheet_url' ); ?>" />
<link rel="stylesheet" type="text/css" media="all" href="<?php bloginfo( 'template_url' ); ?>/css/custom.css" />

Good luck!

Hi,

Any updates to fixing the bug, we’re also getting this error.

What is causing it? Anything we can do to our code to fix it/quick fix?

Thanks.