Category: Feature request

Similar to {wish id=5778}

https://indieweb.org/hashtags
https://indieweb.org/hashtag-cache

See also ((Freeform Relationships))

Please see:
http://www.wikimatrix.org/wiki/feature:CREOLE%20support
http://www.wikicreole.org/wiki/TikiWikiCMSGroupware

Related:
http://dev.tiki.org/Why+Wiki+Syntax+is+Important
http://dev.tiki.org/tiki-index.php?page=2007-07-18+IRC+MediaWiki+discussion&highlight=creole
http://tiki.org/RFCWiki


Related:
*[wish1531|Wiki markup for icons]
*[wish1805|Universal Wiki Edit Button]
*[wish2102|Support some of the MediaWiki syntax that doesn't conflict with TikiWiki syntax]
*[wish1843|Infoboxes like MediaWiki/Wikipedia, but making use of trackers to be future-proof]
*[wish1220|MediaWiki import script]

Support inclusion of media in blogs to provide podcasting, vodcasting, etc.

- Attachment of media files to blog posts
- Association of URLs to other media files on Tiki or elsewhere to blog posts
- Automatic recognition of relevant data from media files using getid3
- Creation of fields in database to store relevant media data
- Creation of enclosure and media XML tags in RSS feed
- Display of media controls in blog entries
- Test using iTunes and iPod, iPodder, Thunderbird, among others

This should be an optional feature, admin through the Blogs Admin panel
Should allow choice of db or file storage, but probably file storage will normally be used, as media files tend to be quite large.

Existing image attachment functionality in blogs will need substantial improvement to support this.

Please go to "Syntax Examples" here:
http://www.wikimatrix.org/compare/TikiWiki-CMS-Groupware+MediaWiki

Please also see:
http://meta.wikimedia.org/wiki/Help:Wikitext_examples

Some syntax could be supported as it doesn't really conflict with the existing.

__Basic formatting markup__
{img src=images/code.png}%%% {CODE()}
You can ''italicize text'' by putting 2 apostrophes on each side.

3 apostrophes will '''embolden the text'''.

5 apostrophes will '''embolden''' and ''italicize''
'''''the text'''''.
{CODE}


__Signature/timestamp__
{img src=images/code.png}%%% {CODE()} You should "sign" your comments
on talk pages:
- Three tildes gives your
signature: ~~~
- Four tildes give your
signature plus date/time: ~~~~
- Five tildes gives the
date/time alone: ~~~~~ {CODE}

__Section headings__
{img src=images/code.png}%%% {CODE()} == Section headings ==

''Headings'' organize your writing into
sections.
The ''Wiki'' <u>ab</u>
##software can automatically
generate a [[table of contents]] from them.

=== Subsection ===
Using more "equals" (=) signs creates a subsection.

==== A smaller subsection ====

Don't skip levels,
like from two to four equals signs.

Start with 2 equals signs not 1
because 1 creates H1 tags
which should be reserved for page title. {CODE}


However, links & images could be more problematic.

Related:
*[wish1531|Wiki markup for icons]
*[wish1191|Wiki editing: Preview with diff, like Mediawiki]
*[wish1843|Infoboxes like MediaWiki/Wikipedia, but making use of trackers to be future-proof]
*[wish1781|Support for the Wiki creole markup (syntax)]
*[wish1220|MediaWiki import script]

It will be nice to allow the setting of limit of levels to show for maketoc:
{CODE()}
{maketoc maxlevel=2}
{CODE}
will cause only ! and !! headers to be shown, not !!!.

nothing more to say...

We can now use the login box but it's not very obvious. There should be an icon / button somewere in tiki-adminusers.php

Just after creating a user or adding to a group would be a good time to Switch User and see what (s)he sees.

Synchronize a Tiki Forum with a (Mailman) Mailinglist

a) Forum outbound email (Regression)
In Tiki 11 it was observed that Tiki cannot send emails out from a forum post to a mailinglist. This problem might be produced by Zend/composer. This is a regression. It works in Tiki9.5 (not clear about Tiki10). More Info:
https://dev.tiki.org/Regressions+in+11x
https://tiki.org/tiki-view_forum_thread.php?comments_parentId=47927

b) Forum inbound email (Error)
In Tiki 9.5 it was observed that postings from a mailinglist are shown in Forum with wrong author sometimes. Users of Forum and Mailinglist are not necessarily identical. Some users are registered at forum and mailinglist, and they are recognized by Tiki via email address correctly. Every now and then (no clear pattern yet) an inbound email from mailinglist is registered in the forum with wrong username and wrong email, apparently random chosen by someone else who wrote earlier to the list and was listed in the forum with his post.
In addition Tiki Forum breaks threading if the email topic is changed. This might be intentional and due to lack of internal handling of emails' Message-Id header.

