bdoga

tdawg2

The Browser Blocker Plugin puts the power in your hands to control what browsers(versions) can access your website content and which ones cannot. For the browsers(versions) that you block, the user has control over the splash screen that their clients receive. There is a “simple” mode for those who just want to block some browsers with the default settings, and there is an “advanced” mode for those who want to have a little more control over what is displayed to their clients.
If you would like to see more of our plugins feel free to drop by the <a href="http://www.macnative.com/development/browser-blocker/" rel="nofollow ugc">Browser Blocker plugin page</a> or the <a href="http://www.macnative.com/" rel="nofollow ugc">Macnative.com Homepage</a>.
This plugin utilizes the <a href="http://chrisschuld.com/projects/browser-php-detecting-a-users-browser-from-php/" rel="nofollow ugc">Browser detection library</a> that was built by <a href="http://chrisschuld.com/" rel="nofollow ugc">Chris Schuld</a> A big thanks to him for his major contribution. 
A big thanks to Vistaicons.com for creating the Web Browsers Icon Set that is used with the plugin. <a href="http://www.vistaicons.com/" rel="nofollow ugc">Follow the link to see more of their icons</a>.
Another big thanks to Yusuke Kamiyamane for the use of many of his Fugue Icon set icons throughout the Plugins Administrator, <a href="http://p.yusukekamiyamane.com/" rel="nofollow ugc">please visit their homepage</a>.

Browser Blocker

Browser Blocker allows you to pick and choose which browsers(versions) can access your web page and which ones are given a blocked splash screen.

LingoJon

Firefox allows a user to drag and drop an image from their desktop into the TinyMCE editor (Visual), where it is immediately converted to base64 code, which is undesirable as the image file size is much larger than the equivalent added by the standard WordPress method because…
<ul>
<li>base64 images are larger than binary images</li>
<li>WordPress would normally have ‘crunched’ the image to give various different sizes, including a thumbnail, all smaller than the original</li>
</ul>
To prevent this, “TinyMCE remove-base-64-image” contains a small piece of javascript that checks the TinyMCE editor every 1.5 seconds and immediately removes any base64 image found, also displaying an alert message:
‘Sorry, dragging images into the editor is blocked as it will cause your webpages to load slowly, please use the “Add Media” button!’.
If you manage multiple WordPress sites this plugin will save you time checking if your clients are unwittingly crippling their page downloads.
A <a href="http://www.pixeltiger.co.uk/program.html" rel="nofollow ugc">PixelTiger</a> plugin.
<h3>Developer Notes</h3>
I am aware that using setInterval to detect a freshly dropped image is not ideal from a theoretical standpoint as most of the time it’s unnecessary and it could impact TinyMCE performance, albeit by a tiny amount. If you check the TinyMCE forums you will find another suggested method: <a href="http://www.TinyMCE.com/forum/viewtopic.php?id=5090" rel="nofollow ugc">Disable drag/drop facility</a> (last post by Arvind, 2012-07-09) which involves modifying tiny_mce.js to detect the DOMNodeInserted event then deleting the new image node. While this seems sound, if you try to locate the ‘_addEvents function section’ mentioned you’ll find it’s not in tiny_mce.js version 3.5.8-wp. I also searched the TinyMCE documentation for a way to bind this event in a plugin, but no joy there either.
So if you’re a javascript genius feel free to make this plugin redundant with a DOM checking one. Until that time arrives I hope people find this useful.

TinyMCE remove-base-64-image

"TinyMCE remove-base-64-image" immediately removes images dropped into the TinyMCE editor with Firefox and alerts the user with the reason.

Browser Blocker vs TinyMCE remove-base-64-image