• Resolved sepidpooy

    (@sepidpooy)


    When I activate this plug-in and wordpress DEBUG mode, following errors show up on the site screen. It seems the plug-in does not call wp_enqueue_style appropriately since all of these errors show-up on when this plug-in is activated:

    Notice: wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. Please see Debugging in WordPress for more information. (This message was added in version 3.3.) in /export/scratch/zahra/wordpress/wp-includes/functions.php on line 3245 Notice: wp_enqueue_style was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. Please see Debugging in WordPress for more information. (This message was added in version 3.3.) in /export/scratch/zahra/wordpress/wp-includes/functions.php on line 3245 Notice: Undefined index: force_upgrade in /export/scratch/zahra/wordpress/wp-content/plugins/sp-client-document-manager/classes/install.php on line 7 Notice: bbp_setup_current_user was called incorrectly. The current user is being initialized without using $wp->init(). Please see Debugging in WordPress for more information. (This message was added in version 2.3.) in /export/scratch/zahra/wordpress/wp-includes/functions.php on line 3245 Notice: bp_setup_current_user was called incorrectly. The current user is being initialized without using $wp->init(). Please see Debugging in WordPress for more information. (This message was added in version 1.7.) in /export/scratch/zahra/wordpress/wp-includes/functions.php on line 3245 Notice: Indirect modification of overloaded property BuddyPress::$group_invite_email has no effect in /export/scratch/zahra/wordpress/wp-content/plugins/buddypress-group-invite-email/index.php on line 65 Notice: Indirect modification of overloaded property BuddyPress::$group_invite_email has no effect in /export/scratch/zahra/wordpress/wp-content/plugins/buddypress-group-invite-email/index.php on line 66 Notice: Indirect modification of overloaded property BuddyPress::$group_invite_email has no effect in /export/scratch/zahra/wordpress/wp-content/plugins/buddypress-group-invite-email/index.php on line 67 Notice: Undefined variable: alters in /export/scratch/zahra/wordpress/wp-content/plugins/sp-client-document-manager/classes/install.php on line 183 Notice: Trying to get property of non-object in /export/scratch/zahra/wordpress/wp-content/plugins/buddypress/bp-groups/bp-groups-template.php on line 596 Notice: Trying to get property of non-object in /export/scratch/zahra/wordpress/wp-content/plugins/bp-group-tinychat-pro-1.3/includes/bp-group-tinychat-core.php on line 41 Notice: Trying to get property of non-object in /export/scratch/zahra/wordpress/wp-content/plugins/buddypress-group-css/bp-group-css.php on line 36 Deprecated: Function split() is deprecated in /export/scratch/zahra/wordpress/wp-content/plugins/buddypress-group-css/bp-group-css.php on line 39 Notice: Trying to get property of non-object in /export/scratch/zahra/wordpress/wp-content/plugins/buddypress-group-css/bp-group-css.php on line 60 Notice: is_site_admin is deprecated since version 1.5! Use is_super_admin() instead. in /export/scratch/zahra/wordpress/wp-includes/functions.php on line 3078

    https://wordpress.org/plugins/another-wordpress-classifieds-plugin/

Viewing 1 replies (of 1 total)
  • Hi sepidpooy,

    Looking at those errors, a number of them are coming from non-AWPCP scripts, such as BuddyPress. Some of the API calls aren’t even from our plugin at all (such as bbp_setup_current_user)

    I’d try a conflict test to see if AWPCP is the true cause of these, or if others are simply showing up because we are running. Here is an article about how to test for theme and plugin conflicts with AWPCP, which may help pinpoint the issue: http://awpcp.com/forum/faq/how-to-test-for-plugintheme-conflicts/

    We also have an update coming out–fixing a number of minor bugs, so this could be related to that as well. You’re welcome to try it–contact me here to get it: http://awpcp.com/contact/

Viewing 1 replies (of 1 total)
  • The topic ‘wp_enqueue_style was called incorrectly’ is closed to new replies.