I have a home network that contains a mixture of devices, some of which that receive a...
Version 1.0.6 of Background Manager has been released today!
There were a few minor bug fixes based on reports from other users. I have also changed the code for the ‘Slide’ and ‘Cover’ effects as they did not account for browser windows smaller than 1024 pixels wide. This width is the ‘cut-off’ for the CSS code Background Manager uses and will not reduce background images any smaller than that, switching to centering instead. read more →
Background Manager has progressed out of its Beta stage with today’s release of version 1.0!
New features have been added, which allows you to select from a number of Transition Effects – or none at all – for the background images. This applies only to full-screen background images that change at a specified interval. The effects, in addition to the original Crossfade, include Slide and Cover. The Slide effect “pushes” the old image out of the way, whereas the Cover effect will slide a new image on top of the old one. This can be set to happen from any of the four positions on the screen. It is also possible to set the Transition Speed now, which before was fixed to 600 milliseconds – it can now be set from 100ms (0.1 second) to 7500ms (7.5 seconds). read more →
An update to Background Manager (0.9.3) has been released today, which adds support for a user-defined background opacity. In combination with the background color, this will allow the user to set a “brightness” of the background, without having to edit any of the images.
The update also addresses an issue where background overrides, either on a page, post or a custom post type, would not be honored if the plugin was set to select a random image at each browser session. It would remember only the first random image, regardless whether the current viewed post or pages used a different image set. read more →
Note! This plugin has been deprecated; it is no longer maintained nor supported.
It allows you to create multiple image sets, from which a random image is selected and displayed as the website background. The images can be uploaded from your local computer, selected from images available in your Media Library, or import them from other plugins and third-party sources.
Version 1.1.1 of the WP Flickr Background plugin has been released today. This is a minor release to bring the plugin in line with the recent WordPress version 3.1.1 release, and corrects a bug.
The (x)HTML output has also been cleaned up to pass the W3C validation for XHTML 1.0 Transitional, in part due to the reported bug where the main configuration settings would not be saved in MSIE.
As you may have noticed, I have recently updated theme of my website. I’ve also cleaned up some hardly used features, including the translation bits; It seemed to annoy people more than anything.
From working with jQuery, I remembered that their Disqus comments only get loaded once you’ve reached a certain point on the page. Looking into their solution, I figured I could implement the same method with Disqus in WordPress. read more →
WP Flickr Background is maturing nicely and we’re now at version 1.1!
This version introduces the ability to use photos from the WordPress Media Library, which means you can upload your own photos or use those from websites other than Flickr. It gives the added advantage that photos can now be hosted locally (on your own server) or on a CDN. read more →
Version 1.0.4 has been released! It is not a major release as some may have hoped, but I have had limited time to work on it in recent months – I apologize.
This version fixes some minor but annoying bugs, one of which that was introduced in the recent WordPress 3.1 release (which caused the plugin to display a background image on the admin login page). read more →
Some websites are still being hit with the infamous “w00tw00t” scans. You might see these scans in your logs as:
... "GET /w00tw00t.at.ISC.SANS.DFind:) HTTP/1.1" 400 ...
The quickest method of making sure it never reaches your webserver (and thus wasting resources like processor, disk space [log files], etc) is to use iptables, and it can be done with a one-liner like this:
iptables -I INPUT -d xxx.xxx.xxx.xxx -p tcp --dport 80 -m string --to 70 --algo bm --string 'GET /w00tw00t.at.ISC.SANS.' -j DROP
Simply replace xxx.xxx.xxx.xxx with the IP of your web server. If you want to use this for a range of IPs (ie., you’re using multiple IPs to host web servers), simply replace the “-d xxx.xxx.xxx.xxx” portion with:
-m iprange --dst-range start.xxx.xxx.xxx-end.xxx.xxx.xxx
where start.xxx.xxx.xxx and end.xxx.xxx.xxx are the first and last IPs of your web servers respectively. read more →
It looks like I have neglected to write a new article in quite a while! Shame on me. But, thanks to a website outage, I’ve finally got some more good stuff to share with you.
My previous Nginx configuration became a nightmare to maintain and WordPress had become slower because Apache’s children were being killed by OOM. This was due to a misguided PHP cache (PHP XCache to be precise) that decided to take every available bit of memory from my system, despite having max-requests per child set low (before it was purged).
This, along with my endeavors in seeking the fastest solution to everything and the introduction of a new Cloud servers by OVH, lead me to today’s article. read more →