badabingbreda

Cookie Connector for (Beaver) Themer
<h3></h3>
<h3>Plugin description</h3>
Cookie Connector for Beaver Themer is an unofficial addon-plugin for the popular Beaver Themer plugin. It allows you to read cookie-values using the Beaver Themer Connector and use Conditional Logic to hide/show seperate nodes (modules, columns and/or rows) using cookie values.
Cookie Connector also allows you to create cookies using an AJAX call. For security measures you will need to write the AJAX yourself, but an example file on how to do that can be found here, in the example folder:
<a href="https://github.com/badabingbreda/cookie-connector-for-themer/" rel="nofollow ugc">https://github.com/badabingbreda/cookie-connector-for-themer/</a>
Using the Cookie Connector 
You can display the Cookie Connector wherever you’d normally insert it as a string, using either the connect or insert button.
Using the Conditional Logic filter 
Because cookies have a certain validity, it can’t return a value when the cookie isn’t there or has become invalid. The Conditional Logic filter has an extra parameter to set a default value for whenever it doesn’t return anything. Setting this parameter return that value whenever it doesn’t exist.
Writing cookies values 
Cookies are written before any headers are written to the visitor’s browser. The downside to that is that cookies can only be read when the visitor’s sends a request, since they are sent over WITH the request. This means that you can’t write a cookie’s value and immediately read that cookies new value, within a single run of a page-call.
To work around that, cookies can be written using an AJAX call. 
“Cookie Connector for Themer” enqueues a script that registers the <code>cookieConnector</code> object, which handles the security and sending of requests. 
Let’s consider the following html-code that is used in a HTML module:
<pre><code><a href="javascript:cookieConnector.set( 'setmycookie' , { cv: 'my cookie value' , valid: 3600 } );">Set cookie value</a>
<a href="javascript:cookieConnector.set( 'unsetmycookie' );">Unset cookie value</a>
</code></pre>
The first parameter is the <code>actionname</code> that is going to be called in the PHP script, so in this example (see below) the part after ‘wp_ajax_’ and ‘wp_ajax_nopriv_’. 
You can also add an extra, optional, third parameter <code>debug</code> that will add a console.log dump of the response, should you need to know what’s being answered:
<pre><code><a href="javascript:cookieConnector.set( 'setmycookie' , { cv: 'my cookie value' , valid: 3600 } , true );">Set cookie value</a>
<a href="javascript:cookieConnector.set( 'unsetmycookie', {} , true );">Unset cookie value</a>
</code></pre>
Adding the PHP code to create/change/delete the cookie 
Clicking the link wil trigger an AJAX call that will set a cookie on the visitor’s device, if their browser allows it.
On the server-side, you will need to add one or two ajax callbacks, depending if the call can be made without being logged in.
<pre><code><?php
 add_action( 'wp_ajax_setmycookie' , 'callback_setmycookie' );
 add_action( 'wp_ajax_nopriv_setmycookie' , 'callback_setmycookie' );
 add_action( 'wp_ajax_unsetmycookie' , 'callback_setmycookie' );
 add_action( 'wp_ajax_nopriv_unsetmycookie' , 'callback_setmycookie' );

 function callback_setmycookie() {
 // first check if this ajax call is
 // done using the script belonging to the installation
 //
 if( ! check_ajax_referer( 'cookie-security-nonce' , 'security' ) ) {
 wp_send_json_error( 'Invalid security token sent.' );
 wp_die();
 }

 // Check if visitor has accepted the cookies from Cookie Notice plugin
 // If you're using another plugin, you should write your own check here
 if ( !function_exists('cn_cookies_accepted') || !cn_cookies_accepted() ) {
 wp_die();
 }
 if ( !defined( 'DOING_AJAX' ) ) define( 'DOING_AJAX' , TRUE );

 // set your cookie name here
 $cookie_name = 'mylanguage';
 $default_validity = 60 * 60; // = 60 minutes

 // try to get the cookie_value
 $cookie_value = isset( $_GET['cv'] ) ? $_GET['cv'] : false;
 // try to get the cookie validity period. If not default to default validity
 $cookie_valid = isset( $_GET['valid'] ) ? $_GET['valid'] : $default_validity;

 // if the action is setmycookie we need a cookie_value (cv) because else it will fail. Check for it and return an error if there isn't one.
 if ( ! $cookie_value && $_GET['action'] == 'setmycookie' ) {
 wp_send_json_error( array( 'success' => false, 'error' => '402', 'message' => 'cookie not set, no value given. ( cv )' ) );
 }

 // check action parameter
 // UNSET mycookie
 if ( 'unsetmycookie' == $_GET['action'] ) {
 setcookie( $cookie_name , 'unset value' , time() - 1 , COOKIEPATH, COOKIE_DOMAIN , isset($_SERVER["HTTPS"]) );
 wp_send_json( array( 'success' => true, 'message' => "Done unsetting cookie '{$cookie_name}'." ) );
 } else if ( 'setmycookie' == $_GET['action'] ) {
 setcookie( $cookie_name , $cookie_value , time() + $cookie_valid , COOKIEPATH, COOKIE_DOMAIN , isset($_SERVER["HTTPS"]), true );
 wp_send_json( array( 'success' => true, 'message' => "Done setting cookie '{$cookie_name}' to value '{$cookie_value}' with validity $cookie_valid seconds." ) );

 }
 wp_die();
 }
