BU Web Team

Fixed in 1.2.7. Thank you for the report & patch.

https://github.com/bu-ist/bu-navigation/issues/13

Out of the box modifying the navigation label and visibility setting will only be reflected in page listings generated by the “Content Navigation” widget.

The plugin also provides a theme support flag and template tag which can be used to display a primary navigation menu that also respects these settings. We find it useful as it uses the existing page hierarchy, which saves you from having to maintain a separate structure in a custom menu.

Instructions for modifying your theme to support this can be found here:
https://github.com/bu-ist/bu-navigation/wiki/Adding-Theme-Support-for-Primary-Navigation-Menus

That doesn’t sound right — you shouldn’t have to modify the plugin code to get it to work. ??

I was unable to reproduce in 3.9.1 (or any WP version for that matter) so I’m wondering if perhaps it is browser specific or maybe there is a conflict with another plugin you’re running. Was this issue limited to a specific browser / OS?

You’re trying to add section editors through the “Edit Section Group > Members” tab, correct?

We’re unable to reproduce this behavior in a fresh WP 3.9.1 install. Could you provide more detail as to your setup? Browser, other active plugins, etc. Are there any Javascript errors showing up in your console?

Thanks for your interest in the plugin!

While there are certainly functions that do these things, they are internal to the plugin and would not be considered a public and officially supported API at this time.

I’ve added this as an enhancement request to the Github repository: https://github.com/bu-ist/bu-section-editing/issues/8.

The filtering of the “file://” protocol in links occurs for any role below Editor due to the lack of the unfiltered_html capability. See https://codex.www.ads-software.com/Roles_and_Capabilities for more info.

By default the capability set for section editors is quite restrictive. This can be modified programmatically or through a role management plugin such as Members. See this Github Wiki page for more details.

A primary goal of this plugin is to prevent section editors from creating or editing published content unless they are explicitly allowed to do so. As a result the default capability set is quite restrictive.

The BU Versions plugin compliments this functionality by adding a workflow that permits section editors and other less capable roles to create “Alternate Versions” of published content, allowing them to make modifications that are not publicly visible which can then be submitted for review by users with greater privilege.

Additionally, it is possible to modify the default capabilities for the section editor role programmatically or by using a plugin such as Members. More details on how you could go about this available in the Github Wiki.

Currently plugins that utilize post meta / custom meta boxes need to explicitly add support for the BU Versions plugin in order to work properly. There are a couple open issues in our Github repository with discussion around this decision:

https://github.com/bu-ist/bu-versions/issues/7
https://github.com/bu-ist/bu-versions/issues/2

We are kicking around some ideas to smooth out this experience in a future release.

The workflow we envisioned when creating these plugins was to limit full editing capabilities to specific pages with BU Section Editing, but give the ability to suggest changes to all content with BU Versions. With this setup “Section Editors” can create alternate versions for pages they are not allowed to edit and then “Submit for Review”. (By default, section editors are not allowed to edit any published content).

It’s on our radar! Just added an enhancement issue to our Github repos:
https://github.com/bu-ist/bu-versions/issues/15

Section editors should only be able to publish posts if a section group that they belong to permits it. If a new post is placed underneath a post for which a section editor is allowed to edit (within an editable section), the new post will inherit section editing permissions and they will be permitted to publish that page.

Could you please provide more detail so that we can determine whether or not it is a bug?

Thank you for your feedback. I have added this suggestion as an enhancement to the plugin page on Github.

This issue has been resolved in the latest release (1.1.4).