Ray

I had the same issue. It was easily resolved by creating the non-existent cache directory /wp-content/plugins/wp-scss/cache/

I tried this:

function fix_encoding_or_something_else( $record , $submited_data , $qs_cf7_data_map , $type , $template ){
   //manipulate the record as you see fit ($record)
   //$record = urldecode($record);
	$urldecode = $record['url'];
	$urldecode = urldecode($urldecode); 
	$record['url'] = $urldecode;
   //dont forget to return the $record
   return $record;
}

but the url is still encoding everything

I have what I think to be a similar issue. I need to send and API key that contains “%” and a username that contains “@”. These characters are being encoded and received by the remote server as “%25” in replace of “%” and “%40” in replace of “@”. How can I prevent the encoding with the above filter?

This appears to have resolved when updating the plugin to 1.2.1

• This reply was modified 7 years, 7 months ago by Ray.

@bamadesigner — thanks for the reply Rachel. If you cannot replicate the checked terms bug in your dev environment, let me know and I will set you up with admin access to our staging location. Best of luck!

We are eager to upgrade to 4.7 due the exposed security vulnerabilities….but I am patiently waiting for this update…Cant update Core until this plugin is compatible!!!

Every term is checked on every post after upgrade. I cant uncheck them.

I figured out that is not because I am using ajax, but rather because I am using a custom template to display all the products. I can get the event to fire if I add (.single_add_to_cart_button) to the jQuery click() function on line 534 of woocommerce.php, but it is not capturing the product data in the datalayer — everything is just undefined.

SAME
PI Status
23.239.13.127 Error

Your site cannot connect to the Kebo API, this will prevent the plugin from functioning as expected. You are welcome to ask for help on the support forum.

Feed: Sorry, the Tweet data is not in the expected format.

Hopefully Kebo gets us a fix soon…so we dont have to burn time customizing feeds after switching plugins

I was able to add “wp-content/plugins/nextgen-gallery/” to the Secure Filters in the HTTPS plugin settings, and that seems to have fixed the issue. All content is now being loaded securely and properly.

As for the second question regarding “Charge Amount”—disregard. I was able to create a “Total” field that can be integrated with First Data. Any help with the first question—recurring payment options will be greatly appreciated!