-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
enhancement: Add new namespace #64
Comments
I would recomment this too! I also tried to create the new page as the "start" page of a new namespace. So the logic is turned around, that what you enter in the inputfield is not the NAME of the new page but the NAMESPACE. |
Since you write @igittigitt I can tell that I have instead used the Bureaucracy Plugin. |
@sorenweber Could you share the bureaucracy plug-in snippet you are using for this? Thank you! |
@aov-arnold, I am creating a non-conformance report (NCR) page which has its own sub-namespace below the NCR namespace, and within which files relevant to the NCR are uploaded. Below are the page with the form that is presented to the user and the template it calls. I hope you can use them as inspiration for what you want to do. The page with the form:
And this is the template (
|
Thank you but for us it would be enough to add a "create namespace" button. @samwilson Would this be difficult to implement? |
@dregad Could you add a new button |
This should be covered by #72, which I've been working on to resolve the merge conflicts. That's nearly done (testing in progress) and should be released soon. |
This is related to #50.
Is it possible to get the option that the page created is the start page of a a name space? That is, if I write "some_page" in the input field, the page created is actually "some_page:start".
Perhaps it could be generic, the syntax could be modified with an optional "subnamespace":
{{NEWPAGE>namespace>subnamespace}}
If you wrote "MY_PAGE" in the input field, your new page would be
namespace:MY_PAGE:subnamespace
, e.g. from{{NEWPAGE>reports:electrical>start}}
I would getreports:electrical:MY_PAGE:start
.Or even
{{NEWPAGE>reports:electrical>some:deep:structure}}
to getreports:electrical:MY_PAGE:some:deep:structure
.The reason is this: we use this plugin to create new problem report pages (bug reports, non-conformity reports), but people also need to upload various files relating to the problem, and I would like that these are stored in sub-namespaces withe the report's name.
I could ask people to write "the name of the page:start" in the input field, but I know many are not that technically minded and some will find this complicated and make errors, e.g. add spaces around the colon.
The text was updated successfully, but these errors were encountered: