Category: Developer Training

Create a profile for an improved Issue Tracker (with linked trackers) using the latest improvements in 14x

See this discussion:
[http://irc.tiki.org/irclogger_log/tikiwiki?date=2015-03-17,Tue&sel=180#l176]

When you load a tracker list at the bottom you have an action dropdown to do bulk modifications.
By default "Delete selected" (items) is selected.

{img fileId="1607" thumb="box"}

This is not safe and shouldn't be like this as manipulation or unwanted click (on mobile, delays between display and click, etc) may have catastrophic consequences.

Empty selection is the safest option but anything else should be better.

Just compare the footer of profiles.tiki.org to dev.tiki.org

{img fileId="300"}


(previously titled: ''dev.tiki.org: The footer links are squished after the upgrade from 10.x to 11.x'')

This is from Google monthly report for Doc.

{img fileId="1628" thumb="box"}

Obviously we want people searching in google to land on real and good content that promote Tiki, give information or help (support).
Not printing...

Using strasa.css in demo.t.o/11.x (reproduced else where also)

Log in as admin
Edit a wiki page,
click at a tool in the toolbar (help icon clicked in the screenshot below)
popup box is shown under the text area, no button are shown, most controls are hidden, etc.

See screenshot

{img fileId="288" thumb="y" rel="box[g]"}

{syntax type="tiki" editor="plain"}
When I click the emoji icon on the toolbar in master, nothing happens.

There is an empty comment from Adrien at https://dev.tiki.org/tiki-view_tracker_item.php?itemId=7935&threadId=9839
It is displayed as "" in the plugin Since last visit...

{img fileId="1642" thumb="box"}
{img fileId="1643" thumb="box"}

{syntax type="tiki" editor="plain"}
Empty slides are added on the Wiki page slideshow

Visible here : https://doc.tiki.org/slideshow

{syntax type="tiki" editor="plain"}
The original Pagetop Hero idea included some JavaScript to dynamically relocate a -+top-image+- class image from the wiki page, blog, article, etc. text to the topbar module location. This is demoed at https://themes.tiki.org/Topbar%20hero. This way, the image can be easily specified while editing the page or post content, can easily be specific to the page or post, and there's no need to do any content editing in the admin modules interface. If this JavaScript and the dynamic function it enabled were added to the implemented module code, I think the module would be greatly improved.

Set a tracker to display items with a wiki page template.
Don't create the template so it is missing.

When viewing a tracker items popup this (ugly) error.

{CODE()}Fatal error: Uncaught exception 'SmartyException' with message 'Unable to load template file 'promo_tpl' in 'tracker_pretty_item.tpl'' in /var/www/sites/xxx/xxx/subdomains/www/html/vendor/smarty/smarty/distribution/libs/sysplugins/smarty_internal_templatebase.php on line 127 SmartyException: Unable to load template file 'promo_tpl' in 'tracker_pretty_item.tpl' in /var/www/sites/xxx/xxx/subdomains/www/html/vendor/smarty/smarty/distribution/libs/sysplugins/smarty_internal_templatebase.php on line 127 Call Stack: 0.0020 1106896 1. {main}() /var/www/sites/xxx/xxx/subdomains/www/html/tiki-view_tracker_item.php:0 0.2151 29471160 2. Smarty_Tiki->display() /var/www/sites/xxx/xxx/subdomains/www/html/tiki-view_tracker_item.php:723 0.2151 29471896 3. Smarty_Internal_TemplateBase->display() /var/www/sites/xxx/xxx/subdomains/www/html/lib/init/smarty.php:348 0.2151 29472056 4. Smarty_Tiki->fetch() /var/www/sites/xxx/xxx/subdomains/www/html/vendor/smarty/smarty/distribution/libs/sysplugins/smarty_internal_templatebase.php:374 0.2152 29475872 5. Smarty_Tiki->fetch() /var/www/sites/xxx/xxx/subdomains/www/html/lib/init/smarty.php:229 0.2154 29476112 6. Smarty_Internal_TemplateBase->fetch() /var/www/sites/xxx/xxx/subdomains/www/html/lib/init/smarty.php:254{CODE}

Should display the item with the tracker standard view (no template).
Eventually display a small error to admin only.

It would be good to be able to prevent wiki pages in a specified category from being listed by this module (last_modif_pages). For example, at the *.tiki.org sites, there are "Archived" and "Retired" categories for wiki pages that have old content, etc. and so are for admin users or registered users only. When a page is edited to be categorized in one of these categories, it is then listed in the module, but this isn't a change that needs to be, or should be, publicized, since the page is being removed from access.

There should be a field in the module parameters like "Don't list pages in these categories", where category names or ids could be input and pages in these categories wouldn't be listed in the module.

Logged as admin, when you navigate inside the File Galleries you can see the name of the Gallery you are in and close to it a wrench. The wrench tootip let you understand that you will be able to interact with THIS file gallery settings but in reality you are sent to the Admin Control Panel "File Galleries".
https://dev.tiki.org/tiki-admin.php?page=fgal#File%20Galleries

{img fileId="2091" thumb="box"}

This is quite confusing for new Admins.

Once the file gallery batch feature is enabled:
At https://next.tiki.org/tiki-batch_upload_files.php?galleryId=17 at the bottom if you enable "Upload into galleries according to sub-directories" other options are displayed but the design alignment and position of sentence is broken. Col-4 and 8 are over lapping instead of being one next the other.

As the additional options are child of "Upload into galleries according to sub-directories" they should look like child options (indent)

{img fileId="1649" thumb="box"}

The general translation behaviour for Tiki features is to allow translations of titles and other labels.
Page title, trackers (title, field names), categories and eventually to allow wiki syntax that allow the admin to set TR tags where it is needed (tracker description, wiki page content, etc...).
But not for Tiki file gallery. ??‍♂️

The translation of term(s) is found in tiki lang/../language.php or lang/../custom.php

Following the discussion in the comments the conclusion is:
1/ There are reasons for this as it may be unwanted to automatically translate terms of a file title (file name on import if none is specified).

2/ To allow translation of file title and file description it will made sense and easier to do it at the wiki plugin level, something like:
{CODE()}
{file type="gallery" fileId="1225" browserdisplay="y" translatetitle="y"}
{CODE}

There is no option to display the file description using the plugin and it is not necessary to add one.

{img fileId="1618" thumb="box"}
Those radio buttons should look like bootstrapped Tiki (colors, borders rounded, etc).

At https://tiki.org/tiki-syslog.php we have a link to "Log SQL".
If we click on it we have the following error.

{CODE()}
×
Error
This feature is disabled: adodb
{CODE}

The link shouldn't be displayed if the feature is disabled.

{syntax type="tiki" editor="plain"}
In dark color mode, the page background is dark and foreground text is a light color, but when a new post is added in Tiki's forums, it is highlighted like this:

-+ <article class="card post commentStyle_plain mb-3" id="threadId11" style="background-color: rgb(255, 255, 255);"> +-

That inline CSS produces a white background, making it impossible to read the light-colored text in the post. Instead of inline CSS, a class or a CSS variable, like

-+style="background-color: var(--bs-primary-bg-subtle);"+-

should be used, so the color will be appropriate in light or dark (or other) color mode.

Tiki has a way to create "user" plugins with: https://doc.tiki.org/Plugin+Alias

At https://doc.tiki.org/tiki-admin.php?page=textarea or on the instance I created:
Go to Admin, Control Panels => Editing and Plugins => Plugin Aliases.
Create Aliases (or edit) and click on "Plugin parameter documentation" you will see a new form with checkboxes.

This happen on Safari 14.1.2 on Mac OSX but not on Chrome

The "Safe" checkbox overlap with text.
{img fileId="1638" thumb="box"}

improve doc for devs about the right way to develop permission checks (global, category and local)

I wish there was a place (ideally) were permission checking in tiki was explained for dev dummies: global, categ and local object perm checking.
That documentation at dev.t.o should be linked, at least from:
* https://dev.tiki.org/Permission
* https://dev.tiki.org/Permission+inheritance
* https://dev.tiki.org/Hello+world#To_check_a_permission

At /categories and https://dev.tiki.org/tiki-admin_categories.php we can see the categories list.
It is a bit stiff and when you have a lot of categories and start to open them to see the child categories the UI/UX is not very good.

{img fileId="1662" thumb="box"}

At tiki-admin.php?page=i18n if you enable "Restrict supported languages" you see a text area with 5 languages.
This is too small and make painful selecting several languages.

The text area size cannot be extended.
It should be possible.

{img fileId="1625" thumb="box"}

In history, a user can view pages, version after version, to find a change.
He can do it using the left and right arrows when viewing a page.

In the top nav bar (t_navbar) the buttons doesn't refers to the actual page he is previewing (displayed) but to the actual version of the page published.

{img fileId="1646" thumb="box"}

# It is a bit confusing for most users are expecting unspecified-target actions to be applied to what they see.
## First button label should be changed to "Go back to the actual page (last version)"
## Second button label should be changed to "Edit actual page (last version)" (or eventually removed)
# To view the source of this version of the page (if I'm looking for a plugin code or some syntax), I have to remember the page version number, go back to the page, go back to history and view the source (if available).
## A "View this version page source" is missing

Gary may be consulted for better wording. ;-)

