Parametric page name and other changes (v2)

[dregad]

This is @splitbrain's original contribution (see PR #72), with merge conflicts resolved and some additional code cleanup and fixes, including French translation.

• a new @INPUT@ placeholder can be used to reference the given input in namespace setup. For example you could use something like {{NEWPAGE>foo:@INPUT@:start}} to let users create new namespaces inside the foo namespace. This makes Add alternative syntax to add entire namespace #70 obsolete
• a new ? syntax allows to overwrite config options from the syntax (defaults still come from the config setting) Example: {{NEWPAGE>foo:bar?nohide}} overwrites the default hide setting.
• support for strftime placeholders in the namespace config. Allows to create a daily page for example. Example: {{NEWPAGE>projekt:notes:%Y-%m-%d}}
• New option autopage which hides the input field. Together with the new date placeholder this allows to create a daily page on a single button click. Example: {{NEWPAGE>journal:%Y-%m-%d?noautopage}}
• This PR includes the changes of Always use id of main page in replacements #71

I did that many months ago, and never managed to finalize the testing due to lack of time.

Feedback and testing is welcome.

[Whyglobaleyes]

Hello,

Firstly many thanks to everyone - DW creators & core team as well as this plugin's authors - I'm not a programmer but manage to follow instructions well enough to meet my simple needs. For a few years I've been using add-new-page for every entry I create and love it.

• I've arrived here from issue {{NEWPAGE>foo:@INPUT@:start}} syntax does not work (Jackrum, current versions) #98 because I've got exactly those problems using the datetime and @input@ substitutions.
• In my dokuwiki instance I've updated the plugin to version 2024-09-14. I think that includes the merge above but it still doesn't work - I get new pages with names like "y-_m-_d:autopage:alaska".

Do I need to do something else to should use the 7id2fib commit mentioned above please. If so then please can someone describe how I apply it please? If not then any other ideas how I can troubleshoot or fix the behaviour please?
thanks in advance

[dregad]

@Whyglobaleyes

version 2024-09-14. I think that includes the merge above but it still doesn't work

Actually it does not. If it did, this pull request would not be open, it would have a merged status. You can also see that in the network graph, which shows that this PR's branch (pr72) has not been merged into the master branch, the tip of which is release 2024-09-14.

As explained in the PR's description above, the reason I did not merge it, is because I did not have time to properly test this code (as I don't use this functionality myself), and I was hoping to get feedback from the community but that has yet to come

Do I need to do something else to should use the 7id2fib commit mentioned above please

