(Optional) Configure the form, including minimum age, and all messaging for the form on settings>>>Easy Age Verifier

That needs changed to

(Optional) Configure the form, including minimum age, and all messaging for the form by clicking on "Age Verifier>>>Age Verifier"

From my inbox: >firstly I really like your plugin, the only issue I have is it opens on other pages after the person has already verified.Not on the various wines but on things like about/legal in the top menu.... >The site is http://ift.tt/1PyoP09 where they must be 18 or over... >How can I stop this? >Cheers >Rick Carter

dadesignsa on "[Plugin: Easy Age Verifier] Doesn't work in Explorer 11" http://ift.tt/29svA6O On Explorer 11 on Windows 10, the fields can't be filled in. Clicking in a field seems to activate a blinking text line somewhere way below the fields and typing numbers in does nothing. I can't include a link because the site is in development. http://ift.tt/29p1IEH via WordPress › Support » View: Plugin Support http://ift.tt/29svFYe July 07, 2016 at 09:33PM

Need to set the cookie to \ so it covers the entire domain instead of the current page
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie

I've tried this on two different WP installations and it simply doesn't show up at all. It used to work fine and stopped working with the last update that now uses the Customizer. Am I missing something?

This will keep the plugin from enqueuing the JS and CSS files when they're a user has already verified their age.

Currently, the verifier form displays via an ajax call in Javascript. Instead of doing it this way, it would be a lot cleaner to load the form content via an output buffer before sending the data to the JS. This would make the template run a lot more smoothly, reduce server calls, and improve the form's overall reliability.

This section tells users to save their custom template in the wrong directory:
https://github.com/alexstandiford/easy-age-verifier#custom-verifier-template

the template should be saved in eav/default.php

I have errors such as

Undefined index: page in wp-content/plugins/easy-age-verifier/easy-age-verifier.php on line 159

due to a missing test whether the key page does exist in the following function:

function redirect_to_customizer(){
  global $_GET;
  if($_GET['page'] == 'eav-options'){
    wp_redirect(admin_url().'customize.php?autofocus[section]=eav_section');
    die;
  }
}

Please add an isset($_GET['page']) or something else. Thanks!

See: https://wordpress.org/support/topic/bug-non-existence-of-key-in-_get/#post-8844429

Recent support message:

Looks like a great plugin but I can’t seem to save the

Display the age verifier in the customizer
activates the age verifier in the customizer

setting. I load the setting page in the customizer and I can check the box. When I check the box I get a preview of the age verification and it looks great. I click the save and publish button everything looks as it should but when I back out of the customizer and test the plugin it is not working. When I go back into setting the

Display the age verifier

setting is not checked. All other setting are fine and saving as they should. It looks like it is not being saved in the database maybe? Have you seen a bug like this and do you have any suggestions?

I am using the uncode template if that matters.

Garrett

Garrett's issue was that he didn't understand why the customizer setting wasn't saving, but everything else was. To resolve this, I need to either remove the reset function or add a note that clarifies that the setting resets.

https://vimeo.com/202638210

Add a z-index to the age-verify class

Need to have a feature that allows users to generate a debug file from the dashboard.

Some info I need:

1. All verifications, and if they passed or failed
2. The HTML markup of the form, rendered from the JS
3. A list of all installed plugins
4. Age Verifier version
5. WordPress version

Please work from the 2.05 branch, not master as that is the current working copy, and master is what's currently released.

When a fresh install of the plugin is installed, several of the settings are displaying in the form fields, but are not displaying in the actual verifier. This is because the verifier is looking to the database for this information, but the actual data hasn't been stored yet.

The proposed solution is to simply save the default values in the database if they're not already set.

Please work from the 2.05 branch, not master as that is the current working copy, and master is what's currently released.

https://wordpress.org/support/topic/is-it-posible-to-remove-underage-message/#post-9089455