Category: Feature request
Request to add a totally new feature or to enhance an existing feature. Also called Request for Enhancement (RFE)
Show subcategories objects
| Name | Type |
|---|---|
| It should be possible to hide page listing based on group membership | tracker item |
|
It should be possible to hide the "More" button (especially if it is "empty")
The more button display should be controllable by admins without using css. See : ... I can’t find the discussion using the forum search tools ? |
tracker item |
|
It should be possible to include the ALTERNATE value of a plugin List within the results template
{syntax type="tiki" editor="plain"} With the plugin List you can use a template. If there are no results you can set the alternate value that will be displayed. But this value won't be display using the template design but as an element on its own. Use case: I want to create a dashboard with several gauge where 0 items is a valid value that lead to specific design with conditions. Just to give an idea: 0 item = green background 1 item = warning background >5 items = red background The Alternate value should be used in the template as a value and not as a string on its own. |
tracker item |
|
It should be possible to use keyboard to select an option of the status resolution dropdown at dev.t.o
On the tracker 5 when you edit an item you can't type the first letter of an option in the "Resolution status" dropdown to jump to the option. You use a search field, but the more "natural" type first letters option should work too. {img fileId="1636" thumb="box"} |
tracker item |
|
It's too difficult to re-use image gallery and file gallery content in wiki pages, trackers, etc
As reported here: https://bugzilla.mozilla.org/show_bug.cgi?id=398767 {THUMB(image=>img/wiki_up/2008-01-17_low-tech-image_picker_TikiWiki.jpg,url=#)}{THUMB} {THUMB(id=13,url="show_image.php?id=13")}{THUMB} {THUMB(id=16,url="show_image.php?id=15")}{THUMB} Some ideas of nice links to have: Thumbnail with link: {img src=images/code.png}%%% {CODE()} {THUMB(id=13,url="show_image.php?id=13")}{THUMB} {CODE} [tiki-upload_image.php|You can test some experimental stuff here] (upload a pic and see the suggested wiki markup to copy in a ((test)) page.) Nelson Ko and Marc Laporte were planning to work on tiki at ((tw:TikiFestToronto)) but something else came up so it's still on todo list :-) |
tracker item |
|
Quick Edit module should detect and warn about special characters in page names
Sometimes, we end up with some strange characters in pages names (accents, punctuation, etc). While it generally works, people should keep URLs with simple characters (like in emails) for nice readable URLS. For example: ((I know this is all wrong, but fear it might be right - Alain Désilets)) |
tracker item |
|
Side-by-side edit of two languages, with a "translation is in sync" button to save both wiki pages
Full page mode would be quite important ** Need to evaluate usefulness with Alain Désilets ** LP says it's doable (from back-end perspective) Coordinate with other work on: http://wiki-translation.com/ |
tracker item |
|
Plugin to display the toc of a selected page.
For multipage wikis the display of the "table of content" using __maketoc__ isn't ideal as this statement requires to be placed on every page otherwise it wouldn't be visible for other pages. Usually this "table of content" is used for quick navigation purposes. Therefore an alternate to the __maketoc__ statement should be provided which should allow to specify the wikipage which shall be outline. Such a statement can then be used in a module nearby the original wikipage. |
tracker item |
|
Bad SQL-Mode
{syntax type="tiki" editor="plain"} 'ziit_tikiwiki.tf.galleryId' isn't in GROUP BY Die Abfrage war: SELECT tab.* FROM ((SELECT 0 as `isgal`, tf.`fileId` as `id`, tf.`galleryId` as `parentId`, tf.`name`, tf.`description`, tf.`filesize` as `size`, tf.`created`, tf.`filename`, tf.`filetype` as `type`, tf.`user` as `creator`, tf.`author`, tf.`hits`, tf.`lastDownload`, tf.`votes`, tf.`points`, tf.`path`, tf.`reference_url`, tf.`is_reference`, tf.`hash`, tf.`search_data`, tf.`lastModif` as `lastModif`, tf.`lastModifUser` as `last_user`, tf.`lockedby`, tf.`comment`, tf.`deleteAfter`, tf.`maxhits`, tf.`archiveId`, '' as `visible`, '' as `public`, tf.`fileId`, tf.`galleryId`, tf.`filesize`, tf.`filetype`, tf.`user`, tf.`lastModifUser`, '' as `files`, count(tfh.`fileId`) as `nbArchives` FROM `tiki_files` as tf LEFT JOIN `tiki_files` tfh ON (tf.`fileId` = tfh.`archiveId`) WHERE tf.`archiveId`=0 AND tf.`galleryId`=? GROUP BY tf.`fileId`) UNION (SELECT 1 as `isgal`, tfg.`galleryId` as `id`, tfg.`parentId`, tfg.`name`, tfg.`description`, 0 as `size`, tfg.`created`, tfg.`name` as `filename`, tfg.`type`, tfg.`user` as `creator`, '' as `author`, tfg.`hits`, 0 as `lastDownload`, tfg.`votes`, tfg.`points`, '' as `path`, '' as `reference_url`, '' as `is_reference`, '' as `hash`, tfg.`name` as `search_data`, tfg.`lastModif` as `lastModif`, '' as `last_user`, '' as `lockedby`, '' as `comment`, '' as `deleteAfter`, '' as `maxhits`, 0 as `archiveId`, tfg.`visible`, tfg.`public`, tfg.`galleryId` as `fileId`, tfg.`parentId` as `galleryId`, 0 as `filesize`, tfg.`type` as `filetype`, tfg.`user`, '' as `lastModifUser`, count(distinct tfc.`fileId`) as `files`, 0 as `nbArchives` FROM `tiki_file_galleries` as tfg LEFT JOIN `tiki_files` tfc ON (tfg.`galleryId` = tfc.`galleryId`) WHERE 1=1 AND tfg.`parentId`=? GROUP BY tfg.`galleryId`)) as tab ORDER BY `isgal` desc |
tracker item |
|
Webservice with Tiki data
access tiki data (like trackers, wiki pages, etc.) with webservices. Add an additional option on trackers, wiki pages etc. to make them accessible by webservices (like choosing categories) Administration UI where security can be configured (Password on specific webservices etc.) |
tracker item |
|
return itemId after adding tracker item
after new tracker item is added there should be any variable like itemId or lastItemId that can be used after adding, like: {CODE(colors="tiki")} {TRACKER(trackerId="8",fields="51:52:53:79",showdesc="n",showmandatory="n",showstatus="n",embedded="n",reset="Reset",newstatus="o")} Action Point was added with itemId = {{lastItemId}} {BUTTON(href="tiki-view_tracker_item.php?itemId={{lastItemId}}",_text="Details")} {BUTTON(href="tiki-index.php?page=Add+Action+Point",_text="Add_Next")} {TRACKER}{CODE} |
tracker item |
|
button does not accept space and other non [A-Z,0-9] characters
Button does not accept any separtators other than '_' in _text variable. There are many reasons to create button with two or more words on it. |
tracker item |
|
Multigual File Descriptions
This item pulled out of Ticket ID 2874 which had several items. File Galleris should be multilingual including *Descriptions *Names e.g. description has different content for different languages which is then displayed with the image 'caption' automatically in user's language. See detyailed discusssion and real world use cases at [http://dev.tiki.org/tiki-view_tracker_item.php?page=user&itemId=2874&show=view|linked ticket|_blank]. |
tracker item |
|
HTML links for FIle Gallery Images
{syntax type="tiki" editor="plain"} No html links are shown for uploaded images in the file gallery. Only wiki display and download links appear in the "Additional Info" screen. Users just have to "know" that to display in html you must use /displayFilenumber Also, there is no direct way to get BACK to that Additional Info screen from the gallery once the file is uploaded. i.e. it does not appear in the image's 'tool' pop-up menu, which just lists for us Dowload, Replace, Properties, Open in WebDav, Email this, and Delete only. No way to get back to the "additional info" screen. Also, the images don't have a suffix when the URI format is /display123 and this causes problems with some software which expects one. The old image galleries had an html link for the images. |
tracker item |
|
Renumbering menu option positions
It would be nice if menu option positions renumbered when you make changes. I know they're positioned 10 apart, I assume so you can insert things later, but I'm OCD so I'd renumber them anyway if I ever had to make changes (:razz:) If I had to guess, this would be a fairly easy change, module orders already do this so the code can probably pretty much be copy/pasted from there. |
tracker item |
|
Tracker page : little ergonomy enhancement
A proposal of enhancement : If the tracker can be edited a tab can remain but why not display too the familiar standard edit icon used for content edit allowed ? It is sure that not everything can be edited, but it is the edition of a tracker. |
tracker item |
|
Wishlist and bugs reporting : why not to have defined "Related project : Release 70 ; Release 80 ?
All in the tittle. Where is the official list of "projects" which can be used into trackers selection and which would correspond to real stage of Tiki. The project list for selection must naturally be coherent with the history of the whole project (since 2.0) This is necessary for accurate upgrade and users feeling good. |
tracker item |
|
Read-only mode (ex.: when migrating a Tiki to a new server and you want the old one to still show content but not have edits)
We have a site_closed preference which is very useful. However, this permits only the admins to access the site. What if we want a read-only mirror? It would be nice to a have a preference for this, along with a message to users: "This site is in read-only" and admins could change this message to indicate where the live site is. Perhaps it could be interesting to check if the mysql user is "read only" as well... This could also be interesting if a project is completed and we want to keep a site an an archive but no longer have any changes. Things like tiki-logs, date of last login, etc. will need to considered. Perhaps there could be a check: If current users has an edit/add permission (we'd have to make a list), then, he gets a warning that site is read-only (a message that the admin could change) and that any changes will be lost. |
tracker item |
|
Site dev.tiki.org Tracker updates : options in features
Some feature to be better in categorizing trackers of dev.tiki site, I suggest to introduce : * Styles parameters * Styles display defaults and appearance * Options in tiki.org site * Texts of interface : defaults or suggestions |
tracker item |
|
The results of a search in text or title with beginning of text don't decode any text
{syntax type="tiki" editor="plain"} After a search (general by text) the beginning of text which is displayed is not decoded-re-encode for the context. On the screenshot joined you can see parts of text with tiki tag (!! for h2), HTML tags, problem of encoding UTF8 probably or old text not re-encoded (not yet checked). |
tracker item |
|
Sort of "whishlist : list yours" on dev.tiki.org : the list is unsorted, need to displays to get the most useful
{syntax type="tiki" editor="plain"} When you use on whishlist of dev.tiki.org the option "listyour", you get an unsorted list. The most useful list is inverted sort by ID. To get this you need : #to sort by id #Use again the column header to sort in reverse order. I place it in bug usability and whishlist. The first default display should be : ID reverse order sorted |
tracker item |
|
Limit users from CAS
While CAS authentication is great, it allows multiple users to login if you have a widely common CAS server. For example, SecurePass [1] strong authentication allow ALL securepass users to login through their CAS. The need is to optionally limit which users or users domain can login to tikiwiki through CAS. [1] www.secure-pass.net |
tracker item |
|
@user wiki syntax
Related to {wish id=1409}, it would be nice to have a syntax to leave messages to people or groups on wiki pages * It could send an alert |
tracker item |
|
Glossary by way of Hotwords
I was recently looking for a way to easily make a Glossary when I came across the Hotwords feature. I immediately took to the feature and began using it. But I got to thinking, it would be nice if I could enter a description, check mark a box(to include the word in a glossary page) and check mark a box(to use the word as a Hotword). Then just have a wiki page with a {glossary} tag or have a predefined wiki Glossary page. |
tracker item |
|
Import phpBB data
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. |
tracker item |
When a group, including anonymous, can view pages, the group can view the page listing at tiki-listpages.php.
Actually we switch to enable or disable the option for this at tiki-admin.php?page=wiki -> Page listing but it is quite radical. If the "Page listing" is disabled even "admin" doesn't have access anymore to the page listing.
It should be possible for a webmaster to decide which group can see the page listing and which cannot.
I suggest adding such permission.