There are places Tiki ask to confirm "an" action but the action is not stated.
User should be told "what" is to be confirmed.

Here a video from Calendar, delete event.
{file type="gallery" fileId="1696" showicon="y"}

Thanks, Marc.

I had all the minify's set on tiki-admin.php

I first unchecked:
Minify CSS into a single file (found in performance)
and got:
Invalid CSS property declaration at: . temp/public/minified_b0ce6c498b992dbbce71a8e58b27e5e9.css:4
Invalid CSS selector: input.ui-button::-moz-focus-inner,button.ui-button::-moz-focus-inner temp/public/minified_9853f6dd93c8f0e01d7638e38b456649.css:19
Invalid CSS property value: #blue temp/public/minified_814bb502a7fbafe471223475b3b5128f.css:1
Invalid CSS property name: -webkit-overflow-scrolling temp/public/minified_6df987c4671ceba4d5b952189c509395.css:1
Invalid CSS property declaration at: . design.css:2528

Clearing caches didn't help. I then unchecked
Minify CSS (found in performance)
and got:
Invalid CSS property declaration at: . lib/codemirror_tiki/codemirror_tiki.css:32
Invalid CSS selector: input.ui-button::-moz-focus-inner, button.ui-button::-moz-focus-inner vendor/jquery/jquery-ui-themes/themes/flick/jquery-ui.css:222
Invalid CSS property name: -webkit-overflow-scrolling vendor/jquery/plugins/colorbox/example1/colorbox.css:9
Invalid CSS property declaration at: . design.css:2528
Invalid CSS property value: #blue temp/public/codemirror_modes.css:94
Invalid CSS property declaration at: ; temp/public/codemirror_modes.css:219



