magnumcreative

@riy you may want to look at the PRO version of W3, it has fragmented caching and is what you are likely looking to implement to resolve cart/quantity caching issues

https://www.w3-edge.com/weblog/2013/09/w3-total-cache-pro/

I am all for this option as well, or at the very least split deny and delete out as 2 separated functions.

Clients complain that they don’t want their customers notified even if the persons email has been in a pending state for 3 months.

Other clients that moderate with admin approval also complain that if they deny access they just don’t want that person to be notified regardless of how we tweak the message.

Great plugin, be better with this tweak. If I was running my own site I get the way it works and wouldn’t care…problem is trying to explain this to a marketing manager who wants things controlled at every engagement point.

Is there is an area to change the error message and if so where is it located?

The main problem is users. A user may never check their email at time of lockout, that email could go to spam or be blocked entirely by the mail server itself thus never arriving. To have a simple message saying “Error, you have been locked out of the site due to too many bad login attempts” would save us a lot of trouble.

Another aspect, one of our clients has a lot of staff who edit the site. We implement very secure passwords with these accounts which in turn means they always mess them up which results in the staff getting locked out. The staff are pretty basic in their understanding of technology and the error msg always freaks them out and we get countless emails in all caps saying “HELP WEBSITE IS DOWN OUR CUSTOMERS NEED TO CONTACT US, FIX THIS!!! WHY DOES IT KEEP HAPPENING AND ENSURE IT DOESN’T HAPPEN AGAIN!!!.

No matter how we explain why they see the error it goes in one ear and out the other since it’s just over their heads or they don’t care.

A message would help immensely ??

You could use ACF as a pretty good alternative to Verve
https://www.advancedcustomfields.com/

Ironically its the same settings in Yoast, it just won’t kick in unless I’ve published a post in to the custom posttype. The assumption of the call depends on published content, thus I had to customize the head title knowing the client may not having any content published due to the custom posttype being event/date based and they will expire and be deleted.

This is what I eventually wrote in the head to solve my issue of titles not displaying on custom posttype archive pages.

<title>
    <?php if (is_post_type_archive('careers')) {
            echo 'Current careers available at '; bloginfo('name'); }
          elseif (is_post_type_archive('seminars')) {
            echo 'Upcoming broker education seminars at '; bloginfo('name'); }
          else { wp_title(''); }
     ?>
  </title>

Ideally Yoast plugin would force the desired title regardless of a post being present in the custom postttype.