Loading...
 
Skip to main content

Category: Feature request

Request to add a totally new feature or to enhance an existing feature. Also called Request for Enhancement (RFE)
Feature request
Show subcategories objects

Name Type
Unified Index: Add spreadsheet
Searching in spreadsheets is important :-)
tracker item
Unified search - OR on two fields
I want to be able to filter on field 1 having one condition, OR field 2 having another condition.
For example, in the LIST() below I want to be able to display tracker items whose beginning date are in the next N days, OR the ending date being in the next M days:
{CODE()}
{LIST()}
{filter content="7" field="tracker_id"}
{filter field="tracker_status" content="o"}
{filter range="tracker_field_TaskStartDate" from="now" to="5 days"} <-- But here I'd like to be able to filter not on one field but rather on two fields, something like: tracker_field_TaskStartDate from="now" to="5 days" OR tracker_field_TaskEndDate from="now" to="10 days"
(...)
{LIST}
{CODE}
tracker item
Prevent common passwords blacklist can be missed
While translating, I came across a feature that has text, description and help - but it seems to be without function?

Prevent common passwords.

"Prevent common passwords":
"For improved security, prevent passwords in your password blacklist from being used."

If you check the checkbox - nothing happens. I would have expected that some sort of blacklist would have to be entered? Or does it work differently?

Thanks
hman
tracker item
Universal Wiki Edit Button
Please see:
http://universaleditbutton.org/

Related:
*[wish1781|Support for the Wiki creole markup (syntax)]


In testing now on:
http://wiki-translation.com

Commit:
http://tikiwiki.svn.sourceforge.net/viewvc/tikiwiki?view=rev&revision=13295
tracker item
Unkown language applied to wiki pages created from structureds
{syntax type="tiki" editor="plain"}
When creating a new structure, Tiki will automaticlly create the strucutre's wiki pages. However, Tiki does not assign a language to the page. Tiki defaults to __Unknown__. This means that the user must still manually open/edit __every__ created page to set the language properly.

It would be nice if Tiki used the ''__site's default language__'' instead of Unknown
tracker item
Update country list and flag list
This could be a good source:
http://www.famfamfam.com/lab/icons/flags/
tracker item
Update email in mail notifications list from intertiki sites when email replaced in user account in master site
Update email in mail notifications list when email replaced in user account

I did change my email in my account settings at t.o. That email was transfered to dev.t.o properly.
And my mail notifications in t.o where updated properly. __However, the mail notifications in the slave sites (from the same intertiki network) did not get updated__

tracker item
Update HAWHAW to latest version in Tiki 1.9.1

"And from version 5.6 onwards, HAWHAW supports special output for the Lynx text browser. This "archaic" browser is still used today, often by handicaped people with screen readers and other special equipment. HAWHAW's Lynx support allows to create barrierfree applications, which validate Bobby-AAA-approved out of the box and additionally are accessible from each telephone by means of HAWHAW's VoiceXML support."

