Category: Toolbars, Quicktags and Smileys
Show subcategories objects| Name | Type |
|---|---|
| [mailto:text|text] doesn't have antispam protection | tracker item |
|
Caldrac
Contributors |
tracker item |
| 12x dev.tiki.org: can't reset toolbars | tracker item |
| 13.x in dev.t.o: some toolbar buttons like wiki link broken (reload the whole page) | tracker item |
|
jonnybradley
Contributors |
tracker item |
|
Bug with IE9 on image icon in the toolbar (tiki 6.3)
There's a bug with the image icon in the toolbar on IE9 only. {img id=121} When we click on it nothing append. The box for the setting doesn’t show up. The bug seems to have been fixed in tiki 7.x and 8.x but I like to know how cause I need to fixed in tiki 6.3 for a client. Thanks |
tracker item |
|
HTML comments in WYSIWYG editor
The WYSIWYG editor should have a button to create HTML comments that will only be visible in edit mode, and not in read mode. As with all HTML, the comment tags should not be visible in WYSIWYG mode. The commented text should be a different color; perhaps grayed out. This feature would enable editing discussion to happen right within the page being edited. Editors could more easily reference the text under discussion, since it would be right next to the comments. Discussing pages separately in the forum would no longer be needed, or would be optional. |
tracker item |
|
Ajax fails with Quicktags admin
Apparently the loadComponent function is not present. I tested ajzxlib->processRequests by changing it to printJavaScript instead of getJavaScript - this had the effect of putting the function loadComponent into the javascript, but it still failed. |
tracker item |
|
add trackers-quicktags to SQL-scripts
Textarea in Trackers checks for quicktags from the "tracker"-category - those are not yet in the db. |
tracker item |
| Admin Toolbars does not reflect saved changes on the toolbars while editing a page | tracker item |
| Ajax | wiki |
|
Allow Quicktags to be defined for multiple features
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). |
tracker item |
|
Allowing for positioning of Quicktags
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 |
tracker item |
| can't upload an image to a file gallery in doc.t.o with elfinder (default UI) since 16.x | tracker item |
|
Cleanup Quicktags
Make 1.9.11 and 1.10 consistant Remove less used quicktags and add some in the spirit of ((EditUIRevamp)) |
tracker item |
| Clicking on icon after file upload from text area through toolbar icons fails for me to add the right syntax for that file | tracker item |
|
Code button in CKEditor WYSIWYG not working for IE 8
This bug is seen by our IE 8 clients. We are running Tiki 6.2 (clean install), on a Windows 2003 Server, Apache 2.2.16 w SSL, PHP 5.3.3, remote MySQL 5 database. Our users are editing in the CKEditor WYSIWYG and try the Code plugin from the toolbar. The Code window opens as expected and the users enter their code in the correct field. On pressing Insert (or Replace) the code plugin is added in the editor but there is no contents in the plugin. If I open the normal editor it displays as%%%~np~{code caption="MyCode.java"}~/np~%%% which is completely the wrong syntax. If I try using the Code option in FF then it opens a new window and I can add the code just fine. I view from the normal editor and it reads%%%~np~{CODE( caption="MyCode.java")}public class MyCode { //testing a point }{CODE}~/np~%%% which is correct. Since IE is our corp standard our users need to be able to add files using that browser. Also, they had no problem in Tiki 5.x but that was a different WYSIWYG system. Thanks, Tim |
tracker item |
| Color picker option in Wiki edit toolbar shows a blank dropdown | tracker item |
|
Content templates should be part of quicktags
It should be at the very least possible to add content templates where the cursor is, like ((quicktags)). |
tracker item |
|
Display freetags in search results
I would like Tiki to display each item's freetags when display the search results. This would help end-users determine the relevancy of each item. |
tracker item |
| Edit toolbars calls for non-existing icon | tracker item |
| Email Scrambling | tracker item |
|
File button in CKEditor WYSIWYG not working for IE 8
This bug is seen by our IE 8 clients. We are running Tiki 6.2 (clean install), on a Windows 2003 Server, Apache 2.2.16 w SSL, PHP 5.3.3, remote MySQL 5 database. When our users are editing in the CKEditor WYSIWYG and try the File option in the toolbar there is a Javascript error for lib/jquery_tiki/tiki-jquery.js at line 808 char 4. What is happening after the error is thrown is that no new window is opened (as expected) but the File selection fields are now under the WYSIWYG Editor. This wouldnt be an issue, but there is no OK button to select the file so our users can not like to a file in the File Gallery. If I try using the File option in FF then it opens a new window and I can select the file just fine. Since IE is our corp standard our users need to be able to add files using that browser. Also, they had no problem in Tiki 5.x but that was a different WYSIWYG system. Thanks, Tim |
tracker item |
| font colour and background colour drop downs 'empty' in wiki editor | tracker item |
|
Full screen edit button visible in quicktags, even if option is disabled
The Full Screen edit button is visible in my quicktags list, even though I have the __Allow fullscreen edit__ option disabled. |
tracker item |
;){kind=link}
;){kind=link}
;){kind=link}
;){kind=link}
{img src=images/code.png}%%% {CODE()} [mailto:text|text] {CODE}
But this prevents the spam protection code from working