On Sat, Sep 7, 2013 at 11:09 PM, Marc Laporte wrote:
> I suggest to un-minify and to see where it comes from.
>
> Then, it is likely worth reporting to http://dev.tiki.org/Make+a+wish
>
> It will likely be low priority, but easy to fix. And we need easy ones
> that we can give to new devs or students.
>
> Best regards,
>
> M ;-)
>
>
>
> On Sat, Sep 7, 2013 at 11:02 PM, Pete Jalajas wrote:
>> While tracking down that other weird problem, I noticed these in my
>> Chrome Dev Tools window:
>>
>> Invalid CSS property declaration at: .
>> minified_28c0e59edef0064ad5ab707ffc53162e.css:338
>> Invalid CSS property declaration at: .
>> minified_28c0e59edef0064ad5ab707ffc53162e.css:622
>> Invalid CSS property value: #blue
>> minified_28c0e59edef0064ad5ab707ffc53162e.css:623
>> Invalid CSS selector:
>> input.ui-button::-moz-focus-inner,button.ui-button::-moz-focus-inner
>> minified_28c0e59edef0064ad5ab707ffc53162e.css:645
>> Invalid CSS property name: -webkit-overflow-scrolling
>> minified_28c0e59edef0064ad5ab707ffc53162e.css:749
>>
>> I'm using tikinewt theme with shadows.
>>
>> Do I care?
>>
>> Thanks,
>> Pete
>>

The "Location" item in a calendar event's information accepts only plain text. Since meetings are often online, it would be nice if the location could be a working link. A URL can be input, but it isn't clickable. Being able to use wiki syntax (or Markdown?) would be easiest for the admin.

By the way, the form layout is messed up for this item. The label and information should be inline (side by side) like the other items, but the information is on the next line instead.