Category: Edit interface (UI)

The capability to include (recursively) with parameters is probably the most powerful and content factorizing feature of our best competitor MediaWiki.

It make not only produce content much faster and in a much more modularised way.

The references :
* [http://en.wikipedia.org/wiki/Transclusion]
* [http://www.mediawiki.org/wiki/Help:Templates]
* [http://doc.tikiwiki.org/PluginInclude]

When you edit a wiki page, you can indicate what you did. Good.

But if you leave it empty, visitors have no indication of what you did. Maybe we could add some of the ideas of wiki-translation.com (Quantify change size) to have an automatically generated message.

Some examples:
*minor change
*10 words changed
*15% changed

In 1.10, there is a "minor" button when you save a wiki page.

When using the wiki for translation, checking minor tells the system that the corresponding translation are __still valid__.

I believe __minor__ also prevents sending notification emails to those watching the page. (why bug them for a corrected typo?)

Font Awesome (and maybe others?) supports rotating the icon, and some of the icon instances in Tiki are rotated (like the "sitemap" icon is used for Tiki's categories feature, rotated 270 degrees). So a PluginIcon parameter like ''rotate="270"'' would be a great addition.

It would be so nice if we could have the ''Character Count: __XX__ Max: __2100__'' textarea option in wysiwyg as we do have in tiki syntax.

Right now I look at a form which mixes wysiwyg and tiki-syntax fields just because the ones which need to support character counting can't be in wysiwyg.

12.x - 15.x: Tracker: filter items is broken when radio button with labels set (0=No,1=Yes,2=Dunno).

No matches are found when there are some items which met the intended criteria.

--It'll be-- reproduced in an attached intance --in short. Stay tuned!-- :-) {sign user="xavi" datetime="2016-02-09T12:21:27+00:00"}
Login in here:
http://xavi-9794-5810.show.tikiwiki.org/tiki-view_tracker.php?trackerId=1
u: admin
p: 12345

You will see the field TestRaduio, with some values (0, 1 and 2; their labels, in fact)

Try to filter by that field:
http://xavi-9794-5810.show.tikiwiki.org/tiki-view_tracker.php?trackerId=1&status=o&sort_mode=f__asc&filterfield=8&filtervalue%5B1%5D=&filtervalue%5B2%5D=&filtervalue_other=&filtervalue%5B3%5D=5+%28high%29&filtervalue%5B8%5D=0%3DNo&filter=Filter#
---
__Update:__ {sign user="xavi" datetime="2016-02-10T10:42:06+00:00"}
the problem is also found (and still unsolved) at teh trackerfilter level. Sorry, I tried for one hour, but I couldn't get the right syntax to port this type of fix there also. :-/
To reproduce, see it here:
http://xavi-9794-5810.show.tikiwiki.org/tiki-index.php?page=HomePage

__The issue is reproduced also for dropdown fields when labels are set, etc. See it reproduced with field "Priority" (Dropdown). __

__Reproduced also with "Dropdown with other" (field __Location__) in the tracker itself, but it works as expceted through Plugin TrackerFilter.__
Does work:
http://xavi-9794-5810.show.tikiwiki.org/tiki-index.php?page=HomePage

Doesn't work:
http://xavi-9794-5810.show.tikiwiki.org/tiki-view_tracker.php?trackerId=1&status=o&sort_mode=f__asc&filterfield=2&filtervalue%5B1%5D=&filtervalue%5B2%5D=0%3Droom+1.1+%2855+seats%29&filtervalue_other=&filtervalue%5B3%5D=5%3Dhighest&filtervalue%5B9%5D=y&filtervalue%5B10%5D%5B%5D=1&filter=Filter#

Multiselect seems to work well, as expected, in both tracker itself and plugin trackerfilter.

It seems that what was achieved with profile
https://profiles.tiki.org/Hide+Fixed+Top+Nav+Bar+on+Scroll

up to Tiki18 (included) is no more working in Tiki 19.x, maybe due to changes related to the Bootstrap4 migration?

I.e.: Top module zone in dev.t.o and other *.t.o sites is no more hidable on scroll, nor topbar module zone gets sticky anymore.

I presume this is easy to fix (<30' ?) by some css & bootstrap 4 master in the tikiverse? (not me for sure)

Thanks

P.S: fyi, Work in progress to get the profile updated:
https://profiles.tiki.org/Hide+Fixed+Top+Nav+Bar+on+Scroll+19

Plugin Pivottable inserts wrong codes in params data, rows and cols through plugin helper ui. Reproduced in 18.x and 19.x as of Jan 19 2019

I selected the name of the tracker in the dropdown shown, and a few of the tracker fields I chose for rows and columns, and the codes inserted in the wiki page sayed later were not the expected ones for each type of field:

Example of codes inserted (which fails to show data nor columns or rows):
{CODE()}
{PIVOTTABLE(data="1" rows="1:2" cols="3" ...)} {PIVOTTABLE}
{CODE}

Expected code to be inserted
{CODE()}
{PIVOTTABLE(data="tracker:1" rows="permNameA:permNameB" cols="permNameC" ...)} {PIVOTTABLE}
{CODE}
---
Reproduced in the show instance for 18.x
u: admin
p: admin
http://xavi-9794-6937.show.tikiwiki.org/tiki-index.php?page=HomePage

The new "saved_msg=y" fails when SEFURL is on - both new pages and editing. It gives me a 404 not-found error. Makes SEFURL pretty useless. Example:
http://www.casesofinterest.com/tiki/Everything+is+Patentable&saved_msg=y

{syntax type="tiki" editor="plain"}
1. The "Leave Page"-Confirmation Box does not show up in TW7.

2. Another problem is that the onchange event is not fired when I leave the page with any browser button, e.g. back, F5, etc.

Using latesst trunk from today (Feb 1st 2010). Installed a new tiki, enabled tikisheets, created one. Edit it and save changes.

Then enable jquery.sheet through Admin > Look & Feel > interface (or whatever name, I don't remember) > tick the jquerty sheet checkbox. also enable ajax.

Create another sheet. Edit it with jquery.sheet, and it , and "A Sheet Id is required" type of message (or something similar) was shown.

I remember it worked for me weeks ago, when I tested the first commits by jonny with jquery.sheet in trunk. But nowadays, it doesn't work for me.

Very similar to this bug that was fixed in Version 5:
http://dev.tikiwiki.org/tiki-view_tracker_item.php?itemId=3017&trackerId=5&show=view

Unfortunately, our host does not support version 5 yet, so I am dead in the water unless this same issue gets addressed in version 4.1

Basically, you can create sheets, but whenever you try to edit them, simply clicking on any of the links (Insert, Remove, etc.) causes a redirect to an error page stating: "A SheetId is required."

I haven't been able to import simple spreadsheets either, but that's another issue.

!Latest status, as of 3 Nov 2013: Action Buttons present but Translate From half of side-by-side screen contains nothing. still unresolved as of r.48452
!Action Buttons missing in various themes when translating

In 3 of the 22 themes (Coalesce, Ohia, and Strasa) the critical action buttons are missing when trying to translate pages. In 18 themes these button show up. In one theme (Utopias) them are partly off the screen, but present enough to click them.

__All screen captures taken from demo.t.o/12.x (this site) on 12 Octover 2013, while the site was running 12.0svn rev. 47983 (of 11oct2013; 12:44 CEST).__
__This situation is reproducible by anyone logging into demo.t.o/12.x/ as admin__, then selecting any page (in the screen captures below, I selected "Page to test translation features"), then either:
a. from the left menu, under "Translate Updates" -> "Outgoing" select one of the languages available (currently French and Korean) and click the leftmost button {img fileId="425" thumb="y" rel="box[g]"} (with pop-up description of "update it" in English), or
b. click the Translate button, and choose to translate into a new language (one other than the ones for which translations already exist.

1. Here is the way the screen should look like, when updating a translation (theme:Fivealive):
{img fileId="422" thumb="y" rel="box[g]"}

2. Here's the way it looks (without action buttons) in Coalesce (same in Ohia and Strasa):
{img fileId="423" thumb="y" rel="box[g]"}

3. Here's what it looks like in Utopias (buttons partly cut off at bottom of screen:
{img fileId="424" thumb="y" rel="box[g]"}

As one can also see, in ALL themes, the titles of both the left and right parts of the screen overlap, i.e. the left part does not wrap in its half, but this is a relatively minor irritant.

The missing buttons prevent users using the system with the themes that don't work.

olaf-michael stefanov (omstefanov), 12 October 2013

Nowadays that JQuery has been added to 3.0svn, there is big opportunity ("low hanging fruit"?) for improving the usability of tiki spreadsheets, adding (optionally, of course) one better interface for spreadsheets through jquery plugins.

My proposal is __jQuery.sheet__:
http://plugins.jquery.com/project/sheet

http://jqueryplugins.weebly.com/jquerysheet.html

demo:
http://jqueryplugins.weebly.com/uploads/3/1/3/8/313814/jquery.sheet.html

This would improve the editing UI (for sheets), as well as big tables, if created and managed through the plugin SHEET directly from the wiki page, as drawing could be created previously.

I could be nice to have the "preview" button at tracker item submission time, to preview the parsing of wiki syntax, and to avoid submitting and editting later on for simple wiki syntax errors... (It happened to me, for instance, with bug report:
http://dev.tikiwiki.org/tiki-view_tracker_item.php?itemId=184&show=view&status=op&trackerId=5&sort_mode=f_41_desc&filterfield=54 )

Some characters inserted using the special characters palette into an article cut the text of the article behind the new character off after saving the article. When still in edit mode, the preview shows the complete text.
I tested a few greek characters, since we need them. Test items can be both omegas, but other greek characters cause the same problem.

1- "Upload image for this post" is not offered at first post. Only after I save and come back to edit?

Html is offered:
{img src=images/code.png}%%% {CODE()}
<img src='tiki-view_blog_post_image.php?imgId=44' border='0' alt='image' />
{CODE}

It should be wiki syntax:
{img src=images/code.png}%%% {CODE()}
{img src=tiki-view_blog_post_image.php?imgId=44 }
{CODE}

Related: [tiki-view_tracker_item.php?itemId=1492|It's too difficult to re-use image gallery images in wiki pages, trackers, etc]

While I added and saved some plugin icon (PluginSign) on toolbars on tiki.org and cleared the Tiki cache, the change is not reflected when editing a wiki page. It still shows the previous older toolbars setup and the icon does not appear there while on Admin Toolbars it is shown. See Row 2 on https://tiki.org/tiki-admin_toolbars.php (when you have Admin access of course).

I often want to edit users that request registration (such as add them to a group). It would be nice if the "user validated" page had a link to the page to edit that user's settings.

When switching between wysiwyg and syntax, or visa versa, an "ajax error" is triggered. I have seen this error since tiki14, it is random, and happens so often, I have not seen the error in a long time since I was using tiki15x, but after installing a fresh instance of tiki16x, the "ajax error" is back. Please see screen shot:
{img fileId="1119" thumb="box"}
---
After configuring the show instance closely to my own tiki instance, and after installing text on the home page, I was able to recreate the "ajax error" when switching between wysiwyg and syntax.

When codemirror is on and its default mode is set to "Off (but switchable)", the end user expects to see a button available in tracker item textareas (like in dev.t.o/t5 bug tracker).

But it's not available still.

To see it reproduced:
Log in here:
http://xavi-9794-5064.show.tikiwiki.org/tiki-index.php?page=Contact_us&itemId=1
u: admin
p: 12345

Codemirror has been set to on (with default theme). If you edit the "Contact_us" page you'll see the content highlighted.
However, no highlighting in the tracker text area field.

Maybe the best option would be to allow the tracker admin to set an option for text areas to include the button to toggle the "highlighter" upon user request (as with text areas in wiki pages).
This way, codemirror could be set to "Disabled but switchable" (default preference in new installs), and each user could decide whether to enalbe highlighting in that text area or not (to prevent side issues in some cases with codemirror on, from happening always in all text areas, etc)

Allow posting comments on a wiki page when viewing wiki page history (for instance, when viewing a diff of page versions from different users): useful on educational scenarios, where it would be easier to report feedback to some students when they make a good or bad change on some content on that page...

Currently quicktags must be defined individually for each different feature. It would be nice if you could define one set of quicktags for multiple features. If you define a good set of quicktags for one feature, say the Wiki, the only way to propagate that set to other features would be to do a manual copy and paste (very time consuming) or modify the database table/s directly (Not easy for the novice user).

Quicktags cannot easily be ordered i.e. the order in which they are displayed to the user. Currently the only way to do it is to prefix each quicktag name with a number to ensure they are sorted in the order in which you want to display them

Anchor are lost after parsing. Tested with WYSIWYG and with normal editor.

insert:
{img src=images/code.png}%%% {CODE()}
<a name="myAnchor01">bla bla</a>
{CODE}

after preview or saving
{img src=images/code.png}%%% {CODE()}
<a>bla bla</a>
{CODE}