Category: Admin Interface (UI)

So we know which admin created a login...


We currently have a log entry when a user is assigned to a group, but not when he is unassigned.

Also, we have:
unassigned perm tiki_p_broadcast from group admin

but not:
assigned perm tiki_p_broadcast from group admin



Maybe adding failed login attempts would be good too...

Tiki User credits: You can create Credit types (which you need to do, because the feature starts empty), but once created, you can never admin/edit them. Not even delete them. This is so basic a function, that I do not open this as a feature request. It is a bug.

Btw., there is no documentation to be found about this feature...

{syntax type="tiki" editor="plain"}
Users can have several status:
*new account (needs to be validated)
*normal account.

Maybe we will want more in the future (ex.: suspended)

It would be good for the admin to be able to see the status in tiki-adminusers.php, filter by type and change/override the status. Ex.: a user never received the validation email because of spam filter.

I'm trying to customize my Tiki instance. On the Look & Feel (tiki-admin.php?page=look) page, in the second tab (General Layout), I want to change the default logo. The only way (I saw) to do so is to specify 'manually' an image path from the img/ folder. I captured the screen, you can have a look ((https://ibb.co/izZ0X7|here)).
UX speaking, it would be better for the user to import an external image (logo) in the img/ folder and select it as a logo easily, through an Image Importer.

I have no idea what version I have.

The Webmail and Cypth connection small alert and feedback (not the real usual Tiki verbose) are hidden under the top navbar when using the Classic Bootstrap layout.

If a package is missing the help/warning information displays a link to the external missing package repository.

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

It is __important to note__ that we have already a similar mechanism when looking to a page (not the admin control panels) that display a message for admins (I hope for admins only ?)

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

---

At http://bsfez-11581-7999.show2.tikiwiki.org/tiki-admin.php?page=fgal&cookietab=6&highlight=feature_docs, enable "Use PDF.js".

It will display an alert (red background):

The first link "Missing tiki package :" with a link to : tiki-admin.php?page=packages

Then "npm-asset/pdfjs-dist-viewer-min" with a link to :https://asset-packagist.org/package/npm-asset/pdfjs-dist-viewer-min

It should display:
"A Tiki package is missing: Install mpdf/mpdf"
"Install mpdf/mpdf" should be a link to : tiki-admin.php?page=packages

1. Tells the user of a problem
2. Explain what is the problem
3. Suggest the user a way to solve the issue
4. Give the user the direction/action to solve the issue

That's the way a missing package should handled, anywhere.

I added "anywhere" because it seems we have different behaviours.
IE: Go to http://bsfez-11581-7999.show2.tikiwiki.org/tiki-admin.php?page=print
For the "PDF from URL" dropdown, select mPDF. The "PDF Orientation" error will show
"Missing tiki package: mpdf/mpdf" with parts with the same link. (not needed)

{file type="gallery" fileId="1771" showicon="y"}

{syntax type="tiki" editor="plain"}
I just did a test install of Tiki 29.0 beta. I'm not sure what the purpose of the "default password" is. This is shown on two screens near the end of the installation process ("Your default password is iw9z3"), but on the next screen is the form to input the actual new password, which makes no reference to the "default password" which is never used, never appearing on the actual password creation page. I was wondering "What was the point of that?"

If the purpose of the default password is to just be there in case the installation process is interrupted before the admin can set a new password (is this the rationale?), then that should probably be stated on the page where the default password is shown, something like "This is the default password for the admin account of this Tiki website, but in the following step please replace it with a password of your choice. This default password is provided in case the installation and configuration process is interrupted." That's what I can come up with based on my impression - I don't know what the actual purpose of the default password is.

Without an explanation, I think the new user will think the installation process is a bit quirky or broken, not a good first impression.

When the system (in this case was a Linux box) runs out of disk space, a Tiki user cannot login. Basically, the user is sent back to the home page. In other words, it looks like the user has authenticated, but is not logged in. So it looks like a PHP session issue. It could well be.

If the user enters a wrong password, a wrong password message is seen.

It would be nice if Tiki could detect that the disk space is low and alert admin users, especially during install. Low priority of course, but still nice to have.

MoinMoin example:
{THUMB(id=29, url="tiki-browse_image.php?imageId=29")}{THUMB}

