There is an example available.
However this is how to reproduce the problem:
Let's say I have a page NamespaceA:_:Home
Then I edit that same page throught WYSIWYG editor creating a wiki-link to the not-yet-existing page "Target". In source code this corresponds to Target.
Once the page is saved I click on Target link. This way Tiki automatically creates NamespaceA:_:Target page.
I'd like to underline this is an extremely useful feature since it allows even not-developer users to create new pages with the correct namespace without having to mess with the source code, which is a desirable feature.
However once NamespaceA:_:Target page has been created, no backlinks are present in there.
However if now I edit page NamespaceA:_:Home by adding a wiki-link to "NamespaceA:_:Target" (in source code this would correspond e.g. to Target ), the link works just fine and moreover a backlink from NamespaceA:_:Target to NamespaceA:_:Home is generated.
Option "Force all non-namespace page links to the same namespace" does not seem to solve the problem.
-----------------------
In short: Target and Target are both valid links towards page NamespaceA:_:Target (starting from page NamespaceA:_:Home), but one is recognized as a backlink by Backlinks plugin while the other one is not.
------------------------
The problem lies in the fact that if a not-developer user were to use Tiki, the above-mentioned feature of automatic page creation with correct namespace would be extremely useful but it introduces the above-mentioned problem.
------------------------
I think one possibility would be to edit Backlinks plugin to recognize Target as a valid link to NamespaceA:_:Target as well (in this context, taking into account the namespace of the page on which the link resides).
Another possible solution would be to have WYSIWYG plugin work (optionally?) in a little different way: if I am in page NamespaceA:_:Home and I write a link towards page Target it should automatically translate the link in Target instead of just Target. Maybe this second solution is cleaner? I don't know.
Thank you very much for your attenction
The URL for the show2.tiki.org instance that demonstrates this bug is at: http://alessandromartinelli-11998-7391.show2.tiki.org. Note that if you get a popup asking for a username/password, please just enter "show" and "show". This is different from the initial login and password for a new Tiki which is "admin" and "admin".
For the install log, see http://alessandromartinelli-11998-7391.show2.tiki.org/info.txt
Note that if you see PHP errors or a Tiki claiming to be missing third party software, the instance creation is probably not finished. Please wait a couple minutes and reload.
Snapshots are database dumps of the configuration that developers can download for debugging. Once you have reproduced your bug on the show2.tiki.org instance, create a snapshot that can then be downloaded by developers for further investigation.
Snapshots can be accessed at: http://alessandromartinelli-11998-7391.show2.tiki.org/snapshots/. Note that if you get a popup asking for a username/password, please just enter "show" and "show".
Create new snapshotfilename | created | hits | comment | version | filetype | ||
---|---|---|---|---|---|---|---|
No attachments for this item |