#5864 a way to make the Admin tool the last tool, for all projects

v1.0.0
closed
nobody
General
Cory Johns
2015-08-20
2013-02-21
No

We'd like to be able to anchor a tool to the end of the project toolbar (the Admin tool, specifically).

It'd be nice if this could fit into the existing anchored tool field for Neighborhoods, but it might have to be a separate field and separate logic.

I think it'd also work to set the Admin tool's default position to a very high number so that it's at the end. And then a script to set it once for all projects in a neighborhood. I don't mind if a project moves it around later. That approach might be easier & cleaner then making another type of "anchoring" work.

Related

Tickets: #5864

Discussion

  • Igor Bondarenko - 2013-02-22
    • status: open --> in-progress
     
  • Igor Bondarenko - 2013-02-22

    Created #285: [#5864] a way to make the Admin tool the last tool, for all projects (2cp)

    I think we'll stick with a second option (set Admin tool's default position to high number plus script)

     

    Related

    Tickets: #5864

  • Igor Bondarenko - 2013-03-05

    Seems like setting default position for admin tool doesn't work as we expected. It applies for all newly created projects, not only for a specific neighborhood.

    If it is ok, then we can override admin tool order in project's sitemap method (like it was done for 'Moderate' app for neighborhoods). However it'll affect an entire site, and also admin tools will be no longer movable.

    If you want a more flexible solution (i.e. configurable for specific neighborhoods) I'm suggesting to extend anchored tools to accept formats like this:

    wiki:Wiki, *, admin:Admin
    

    i.e. all tools before '*' will be anchored to the beginning of nav, after - to the end, anything else - between them. Old format without '*' still will work fine.

     
  • Dave Brondsema

    Dave Brondsema - 2013-03-05

    It's ok to set the default position for the admin tool - affecting all new projects is fine by me. So I think that plus a script to update existing projects still should work.

    I like the syntax you suggest for the flexible format, but would rather keep with the above plan so that we don't have to make more customization in the sitemap/nav code.

     
  • Igor Bondarenko - 2013-03-07

    Closed #285. je/42cc_5864

    Actually, script isn't needed, since this works for old projects too.

     
  • Igor Bondarenko - 2013-03-07
    • status: in-progress --> code-review
     
  • Cory Johns - 2013-03-07
    • qa: Cory Johns
     
  • Cory Johns - 2013-03-07
    • status: code-review --> closed
    • milestone: forge-backlog --> forge-mar-08
     

Log in to post a comment.