Category: Backlinks

{syntax type="tiki" editor="plain"}
So the alias is not 100% an alias.

On: ((doc:Semantic))

There is a link to:
* ((doc:Semantic Alias))

But this ((doc:Semantic Alias)) is an alias of ((doc:Alias))

Also in action here:
http://profiles.tikiwiki.org/handler

Related:
*{wish id=2754}
*{wish id=2729}

When creating a wiki link ~np~((foo)))~/np~, Tiki uses the target pages's ''description'' as the the link's TITLE attribute. It would be nice for external links to also have a TITLE attribute. Tiki could use the link's description, or a generic text. For example:

~np~[http://foo.com|my link]~/np~ would become:
<a href="http://foo.com" title="External link: my link">.....

and

~np~[http://foo.com]~/np~ would become:
<a href="http://foo.com" title="External link">.....

{syntax type="tiki" editor="plain"}
1- Go to ((Keywords))
2- Check Backlinks

You will see a backlink to __Why Use 2.0 for devtwo__ but this page no longer exists. It was renamed or deleted or something :-)

{syntax type="tiki" editor="plain"}
You can see:
* http://profiles.tikiwiki.org/Admin#List_pages
* ((doc:backlinks))

In a tracker item, we often refer to wiki pages. From those wiki pages, we should be able to see the trackers in the backlinks.

Related:
Tracker plugin to get title and make link to tracker item
http://dev.tikiwiki.org/tiki-view_tracker_item.php?itemId=1768

With this second thing done, we could have backlinks among tracker items.


This will be useful for a ((Mindmap))

Update:
Backlinks still fail to display. See https://doc.tiki.org/tiki-backlinks.php?page=Tiki3

CentOS 6.3
APC 3.1.13
PHP 5.4.11 (apache2handler)
MySQL 5.5.30-log

Tiki 12, new/clean install

all related features was be checked(shearched in admin panel), still Missing Backlinks.

1. Backlinks failed to display in the wiki page (top icon, right corner)

2. Backlinks failed to display in a wiki page, which I use inline plugin Tools to insert it, such as:

http://giprs.org/wiki (English & Chinese pages)

http://giprs.org/wiki/Project(external link)

http://giprs.org/wiki/Issue(external link)

If a valid wikilink is included within a comment on a wiki page, that link is reported by BACKLINKS on the page being linked to.

{CODE(caption="Test_MRB_01")}This page uses the BACKLINKS plugin to show pages with links to it -
{BACKLINKS()}{BACKLINKS}{CODE}

{CODE(caption="Test_MRB_02")}This page has three source lines, the second of which is a comment.
~tc~((Test_MRB_01|This link to Test MRB 01 is in a comment))~/tc~
This is the third line, but only two lines visible when viewed.{CODE}

{syntax type="tiki" editor="plain"}
On doc.tikiwiki.org, I renamed pluginBacklinks to PluginBacklinks and the backlinks are gone.

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 ((NamespaceA:_:Target|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 ((NamespaceA:_:Target|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 ((NamespaceA:_:Target|Target)) instead of just ((Target)). Maybe this second solution is cleaner? I don't know.

Thank you very much for your attenction

The title for External wiki links in not parsed, for instance
~pp~ ((wp:Link|Title)) ~/pp~
will display __Link__ instead of __Title__

We need this for *.tikiwiki.org as well
{img src=images/code.png}%%% {CODE()}
((dev:EditUIRevamp|Improve the content editing interface))
((dev:AdminUIRevamp|Improve the admin interface))
{CODE}

Say I need to make a link such as:
{img src=images/code.png}%%% {CODE()}
[http://en.wikipedia.org/wiki/Argument_map|Argument map]
{CODE}

I could use an ((doc:external wiki)) link which is like this:

{img src=images/code.png}%%% {CODE()}
((wp:Argument map))
{CODE}

Even nicer would be an image (instead of {img src=img/icons/external_link.gif}) so the visitor knows he'll be sent to Wikipedia.

Also, would need:
*optional title: to explain what this site is about. (ex.: this is a sister community)
*option to open new window
these would be set centrally and you could override.


Perhaps the direction to take is to build with ((doc:plugin alias))

There are many pages within t.o that have spaces. On the other hand, the WikiSyntax historically uses WikiWords. I also see that tiki supports aliases for pages. This led me to the following suggestion:

- Propose to render WikiWords as "Wiki Words" in the page. This makes it easier to read. Obviously this mean one control more ...
- When parsing a page, and there is no page for a specific WikiWord, look for the page 'Wiki Word' (adding a space before each capital).

Advantage : this would allow people coming from other wikis to make links with WikiWords, even for pages like ((Wiki Plugins)), without the need for clumsy parenthesis everywhere.

{syntax type="tiki" editor="plain"}
I want to use backlinks in File Gallery to show me what wiki pages reference the files. This is how I can identify orphaned files. However, this function is so broken that it is unreliable.

What I would expect from this feature is the following behaviors:
#Each file referenced in a wiki page has a single backlink to that page recorded in the File Gallery that contains the file
#Backlinks to wiki pages are uniquely indexed, so that even if there are numerous references to the same file on a page, there is only one backlink to that page shown in the File Gallery, rather than multiple backlinks to the same page
#Removing a reference to a file from a page will remove the backlink to that page from the file in the File Gallery
#Deleting a wiki page will delete all backlinks to that page in the File Gallery

The behaviors I have been able to duplicate in the demo wiki ([http://demo.tiki.org/11x/tiki-list_file_gallery.php?galleryId=6]) are as follows:
#Linking to a file in a wiki page will create a row in the ''tiki_file_backlinks'' table for that page in the File Gallery every time you save the page, even if there is already a row for that page
#If you edit the page and then save it, the backlinks to the referenced files are sometimes incremented, and sometimes not
#Removing the link to a file in a wiki page and then saving it ''does not remove the backlink'' in the File Gallery to that page
#Completely removing a page from the wiki that is referenced by backlinks in the File Gallery will not remove those backlinks, but will instead leave orphaned backlinks to non-existent pages
#There is no reindex or cleanup function built into Tiki for File Gallery backlinks, and no way to manually fix or remove bad backlinks (other than directly editing the database tables)

((doc:InterTiki)) permits to share login, preferences and groups between various Tiki sites.

We need the Sister Wiki too!
http://www.wikimatrix.org/wiki/feature:SisterWiki
Continue discussion here: ((Sister Wiki))

((doc:backlinks)) are very cool. But what about backlinks from other sites?

We could use list from:
http://doc.tiki.org/External+Wikis


Related:
[wish2086|Backlinks between trackers and wiki pages (and maybe forums)]
[wish1768|Tracker plugin to get title and make link to tracker item]

To reproduce:

Have some pages with backlinks

Then, rename DOMpdf to dompdf and the backlinks to dompdf will be broken.

Try to edit a wish on dev.tiki.org and link it to another

Search for "jQuery" and you will see many are missing compared to: http://dev.tiki.org/tiki-view_tracker.php?trackerId=5&status=o&sort_mode=f_41_desc&filterfield=26&filtervalue[26]=jquery&filter=Go

This tracker is made to help filtering and sorting the features vs categories vs options we need to tag a bug/regression/wish with.

For example I have specified a prefix for all of my pages so I can have structures like
STR1_pageName alias pageName
-STR1_Another alias Another
STR2_pageName alias pageName
-STR2_Another alias Another

The issue comes when I want to have consistent naming for my left navigation and on breadcrumbs module. Structures are displayed correctly on the left navigation every single item has that alias. But on the breadcrumbs module the current page you are on is displayed by pages realname. For example pageName >> STR1_Another
I've received complaints from clients that this behaviour is confusing , and I've yet to find the solution to this issue. This may somewhat be related to ((https://dev.tiki.org/item4891|this)) issue. If someone has ideas how to overcome this issue I could try to fix it.

((Plugin alias)) which I am considering renaming __Plugin builder__ permits some amazing things.

((Backlinks)) can be cool for dynamic & efficient information organization.


How can we have the two together?

Perhaps an alias of the REDIRECT plugin which includes semantic wiki link "alias" between the two pages...

More on this later...

The ultimate feature of Amazon and all the e-commerce shopcart systems is the one known as "Customers who bought this item also bought .." or "were also interessted in ..".
The feature would show objects or items that were viewed or bought by previous users in conjunction with the actual item or object.

Idea:
Applied for tiki a new plugin "Relation By Views" would allow to list related wiki pages (or even other objects) in a page likewise to existing backlinks and alias plugins as well as semantic links.
Though, the information is based on previous view counts / his of wiki pages (or other objects) that have been hit by users wihtin the same session as the actual wiki page / object.

The enhancement is obvious: we would make a step further to get implicit relations between pages / objects based on user behaviour.
Just as the advantage in ecommerce is crossselling, we would provide cross-links and encourage readers to have a look to further pages / objects.
In regard to enhancements of the basic shopping cart feature in Tiki 5, this plugin could even be used as a real "customers were also interessted in" feature.

You can see here: ((WantedPages))

Some wanted pages have links to the alias.

If I enter a PluginCategory on page A, and the plugin lists page B, then page B should have a backlink to page A.

If you rollback a page to a previous version, the links to that page are show with a question make instead of a proper link.

Semantic link relationships seem until now only browsable by admins.
Since there is - besides the admin view - no other way to get the semantic relations listed, no one else can get advantage of semantic links and will make no efforts in setting semantic relations.
Concidering the importance of semantics in wikis a plugin seems highly necessary to get the feature of semantic links in tiki started.

__Request:__
Likewise to the Plugin ((Backlinks)) all pages that link to a specific page in a specific semantic relationship.

__So far:__
The semantic_links module is supposed to enable views on semantic relationships.
And indeed, when selecting a semantic type and push the button "show usage", the result shown is exactly what I need.
However this view is only possible for admins.
But since that view for admins is already existing, I would estimate the efforts to implement a plugin as low.

__Plugin idea:__
Relating to the example shown in the documentation of ((SemanticAdmin)) dogs and cats are subsets of animals.
We want the page "animals" to list all subsets by a plugin likewise to

{SEMANTICLINKS (semantictype=subset, page=animals, info=hits|user, noheader=1}
{SEMANTICLINKS}

The result would be:
- dogs
- cats


__Insufficient workarounds:__
Until now the above shown results have to be specified manually as invert relations.
For automatic listing, existing plugins ((PluginShowpages)) / ((PluginListpages)) / ((PluginSearchtitles)) do not work.
So the only workaround without the requested plugin I could image would be to tag the pages "dogs" and "cats" with the a tag "subset-animal" and than use freetags plugin for a listing dogs and cats in the animal wikipage - likewise to the status tags in this tiki. However, that sounds like a bad abuse of tags, since we already got that information saved in our semantic links relationship - we just need to get it readable.

__Related pages:__
Relating to forum discussion with marclaporte:
[http://tiki.org/tiki-view_forum_thread.php?topics_offset=20&topics_sort_mode=lastPost_desc&forumId=4&comments_parentId=38751]

Please read:

[http://irc.tiki.org/irclogger_log/tikiwiki?date=2009-04-18,Sat&sel=117#l113]


Something like:

{img src=images/code.png}%%% {CODE()}
{if isset($objectCategoryIds) and in_array(1, $objectCategoryIds)}
This is the documentation for {$page}. For bug reports and feature requests, please visit [http://dev.tiki.org/{$page}]
{/if}
{CODE}