emasters

I’ve rolled back CF7 to version 4.4.2 and it works as expected with reCAPTCHA. Anything newer than that generates the errors breakage outlined above.

It’s a bit complicated. We’re using the plugin in a multisite setup. It’s used by about 36 sites in the network and seems to be failing everywhere. For an example see https://testing471.classcaster.net/2017/01/25/contacting/. This is a test blog running the stock Twenty Fifteen theme. Network activated plugins include BWP reCAPTCHA (CF7 integration disabled), Google Analytics, Limit Login Attempts, TinyMCE Advanced. The only plugin activated for the site itself is Contact Form 7.

Since this seems to have cropped only recently I’m going to try rolling back to an earlier version of the CF7 plugin and see if that makes a difference.

Thanks.

I am also having this issue. No URLs turn up in the posts to Twitter.

• WP Twitter v3.5
• PHP 5.2.17
• WP 3.4.2
• cURL libcurl/7.15.5

Set to WordPress default I get nothing where the URL is supposed to be.
Set to TinyURL it simply prints “error”.
Set to is.gd it reports “Error: Please specify a URL to shorten.”
It certainly seems like #url# is not being properly handled.

And remember to not overwrite schema.php in an upgrade! ??

Here’s an example of what to add, just put this in the populate_options() function.

//ex_db_auth defaults
	'ext_db_type'=>'MySQL',
	'ext_db_mdb2_path'=>'',
	'ext_host'=>'localhost',
	'ext_db_port'=>'',
	'ext_db'=>'drupal6',
	'ext_db_user'=>'dbuser',
	'ext_db_pw'=>'dbpassword',
	'ext_db_table'=>'users',
	'ext_db_namefield'=>'name',
	'ext_db_pwfield'=>'pass',
	'ext_db_first_name'=>'',
	'ext_db_last_name'=>'',
	'ext_db_user_url'=>'',
	'ext_db_user_email'=>'mail',
	'ext_db_description'=>'',
	'ext_db_aim'=>'',
	'ext_db_yim'=>'',
	'ext_db_jabber'=>'',
	'ext_db_enc'=>'MD5',
	'ext_db_error_msg'=>'Please login using your Drupal website username and password.',
	'ext_db_other_enc'=>'$password2 = $password;',
	'ext_db_role_bool'=>'',
	'ext_db_role'=>'',
	'ext_db_role_value'=>'',

The result is that every blog created gets these defaults with the ext_db_auth plugin.

I solved my problem by adding the default values I needed to schema.php and activated the plugin site wide. Now when a new blog gets created the appropriate values get added to the options table for that blog.

unless you actually hardcode those values in the plugin itself.

I tried that but it didn’t work. Another post had suggested that it was necessary to add a set of defaults to the plugin that matched the values needed to connect to the external database, so I added the values, but they don’t show up when a new blog is created.