Category: Feature request

I've been thinking for ages that this kind of option is REALLY needed, and I thought it should not be much coding effort:

Automonitoring each own's posts, through either:
# Add a select box to monitor each own's forum post or tracker submission at post time, in a "per forum post or tracker item insertion" basis, or
# with a user preference for all forums, or all trackers, blogs, etc..
---
Still needed...

I test the field duration on nextdev and suggest some improvements.

I wonder if end-users (not Tiki/Techie) won’t be confused by so many modals, buttons and with many click before starting a simple timer (not happy UX). From the item creation to the timer running it is 4 to 6 six click/selection not to mention other fields that may be in the trackeritem.

Actually to user the timer function you have to give a title, a descriptopn and you have more options. That’s is good if you have ONE item and you will attach to it SEVERAL durations. While you are limiting yourself with the information you can attach with a duration.

It make more sense to me to create ONE item per duration and use the item fields to attach what you need with it. (label, description, date, reason, category, etc). Then using trackers or list plugins you can do whatever you want and use whatever you want. In that case the user can see a simpler version of the timer with a start/stop/pause (reset?) buttons only.

We could have an in the tracker field options an option to have only ONE duration recordable per item simplifying everything. So both case are covered.

There are several cases an Admin want to use the login module but need to add some informations.
To solve this it is possible to use the module in a page or in another module.
This is not very intuitive and require editing work.

Adding a "free text" field will make much easier to add login or registration information (or whatever want the admin/editor).

This tracker item could not be found

The ability to subscribe to a specific structure via RSS feed would be very useful. Currently one can subscribe to an RSS feed related to the entire wiki, but if several groups are using the wiki for different projects or purposes or topics, this may not be at all useful. For example, on the Southern New Hampshire University wiki, we have the online faculty handbook plus a variety of page sets related to different course projects. Most faculty should be alerted of changes to the faculty handbook, which resides in a structure, and some students and faculty may want to track changes to structures involved with specific courses or departments, but few if any users need to be alerted of every change to the wiki as a whole. The ability to generate an RSS feed specific to a structure (and possibly also specific to a category) would be very helpful.

In the Tiki calendar admins can create custom priorities, locations, etc. We need a way to create custom Status, too.

Additionally, it would be nice to let the admin decide which status is the default for newly created calendar events.

