Skip to:

Opened 13 years ago

Closed 11 years ago

#1500 closed enhancement (fixed)

Split settings into relative WordPress settings screens

Reported by: johnjamesjacoby's profile johnjamesjacoby Owned by: johnjamesjacoby's profile johnjamesjacoby
Milestone: 2.4 Priority: normal
Severity: normal Version:
Component: General - Administration Keywords:
Cc: georgemamadashvili@…, stephen@…, jared@…


The bbPress settings screen should be split up and integrated more tightly into the existing WordPress settings screens. There is a core WordPress ticket that's currently preventing this from happening:

Once the WordPress permalinks page allows for custom fields to be saved from it, this is easily possible.

Change History (17)

#1 follow-up: @johnjamesjacoby
13 years ago

Doesn't look like this is going to make it into WP 3.2.

#2 in reply to: ↑ 1 @cnorris23
13 years ago

Replying to johnjamesjacoby:

Doesn't look like this is going to make it into WP 3.2.

Or 3.3

#3 @johnjamesjacoby
12 years ago

  • Milestone changed from 2.1 to Future Release

Correct. Punting.

#4 @Mamaduka
12 years ago

  • Cc georgemamadashvili@… added

#5 @Mamaduka
12 years ago

I think this won't happen before new Settings API -

#6 @netweb
12 years ago

  • Cc stephen@… added

#7 @jaredatch
12 years ago

  • Cc jared@… added

#8 @johnjamesjacoby
11 years ago

  • Milestone changed from Future Release to 2.4

Bumping to 2.4. Going to put a switch in to allow an easy transition for this when it's time.

#9 @johnjamesjacoby
11 years ago

In 4932:

First pass at settings and options redux:

  • Introduce toggle to break forum settings up into existing WordPress settings pages. Off by default, this allows us to migrate easier later, should we decide to go this route. See #1500.
  • Introduce setting to handle the forum-root toggle. This eliminates the possible forum/topic archive slug conflict, if using topics archive as forum root. More to integrate here, including changing the main query and template part output.
  • Break user slugs into their own section, and allow favorites and subscriptions slugs to be edited.
  • Turn Forum Root into it's own section, and move topic/reply archive slugs into the new user section.

#10 @johnjamesjacoby
11 years ago

In 4933:

Move user base setting into new Users section. Tweak some verbiage to be more succinct. See #1500.

#11 @johnjamesjacoby
11 years ago

In 4935:

Allow topics to replace the forum archive:

  • Add condition to bbp_parse_args() and add a specific query variable early, and use this variable in bbp_is_forum_archive().
  • Add condition to display_forum_archive() shortcode, to output topics if set.
  • Add forum archive check to bbp_has_topics(), to ensure pagination links are correct.
  • See #1500.

#12 @johnjamesjacoby
11 years ago

In 4936:

Correct typo that snuck in after testing. See #1500.

#13 @johnjamesjacoby
11 years ago

In 4937:

Tweak include_root Settings verbiage to hopefully provide more context. See #1500.

#14 @johnjamesjacoby
11 years ago

In 4938:

s/Base/Root. See #1500.

#15 @johnjamesjacoby
11 years ago

In 4939:

Add bbp_settings_user_slugs section to mapped capabilities method. See #1500.

#16 @johnjamesjacoby
11 years ago

In 4940:

Check for both forum/topic archives when setting 'bbp_show_topics_on_root' query arg. Fixes paged 404's in configurations where a WordPress page is used in place of the normal Forum archive. See #1500.

#17 @johnjamesjacoby
11 years ago

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

This is largely finished, pending a WordPress core patch. Closing as fixed.

Note: See TracTickets for help on using tickets.