Skip to:
Content

BuddyPress.org

Opened 4 years ago

Closed 4 years ago

#6956 closed defect (bug) (fixed)

Managing widgets into the customizer is not possible when BuddyPress 2.6.0-alpha is activated

Reported by: imath Owned by: boonebgorges
Milestone: 2.6 Priority: high
Severity: major Version:
Component: Emails Keywords: has-patch
Cc:

Description

For a reason i still ignore: the admin-ajax url returns a 500 internal server error ??

What's sure is switching to 2.4 branch is bringing back the possibility to manage widgets within the customizer. So it's a bug introduced by 2.5.

See screenshot:

https://cldup.com/Q_5JMJpTXY.png

Attachments (1)

6956.patch (549 bytes) - added by imath 4 years ago.

Download all attachments as: .zip

Change History (11)

#1 @imath
4 years ago

  • Component changed from API to API - Emails

If i remove add_action( 'bp_customize_register', 'bp_email_init_customizer' ); then it's possible to manage widgets within the customizer. So i guess it's narrowing the investigation field to the Email Feature

#2 @r-a-y
4 years ago

I cannot duplicate this on 2.5.x or trunk; I am able to move around widgets in the Customizer, edit widget properties and save.

Tested on WP 4.4.2. Haven't tested WP trunk yet.

#3 @imath
4 years ago

I'm using WP trunk (4.5). Probably the new feature that allowes part refreshes ?

Add the search widget, try to edit the widget title, and admin-ajax.php should return a 500 internal error.

#4 @imath
4 years ago

This is some more infos about the error:
PHP Fatal error: Class 'BP_Customizer_Control_Range' not found in /path/to/bp-core-customizer-email.php on line 65

#5 @DJPaul
4 years ago

Autoloader related?

#6 @imath
4 years ago

  • Summary changed from Managing widgets into the customizer is not possible when BuddyPress 2.5 is activated to Managing widgets into the customizer is not possible when BuddyPress 2.6.0-alpha is activated

There's a good chance yes, because i've just checked out on branch 2.5 and there's no problem with it.

#7 @imath
4 years ago

  • Milestone changed from 2.5.2 to 2.6
  • Version 2.5.0 deleted

Branch 2.5 is ok. Problem appeared in 2.6-alpha.

#8 @imath
4 years ago

  • Keywords has-patch added; needs-patch removed

I confirm it's an "autoload" issue. The attached patch is fixing the issue, but i'm unsure it's the best way to solve it.

@imath
4 years ago

#9 @boonebgorges
4 years ago

Thanks for debugging, @imath. I missed this when building the autoload whitelist.

#10 @boonebgorges
4 years ago

  • Owner set to boonebgorges
  • Resolution set to fixed
  • Status changed from new to closed

In 10684:

Add BP_Customizer_Control_Range to autoload list.

Props imath.
Fixes #6956.

Note: See TracTickets for help on using tickets.