https://doc.tiki.org/tiki-admin.php?page=wiki is broken:
{CODE()}Fatal error rendering template resource tiki.tpl
TypeError: Cannot access offset of type string on string in /home/tiki-doc/public_html/temp/templates_c/en_social^ea0943f75a262d8be544059ae17e04e9602d1469_0.file.header.tpl.php:65
Stack trace:
#0 /home/tiki-doc/public_html/vendor_bundled/vendor/smarty/smarty/libs/sysplugins/smarty_template_resource_base.php(123): content_64ff5e10934248_92322649()
#1 /home/tiki-doc/public_html/vendor_bundled/vendor/smarty/smarty/libs/sysplugins/smarty_template_compiled.php(114): Smarty_Template_Resource_Base->getRenderedTemplateCode()
#2 /home/tiki-doc/public_html/vendor_bundled/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(217): Smarty_Template_Compiled->render()
#3 /home/tiki-doc/public_html/vendor_bundled/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(386): Smarty_Internal_Template->render()
#4 /home/tiki-doc/public_html/temp/templates_c/en_social^0c780eb23ca96bccad634bcfe8b1582ea34cbefc_0.file.layout_view.tpl.php(40): Smarty_Internal_Template->_subTemplateRender()
#5 /home/tiki-doc/public_html/vendor_bundled/vendor/smarty/smarty/libs/sysplugins/smarty_template_resource_base.php(123): content_64ff5e1268df80_55684014()
#6 /home/tiki-doc/public_html/vendor_bundled/vendor/smarty/smarty/libs/sysplugins/smarty_template_compiled.php(114): Smarty_Template_Resource_Base->getRenderedTemplateCode()
#7 /home/tiki-doc/public_html/vendor_bundled/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(217): Smarty_Template_Compiled->render()
#8 /home/tiki-doc/public_html/vendor_bundled/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(386): Smarty_Internal_Template->render()
#9 /home/tiki-doc/public_html/vendor_bundled/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(116): Smarty_Internal_Template->_subTemplateRender()
#10 /home/tiki-doc/public_html/temp/templates_c/en_social^a242164352b905110d239d535f6a556a33d17bf9_0.file.tiki.tpl.php(38): Smarty_Internal_Runtime_Inheritance->endChild()
#11 /home/tiki-doc/public_html/vendor_bundled/vendor/smarty/smarty/libs/sysplugins/smarty_template_resource_base.php(123): content_64ff5e121411a2_61382528()
#12 /home/tiki-doc/public_html/vendor_bundled/vendor/smarty/smarty/libs/sysplugins/smarty_template_compiled.php(114): Smarty_Template_Resource_Base->getRenderedTemplateCode()
#13 /home/tiki-doc/public_html/vendor_bundled/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(217): Smarty_Template_Compiled->render()
#14 /home/tiki-doc/public_html/vendor_bundled/vendor/smarty/smarty/libs/sysplugins/smarty_internal_templatebase.php(238): Smarty_Internal_Template->render()
#15 /home/tiki-doc/public_html/vendor_bundled/vendor/smarty/smarty/libs/sysplugins/smarty_internal_templatebase.php(134): Smarty_Internal_TemplateBase->_execute()
#16 /home/tiki-doc/public_html/lib/init/smarty.php(492): Smarty_Internal_TemplateBase->display()
#17 /home/tiki-doc/public_html/tiki-admin.php(515): Smarty_Tiki->display()
#18 {main}
{CODE}

Wish: integrate 'Terms of Service, Didn't read' options https://tosdr.org into our Terms and Conditions feature

Maybe some options to let the tiki admin choose (radio button?) which of the policies from "Terms of Service, Didn't read" they have in their tiki site.

^From https://tosdr.org
__Terms of Service, Didn't read__
We are a user rights initiative to rate and label website terms & privacy policies, from very good Class A to very bad Class E.

Terms of service are often too long to read, but it's important to understand what's in them. Your rights online depend on them. We hope that our ratings can help you get informed about your rights. Do not hesitate to click on a service below, to have more details! You can also get the ratings directly in your browser by installing our web browser add-on:
^

Our feature:
http://doc.tiki.org/Terms+and+Conditions

When a fixed-top navbar is used, the page needs top padding of the same height as the navbar to prevent the navbar from obscuring the page content. Also, when an in-page TOC is used, and a link is clicked to go down the page to the relevant heading, the heading will be positioned at the browser window top, and under the navbar, unless there is an offset (such as margin/padding on the target heading).

Currently there is default pagetop padding for layouts using fixed-top navbars, but there isn't a fix yet in the Tiki stylesheets for the TOC problem (the Tiki project sites have a custom CSS rule as a fix). However, the height of the padding may not be right for all sites because the navbar height can vary depending on navbar content, font size, and so on.

Being able to specify the navbar height would ensure having the right px value for the site. (If there is a JavaScript solution instead that could be automatic and solve the problem, that would also be an acceptable solution, as far as I know.)

You can get to help easily enough, but it's kind of hard to find the "wishlist" page.