[http://www.hawhaw.de/]



Todo: add the powered by HAWHAW logo in the tiki-bot_bar.tpl when tiki-mobile is activated.
tracker item
Update module last_youtube_playlist_videos to v3 api (v2 deprecated since 2014)
Youtube has deprecated v2 api, that was used in module last_youtube_playlist_videos
https://developers.google.com/youtube/2.0/developers_guide_protocol_playlists

v3: https://developers.google.com/youtube/v3/docs/playlistItems/list?hl=es

Example of (defective) output, see:
https://doc.tiki.org/Module+last_youtube_playlist_videos

tracker item
Update monitor tracker e-mail adress, when user changes it in prefs
I am monitoring the dev.tw.o tracker and changed my e-mail adress to get the new tracker items to another mailbox.

Well, that didn't happen! ;)
And after re-subscribing to the tracker, now I get them twice - in both accounts.

I guess I'll have to change my mail-adress back and forth to unsubscribe..

amette update: just checked 1.9.x checkbox - more update: changing e-mail back and unsubscribing works flawlessly
tracker item
Update Plugin Jabber to working state again
Update ((doc:PluginJabber)) to working state again, so that we can reuse it for cases in which tiki sites are setup to handle real time chats with xmpp servers, and this could be an improvement to our tiki community by facilitating to aggregate the information ("the wisdom of crowds") of real time chat from irc to xmpp, and display that in activity streams within tiki, etc.
tracker item
Update Tiki importer to current MediaWiki XSD 0.11
I tried to import a mediawiki 1.31 and 1.35
I get the error message, the xml schema is not supported by tiki 22.0

The current spec for the XML format is here: https://www.mediawiki.org/xml/export-0.11.xsd

I tried to put the xsd in lib path from the importer, changed the filename to match the other and add an entry in the file tikiimporter_wiki_mediawiki.php "case '0.11':"
but i'm not an programmer and it doesn't work.
I followed this https://sourceforge.net/p/tikiwiki/code/65119
tracker item
Update Tiki importer to support current MediaWiki XML spec
The existing Tiki importer which supports MediaWiki needs updating to support the latest MediaWiki spec. The Tiki importer seems to be several years out of date. Supporting the latest MedaWiki spec would help increase Tiki adoption from other platforms, where many users have large amounts of existing data that they want - and are currently unable - to migrate over.

The current spec for the XML format is here: https://www.mediawiki.org/xml/export-0.10.xsd

I don’t remember for sure but I think the last supported format in the Tiki importer is 0.6 (maybe 0.4?). If that’s the case it does not look like the changes since then are massive. Certainly it would take time to implement support in the import parser to handle the additional tags, but if they don’t map to anything in Tiki they can just be ignored, and since they were never supported previously, it seems like that would not be much of a loss. In other words I believe that supporting the updates to the format should not be tremendously labor intensive.

Linking to my original forum post and feature request here for details and explanation of why I think this is important and valuable for the Tiki project:
https://tiki.org/forumthread65578#threadId65617
tracker item
Update Tracker Field Types Page
The page describing tracker fields hasn't been updated since Tiki 9.x, so several types are missing.

So either manually update ((Tracker Field Types)), or (even better) write a small wiki plugin to automatically generate that list.
tracker item
upgrade all databases in a multitiki installation in a single go with console.php
upgrade all databases in a multitiki installation in a single go with console.php

with some param like "--site=all":
{CODE()}
php console.php d:u --site=all
{CODE}
tracker item
Upgrade CodeMirror to latest stable version
We are still at 2.25:
http://sourceforge.net/p/tikiwiki/code/46914/tree/trunk/composer.json#l14

The updated zip is at:
http://codemirror.net/codemirror-3.16.zip
tracker item
Missing Tracker Item #1560
This tracker item could not be found
tracker item
Upgrade script
Please see: ((Upgrade script))
tracker item
Add an upgrade script for duplicate cascade
{syntax type="tiki" editor="plain"}
When upgrading Cartograf from Tiki 21.x (possibly 24.x?) to 27.x we found that "[https://gitlab.com/tikiwiki/tiki/-/merge_requests/2170|duplicate cascade]" wasn't set on the child trackers to duplicate features when a map is duplicated.

This used to happen always before this option was added but it would be nice, espescially if "Cascade actions" is set to "All" on the ItemLink fields, then -+duplicateCascade+- should be set to "Yes" (1).
tracker item
Upgrade Tiki tests to use PHPUnit 11.x
{syntax type="tiki" editor="plain"}
Tiki 28.x requires PHP 8.1 so we are at PHPUnit 10: https://phpunit.de/supported-versions.html

We should [item8700-Tiki26-Tiki27-and-Tiki28-require-PHP-8-1-Discussion-about-bumping-up-the-requirements-to-PHP-8-2-or-8-3|move to PHP 8.2] or:

"Write your tests for PHPUnit 11.x and run them on PHPUnit 6.4 - 11.x
The polyfills have been setup to allow tests to be forward-compatible. What that means is, that your tests can use the assertions supported by the latest PHPUnit version, even when running on older PHPUnit versions.

This puts the burden of upgrading to use the syntax of newer PHPUnit versions at the point when you want to start running your tests on a newer version. By doing so, dropping support for an older PHPUnit version becomes as straight-forward as removing it from the version constraint in your composer.json file."

https://github.com/Yoast/PHPUnit-Polyfills
tracker item
Upgrade to Google Maps Javascript API V3
Importantly, Google Maps Javascript API V3 is simply just faster than v2. Another big plus is that V3 does not need an api key. The currently used v2 api's key verification is known to have problems. It is also deprecated by google.
Read more here:
http://code.google.com/intl/fr/apis/maps/documentation/javascript/basics.html

Perhaps something for Tiki7?

Or would not it be part of Tiki6 as optional and experimental?
tracker item
Upload and Reference File/Image Resources in one Step
Hi there,

it is very unhandy to attach files or include images in wiki pages, articles or any other content a user provides. Until now, there are means like:

a) Upload a file to a file gallery and reference it manually using the link given.
b) Upload a file to a wiki page and reference it manually.
c) Try using the WYSIWYG editor and realize it does not upload the image.

Well, what I did is I added some quicktags to your code that opens a custom upload file dialog with a preselected file gallery. The user can browse, upload and add the file into his content in one step. Basically it uploads the file and appends the wiki code at the cursor position.

I will attach you all my environment...there is a file itb_readme.txt in the root which describes in chapter 3 all the changes I do...maybe somebody of your development team assesses this as an important feature and can leverage some code...

Regards,

Maic
tracker item
Upload image, Wiki page; It should be possible to drag a picture over a text area for Tiki to understand it has to set an IMG plugin
In 2023 it should be possible to drag a file over a text area in a wiki page and having Tiki to understand what to do (IMG, Mediaplayer, etc...).
tracker item
URL Rewriting Revamp: adding to Tiki log or error log so we catch them all through usage
There was a revamp of ((URL Rewriting Revamp)) in Tiki11, but after the revamp, we found edge cases.

Adding them to logs would be easy and make sure we find anything left.

Also, things like http://dev.tiki.org/abcdef.php should
* offer a nice error message
* be logged so we know about broken links
* Offer a search box (if search is activated) with content of the URL in it?
tracker item
URL structure
{syntax type="tiki" editor="plain"}
When we create a new wiki page we write {CODE()}((My New Page)){CODE} and get the URL http://example.com/My+New+Page

Is it possible to get the following URL structure

http://example.com/my-new-page

i.e. all lower case and hyphens "-" instead of plus sign "+" ?
Thank you
tracker item
Show PHP error messages