kgrondell

That fixed the error which is great thanks but you can’t toggle to code anymore and if you try to add an image to a wysiwyg field it jumps to the top and adds it to the post content.

I am having the same issue. If I deactivate the plugin it’s fine but if the plugin is active the error causes buttons like adding feature image, setting post status or post release date to fail. It essentially makes it impossible to edit a post. Any insights into a fix would be greatly appreciated.

JS error:

post.php?post=1111&action=edit:1308

Uncaught TypeError: Cannot read property ‘indexOf’ of undefined
at HTMLDivElement.<anonymous> (post.php?post=1111&action=edit:1308)
at Function.each (load-scripts.php?c=0&load[]=jquery-core,jquery-migrate,utils,moxiejs,plupload&ver=4.9.1:2)
at a.fn.init.each (load-scripts.php?c=0&load[]=jquery-core,jquery-migrate,utils,moxiejs,plupload&ver=4.9.1:2)
at a.fn.init.$.fn.init_wysiwyg (post.php?post=1111&action=edit:1279)
at HTMLDocument.<anonymous> (post.php?post=1111&action=edit:1269)
at i (load-scripts.php?c=0&load[]=jquery-core,jquery-migrate,utils,moxiejs,plupload&ver=4.9.1:2)
at Object.fireWith [as resolveWith] (load-scripts.php?c=0&load[]=jquery-core,jquery-migrate,utils,moxiejs,plupload&ver=4.9.1:2)
at Function.ready (load-scripts.php?c=0&load[]=jquery-core,jquery-migrate,utils,moxiejs,plupload&ver=4.9.1:2)
at HTMLDocument.K (load-scripts.php?c=0&load[]=jquery-core,jquery-migrate,utils,moxiejs,plupload&ver=4.9.1:2)

That’s essentially the error although it looks like only part of what I got back.

Essentially your server is trying to use CURL to connect to salesforce. The problem is your server only supports TLS 1.0 and salesforce now requires TLS 1.1.

On my server I checked the openSSL and it was a sub 1.0 (.98 I believe) version and openSSL did not support TLS 1.1 until something like 1.13b and our host was unwilling to update openSSL so I had to write a template that rendered the correct web to lead code on the page and disable the plugin.

It’s a shame because the the plugin is fine. Once we migrate their sites to a more modern server we will move the forms back to the plugin.

Salesforce updated the requirements for TLS. I was having this issue and went into the code and had it spit out the salesforce request. What comes back is not an error in the traditional sense so the way this plugin is coded you get no error but if you spit out the request it will tell you that TLS 1.1 or higher is required.

If this turns out to be your issue you’ll have to update openSSL on the server.

To see if this is your issue find the following lines in salesforce.php
”
$result = wp_remote_post( $url, $args );

// Test broken submit
//$result = new WP_Error( ‘broke’, __( “I’ve fallen and can’t get up”, “my_textdomain” ) );
”

Add print_r($result); above “// Test broken submit”

So now it looks like:
”
$result = wp_remote_post( $url, $args );
print_r($result);
// Test broken submit
//$result = new WP_Error( ‘broke’, __( “I’ve fallen and can’t get up”, “my_textdomain” ) );
”

Submit a form that is having issues. It should tell you your error. At least it did for me.

Be sure to delete “print_r($result);” after your test.

• This reply was modified 8 years, 2 months ago by kgrondell.

Salesforce updated the requirements for TLS. I was having this issue and went into the code and had it spit out the salesforce request. What comes back is not an error in the traditional sense so the way this plugin is coded you get no error but if you spit out the request it will tell you that TLS 1.1 or higher is required.

If this turns out to be your issue you’ll have to update openSSL on the server.

To see if this is your issue find the following lines in salesforce.php
”
$result = wp_remote_post( $url, $args );

// Test broken submit
//$result = new WP_Error( ‘broke’, __( “I’ve fallen and can’t get up”, “my_textdomain” ) );
”

Add print_r($result); above “// Test broken submit”

So now it looks like:
”
$result = wp_remote_post( $url, $args );
print_r($result);
// Test broken submit
//$result = new WP_Error( ‘broke’, __( “I’ve fallen and can’t get up”, “my_textdomain” ) );
”

Submit a form that is having issues. It should tell you your error. At least it did for me.

Be sure to delete “print_r($result);” after your test.

• This reply was modified 8 years, 2 months ago by kgrondell.
• This reply was modified 8 years, 2 months ago by kgrondell.

@dwinden I ran into this issue on a client site. Your solution is correct “disable the Filter Suspicious Query Strings in the URL setting in the System Tweaks section on the Settings page” works like a charm. This post saved me some time. Thank you.