c) Tiki Forum header (Wishlist)
Tiki recognizes whether an inbound email was sent by forum or not. This is done by a header. This header should be up to configuration, because it is not possible to connect two different Tiki forums with one mailinglist.

d) Demo and Showcase
Unfortunately it is not possible to construct a showcase easily, because the setup of Tiki plus Mailman is quite complex (spam protection would require an isolated setup which cannot spam real world) and the pattern seems to be dependent on race conditions.

We have no syntax for expressing we want an unlimited number of LIST plugin results.

Using mysql Full-Text indexation, one can express the idea with a huge number like so :
{CODE()}{LIST()}
{filter field="object_type" content="trackeritem" }
{filter field="tracker_id" exact="1"}
{pagination max="99999999"}
{OUTPUT(template=)}
{LIST}{CODE}

It is ugly but it does the job in an expressive way (people will understand 99999999 does not mean exactly 99999999).

Using Elascticsearch, the above will fail with an obscure error message « all shards failed » because Elascticsearch has a hard limit which defaults to 10000 but it can be changed at the server level.
See ''Results Per Query'' in [https://www.elastic.co/guide/en/app-search/current/limits.html]
So I need to use:
{CODE()}{LIST()}
{filter field="object_type" content="trackeritem" }
{filter field="tracker_id" exact="1"}
{pagination max="9999"}
{OUTPUT(template=)}
{LIST}{CODE}
Because "10000" looks like I really want "10000" rather than unlimited.

__It is bad that the LIST plugins need to be rewritten when one changes the unified search indexation method.__ Also, it is not obvious why it fails.

__SUGGESTION__ I feel we should allow for a real syntax for unlimited results such as :
{CODE(caption="SUGGESTED SYNTAX" theme="default")}{pagination max="-1"}{CODE}

Then if Tiki uses Elascticsearch searches it could look up the ''Results Per Query'' value (or assume 10000 for starters) when "-1" is encountered.
If Tiki uses "Mysql Full-Text search" if should not have a limit (or it should have a very high one).

We should have system RSS feeds which links to:
http://info.tikiwiki.org/tiki-articles_rss.php


And this should be hard-coded in tiki-admin.php

The actual plugin table of content (toc) seems to work only within structure.
It is a bit confusing as the plugin is always available (even when you don’t use and didn't enabled structures). If the user miss the little text that says it work with structure from the plugin help modal then it can turn into hours of frustrations.
''Note: from the plugin modal editor window it is not possible to understand it work with structures only).

It would be nice if we can use it without being in a structure, to set a table of content on a single page. A table that could be designed per usage.

The alternative to use auto-toc is too heavier IMO and still doesn’t clean the confusion of having a common plugin you can’t use. (most of other competitor of Tiki just have this working on any page in a few clicks).

PS: I found impressive we have so many ticket for the table of content (common and easy to use feature) for 2018.

Table of contents in the pdf produced by mpdf doesn't respect page orientation param set in plugin pdfpage.

Would be great if TableSorter automatically dropped columns that do not contain data, i.e. a columns of zero's.

This would allow for optimized viewing of more data in one table.

Currently, 'non-critical' columns can be dropped "when browser is too narrow" - from my test, this is only be done manually, but choosing the filters for the fields you would like dropped. I don't understand the rating, 1 - 6, it doesn't seem to have any effect. My set-up is main (center) column for tables and one left column (search bar, last changes, etc.). All my columns do not fit in the main column so I have to scroll right, yet half these columns on the right are assigned '6' as least important, and theoretically should be dropped, but are not.

For example, in farming, you may have 10 or 20 tractors, who do various work (fertilizing, spaying, planting, bailing). While some overlap and can do multiple tasks, most are assigned repetitive tasks. So if I want to see tractors that bail and I have it as the last column on the right, it would be good have all the other columns automatically drop because a high probability of them all being zero.

Thanks,
Mike

The possibility of tagging individual files in file galleries is missing. This is both natural and necessary. Any archival / encyclopedic / knowledge base use of a wiki would need this. The tags feature inexplicably misses it.
Shouldn't be difficult to fix.

Tags: Add a modern beautiful and advanced filtering with HTML5 and jQuery, such as Filtrify
https://github.com/luis-almeida/filtrify
http://luis-almeida.github.io/filtrify/
MIT Licensed

We would use it to let users browse more easily Profiles from https://profiles.tiki.org

Demos:
* Multiple categories: http://luis-almeida.github.io/filtrify/movies.html
* Load images with Lazy Load: http://luis-almeida.github.io/filtrify/lazyload.html
* Add pagination with jPages: http://luis-almeida.github.io/filtrify/jpages.html

Please see:
http://phplayersmenu.sourceforge.net/demo.php

phplayersmenu has 5 types.

$types['vert'] = 'layersmenu.inc.php';
$types['horiz'] = 'layersmenu.inc.php';
$types['tree'] = 'treemenu.inc.php';
$types['phptree'] = 'phptreemenu.inc.php';
$types['plain'] = 'phptreemenu.inc.php';

Tiki is only using 3.

"Two classes are provided to prepare also accessibility solutions, i.e. "server-side based" tree menus (that have just the same look of the above mentioned JavaScript-based tree menus, but require the PHP support on the web server) and plain menus that do not require the JavaScript support to the browser."

Related:
Menu items with link type options (framed, new window, replace)
http://dev.tikiwiki.org/tiki-view_tracker_item.php?itemId=521


We could also let the user determine an icon for each menu item.

Well explained here:
http://twiki.org/cgi-bin/view/Plugins/ActionTrackerPlugin

We'd output in htask microformat
http://microformats.org/wiki/htask

And we'd need some sort of reporting. All tasks assigned to person X.

We currently usually do this with ((doc:trackers)). But doing it fully in the wiki would be more flexible in some contexts.

The system should be able to send email reminders at a certain date. This could be used as well to schedule actions / Email reminders as explained here:
http://www.youtube.com/watch?v=8XwyhSEqTs0

This is part of what is needed for ((Project management))

The application of style templates by category is nice, but it would be nicer if there was an option to have the template apply to all current and future children of the category.

The "Tiki User Registration Request" email that is sent to admins when a new user registers may not contain enough info for the admin to make a decision as to whether or not to approve the registration. The only link in that email automatically validates the user without any second chance (if the admin thought that after following that link he would be given a chance to review the new user info before validating the unknown user, he will be mistaken).

templates/mail/moderate_validation_mail.tpl should be improved to include any user tracker info that the new user has submitted, or provide a link to view any such user info.

This would avoid this type of issue:
http://tikiwiki.org/tiki-view_forum_thread.php?topics_offset=1&forumId=6&comments_parentId=21274

Maybe at each release, we could add one test of the DB to see if the most recent sql additions were done.


phplist does this well. Once click and your DB is in the right format.

I upgraded from php4 to php5. I had some sites with white pages and nothing in the error log.

Finally, it was:

"this web application requires mysqli php extension. We have enabled it and it look ok now."

Tiki could have detected and reported this.

Move discussion here:
((Test server compatibility))

tiki-admin.php?page=gal tells me if GD or Imagick is installed. Nice.

But sometimes, it's installed, but it doesn't work as it should. To rule out that the problem is with Tiki, here is an example of a simple php to test GD in real life. It would be nice to add to tiki-admin.php?page=gal

{img src=images/code.png}%%% {CODE()}
<?php
header("Content-type: image/png");
$im = @imagecreate(110, 20)
or die("Cannot Initialize new GD image stream");
$background_color = imagecolorallocate($im, 0, 0, 0);
$text_color = imagecolorallocate($im, 233, 14, 91);
imagestring($im, 1, 5, 5, "A Simple Text String", $text_color);
imagepng($im);
imagedestroy($im);
?>
{CODE}

Similar to ((doc:PluginAnnotation)) for images.

This would make it easier for people to know who added what comment, when and to distinguish the main content, from notes.

Similar to ((doc:PluginMouseOver)), but should be easier to use.

Related:
{wish id=1409}

The tiny A B C D link navigation help (can be found on tiki-contacts.php) cannot work with several languages (ie hebrew) as it have been implemented a long time ago.

It should be nice to polish it or to change it so it can work with any language.

phpBB is a popular open source forum software.
Sometimes, a forum is not enough.
So, the data must be migrated from phpBB to Tiki forums...

If you want to help:
Please post links to similar scripts.
ex.: phpbb to invision board, etc
If/when we do a script, we should do for all major forums.
---
__From kerrnel22 on 11/20/07:__

I have almost completed an integrated TikiWiki forum migration tool for 1.9.8.x and 1.10. Initial release will be to migrate only Tiki forums from one Tiki install to another. However, hooks are in place, and the intention is there, to work on extending the migration tool to importing of phpBB2 (or any other forum software) into Tiki. If you would like more information, email tiki.kerrnel@kerris.com. I expect a general release of the forum migration tool (for Tiki forums only) into cvs of both branches for beta testing by December 1/07. If all goes well, I'll have something released for phpBB2 migration prior to Dec 31.