Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [phoenix-dev] New Key for the Project Info DB.

Hi Nick,

The problem with defining the left nav in PHP code for the wiki is that you then have user code running inside the wiki code itself, which for security reasons is not a good thing.

Unfortunately we also have some projects who are not interested in any solution other than configuring the left nav in the wiki. We are doing our very best to accommodate them so Matt is working up a solution that addresses security concerns while providing as much flexibility as possible within the wiki structure. Plus it leverages a technology we already have (meta-data) so we don't have to add yet another configuration somewhere else. That's the idea anyway.

Karl



Nick Boldt wrote:
+1 for being able to configure wiki navigation, though it would be great if
it could source from the same place as the project's _projectCommon.php nav,
as Bjorn suggested.

The other approach here, just FYI, is what Remy started doing for ECF via a
common sidebar box: http://wiki.eclipse.org/ECF ... not sure if anyone else
has adopted this approach yet.

Nick

On Thu, Feb 21, 2008 at 6:44 PM, Karl Matthias <karl.matthias@xxxxxxxxxxx>
wrote:

What's special about this one is that it's for allowing projects to
configure the wiki to have a project-specific left nav.  They include a
tag in their wiki page which triggers the skin to load up a custom nav
from the DB rather than using the default wiki nav.  I think Matt is
saying that it could also be used to generate the normal project left
nav as weel, later, if we want to.

Karl


Bjorn Freeman-Benson wrote:
Is this a better solution for the project teams than having them
define the left nav using the $Nav object the way they do now?

Matthew Ward(Esq.) wrote:
As part of solving bug 179537, I'd like to add a new MainKey named
'projectleftnav' to the ProjectInfo database as well as SubKeys of
'title','url','order' and 'separator'.  Here's the proposed definition:

------------------------------------------------------------------------
_______________________________________________
phoenix-dev mailing list
phoenix-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/phoenix-dev

_______________________________________________
phoenix-dev mailing list
phoenix-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/phoenix-dev





Back to the top