See [http://tikiwiki.org/tiki-view_forum_thread.php?forumId=4&comments_parentId=25557|this forum thread] for more info.

Add the new preview tab to other text areas, as seen in {gitlab id=4dc05f6d}

I test the field duration on nextdev and suggest some improvements.

It is really nice and complete however came to me 2 fears when it will be under the hand of end of users (not a Tiki/Techie user).

User will forget it.
Imagine having it running on a mobile device for a training sessions or as employee workclock. People will forget it is running quite easily.

In the tracker field options I suggest we add (simple) alerts parameters:
* enable alert (this duration is running)
* every 15mn, 30mn, hours, 5hours, days... (more seems to me too much, but...)

I suggest also we add a limit (after what we stop the timer)
* After [ ''value'' ] [mn,hours,days] stop the timer (a notification will be displayed)
* Send a mail notification
** to the admin
** to the user/owner of the item
** to this mailbox [''value'' ]

{syntax type="tiki" editor="plain"}
There is already an option to add an unsubscribe link to the bottom of each Newsletter sent out, but this is a new request to be able to add that unsubscribe link to the email's headers.

Here are two articles that go into more detail about what is needed:

[https://digitalmarketinginstitute.com/blog/google-yahoo-email-changes-what-do-they-mean-for-marketers|Google & Yahoo Email Changes 2024: What Do They Mean for Marketers?]

[https://postmarkapp.com/blog/list-unsubscribe-header|List-unsubscribe headers: Here’s everything you need to know]

I copied, and redacted, this from an email header that complies:
{INDENT()}
Subject: *** *** ***
From: "***.com" <***@***.com>
Reply-To: =?utf-8?Q?***.***?= <***@***.com>
To: <***@***.com>
Date: Wed, 10 Jul 2024 18:12:15 +0000
Message-ID: &lt;0c5fce4d5ca3d085d.5d6f829.202120.027e2fd.f6a2d6@***.net&gt;
List-Unsubscribe: &lt;https://***.us11.list-manage.com/unsubscribe?u=0c5fce45a13d85d&id=a2fc1a946&t=h&e=25df82c19&c=024d72f&gt;, &lt;mailto:unsubscribe-***0a64a13dd.02fd-282c19@unsubscribe.***.net?subject=unsubscribe&gt;
List-Unsubscribe-Post: List-Unsubscribe=One-Click
Content-Type: multipart/alternative; boundary="_----------=_MCPart_1392722314"
X-IncomingHeaderCount: 25
Return-Path:
{INDENT}

{syntax type="tiki" editor="plain"}
While it is not wise to create or publish a slider with different height images it happen and the result is really naughty. It push down content then push it up...

See : the show instance of this ticket and https://doc.tiki.org/PluginList-output-control-block#Report_Formatting

As discussed in the January 2020 Tiki Roundtable Meeting it will be great to have a new optional parameter to fix the height no matter the usage (plugin in page or plugin list template).

* Swiper
* Carousel
* Plugin List carousel template


Recording of roundtable is available from: https://tiki.org/Roundtable+Meeting+2020+01

Spamers are very annoying

add antibot captcha for anons to newsletters, calendars and tracker item comments

I believe it would be great to have version numbers added to files and images gallery.
That way someone could have a reference to an archived file that gets sequential numbering, the way wiki pages do.

In my mind it would work exactly the same as on the wiki pages.
Every time a new file version is uploaded, it's version number would increment and that number would be visible as a column in list gallery and file archives. Maybe even rename "archives" to "file history" to make it identical to wiki and show it's working in a similar way.

{syntax type=tiki}
{syntax type="tiki" editor="plain"}
This is the ((Tracking system for Tiki issues)).
If this is your first time, please read: ((How to Submit a new item on the Wishlist))

add automatic sequential id to tracker
or
get read access to internal id

As pointed out by Brendan/drsassafras ([https://tiki.org/forumthread69192-CSS-Compatibility-Issues?topics_offset=14]), the CSS files in trunk are missing vendor prefixes that Bootstrap 4 bootstrap.css normally has. This is because the Autoprefixer script isn't being used in Tiki's current stylesheets workflow. For better browser compatibility (so we aren't supporting only the latest browser versions), it would be good to integrate an Autoprefixer script in our workflow.

I found this script, which could be helpful: https://github.com/vladkens/autoprefixer-php . Or maybe there's another solution that works for the devs who compile SCSS to CSS.

Update: I added Release Blocker category to put this on the front burner. The solution doesn't have to be the script I found, but some solution is needed for Tiki 19 to have maximum browser support.

Update 3/16/2020: This isn't fixed in my local installation; I'd like us to have another look at it. {sign user="chibaguy" datetime="2020-03-16T06:54:46+00:00"}

Update 9/22/2020: This seems to be less an issue as legacy Edge and IE browser usage declines. I can't test IE10 and other instances of vendor prefixes aren't critical. I'm removing the blocker category and changing the status to pending for now, and will check again when we update to Bootstrap 5. {sign user="chibaguy" datetime="2020-09-21T16:21:02+00:00"}

Calendar data is in the "Modified since your last visit module"

However, event data is not findable via the Tiki search engine.

Please see:
http://tiki.org/tiki-slideshow2.php?page_ref_id=565

The canonical should be the "Tiki Suite component interoperability" wiki page.

In 12.x if not risky, else in trunk
The canonical relation for https://themes.tiki.org/tiki-print.php?page=CSS should be:

{CODE()}<link rel="canonical" href="https://themes.tiki.org/CSS">{CODE}

Need to add CAPTCHA/anti-bot option when allowing anonymous submission of articles (tiki-edit_submission.php)

When allowing anonymous users to suggest a new FAQ question, need to include a CAPTCHA to eliminate spam.

{syntax type="tiki" editor="plain"}
It is now done in the category picker and it's very useful.

{img src=show_image.php?id=92}

Add checkbox to tag forum thread as 'expected feedback obtained', or [[SOLVED], and allow filtering and reporting based on that also

Similar to filtering closed item with the chance to reopen, but for support forums and without closing the threaf, but at least indicating to power users that they'd better search first other threads that still require support.

Like the [[SOLVED] manual tag renaming the thread subject in a later stage by the poster of the new thread.

Also show these type of unsolved threads in clear way in the daily reports messages

Add a new panel to Tracker Fields settings for "actions". These will be (to start off with):
* Conditions
** Field Value is/is not/contains : empty or value
** A ((doc:Calculations|Mathematical Calculation)) (should cover everything else)
* Actions
** Show or hide other fields (some mechanism of determining the parent element will be needed to cover tracker edit, legacy edit, wiki plugin tracker and plugin with template)
** Change validation:
*** Add Required (mandatory)
*** Remove all
*** Other rules?

A visualisation (early work)
{img fileId="1342"}

An idea expressed by Mike Kerr (Kerrnel22) at the Nov 2008 Montreal TikiFest:

To include tracker output data in the spreadsheet. This would help make very flexible reports, with charts.