Background Manager 1.2.5.2 released

on October 28, 2013 in WordPress with 10 comments by

Just shortly after hitting the 100,000 downloads milestone at WordPress.org, today brings us a maintenance release of Background Manager, version 1.2.5.2.

The main reason for this release was to address a bug that appeared in WordPress 3.7, which caused a background image to appear on all pages/posts, even if the settings specified otherwise. I believe the bug has now been addressed, and would likely have been due to a change in WordPress’ wp_guess_url() function.

In addition, an option to disable Background Manager on mobile browsers was introduced.  That is considered an experimental feature at the moment, and is purely an on-off switch.  That is, it isn’t a feature that will download a smaller images based on the mobile screen resolution, for example — that is still something to be considered at the moment.

Under the hood there are quite a number of changes, not fully described in the changelog.  The one change that relates to Background Manager directly, is that the body tag override, used for the background colour or non-full-screen backgrounds, has been moved into a class instead (namely, myatu_bgm_body). The main reason for this is that it is easier to remove the background changes, should this be required.  Background Manager itself does this in when a mobile browser was detected and the ‘active on’ setting for mobile browsers is set to off.

The other changes primarily relate to the Pf4wp framework that this plugin uses. For example, it has a new handler for fatal errors, providing the user a better to understand feedback in case the error happened in the WordPress administration area, including details that can be passed to the plugin developer (me!).  If the fatal error occurred on the public side, then the plugin will automatically disable itself – if possible – to prevent it from causing further problems with the website.  Any of these errors are also logged in the plugin’s main directory for easy retrieval and debugging at a later time.

Additionally, the Pf4wp plugin does an additional check when the APC cache is enabled, by verifying if it can store in the cache.  In the past it assumed it could if APC was available, potentially causing the infamous WordPress white-screen-of-death.  This was also a reason for the introduction of the fatal error handler.

Although not enabled nor available in Background Manager, Pf4wp also has the ability to perform remote Javascript debugging, courtesy JSConsole.  The feature is disabled by default in Pf4wp for obvious reasons.

Edit: Murphy’s Law has reared its ugly head, and 1.2.5 contained a bug that affected < PHP 5.4 installations. Hopefully this has been addressed in full now.

10 comments

  1. posted on Jun 24, 2014 at 7:30 AM  |  reply

    Great plugin Myatu! Using it on a website I am creating for a client, http://biennialartpaperfibre.com, and would like to make the background scroll – how do I do that? All the best, Åsa.

  2. posted on Apr 24, 2014 at 9:50 PM  |  reply

    The background images on the home page of forefrontdermatology.com are not clickable. Tried changed all the settings and nothing works. I noticed that others on the WP forum for this plugin have had the same issue. How do we get this resolved?

  3. DERT
    posted on Apr 04, 2014 at 5:17 AM  |  reply

    Myatu, love your plugin! I have done everything correctly, yet the background is still not clickable. Any ideas?

  4. pyemachine
    posted on Mar 26, 2014 at 12:30 AM  |  reply

    Hi
    Love your plugin but it keeps de-activating thus making my clients site not look great.
    Are you aware of this bug? Is there something i can do?

    see http://adamliaw.com.au
    thanks
    Luke

    • Myatu
      posted on Mar 29, 2014 at 5:20 PM  |  reply

      If the plugin deactivates itself without warning, then it encountered an “exception error”, one which could otherwise cause the “blank page” issue. If you look in the plugin’s directory, which should be /wp-content/plugins/background-manager/, then you will likely find a log file that records these errors. This may help you determine what the cause is.

  5. posted on Feb 12, 2014 at 4:30 PM  |  reply

    So sorry, I posted my question in an old post. Here it is again.

    Fantastic Plugin that solved a problem for me. Just one question, is it possible to limit the plugin’s activation to screen size? I’d like to use it with a @media only screen and (min-width: 769px) call.
    Thanks!
    Rick

  6. Salvatore
    posted on Jan 19, 2014 at 4:59 PM  |  reply

    Hi, i have a problem with your plugin, i use wordpress 3.8 and curb framework , if i put a normal background in any position, it doesn’t display it (but if i manually remove the .myatu_bgm_body class with firebug, yes) but if i put it in full screen mode, i can see it. How can i resolve ? Thanks

  7. posted on Jan 18, 2014 at 1:09 AM  |  reply

    I have the plug-in activated and it shows on this page and similar pages in that category

    http://www.noise11.com/vinterviews/nile-rodgers

    but not on most pages like here:

    http://www.noise11.com

    Can you please advise what I might be doing wrong?

    thanks

    Paul

  8. posted on Dec 08, 2013 at 8:17 AM  |  reply

    I keep getting an error message when I try to install the plug in, any ideas?
    Megan

    • Myatu
      posted on Dec 08, 2013 at 1:15 PM  |  reply

      Could you be more specific about the error message, please?

Join the discussion

Your email address will not be published. Required fields are marked *