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
Smarty tabset showing tabs for tabs that are inside permission checks
{syntax type="tiki" editor="plain"}
When a tabset contains tabs that are surrounded by permission checks such that none of the contents will show because the user has not the perm, the tab still shows (because the tabset collects the existence of tabs without checking perms).

This is very ugly to have tabs that users won't see anything in them.
tracker item
Smarty Template indicator: add a note for tiki.tpl and error.tpl after the doctype
[https://sourceforge.net/p/tikiwiki/code/34340/|This change] was made because IE7 & IE8 has trouble with a page which starts with "<!-- TPL:". However, for a new developer, it's useful to know about tiki.tpl and error.tpl

Suggested layout:

{CODE()}<!DOCTYPE html> <!-- TPL: tiki.tpl is used as the global page container -->
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<!-- TPL: header.tpl --><meta http-equiv="Content-Type" content="text/html; charset=utf-8" />{CODE}


{CODE()}<!DOCTYPE html> <!-- TPL: error.tpl is used as the global page container -->
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<!-- TPL: header.tpl --><meta http-equiv="Content-Type" content="text/html; charset=utf-8" />{CODE}
tracker item
Smarty update from 3.1.14 to 3.1.15 with patch or wait for 3.1.16
{CODE()}"An {include} with a cache_lifetime within {block} tags could create wrong results in certain situations.
For that reason 3.1.15 is more restrictive and created an error."{CODE}

source:
http://www.smarty.net/forums/viewtopic.php?t=24599

Should be fixed in 3.16:
http://code.google.com/p/smarty-php/source/detail?r=4797
tracker item
SMTP Configuration from inside Admin Interface
A lot of people who install this aren't doing it via Fantastico and trying to change email settings to suit your hosting provider is a pain. Editing the php.ini isn't always wise either because what works for one app will break another. I know that you can copy the php.ini to the directory, but that's something of a security risk. There's a reason that the default php.ini is stored outside the web root directory.

I know that I see a lot of users posting on the TikiWiki forums with questions about configuring SMTP.
tracker item
Social Bookmarking any content (ex.: digg this) (add the patch to the main code base)
Like Ricks99's great work:
http://tikiwiki.org/tiki-view_blog_post.php?blogId=26&postId=302

current plugin (from mods)
http://tikiwiki.svn.sourceforge.net/viewvc/tikiwiki/mods/trunk/wiki-plugins/submit/wiki-plugins/wikiplugin_submit.php?view=markup

Ex:
http://www.stumbleupon.com/tag/tikiwiki/

Please see:
http://www.addthis.com/
tracker item
Social bookmarking within Tiki
See ((Social Bookmarking Within Tiki)).
tracker item
Social Networking-type transactions between members
While Tiki has a "friendship" feature, it is so basic, that I am putting as "missing". What is missing is proper Social Networking with "transactions" between community members (Ex.: [http://www.nomadics.it/|hospitality exchange network], carpooling, dating service, etc) with reputation system. Something like LinkedIn, Facebook or the www.phpbeer.com project.

Since this is a vast project, we'll coordinate at ((Social Networking))
tracker item
Softaculous: On a fresh install, MyISAM is used instead of InnoDB
Since Tiki 18x, fresh installs of Tiki use InnoDB by default. MyISAM still works but InnoDB is recommended: ((doc:InnoDB)).

((tw:Softaculous)) offers a one-click installer. This installer should be updated to use InnoDB.

Reported by Rafael on the Tiki chat:
https://matrix.to/#/!SLEgqpTNTlGYAhzNvK:gitter.im/$6lFlw5LfooOs5YXvWy_n9sXPjAamMcFFDgCkJcCD0aY?via=matrix.org&via=gitter.im&via=sans-nuage.fr
tracker item
Admin Interface; Some Admin actions reload on a page outside the admin Control Panels
{syntax type="tiki" editor="plain"}
Verified also on Tiki25, login as Admin, go to settings, Control Panels, go to /tiki-admin.php?page=search, click on the rebuilt index button it open a modal.
All this is the control panel area.

If you validate the action and rebuild the index you will be thrown outside the Control Panels area (/tiki-search-rebuild).

{img fileId="1664" thumb="box"}
{img fileId="1663" thumb="box"}

This is related to the action page itself. If you use the top admin bar rebuild-index you will be also exited from the Tiki administration pages.


List of pages/actions with the issue:
* Control panel, go to /tiki-admin.php?page=search, click on the rebuilt index button it open a modal, validate the action (/tiki-search-rebuild)
* Control panel, go to /tiki-admin.php?page=general, tab navigation, Sitemap protocol click on the play button => tiki-admin_sitemap.php
* Control panel, go to tiki-admin.php?page=textarea#contentadmin_textarea-2, click on the link tiki-plugins.php
* Control panel, go to tiki-admin.php?page=metatags, translate metatag throw you out of the admin to tiki-preference_translate.php

May be all top menu action links throw out of the admin area...
* Control panel, top menu tools, Server check
* Control panel, top menu Access, Permissions
* Control panel, top menu Access, Groups
* Control panel, Editing, Plugin approval (tiki-plugins.php)
* ...

tracker item
Some widely spoken languages missing
We are lacking some languages spoken by millions. I'm not asking for translations, but we don't even have them as languages to correctly flag user texts for i18n, they are missing in /lang/langmapping.php.

* Dari (Afghanistan)
* Pashto (Afghanistan) https://en.wikipedia.org/wiki/Afghanistan#Languages
* Persian (Iran). We do have Farsi, but to my understanding the official wording is Persian, an Farsi is rather the name used outside Iran (endonym). https://en.wikipedia.org/wiki/Iran#Languages and https://en.wikipedia.org/wiki/Persian_language

There is an ISO transliteration of Persian into latin alphabet ISO 233-3.
tracker item
Sort by date columns to default to newest first (tables/list)
On most of Tiki list/tables (if not all) when you have sorting tools you have first to click on the header to activate it.
It sort the items in ascendant order based on this column and you can see the ascendant arrow.

When the sorting is based on a text column, the order of the items based on subject col is really weird to the viewer. (see: https://dev.tiki.org/tiki-view_tracker.php?sort_mode=f_26_asc&trackerId=5)
tracker item
Sort by multiple fields using Sort Control Block
Hi,
Is there a way of sorting content by means of "sort" control block sorting by more than one value? for example I'd like to execute a first sorting based on column A value; than, for each column A value, I'd like the content to be further sorted by column B value (hope it'clear).

Currently I use something like

{CODE(theme="default")}
{LIST()}
{filter field="tracker_id" content="..."}
{sort mode="tracker_field_..._asc"}
...
{LIST}
{CODE}

I think it could be used something like
{CODE(theme="default")}
{sort mode="tracker_field_sortingField1_asc"}
{sort mode="tracker_field_sortingField2_desc}
{CODE}

Or alternatively
{CODE(theme="default")}
{sort mode="???" modes="tracker_field_sortingField1_asc, tracker_field_sortingField2_desc, ..."}
{CODE}
in a similar way w.r.t the already existing syntax
{CODE(theme="default")}
{sort mode="randommode" modes="title_asc,tracker_field_example_asc,tracker_field_ticketNumber_nasc, modification_date_nasc"}
{CODE}

Thank you for your attenction
tracker item
Sort by several fields in plugin list
Currently, we can only sort by one field. But it might be useful in many cases to sort by several, in a certain order. It's quite a usual thing to do with MySQL, for example with a -+ORDER BY user_id, created_at+- so it would sort first by user IDs, and then for each user ID it would sort by created_at.

The syntax could be as simple as: -+~np~{sort mode="tracker_fied_user_id_asc, tracker_field_created_at_desc"}~/np~+-
tracker item
Sort forums arbitrarily
As detailed in Support Forums ( https://tiki.org/forumthread68978-Can-I-reorder-the-forums ) the current Forum structure, while allowing to sort by most recent, alphabetic, etc. does not have the ability to sort individual forums arbitrarily.

Depending on the forum type, you want to have the forum owner to be able to sort by forum's importance. This may differ from most recent, alphabetic, etc., and may have to be set arbitrarily (e.g. by assigning a forum number to each forum, which is generally not visible in the Forum view but provides the sorting order).

This has been discussed with Marc Laporte and work should begin shortly.
tracker item
Sort trackers on more than one field
Sort trackers' output on more than one field (sort on ..., then on ..., then on ...)
tracker item
Sorting items in a dynamic link field
Items displayed in/from a dynamic list field type are ordered (or unordered) by item id. It would be nice to be able to sort them alphabetically or by date.

I have a case here where parents have to select days and it is not user friendly (and not very nice).

{img fileId="1432" thumb="box"}
The 9/03 item should be displayed before the 10/03 but the item id of this item comes after the 10/03 one.
tracker item
Spam filtering: Bad Behavior or Mollom or Akismet, Defensio or TypePad AntiSpam
Here are some options
http://framework.zend.com/manual/en/zend.service.akismet.html
http://bad-behavior.ioerror.us/
http://antispam.typepad.com/
http://www.defensio.com/
http://mollom.com/

See: ((Spam Protection))
tracker item
Spam protection: email is obfuscated in javascript, generate image when no javascript is available
In Tiki 1.10, there is a feature to protect all emails against spam harvesters. Great.

1- Check that this protection is indeed powerful (so spammers can't get around it)

2- Have an option to show an image of the email when javascript is not available.

3- Extend this protection to [tiki-view_tracker_item.php?itemId=1147|the e-mail address in tiki-contact.php]
tracker item
change the table definitions to support the new utf8mb4 character
I was creating a wiki page entry and encounter a bug. When a special character is used in the text, text is deleted at the instance of the first special character and below. I just upgraded from 10.2 to 11.1 hoping to fix this problem. Both version delete text using special characters inserted using the character feature of the editor. mu, epsilon, pi, kappa, h bar were used. epsilon is the first special character and was the start of the deleted text.

-----

This is now converted into a Feature Request for tiki 13, See comment thread for reasons why {sign user="pascalstjean" datetime="2013-11-27T16:09:44+00:00"}
tracker item
Special characters in Wiki page titles break the doubled-parentheses type of link
There are many common non-alphanumeric characters that, when part of the title of a wiki page, break the ability to link to that page using the ~np~((Name of page))~/np~ method.

Characters which cause this type of linking to break include: comma (,), apostrophe ('), hyphen (-), question mark (?), asterisk (*), and percent sign (%).

The consequence is (a) you're extremely limited in what characters you can include in titles or (b) you have to link to a page by its URL. (b) is very limiting, because when a page is renamed, all the links to it will break.

Test with this:
~np~
((test,test))

((test's test))

((test-test, hyphen))

((test? question mark))

((test*test asterisk))

((100% correct))

((this should work with no problems))

((test_underscore))
~/np~

You'll see:
~np~
((test,test))

((test's test))

((test-test, hyphen))

((test? question mark))

((test*test asterisk))

((100% correct))

this should work with no problems?

test_underscore?
~/np~
In other words, all but the last two page names ("this should work with no problems" and "test_underscore") were ''not'' treated correctly as being links to web pages.
tracker item
Spellcheck dictionary should be install via mods, in many languages.
This is a perfect use for mods.

words_en.sql weighs 7.5 Megs. This is not super easy to upload via phpmyadmin.
tracker item
Split Ajax settings
As discussed at the TikiFest (?), we need more granularity here, for people that want AJAX for some features, but not for others.
tracker item
Split tracker admin/edit permission
The tiki_p_admin_trackers permission is needed to both edit the main attributes of a tracker and add/change fields etc., as well as to Export or Import csv files.

This means that when it makes sense to allow some users the privilege to Import and Export data in batch mode then they will also have edit access to the field structure etc which may not be appropriate.

tracker item
Spreadsheet: update to latest stable version
Perhaps jQuery.sheet should move to Composer and Packagist?

Use: jQuery.sheet 3.0
http://sourceforge.net/p/tikiwiki/code/48315/
tracker item
Standard permissions for features per groups
Every time a new object gets created (wiki page, blog entry etc) the item recieves only global permissions.

It would help a lot if the admin could define 'standard permissions' for each group for specific features.
(needs to be integrated with improvements to "permissions by category" introduced in 1.9 - which provides a coherent approach for "object" based permissions to compliment user based perms.)

To keep wiki pages inside the group, the admin would assign the read right only to that group, and a member of that group posting a new item would not have to worry about security as much.

Am not sure what to do when user is member of multiple groups... maybe she can select in a drop-down which is the one that wins, or maybe the admin determins that when creating the user?

Reccomendation: Inherit permissions. (particularly for wiki)
The default behavior for a new object should be to inherit permissions from the page it was created from (global if none). Particularly in a wiki, this would facilitate the use of "private areas" - key feature for tikiwiki as groupware so committees. groups, etc. can operate in privacy, if so desired. Whoever create the page should be able to disable this inheriting, but it should be on by default. Admins can then create private wiki spaces by customizing perms on one page (the group home page).
tracker item
Show PHP error messages