People by example using Firefox + NoScript plugin will not notice content-warning-v2.
I btw myself recently chose to go back to version 2.4.6 version. I got the later versions working after your tip (http://wordpress.org/support/topic/plugin-content-warning-cwv2-wp-admin-protection-and-you?) but not long after i noticed that all the Google instant previews got 'thickboxed' making the pages look black and unreadable. Version 2.4.6 somehow does not 'thickbox' the instant previews.
I was thinking perhaps if we put the WP installation along with the contents that will be under the warning plugin into a sub-directory and create a static landing 'homepage' index into the root with a primary warning that will always display for (js or not) visitors or every time a 'home' link is clicked sitewide, then the secondary (plugin) will kick any time a visitor will be redirected from the homepage to whatever page we target with a simple enter button, the trick will be to authenticate the (js enabled) users once they pass the static warning so they don't see the secondary warning (plugin) only if they decide to enter the site thru any page other than the homepage, can that be done?
This topic has been closed to new replies.