Category: Content template
Show subcategories objects| Name | Type |
|---|---|
| {{itemId}} broken in templates in 27.3 (works in 27.2) | tracker item |
|
Tracker templates (import/export tracker definitions/structure)
If Trackers had the "tracker template" feature, it would allow for better pre-made extended features for Tiki at install time. In tw.o forums, some people requested like: address books (imagine with the same basic fields as Mozilla Thunderbird & Evolution, etc. address books, ... Export from you local program (through csv), and import to your address book in Tiki (through csv). The same for "Offers & Demands (linked or linkable)", that many people/communities would like to use like "out of the box" feature. I do have that kind of trackers made (basic, but working for production already: http://valldelcorb.org/trackers - http://valldelcorb.org/Comparteix (1.9.x) or http://intercanvis.net (1.10.x) using tracker plugins in a general Wiki page). Since duplicate tracker is already coded in 1.10, and templates concept already exists in Tiki, Tracker templates would be a nice MUST in the MID and LONG run. Tracker templates should be selectable at install time (in the new installer devs. are thinking/designing -> ((Install)) ), or at a later stage through Mods, maybe? |
tracker item |
|
13.x doc.t.o: apply template to wiki page adds no new content on reload
13.x doc.t.o: apply template to wiki page adds no new content on reload See it reproduced in doc.t.o. , in this screencast: [http://tiki.org/display596|140915_bug_apply_template_wiki_page_ko.webm] ([http://tiki.org/display596]) |
tracker item |
|
jonnybradley jonny B
This should be migrated to the community site, and handled with ((doc:Organic groups)) and ((doc:User Trackers)) |
tracker item |
|
thess
This should be migrated to the community site, and handled with ((doc:Organic groups)) and ((doc:User Trackers)) |
tracker item |
|
Admin templates uses WYSIWYG editor even if WYSIWYG was not enabled
{syntax type="tiki" editor="plain"} Since r19838, Admin templates uses the WYSIWYG editor even if WYSIWYG was not enabled. The root of this problem is usage of the Smarty wysiwyg variable, which is not always set since r9595. |
tracker item |
|
Apply last approved wiki template version and not just last version when revision approval system is set on wiki pages
Use case: * You have content templates enabled, and revision approal system set for wiki pages. * You create a new content template "MyTpl" based on a wiki page, under revision approval. * MyTpl Version 2 is approved. Version 3 is the last edited version of the content template, with no approval yet. * You create a new wiki page "MyPage", apply the template MyTpl, and you get applied v3 (non approvaed), instead of V2, which is the approved one and should be the one applied by default. To reproduce, log in as admin: u: admin p: 12345 Wiki page: http://xavidp-1553-5818.show.tikiwiki.org/tiki-index.php?page=MyPage Template: http://xavidp-1553-5818.show.tikiwiki.org/tiki-index.php?page=MyTpl History of versions of the wiki page template: http://xavidp-1553-5818.show.tikiwiki.org/tiki-pagehistory.php?page=MyTpl See that last approved version is v2, but there is a v3 which has more content. Edit the wiki page and try to apply the template: http://xavidp-1553-5818.show.tikiwiki.org/tiki-editpage.php?page=MyPage V3 is applied instead of v2 (the last approved version) |
tracker item |
|
Being able to 'lock' and categorise content templates: New Feature request
Content templates very usefully allow complex/rich formats to be pre-established for Wiki pages etc - but if there are a number of users with full 'editor' permissions it would be very useful to be able to put individual Content templates under a 'change control' process where only one individual (and the admin) can change/update it, ===and=== to be able to segment the access to a large number of content templates by an individual Category. Being able to 'lock' a template in the same way as a Wiki page etc is assumed to be a simple way of achieving the 'lock' request but there may be better ways of achieving the effect. Adding a Category function may have some more 'interesting' consequences since some thought should be given as to whether the categorisation is inherited by the wiki page/newsletter or whether the template, whilst only being available to a user with the right category permissions, should then just be pasted into the edit screen and the resultant page categorised as required. update June 2013 - still a very useful Feature Request ! |
tracker item |
|
Better layout of the wiki top (.tocnav, .wikitopline, .categbar)
Hello ! Currently the top af the wiki article has 4 lines, each for an item. Space could be saved (in my site wikispiral.org I'm putting those in a special slider fixed on top)... |
tracker item |
| Citation | wiki |
|
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 |
|
Form element "select" are missing "custom-select" in CSS class to refine UI of themes using Bootstrap
The form element "select" in forms of Tiki Forum and in other features of Tiki is missing the term (selector) "custom-select" as part of the CSS class to render it correctly in the Bootstrap theme design. Making this simple change would greatly improve and unify the UI of Tiki with the currently available Themes. See attached screen shot of added term in inspector for Tiki Forum feature. {img fileId="1380" thumb="box"} |
tracker item |
|
Trackerlist ActionUrl
When using the checkbox option in TrackerList the actionUrl is stated as $checkbox.action and not as the link you entered. |
tracker item |
|
Can not edit content templates with WYSIWYG editor
Using my version is 8.4 (MyISAM), installed via softaculous, when WYSIWYG is enabled the editor does not show up on the Admin>ContentTemplate page. I looked at the generated source code where the editor should appear and what it shows is this : ~lt~tr> ~lt~td/> instead it should show: ~lt~tr> ~lt~td> (code for WYSIWYG editor goes here) ~lt~/td> Both features work fine independently, just not simultaneously. |
tracker item |
|
Registration tracker with file pretty tracker template is impossible
I want to setup a custom registration with extra data in a tracker and with a file template for registration presentation. This works with a wiki page used as template, but it fails with a template file used as template. This fails because in the following way: * The registration displays one error message per field in «Registration Fields» (in Registered group config) + ''Incorrect fieldId: 2. Please ensure you are using the correct field ID and that it is properly included in the template, if any.'' * The extra fields do not show upo in the registration page. I tried many syntaxes: $f_2 (as documented), $ins_2, $ins_firstName, etc. A show instance below demonstrates the bug. !More More testing shows an issue when users enter invalid values. * Click on "Login→Register" * Fill some invalid values (no password, email does not contain "@") * Observe that the page now asks to fill data again but it does not use the template :-( |
tracker item |
|
RFE: admin interface 4 template message emailed to new users to a group (registered, or others)
Copied some suggestion I just throwed on irc..., after fighting each time on some of my production sites to manually send messages to many users which are kind of lost some times at the beggining of their participation in a tiki-site-powered community. {QUOTE()} (11:37:39) xavi: I was just wondering about a new and easy improvement of the registration process of new users to a community sit eusing tiki (11:38:07) xavi: just through allowing an admin to add acustomized welcome message to new users successfully registered to the site... (11:38:29) xavi: ... with the text and links he might need to tell to new users.... (11:38:52) xavi: ...in a similar way to what mailman does for the welcome message to new users... (11:39:48) xavi: ...I imagine a simple text area, like site identity does, where the admin can write any simple text (with or without wiki markup? like the newsletter feature does/allows)... (11:40:45) xavi: ...so that the admin can set that message easily (without manualy searching for the appropiate template to hack through ftp)... (11:42:48) xavi: ..and the the new user, can review the infos and tips that he/she needs to know on that site: "now you can: # watch that forum where that important thing is discussed.... #join that newsletter/blog/articlefeature to be up to date about news from that community, #review and/or subscribe to that tracker..., ... (11:45:22) xavi: oh well, I can't code php+mysql myself (yet, at least ;-) ), but I guess that this shouldn't be that difficult nor time consuming to an experienced coder, provided that that person agrees on that this feature is "low hanging fruit" to improve the experience of newcomers to a community, through improving the communication while the first steps of that person in the community site... {QUOTE} This could also be important for ((Workspaces)), and ((Organic Groups)). So that, not just to register (join the registered group), but as a customized message per group, so that, when joining a new group (at registration time, or later on through the subscribe groups plugin), you get the specific message with hints, links and remindings of things adapted for that group. |
tracker item |
|
Site customisation should be highlighted and All features enabled by default, empty header.tpl
a) I spent weeks testing these features one by one. It will save time if all these features are enabled and complete with samples. This is the approach used by Joomla and Mambo. It also helps us learn faster. b) The assist module is useful but asking users to read a tedious configuration as the first step will eat up too much time. Site configuration or Look at Feel should be the first one. It is also the most dangerous but essential. c) Provide a clue, in the assist if possilbe, to replace a damaged header.tpl with a skeleton header.tpl |
tracker item |
|
syntax type=markdown code disappears from Content Template
I'm trying to create a Content Template that indicates intention to use markdown, like shown on this page (for example): [https://markdownthemes.tiki.org/tiki-pagehistory.php?page=Markdown+Plain&source=0] After I put the following code at the top of that Template {CODE(theme="default")}{syntax type=markdown}{CODE} and then Save the template, this code disappears after I re-open for editing. If the template is used in a Wiki Page, the above code is also invisible. Unfortunately, the content of the template only shows as a binary blob in the database, so it can't be edited directly and cleaned up. |
tracker item |
|
unable to activate various functions like google analytics
It is impossible to activate various Functions... In the Administration Menu under "Editing and Plugins" it is impossible to activate functions like "google analytics" and lots more... everytime I want to save I get a "permission denied" {CODE()}Forbidden You don't have permission to access /content/tiki-admin.php on this server.{CODE} The Module is unusable right at the moment... I did: - disable the searchengine friendly urls - did a complete reinstall - applied chmod 755 over everything Nothing did work... |
tracker item |
|
Unable to Lock Content Template
__Describe precisely what you did (how to reproduce).__ During creation of a Content Template, the "Paddle Lock" symbol seems to be inoperable. Also the list page for Content Templates, has a "Paddle Lock" symbol that is no operating either. __Describe exactly the faulty consequences.__ After Content Template creation, there is a "Paddle Lock" when clicked, does nothing. __Explain what you expected instead of the faulty consequences. __ I expected the "Paddle Lock" symbol to lock itself upon clicking, thus rendering the Content Template only editable by admin. |
tracker item |
|
Wiki pages: define a content template as default?
Content Templates are an easy and comfortable way to change the look and content of wiki pages. It would be nice to be able to define such a template as your default for wiki pages, instead of having to choose it every single time you create a new wiki page, or changing the template of wiki pages in general. |
tracker item |
Using { { itemId } } in a template shows the actual itemId followed by an equal sign in Tiki 27.3. This works normally is Tiki 27.2