The easiest way is to manually install the code from this PR (download it from https://github.com/dregad/dokuwiki-plugin-addnewpage/archive/refs/heads/pr72.zip) instead of using the Extension Manager.

It would be great if you could perform some tests and confirm if everything is working as expected.

[Whyglobaleyes]

Dear @dregad, monsieur
I am not worthy; honestly I'm quite excited to have the attention of a proper programmer and especially one of the team that's done so much - thank you for that. It must be obvious that I don't know the first thing about using github so thanks for explaining. I've tried the PR version and I'm not sure where/ how to report back but here goes my description ...

EDIT:
A few moments later: My entire post earlier can be disregarded. because I rebooted the dokuwiki server and all the code is working as expected.
Beautiful.
Thank-you.
bw
ygi

---

ORIGINAL POST ...

attempt 1a - core functionality

• page code = {{NEWPAGE}}
• input on live page = deleteme_2024_11
• created new page = deleteme_2024_11 = as expected
• UNEXPECTED BEHAVIOUR: I think this is new since I installed the PR and didn't happen when I used the last version from the plugin manager:
  • PREVIOUSLY the namespace dropdown selection box would actually show only the 3 or 4 namespaces I actually use ::
  • NOW it shows the plugins folder with dozens of subdirectories (perhaps over 100) and doesn't show the final few actual namespaces.

attempt 1b - core functionality

• page code = {{NEWPAGE>:}}
• input on live page = deleteme_2024_11
• created new page = deleteme_2024_11 = as expected
• AS EXPECTED: specifying the namespace suppresses the namespace dropdown selection box
• UNEXPECTED BEHAVIOUR: I think this is new since I installed the PR and didn't happen when I used the last version from the plugin manager:
  • I use the addnewpage plugin in the topbar to create new pages VERY quickly.
  • with the PR72 version the namespace dropdown selection box is shown in the topbar and for some reason I can't see the ROOT namespace (which is where I put the majority of my pages)

attempt 2

• page code = {{NEWPAGE>wiki:}}
• input on live page = deleteme2024_11
• created new page = wiki:input:deleteme2024_11
• expected new page = wiki:deleteme2024_11

attempt 3

• page code = {{NEWPAGE>wiki:@INPUT@}}
• input on live page = deleteme2024_11a
• created new page = wiki:input:deleteme_2024_11a
• expected new page = wiki:deleteme2024_11a

attempt 4

• page code = {{NEWPAGE>wiki:@INPUT@_%Y_%m_%d}}
• input on live page = deleteme2024_11b
• created new page = wiki:input_2024_11_09:deleteme_2024_11b
• expected new page = wiki:deleteme2024_11b_2024_11_09

attempt 5

• page code = {{NEWPAGE>wiki:%Y-%m-%d?autopage}}
• the "Add Page" button on the live page isn't clickable

These 4 attempts had the same behaviour when I omitted the wiki: namespace definition.

I'm not sure if that's usable feedback. Please let me know if any other information would be better.
many thanks in advance.

[dregad]

@Whyglobaleyes
I'm glad I could help. So if I understand correctly, everything is working as expected ?

@WetenSchaap @bhartshorn @Chris75forumname @Hirschii @cblte @Fabien4941 @jonathanwgebb @gnoownow10 @stvoigt
You all mentioned interest in this feature / complained that it didn't work at some point (#72, #98), so it would be great if you guys could also test that this PR fixes the problem for you. Thanks in advance for your feedback.

[bhartshorn]

I installed using the Extension Manager by pointing to the zip file for the PR. I'm working on testing now, but I apparently deleted the original config which wasn't working. Give me a bit to restore the syntax I was using and try it out, I'll report back.

[bhartshorn]

I did not test extensively, but the strftime and autopage override feature both seem to be functioning. I didn't notice any bugs but will keep an eye out and update you if I notice anything.

[dregad]

@bhartshorn many thanks for taking the time to test

[Whyglobaleyes]

@Whyglobaleyes
I'm glad I could help. So if I understand correctly, everything is working as expected ?

yep exactly1
thank you

[WetenSchaap]

Hi,
Thanks a bunch for working on this!

As other have mentioned, strftime and autopage features work well, I tried a few random variations (also with subnamespaces and stuff), and Dokuwiki did what I expected it to do.

What did not work is combining the parametric names with pagetemplates:

{{NEWPAGE>@NS:@INPUT#pagetemplates:example1,pagetemplates:example2}}

will use the correct templates, but place the new page in ns:input, instead of the current namespace with the given input.

[dregad]

Thanks for testing @WetenSchaap

What did not work is combining the parametric names with pagetemplates:

{{NEWPAGE>@NS:@INPUT#pagetemplates:example1,pagetemplates:example2}}

will use the correct templates, but place the new page in ns:input, instead of the current namespace with the given input.

Is this the actual, exact markup ? If so can you please try with @NS@:@INPUT@ ?

[WetenSchaap]

Oops, yes, made a typo there. Sorry! Don't know why the @ got lost.

With the correct syntax, everything works as expected.

[Whyglobaleyes]

Brilliant, @dregad

Many thanks for finishing and finalising the features. Makes my DW a whole lot more comfortable and I'm sure it'll be enjoyed by many other people to o.

bw
ygi

[dregad]

@WetenSchaap many thanks for your sponsorship ❤️ ! I must say, that was a very unexpected and pleasant surprise, the first time in so many years of open-source contributions and support that this actually happens. I'll drink a 🍺 to your health !

@Whyglobaleyes thanks for the feedback.