Updates make a great plugin unusable

  • creativecatapps

    (@creativecatapps)


    6 years ago

    After clearing my cache and testing in a guest browser, I’m disappointed that:
    1) the age verification window appears mostly off the bottom of the screen;
    2) the background blurring that shows in the customiser isn’t on the frontend;
    3) despite having set which website to visit in the settings (yes, that’s two separate locations for one plugin in the dashboard), the page just reloads.

    Further, I did have a custom function for my client so when they logged in, they wouldn’t see the age gating. This now doesn’t work either.

    It used to be a great plugin, I will be rolling back to the previous developer’s version.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author patrickposner

    (@patrickposner)

    Hey @creativecatapps,

    thanks for your honest feedback.

    I’m sure you allready switched but let me take a little statement to your given points:

    1) This belongs to your theme or custom css. If, for any reason, your styles overwrites the positioning of the age gate it will load at the bottom.

    2) You need to enter the right class in the blur field. The “#page” placeholder only works for quality themes like the standard themes or mostly genesis themes. Hower if your theme does not have an #page element this can not work.

    3) Have you checked your console? If you have error in your JavaScript this can prevent age gate from work since most of it runs before the age gate JavaScript.

    You don’t need a “custom function” to hide this for logged in people, there is a setting for this, simple activate it.

    Next time better take the time to add a support ticket in the forum since this could help others (and me) to improve the plugin and make it better in the future.

    Nevertheless all the best and have a great day,

    Patrick

    Thread Starter creativecatapps

    (@creativecatapps)

    Hi Patrick,

    1) I checked through all the CSS when my client complained something had gone wrong and couldn’t see where it was.

    The usual problem is that the plugin CSS hasn’t been fully named-spaced, so the code can be overwritten. I couldn’t see this in the source code but did have to overwrite one of the PSAG classes.

    2) No console errors. I cleared the cache several times and put it into development mode to check, but the URL variables aren’t carrying through – showing as empty in the source code.

    I deleted the plugin and found a different solution for my client so didn’t log a ticket.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Updates make a great plugin unusable’ is closed to new replies.