sarkfultion
⌂
›
wp-content
›
plugins
›
wplegalpages
›
public
›
js
sarkfultion
7 dreads
↑ redisq
📄
jquery.cookie.min.js
1,300 B
sarkfultion
dreads
📄
wplegalpages-banner-cookie.js
1,230 B
sarkfultion
dreads
📄
wplegalpages-banner-cookie.min.js
205 B
sarkfultion
dreads
📄
wplegalpages-public-adult-content.js
2,628 B
sarkfultion
dreads
📄
wplegalpages-public-adult-content.min.js
1,108 B
sarkfultion
dreads
📄
wplegalpages-public-popups.js
3,419 B
sarkfultion
dreads
📄
wplegalpages-public-popups.min.js
1,305 B
sarkfultion
dreads
redisq: wplegalpages-banner-cookie.js
/** * Banner cookies JavaScript. * * @package Wplegalpages * @subpackage Wplegalpages/public * @author wpeka <https://club.wpeka.com> */ (function( $ ) { 'use strict'; /** * All of the code for your public-facing JavaScript source * should reside in this file. * * Note: It has been assumed you will write jQuery code here, so the * $ function reference has been prepared for usage within the scope * of this function. * * This enables you to define handlers, for when the DOM is ready: * * $(function() { * * }); * * When the window is loaded: * * $( window ).load(function() { * * }); * * ...and/or other possibilities. * * Ideally, it is not considered best practise to attach more than a * single DOM-ready or window-load handler for a particular page. * Although scripts in the WordPress core, Plugins and Themes may be * practising this, we should strive to set a better example in our own work. */ for(var i=0; i<cookies.length; i++) { var name = cookies[i]['cookie_name'] var end = new Date(); end.setTime(end.getTime() + (cookies[i]['cookie_expire'] * 1000)) $.cookie( name, name, {expires: end } ) } location.reload() })( jQuery );
sarkfultion