I often need a select by _fullname = "data-entry-page-path-field" to read ONE page only in a ListPages module.
Any trick with hidden fields ( i.e. "origname" , value: %%fullname%% ) does not work for selection.
To handle such "direct read" we need now always a tag with the _%%fullname%% too. Only for such reading!
Or is there a little wotrkaround ( like my test with the hidden field) to get the same result?
Is in real the same wish as from Steven: http://feedback.wikidot.com/wish:289 (I wish for a page selector by %%name%%)
**It is soo needed in a sense of database-funktion to read by Primary-Index!**
Question:
If I have the need to read directly a pagepath type datafield - I should be able to use the
Edit:
No, this brings only all pages which have a link to this page anywhere in their source.
Not the exact only one I need .. :(
Service is my success. My webtips:www.blender.org (Open source), Wikidot-Handbook.
Sie können fragen und mitwirken in der deutschsprachigen » User-Gemeinschaft für WikidotNutzer oder
im deutschen » Wikidot Handbuch ?
If page-id is a pagepath…
does include not work?
also… redirect module.
I know this works but up till now I never tried it with a form-data-value
A - S I M P L E - P L A N by ARTiZEN a startingpoint for simple wikidot solutions.
Include could work only in the first level - at the _template level direct. - but brings ALL content of the page source at this moment… I need only 1 - 2 dataform fields (pagepath-links again to the next deeper "step" value - the parents of my person page "per:1")
In ListPages i can build the "outcome" of the module with the dataform variables of the level -1 of the searched/red next page and one of the fields is the pagename-(=Link) of the second level (=grandparents)
Now I have to use the tags with the %%fullname%% - using iftags to check if the tags are missing - and can read by this second index the exact page ( and the important pagepath key Link too).
If we could use LisdtPages nested - than I could go down into the next step of reading the pages of the parents of the granparents… and so on… - but this is not really necessary….
Bad is realy the need to tag all the pages with their own name to read exact this one page by their fullname.
Is in real the same wish as from Steven: http://feedback.wikidot.com/wish:289 (I wish for a page selector by %%name%%)
Service is my success. My webtips:www.blender.org (Open source), Wikidot-Handbook.
Sie können fragen und mitwirken in der deutschsprachigen » User-Gemeinschaft für WikidotNutzer oder
im deutschen » Wikidot Handbuch ?
I have found a "workaround" with help of Kenneth Tsang:
I use the Wikidot API http://community.wikidot.com/app:jsapi (**Wikidot jsAPI Library **) which starts an tagtool Utility Screen (working at the moment only in CHROME!) :
https://jsapi.wikidot.com/tagtool
This needs an API write key for the user and the API allowness of the changing site.
You can use:
_%%name%% — for a hidden name tag (without category)
%%name%% — for a normal name tag (without category)
_%%fullname%% — for a hidden full name tag (with category)
%%fullname%% — for a normal full name tag (with category)
When I have tagged all Pages in a specific category with a hidden Tag "_%%fullname%%" I can select one page by this tag ( using a dataform field content with the page "name" ) to find exact this one page in a ListPages Module.
This works well - but only for a pro account ( the API key!)
A select by fullname=".." or pagename="…" category="…" would be easier… :)
Service is my success. My webtips:www.blender.org (Open source), Wikidot-Handbook.
Sie können fragen und mitwirken in der deutschsprachigen » User-Gemeinschaft für WikidotNutzer oder
im deutschen » Wikidot Handbuch ?
is implemented!
Service is my success. My webtips:www.blender.org (Open source), Wikidot-Handbook.
Sie können fragen und mitwirken in der deutschsprachigen » User-Gemeinschaft für WikidotNutzer oder
im deutschen » Wikidot Handbuch ?