Skip to:
Content

BuddyPress.org

Opened 10 years ago

Closed 10 years ago

Last modified 8 years ago

#6166 closed defect (bug) (worksforme)

Profile Group Tabs - UI Brocken in Admin

Reported by: lebearuk's profile LeBearUK Owned by:
Milestone: Priority: normal
Severity: normal Version:
Component: Templates Keywords: reporter-feedback
Cc:

Description

A fresh install of WP 4.1 and BP (trunk-9288) Twenty Fifteen Theme.

Profile field groups admin UI broken.

Attachments (2)

Profile Fields.png (60.4 KB) - added by LeBearUK 10 years ago.
Screen shot of broken UI for profile field groups assignment.
field group name.png (38.3 KB) - added by LeBearUK 10 years ago.

Download all attachments as: .zip

Change History (10)

@LeBearUK
10 years ago

Screen shot of broken UI for profile field groups assignment.

#1 @slaFFik
10 years ago

  • Keywords close added

The reason is obvious - your BuddyPress activated from /src folder. It has broken url to styles/js. So you need to actually build a BuddyPress and activate that "build"-ed version.

Last edited 10 years ago by slaFFik (previous) (diff)

#2 @slaFFik
10 years ago

Also please read starting from this comment: https://buddypress.trac.wordpress.org/ticket/6015#comment:5
I had the same issue.

This ticket was mentioned in Slack in #buddypress by slaffik. View the logs.


10 years ago

#4 follow-up: @DJPaul
10 years ago

Building from src is not necessary to run BuddyPress.

If it's broken still with the same reason as #6015, then that's a bug we need to fix.

#5 in reply to: ↑ 4 @boonebgorges
10 years ago

  • Keywords reporter-feedback added

Replying to DJPaul:

Building from src is not necessary to run BuddyPress.

If it's broken still with the same reason as #6015, then that's a bug we need to fix.

Building is necessary if you want to have the minified JS/CSS. If you're running from src, you need to have SCRIPT_DEBUG defined if you want these assets to load properly. We could probably do some magic to detect whether we're being run out of src and set SCRIPT_DEBUG, but IMO this is too much hand-holding and may lead to other bugs. Perhaps we could document the requirement to run SCRIPT_DEBuG somewhere, but I suggest that we don't make any changes in the source itself.

@LeBearUK, please put the following line in your wp-config.php and verify that it fixes the problem:

define( 'SCRIPT_DEBUG', true );

This ticket was mentioned in Slack in #buddypress by djpaul. View the logs.


10 years ago

#7 @johnjamesjacoby
10 years ago

  • Component changed from Core to Theme / Template Parts
  • Keywords close removed
  • Milestone Awaiting Review deleted
  • Resolution set to worksforme
  • Severity changed from major to normal
  • Status changed from new to closed

Closing this as worksforme.

#8 @DJPaul
8 years ago

  • Component changed from Appearance - Template Parts to Templates
Note: See TracTickets for help on using tickets.