</code></pre>
It is advised to use wp_send_json with a ‘success’ parameter (either true or false) so that you check it in your javascript and add actions after sending the cookieConnector() command, for instance a reload of the page or forwarding to an url that you received from the server based on the click. 
For instance, the javascript below will try to create the cookie. When successful it will display an alert on the browser and reload the page after 1.5 seconds.
<pre><code><script>
 function cookie_trigger() {
 jQuery.when( cookieConnector.set( 'setmycookie', { cv: jQuery( '#selectlanguage' ).val(), valid: 5 * 60 }, 1 ))
 .done( function( data ) {
 if ( data.success ) {
 alert( data.message + '\r You can now safely shut down your browser, restart and visit this URL. This selectbox will reflect the last cookie value.' );
 setTimeout( function() { location.reload(); }, 1500);
 }
 });
 }
</script>
</code></pre>
Special thanks 
Thanks to 10UP for creating this github action for easy deployment. https://github.com/marketplace/actions/wordpress-plugin-deploy
version history
1.3.1 
Forgot to update readme.md (this file). Small fix for isset because it’s not the value that we want (could be falsy) but return if the cookie is set.
1.3.0 
Rewrite of plugin using Autoloader. Fixed isset error.
1.2.0
Removed admin_notice so that plugin can be used without Beaver Themer and Beaver Builder too (scripts), for ajax calls.
1.1.0
Updated the version because it works on WP 5.4 too
1.0.1
Updated example code
1.0.0
Initial release (January 18th, 2019)

Cookie Connector For Themer

Description
Easily connect ACF fields in Beaver Themer. No need to remember the fieldnames, easily select from the dropdown. It returns all fieldnames, across all fieldgroups.
Easy ACF Connect for Themer also supports ACF Fields on the current post, another post, user_id, tax_termid or even from your ACF Options pages.
Select the Easy ACF Connector… Then simply select the fieldname.
Using the Conditional Logic filter
Easy ACF Connect for Themer also supports adding conditional rules using ACF Fields on the current post or from your ACF Options pages. For that select either “Easy ACF Field” or “Easy ACF Option Field”.
Supported fieldtypes:
<ul>
<li>color-picker</li>
<li>date-picker</li>
<li>date-time-picker</li>
<li>email</li>
<li>file</li>
<li>flexible content</li>
<li>gallery</li>
<li>group</li>
<li>image (array, url or image ID)</li>
<li>link</li>
<li>message</li>
<li>number</li>
<li>page link</li>
<li>password</li>
<li>post object</li>
<li>checkbox</li>
<li>radio</li>
<li>range</li>
<li>relationship</li>
<li>repeater</li>
<li>taxonomy</li>
<li>select</li>
<li>text</li>
<li>textarea</li>
<li>time_picker</li>
<li>true_false</li>
<li>url</li>
<li>user</li>
<li>wysiwyg</li>
</ul>
Please note that field support means that it will return the ACF-value as a variable (object, array, string or number). It’s up to the module to handle the returned variable.
Adding support for more fieldtypes in list
If you use any third party or custom fieldtypes for ACF ( which can be found on <a href="https://awesomeacf.com" rel="nofollow ugc">https://awesomeacf.com</a> ) you can add those using a filter in your function.php:
<pre><code>add_filter( 'easy_acf_accepted_acf_field_types' , 'my_custom_add_acf_field_types' );

/**
 * Callback that adds one or more fieldtypes to the the easy_acf_accepted_field_types filter
 * @param {array} $fieldtypes array with name->value, label->value pairs
 * @return {array}
 * @since 1.0.0
 */
function my_custom_add_acf_fieldtypes( $fieldtypes ) {
 $new_fieldtypes = array(
 array( 'name' => 'custom_fieldtype' , 'label' => 'Custom Field Type' ),
 );

 $fieldtypes = array_merge( $fieldtypes , $new_fieldtypes );
 return $fieldtypes;
}
</code></pre>
Conditional Rules for 3rd party fieldtypes
There is currently no support or way to extend for 3rd party fieldtypes using the conditional rules. This means that you won’t be able to pick fieldtypes based on the type. Use the conditional rules provided by Beaver Themer instead, but you will need to enter the fieldname manually.
version history:
v1.1.5
bugfix: added permission_callback to rest request
v1.1.4
added checkbox fieldtype to Beaver Builder conditional rules, it was missing.
v1.1.3
added all remaining fieldtypes (flexible content, group, repeater, page link, post object, relationship, taxonomy, user)
v1.1.2
added Conditional Logic settings
v1.1.1
added image-size on image fields, tweaked the code, changed way to test for acf 4/5, fixed save_format/return_format for acf 4/5, added textdomain and .pot file
v1.0.0
image and gallery field support

Easy ACF Connect For Themer

Description Easily connect ACF fields in Beaver Themer. No need to remember the fieldnames, easily select from the dropdown.

Cookie Connector For Themer vs Easy ACF Connect For Themer