Skip to:

Opened 13 years ago

Closed 13 years ago

#3026 closed defect (bug) (fixed)

Activating components after setup needs to create a WP page

Reported by: boonebgorges's profile boonebgorges Owned by:
Milestone: 1.5 Priority: critical
Severity: Version:
Component: Core Keywords: has-patch dev-feedback


Otherwise the directory won't work

Attachments (1)

3026.patch (5.1 KB) - added by boonebgorges 13 years ago.

Download all attachments as: .zip

Change History (4)

#1 @boonebgorges
13 years ago

  • Keywords has-patch dev-feedback added

3026.patch takes the following tack: After components are activated or deactivated, a message is displayed in the success box explaining that the admin will have to do the new page association manually (with a link to the "New Page" Dashboard panel) in the case of activated components, and a message that the admin may want to delete/unpublish pages for deactivated components (along with a link to the Pages panel) in the case of deactivation. In short: display a helpful message, but let the admin take care of the configuration himself, so we don't have to mess around with automatic page creation/deletion, which is IMO very icky.

Can anyone take a look and see whether they think this is a fair strategy?

13 years ago

#2 @boonebgorges
13 years ago

Boone note to self:
[2:29pm] jjj: Check if the newly activated component has a ->root_slug, if it does we know it's looking for a component page.

#3 @boonebgorges
13 years ago

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

(In [4183]) Adds warning notices to Dashboard when required BP component directory pages are missing. Fixes #3026. Adds warning notices to Dashboard when bp-pages are present but the corresponding component is deactivated. Fixes #3025. Removes root_slug declaration from components that should not have top-level directories.

Note: See TracTickets for help on using tickets.