moqume / background-manager-wp Goto Github PK

For the Flickr importer, the description should include the username of the photographer/designer of the Flickr image, as well as the attribution.

Is there a way to disable touchmove for the background?

Reported at http://wordpress.org/support/topic/plugin-background-manager-settings-background-image-set-menu-showing-only-one-entry:

To get the plugin to show all of them change line 420 in Main.php:

'numberposts' => 0,

to

'numberposts' => -1,

or delete the whole line as the default value for the get_posts() function for numberposts is -1!

The developer might want to fix this too!

Does the backgroundslideshow work in IE8?

Either option, or automatic override, of jQuery.ajax() (http://api.jquery.com/jQuery.ajax/) using crossDomain. Personal preference is for automatic override, given security complications.

Problem related to issue #6 in MSIE 7+ and Google Chrome (should also affect FF 3.5+).

From http://wordpress.org/support/topic/plugin-background-manager-call-to-undefined-function

A really great background image plugin. But I get this error.

context: trying to import images in with NextGen uploader. selecting to only show background images for home page.

Here's my php error trace.

Fatal error: Call to undefined function Pf4wp\Menu\add_theme_page() in I:\xampp\htdocs\meredith\wp-content\plugins\background-manager\vendor\pf4wp\lib\Pf4wp\Menu\MenuEntry.php on line 255
Call Stack
# Time Memory Function Location
1 0.0009 334096 {main}( ) ..\index.php:0
2 0.0015 337896 require( 'I:\xampp\htdocs\meredith\wp-blog-header.php' ) ..\index.php:17
3 0.6173 22452496 require_once( 'I:\xampp\htdocs\meredith\wp-includes\template-loader.php' ) ..\wp-blog-header.php:16
4 0.6202 22461808 include( 'I:\xampp\htdocs\meredith\wp-content\themes\bdangtheme\page-about.php' ) ..\template-loader.php:43
5 0.6476 22537376 get_footer( ) ..\page-about.php:39
6 0.6476 22537752 locate_template( ) ..\general-template.php:63
7 0.6479 22537896 load_template( ) ..\theme.php:1091
8 0.6485 22546688 require_once( 'I:\xampp\htdocs\meredith\wp-content\themes\bdangtheme\footer.php' ) ..\theme.php:1115
9 0.6485 22546688 wp_footer( ) ..\footer.php:16
10 0.6485 22546744 do_action( ) ..\general-template.php:1587
11 0.6493 22548248 call_user_func_array ( ) ..\plugin.php:405
12 0.6493 22548264 wp_admin_bar_render( ) ..\plugin.php:405
13 0.6493 22548488 do_action_ref_array( ) ..\admin-bar.php:58
14 0.6620 22546048 call_user_func_array ( ) ..\plugin.php:486
15 0.6621 22546064 Myatu\WordPress\BackgroundManager\Main->onAdminBarMenu( ) ..\plugin.php:486
16 0.6668 22810872 Pf4wp\Menu\StandardMenu->display( ) ..\Main.php:860
17 0.6668 22810872 Pf4wp\Menu\MenuEntry->display( ) ..\StandardMenu.php:330

Seen as:

Resource interpreted as Image but transferred with MIME type text/plain: "data:;base64,iVBORw0KGgoAAAANSUhEUgAAAAQAAAAECAYAAACp8Z5+AAAAAXNSR0IArs4c6QAAAAZiS0dEAP8A/wD/oL2nkwAAAAlwSFlzAAALEwAACxMBAJqcGAAAAAd0SU1FB9sKHQwZOZHxCdsAAAAZdEVYdENvbW1lbnQAQ3JlYXRlZCB3aXRoIEdJTVBXgQ4XAAAAFUlEQVQI12P4//9/PQMSYGJAA4QFAOYKA4OpYuGvAAAAAElFTkSuQmCC".

This could cause problems with security restrictions on some browsers, in turn not displaying the overlay. Default MIME should be PNG for this plugin (not text/plain).

Well, first of all I wanna thank so much for this wonderfull wordpress plugin.

I have develop my project in localhost and note this, if I install the plugin with default permalinks configuration, and after this instalation I change the permalinks the images set defined in plugin not show with new permalinks configuration... if I move back to default permalinks, everthing works fine again...

I note this problem in custom post type too... 👍

Well, my main objective is contribute to this plugin reported this problem. Hope this is fixed soon. Thanks again!

😃

See http://wordpress.org/support/topic/urgent-posts-page-problem

My problem is that the background appears fine on all the pages until I allocate a page to be used for my posts. (settings - reading - posts page).

Could the background override panel on posts and pages be modified to select a single image versus an entire image set?

For instance, on my portfolio I'd like to use a different static image as the background for each portfolio post. As the plugin stands I must create a new image set for each post and fill it with one image.

It would be fantastic if I could choose an image from the media library (or from a background images set) to use. That way I could have one background set called "Portfolio" with an image for each.

Haven't looked through the plugin code too thoroughly, but thought I'd bring this up before I forget.

See http://wordpress.org/support/topic/plugin-background-manager-overriding-for-posts-pages-does-not-work

"Hello,

I love your plugin and it seems to be the best way to sort the backgrounds in a website.

There's only one problem I've run into with my installation. Even though the background works fine when I assign it in the settings page, when I'm assigning a different set in a page or a post, it'll always show the default background, not any from the image set I assigned.

For example, I want a default background in the homepage, different background when I do an album review and different when I do a book review.

Theme used with : Avenue from Themeforest
Plugins installed:

CataBlog
CSV Importer
Dave's WordPress Live Search
Facebook AWD All In One
Navayan CSV Export
Shortcodes Pro
Social Author Bio
Under Construction
Widgets on Pages"

i just installed the plugin. when i try to active it in wordpress i get the following error:

Plugin could not be activated because it triggered a fatal error.
Restricted Access

i'm assuming it needs write permissions in some folder. which ones would that be?
or is it something else? i have a fairly standard wordpress install on debian wheezy.

thanks & greetings,
david

Reported by user: "My background images are only 1980 x 246 I have no scaling on but the program scales the picture smaller to 1024 x 40"

Hi,

when I active "Restricted Site Access" plugin the background appears but it is not clickable anymore. It seems a problem with the call of 'parse_request' action.

thank you.