Title: [Plugin: Content Warning] js disabled browser
Last modified: August 20, 2016

---

# [Plugin: Content Warning] js disabled browser

 *  [fjavier](https://wordpress.org/support/users/fjavier/)
 * (@fjavier)
 * [14 years, 2 months ago](https://wordpress.org/support/topic/plugin-content-warning-js-disabled-browser/)
 * So what happens if a visitor is accessing the site with a JavaScript disabled
   browser?, is there a workaround for it?
 * [http://wordpress.org/extend/plugins/content-warning-v2/](http://wordpress.org/extend/plugins/content-warning-v2/)

Viewing 4 replies - 1 through 4 (of 4 total)

 *  Anonymous User 9105421
 * (@anonymized-9105421)
 * [14 years, 1 month ago](https://wordpress.org/support/topic/plugin-content-warning-js-disabled-browser/#post-2663615)
 * If someone visits with a browser that has JavaScript disabled then there will
   be no warning. For the rest it has no consequences for viewing the site.
 * People by example using Firefox + NoScript plugin will not notice content-warning-
   v2.
 *  [Jay](https://wordpress.org/support/users/phyrax/)
 * (@phyrax)
 * [14 years, 1 month ago](https://wordpress.org/support/topic/plugin-content-warning-js-disabled-browser/#post-2663637)
 * Currently this is not implemented, an easy way around would be definitely to 
   disable JavaScript. I’ll look into this, though the first thing that comes to
   mind is hook onto a page/content/post filter and overwrite what you would see….
   I have it in my head, just don’t know how to say it 🙂
 *  Anonymous User 9105421
 * (@anonymized-9105421)
 * [14 years, 1 month ago](https://wordpress.org/support/topic/plugin-content-warning-js-disabled-browser/#post-2663640)
 * Curious to what you can come up with to make a Content Warning that will work
   without any use of JavaScript. Will keep following the development.
 * 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](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.
 *  Thread Starter [fjavier](https://wordpress.org/support/users/fjavier/)
 * (@fjavier)
 * [14 years, 1 month ago](https://wordpress.org/support/topic/plugin-content-warning-js-disabled-browser/#post-2663650)
 * 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?

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘[Plugin: Content Warning] js disabled browser’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/content-warning-v2_9968c9.svg)
 * [Agy - Age verification for WooCommerce](https://wordpress.org/plugins/content-warning-v2/)
 * [Support Threads](https://wordpress.org/support/plugin/content-warning-v2/)
 * [Active Topics](https://wordpress.org/support/plugin/content-warning-v2/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/content-warning-v2/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/content-warning-v2/reviews/)

 * 4 replies
 * 3 participants
 * Last reply from: [fjavier](https://wordpress.org/support/users/fjavier/)
 * Last activity: [14 years, 1 month ago](https://wordpress.org/support/topic/plugin-content-warning-js-disabled-browser/#post-2663650)
 * Status: not resolved