{syntax type="tiki" editor="plain"}
For themes that don't have child themes, the child theme selectors on tiki-admin.php?page=look should be empty and ghosted. But currently in master and branch 29, child themes are listed in the selector for all themes. The specific child themes that are shown change based on what parent theme was selected (but not necessarily submitted). Whatever the method is to show the correct child theme(s) for each theme, it's broken. This behavior goes away if Element Plus is turned off. (Selecting an incorrect child theme doesn't do anything, but the UI should be accurate, as it was up until Tiki 27.)

All of the wizards use icons that are hardcoded, and this results in them being un-influenced by the choice of iconsets, so they can look out of place.

This should be switched to the way almost all other icons are used (declaration by a given name, and redirection in /themes/basefiles/iconsets.

Almost, because tiki-sheet also uses hardcoded icons (should also be switched one day).

Please see ((workspace roadmap))

In a number of places in the admin interface, there's a wrench icon that, when hovered over, causes a popover/popup containing action links. Since the update to Bootstrap 4, this popup disappears with no delay as soon as the cursor leaves the wrench icon. The popover and its links disappear before any link can be clicked. There needs to be a longer delay before the popover disappears, similar to how it was with Bootstrap 3.

Please correct me if I'm wrong (if I am, this bug may be resolved invalid). If not then these strings need a correction.

In /lib/prefs/feature.php I find these escaped strings, line 2082:
{CODE(Colors="Tiki")}
'feature_jquery_zoom' => [
'name' => tra('jQuery zoom'),
'description' => tra('Enables zoom in images on mouseover or click. Used in Plugin Img with the parameter \"thumb=zoombox\"'),
'type' => 'flag',
'help' => 'PluginImg#Zoombox',
'default' => 'n',
],
{CODE}

And this is just one example, /lib/prefs/feature.php contains more.

tra() is called with a string that is enclosed in single quote and that contains double quote characters. But why is there a backslash in front of them?

That should - to my understanding of PHP - be unnecessary. On the contrary, only single quotes inside single quote marked strings need a backslash escape. Escaping a double quote character inside single quote strings would lead to backslashes being shelled out to the user in plain visibility (and irritate fellow translators trying to catch this string :-)

Or did I miss something?
Thanks for bringing me up to speed
hman

{syntax type="tiki" editor="plain"}
On tiki-admin_modules.php, the "Add module" button should link to the first tab "Edit module", not "Custom modules", because in most cases an existing module will be assigned, not a new custom one created. (The Edit module tab content contains the heading "Assign new module", which reflects that process.)
* So the "Add module" button link should be tiki-admin_modules.php?edit_assign=0&cookietab=1, not tiki-admin_modules.php?edit_assign=0&cookietab=2.
* Thinking about it more, it seems like the first tab label should be "Configure new module", not "Edit module", to better reflect the content of the tab. Modules are edited after being assigned, from their actions link, not in this tab, or else are edited as custom modules, but again not here.
* The "Assign new module" heading in the first tab content can then be removed, as it would be redundant.
I believe the button link issue is a regression but I don't know when it happened offhand.

Another thing, after selecting the module to assign, the page refreshes to an "Edit module" tab and there's a heading "Edit this assigned module: login_box". This is a smaller issue, maybe, but this heading is incorrect because the module is not yet assigned, which might confuse new users. To be accurate, it should be "Edit module: login_box".

When I click a user, I am offered to send him a message. But then I get:

User XYZ can not receive messages
ERROR: No valid users to send the message

1: WYSIWYCA: I should not be offered to send a message if the user has disabled that. (frustrating to write such a message for nothing)

2: tiki-user_preferences.php: "Allow messages from other users" default should be yes

3: tiki-user_preferences.php: "Send me an email for messages with priority equal or greater than:" default should be "3"

tiki-admin.php?page=login
3- Users accept internal messages by default: default should be yes -> $allowmsg_by_default

4- Users can opt-out internal messages: default should be yes -> $allowmsg_is_optional


All these should be the default settings (most logical) if a Tiki site admin choose to activate inter user messages.

Related:
Easier Inter-user message management for Tiki admins:
http://dev.tikiwiki.org/tiki-view_tracker_item.php?itemId=959

Also related:
Should sender email be disclosed when receiver gets notification via email? goals: balance privacy & facilitate communication/collaboration

Started in 3.0, needs to be used in tiki-admingroups.php and propagated to various places where permissions are set.


Also on wish list: A way to put more emphasis on more important permissions.

Either basic vs advanced or an ordinal column (top put more important stuff at the top)

So for a wiki page, view, edit and history should be at the top or in basic while tiki_p_use_as_template and tiki_p_export_wiki should be in advanced

The "Quick Admin" module is no longer assigned in default installs starting from {commit id=67387} (Tiki 19).

When defining a field in a mirrored Tracker, the Description of the field is not stored. This was in 2.0, and I'm told on IRC that mirrored trackers are not supported. But mirroring is an option in Admin>Trackers.

I looked today at http://info.tikiwiki.org/tiki-list_submissions.php and there are nearly 300 spam submissions there so far, and no way to delete them in groups. Maybe that's why nobody noticed my prior submission as info.tw.o editor from last month...

(the user need to be in info.tw.o Admin group in order to see the spam list. If your users is just in the info.tw.o_editors group, you'll see nothing but your own submissions if any.)

A text box to select the amount of rows to be listed would be welcome, and multiple checkboxes to select some or all, like with users, etc.

---
By the way, how can anonymous spammers post submissions to info.tw.o? They can't through http://info.tikiwiki.org/tiki-edit_submission.php (at least, nowadays)... Spam hole somewhere?

Our users keep adding large .ogg files in our files galleries and we have been asked to externalize theses files in a special download directory of the web server. Problem is that the admin screen of the files galleries doesn't have a DISPLACE section. You can set the option for the files to be added in an external directory, and the new ones are indeed placed into it, but the existing files stay in the database.

I have discovered that the *Image* galleries admin screen has this DISPLACE section but it will work only for the image galleries, no way to use it for the non image galleries.