Category: Feature request

The form element "select" in forms of Tiki Forum and in other features of Tiki is missing the term (selector) "custom-select" as part of the CSS class to render it correctly in the Bootstrap theme design.

Making this simple change would greatly improve and unify the UI of Tiki with the currently available Themes.

See attached screen shot of added term in inspector for Tiki Forum feature.

{img fileId="1380" thumb="box"}

Tiki 1.9.x forums have improved nicely over the last few months. One more thing to make them cleaner is to make the default threading to plain.

Let's face it, it looks cleaner :-)


{img src=images/code.png}%%% {CODE()}
===================================================================
RCS file: /cvsroot/tikiwiki/tiki/comments.php,v
retrieving revision 1.31.2.50
diff -c -r1.31.2.50 comments.php
*** comments.php 11 May 2007 23:15:50 -0000 1.31.2.50
--- comments.php 31 May 2007 04:01:10 -0000
***************
*** 386,392 ****

if (!isset($_REQUEST["comments_style"])) {
// TODO: Make this an option.
! $_REQUEST["comments_style"] = 'commentStyle_threaded';
} else {
$smarty->assign('comments_style_param', '&comments_style='.$_REQUEST['comments_style']);
$comments_show = 'y';
--- 386,392 ----

if (!isset($_REQUEST["comments_style"])) {
// TODO: Make this an option.
! $_REQUEST["comments_style"] = 'commentStyle_plain';
} else {
$smarty->assign('comments_style_param', '&comments_style='.$_REQUEST['comments_style']);
$comments_show = 'y';

{CODE}

the problem is moderation of forum posts.

Does anyone know of a migration script / strategy for moving tiki forums
from one Tiki to another?

I want to move this Galaxia forum:
http://tikiwiki.org/tiki-view_forum.php?forumId=11
to:
http://workflow.tikiwiki.org/

The themes forum
http://tikiwiki.org/tiki-view_forum.php?forumId=14
to:
http://themes.tikiwiki.org/

And the Multilingual/i18n <tiki-view_forum.php?forumId=13> forum:
http://tikiwiki.org/tiki-view_forum.php?forumId=13
http://tikiwiki.org/tiki-view_forum.php?forumId=10
http://tikiwiki.org/tiki-view_forum.php?forumId=15
http://tikiwiki.org/tiki-view_forum.php?forumId=7
http://tikiwiki.org/tiki-view_forum.php?forumId=8
http://tikiwiki.org/tiki-view_forum.php?forumId=9
http://tikiwiki.org/tiki-view_forum.php?forumId=16
to an eventual i18n.tikiwiki.org

Forums tools and names support Tiki Multilingual feature but the breadcrumb that doesn’t display translation.

When deleting forum posts / topics it just asks to confirm without telling the user again what he/she is trying to delete.

This permits mailing-list-like functionality.

After, adding or removing a user from a group dictates which forums they can read and get notifications for.

Maybe we should use the newsletter functionality as it already handles group inclusions and individual opt-outs...

Like newsletters, it should be possible for people to remove themselves from a mailing. Better than 1.9.7 newsletters, it should also be possible for the admin to see who removed themselves.

At https://tiki.org/forum26 I see 2 search forms.
One at the top (look to me like the website general search)
One inside the forums "boundaries", above the forum title.

When I use the second Search form I redirected to the Tiki search page which doesn't allow me to search by forums, author, etc.
Basic tools a forum should have.

It should be possible to have dedicated tools (or at least how they look like) to search with Forums object fields.
We have everything needed in the unified index
parent_object_type
parent_object_id
lastpost_modification_date
object_typecontents
post_author
score
Etc...

I used https://tiki.org/forumthread78791-New-Wiki-pages-wont-take-the-Groups-default-Category and https://tiki.org/forumthread77665-What-is-the-Markdown-syntax-for-LaTeX-equations on Firefox.

It is about the first comment header and the last message elements.
Better separation between "section" is required (especially on mobile).

{img fileId="1868" thumb="box"}

{img fileId="1869" thumb="box"}

{img fileId="1870" thumb="box"}

{img fileId="1871" thumb="box"}

{img fileId="1872" thumb="box"}

{img fileId="1873" thumb="box"}

In forums:

Topics are first level (discussion starters)
Message are replies. This uses the same code as comments (used in wiki pages, image gallery, etc) and has threading.

In 1.9.x, an admin can move a reply to another topic. This is of limited use. It is as if the admin decides "Your answer is more suited to another question"...

What would be much more useful:
To change a topic (and all threaded replies) to another forum.

So an admin could start with one general forum, and create more specific forums if/when the volume of messages justifies it. Right now, the admin has to plan all these forums in advance. And a list of empty forums is not very inviting...

If someone starts a thread in the wrong forum, it should be easy to correct.

CLIP from my whining about why the search doesn’t work in TW.



#1 - why isn’t there a proper SEARCH ?

- to start this off can we at least agree on a couple things:
o standard search for - RED BALL would search on RED AND BALL
o TW does RED OR BALL – which is WRONG!!

- BASIC search should be capable of:
o RED BALL = RED AND BALL
o “red ball” = only match “red ball” as quoted
o and then, maybe RED or BALL = RED OR BALL


with a little more digging and some input from marclaporte, redflow and mose I think I have figured out the problem:

- TW supports the concept of FULL TEXT SEARCH (FT)
- this allows user to (from example above) do a search like “+red +ball” to achieve “red AND ball”.
- but these is a bug in concept in searchlib - function _find()
- if FT is set then _FIND does the right thing by doing a MATCH AGAINST sql query
- HOWEVER – if it doesn’t find any results it ALSO will do a simple (i.e. non-FT) search
o in concept this is silly since it defeats whole point of doing FT in the first place
o also, it generates an sql error because for simple search a REGEXP query is done which will choke on the + signs in the search string

"Fullscreen Edit" is a new cool feature of 2.x

Quicktags are kept, but Wiki & Plugins Help are missing so it makes editing less enjoyable.

"Edit Summary" is missing as well. Maybe it's intentional?

To allow admins to set an exclusion list of pages to be included in the list of top pages or rankings. Useful for excluding pages like home pages.

Please see: ((Project Management)) and ((TrackerToGanttChart))

Tracker form can be used as contact forms and subscription forms.

Especially when it comes to subscription form the GDPR regulation from 2018 makes it necessary to do some kind of validation - usually with a validation email similar to the validation email Tiki optionally sends out when a user registers.

If I would use Tracker forms for validation of subscriptions or registrations (ex for conferences) the tracker should have the option to automatically send a validation email and a filter (index!) to display validated and non-validated items and further more an option to manually validate ... in case there has been personal or phone contact between office and registrant.

There is a validation option in Trackers, but that seems to address another problem and is not usable for the described type of use cases.
See here: ((doc:Tracker-Field-Validation))

Feedback welcome and thanks for considering,
regards
Torsten

I would suggest the creation of two simple tikilib functions: have_permission() and feature_enabled(). These functions need to take the name of a Tiki permission or feature respectively, and should return a boolean if the permission is set, or feature enabled.

These two functions are obviously pretty simple to implement. After their introduction, all Tiki applications should be migrated to use them (a job I would suggest may take until 1.11 or later!).

The benefits of doing this include:

* Less programatic reliance on global variables
* No need to read entire permissions or feature database tables to return each page
* Lower in-memory information required to run the application
* Allows for finer grained permissions and feature control without affecting scalability
* Permissions and features can subsequently be replaced by more sophisticated, scalable, usable or effective solutions later without futher disruption to applications.

The last point is the key here: Whilst there are currently hundreds of permissions and features, there are lacking in places where they should exist. Clearly adding yet more permissions and features isn't really viable.

Also, having a replaceable solution means it would be possible to move to an "entitlements" based solution without breaking the entire system. Entitlements may offer a way to provide extreme customisation abilities, with scalable and flexible permissioning, control of features etc.

The subject of permissions and feature control is obviously broad. This RFE only aims to facilitate the future discussion and adoption of a more generic model for control of the application.

! How to choose the right software library for tiki.

After reading the article that explain the best way to choose a software library for tiki (((https://dev.tiki.org/How-to-pick-a-software-library|pick_a_software_for_tiki))).

Related to the task ((https://avan.tech/item71402-Generate-Avatars-in-Tiki-until-users-upload-their-own|Generate Avatars in Tiki)), some research has been done to to try to find out witch libray will be good for tiki.
The choice of libray was based on some criteria:
- number of download
- number of dependances
- number of stars
- and easy to implement

The fist one is ((https://packagist.org/packages/multiavatar/multiavatar-php|Mutliavatar)), the library does not required extenal depences and everything has been design with a single class.
easy to use and generate SVG image with can be stored.

The sencond is ((https://packagist.org/packages/laravolt/avatar|Laravolt Avatar)) it has a large community and have more that 1M download.
It has been design to be used in laravel project but can be used in other project, but it has so much pendencies and some of symphony, knowing that tiki also used to dependcy of symphony.
It can generate PNG or JPG file or SVG.

And the last one is ((https://github.com/splitbrain/monsterID|monsterID)), it a good tool, but i realised that, all avatar are PNG file created and stored on a folder ready for use, with can be easy replaced by ((https://packagist.org/packages/multiavatar/multiavatar-php|Mutliavatar)).

Some library where design to be use only with laravel (most) or for wordpress.

Like Wikipedia



In a more advanced form, the references could be kept in trackers, as Tiki would be a
[http://info.tikiwiki.org/Use+Cases#Bibliography_D_|Bibliography Management System].


Related:
[wish1769|Bibliography management system (references)]

This is an RSS feed:
http://sourceforge.net/export/rss2_projsummary.php?group_id=64258


It's not the traditional way of using RSS but it can be very useful :-) It permits us to get up to date info (Ex.: number of devs, number of downloads, etc.) from SourceForge, using RSS. We can then publish on http://info.tikiwiki.org/



This idea could be used for serving ads.
http://en.wikipedia.org/wiki/Ad_serving

This is also in the same idea as:
http://dev.tikiwiki.org/Connect
http://tikiwiki.org/Viral+Tiki

Two immediate uses
# Manage the footer of all *.tikiwiki.org sites from one place
# Permit to push news & calls to action (Current version of Tiki, vote for Tiki in an Award, new release, etc)


Tiki5 as of now:
http://tikiwiki.org/tiki-index_raw.php?page=rsstest

Tiki4 as of now:
http://info.tikiwiki.org/tiki-index_raw.php?page=DeployWikiPageContentAsRSS



Related
{wish id=1396}

((doc:PluginCode)) doesn't show colors for php code, as it should according to doc page:
[http://doc.tikiwiki.org/PluginCode]
Tried with param colors=>php or colors=>phpcode:
{CODE()}
{CODE(colors=>php)}
/** Return system defined temporary directory.
* In Unix, this is usually /tmp
* In Windows, this is usually c:\windows\temp or c:\winnt\temp
* \static
*/
function tempdir() {
static $tempdir;
<b>$tempdir = '../tmp';</b>
<b>/*</b> if (!$tempdir) {
$tempfile = tempnam(false,'');
$tempdir = dirname($tempfile);
@unlink($tempfile);
} <b>*/</b>
return $tempdir;
}
}
{CODE}
{CODE}

And it returned:
{CODE(colors=>php)}
/** Return system defined temporary directory.
* In Unix, this is usually /tmp
* In Windows, this is usually c:\windows\temp or c:\winnt\temp
* \static
*/
function tempdir() {
static $tempdir;
$tempdir = '../tmp';
/* if (!$tempdir) {
$tempfile = tempnam(false,'');
$tempdir = dirname($tempfile);
@unlink($tempfile);
} */
return $tempdir;
}

}
{CODE}

---
Update: RFE for plugincode:
Why not using "wrap=>1" as default param instead as "wrap=>0"?

Not totally sure if this is feature request, bug, or lack of knowledge. Basically I need some way of supporting maketoc with WYSIWYG pages.

Hello, especially the Admin UI revamp team.

I love the new Tiki Admin UI, whilst I am quite massively missing a few nice ideas or our old one. When I supported the idea of a more WP-like approach, I never thought we would lose the old feature tiles panel, which has a lot of advantages in respect of time saving.

I suggest, that we could put it into a module and then add it to the list of standard admin modules, that can be optionally loaded into the admin dashboard.

Aswell there are a number of administration places, where the new admin dashboard style is not yet applied. I assume that is just a matter of time and ressources.

Comments welcome.
Best regards,
Torsten
---

"__Getting Things Done__ (commonly abbreviated as __GTD__) is an action management method of the __David Allen Company__, and the title of the book by __David Allen__ that describes the method. Both __Getting Things Done__ and __GTD__ are registered trademarks of the David Allen Company.

__GTD__ rests on the principle that a person needs to ''move'' tasks out of the mind by ''recording'' them somewhere. That way, the mind is ''freed'' from the job of ''remembering'' everything that needs to be done, and can ''concentrate'' on actually '' performing'' those tasks. What distinguishes GTD from other time- or action-management systems is the idea of __''grouping tasks'' by the context__ (defined as a place or set of available resources) in which they are to be __performed__."

http://en.wikipedia.org/wiki/Getting_Things_Done


TikiWiki can be configured for this.

http://www.priacta.com/Articles/Comparison_of_GTD_Software.php

Currently, when you create a process and initiate an instance, the user is prompted to name the instance, presumably as some way they can remember it in their own jumble of process instances (or tickets, as I like to call them).

I would like the admin to have the ability of eliminating that need on a per-process basis, and instead automatically naming the instance with the instance ID. This should give people the flexibility, if they want, to allow the user to create a memorable moniker, or allow it to traditionally take on a "ticket number" type of designation.

It really depends on the environment that the workflow is being used in. In a high-volume workplace, it may be best to use a ticketing style of identification. In a smaller-volume workplace, I can definitely see how custom names would be beneficial.

If I get time, I'll work on this.

This feature request is for a tool that would enable easy quoting and referencing of any content on a Tiki site, for example, to quote a forum post on a wiki page, or one blog post in another, etc.

Maybe it would be activated by clicking a switch in a module (side column), then selecting some text. Then in the referencing page, when you paste, it pastes not only the selected text but also wikiplugin syntax in which the text is the data and the url of the text's source as a parameter. The quote is displayed like a quote plugin output, and the source is displayed as a link.

The use case that started the thinking about this was a question about how to easily cite Tiki forum posts from a wiki page, without a lot of copying and pasting. Rather than hardcoding it to be forum and wiki specific, a global copy-paste site content referencing tool could be useful in other ways.