Category: Admin Interface (UI)

The code looks like this (right, it's also missing ARIA attributes):
{CODE()}
<label class="col-sm-4 col-form-label">{tr}Forum Order{/tr}</label>
<div class="col-sm-8">
<div class="form-text">
{tr}{$forumOrder|escape}{/tr}
</div>
</div>
{CODE}

but only the label displays. There's no forum order information. Apparently this page is related: tiki-admin.php?page=forums&cookietab=2&highlight=forums_ordering so maybe something set here should show up as forum order on the forum's main admin tab, but I don't really know. Anyway, either the data should display or the label should be removed.

I spot it on three branch 21 sites (themes.tiki.org, doc.tiki.org, and my localhost branch 21, but not in trunk): on tiki-admin_modules.php#content_admin_modules1-1, only "Edit" shows up in the action popup for each module. There's no "Move up", "Move down", or "Unassign".

Once again I stumbled upon texts of Tikis admin GUI had resisted being translated, and later I found that nonprinting characters were hardcoded that will block tra() or tr() from pattern matching. Even spaces can block a translation. I won't make new bug reports for those, but rather use this one as sort of an umbrella bug report which I will amend with comments.

So the first new occurency of nonprinting characters that block translations is found on line 130 of /lib/prefs/tracker.php:

{CODE(Colors="Tiki")}
'description' => tr("Require users to fill in a tracker form if not done already by prompting them with a modal dialog "),
{CODE}

Those two spaces (yes, two, not one or three...) may look like a little glitch from a dev's perspective, but since they do not print, you cannot translate this string by copy & pasting from the GUI into custom.php giving a translation: The pattern matching cannot find it. There is a workaround, but this may not be so easy for translators with little experience and with small toolboxes (Windows comes with FAR less useful tools for this than Linux...), since if you encounter those, you have to grep through the entirety (!) of Tiki source code to find the origin of the string, to be able to look at it's source code, to be able to copy & paste from there...

It's minor but should it worry a site admin?

To reproduce this bug:
1) Open Admin Groups Page
2) Number of Displayed Rows will default to 10
2) Change "Number of Displayed Rows" to 20
3) Hit Enter.
4) Additional Rows will display.
5) Add a Group.
6) Hit Save
7) Number of lines displayed changes back to 10.

Thanks for looking at this. dthacker.

Tiki has an online support feature. In order to use it, users must become "operators" by granting from the admin. If they are no operator, and try to open the support console, then they get an error message, that they need to be operator. So far okay. I tried that feature (in order to translate it), and to do that I activated it. And as I wanted to see the error message that unauthorized users get, I clicked to open the support console.

Underneath the error message that I was no operator was the info "no support requests". That info IMHO should not be given out to non-operators.

{syntax type="tiki" editor="plain"}
With the new build system, custom theme option names show up in selectors, but the themes aren't applied.

{syntax type="tiki" editor="plain"}
On a fresh Tiki27 at tiki-admin.php?page=orphanprefs the admin will see the following message:

"The jQuery Sortable Tables feature must be activated for the sort feature to work."

A link or an option to enable the jQuery Sortable Tables feature should be added as well.

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

Many times, I don't want the Orphan page feature. But I do want the list pages. Since they now use the same option (feature_listPages), it's annoying.

Let's create feature_OrphanPages (off on a clean install). Menu items will need an update.

I wonder why I did not see this before... But now it's clear to see.

The function to count page accesses is completely (!) out of order. My site contains > 300 pages. ALL OF THEM have an access counter in the "list pages" view of 0. Zero, nada, nothing. During my efforts to create a readable German translation I have visited numerous pages time and again, there must have been thousands of page impressions, and yet every single page is counted as having zero visits...

The absolute minimum for every page would be the number of page revisions plus one, because every page is visited after creation or modification. But all of the >300 pages list as 0...

And again, the need of a bug category "LOSS OF DATA" arises...

When the fullscreen feature is available but not on, and I make the wiki edit screen fullscreen (using toolbar icon), the side-column toggle icons continue to display, inappropriately. They are visible in their normal positions (when side columns are active) even though the edit screen is already fullscreen.

Their should be a check to not show these icons when the wiki editor is fullscreen. (Checking with the DOM inspector, I see the normal Tiki columns are still in place "under" the fullscreen editor, but their content doesn't display. The side-column icons are the exception. So it's kind of like a z-index problem but I don't see what z-index properties are involved, if they are.)

To be specific, the perspective's theme is applied on pages like tiki-admin_calendars.php, but not on tiki-edit_perspective.php or pages like tiki-admin.php or tiki-admin.php?page=general. On these pages, the default theme of the site is used instead. I haven't checked yet if other perspective preferences are also ignored.

{syntax type="tiki" editor="plain"}
Tiki has the option to interact with Google Analytics.

Now the first court rulings are there: Google Analytics directly violate the GDPR, therefore they are illegal throughout the EU. Fines are VERY heavy, so this must not be taken lightly. The fines range up to 20 million Euro or 4 percent of a year's turnover (sic! Not profit!), whichever is HIGHER.

Yes, Analytics is optional, and it's the decision of an admin, correct.

But IMHO Tiki should inform the admin when he/she activates this, that compliance with current law must be observed, and that Analytics can be (very) problematic in this regard. And to be on the very safe side, IMHO there should be a checkbox that spells out as confirmation "Yes, I am aware of the compliance issues imposed by this".

Please add a feature to Tiki to automatically sort marked content. And please use it on tiki-admin.php, because due to the translation, the list of plugins is__totally__ ill-sorted, making the use much harder than necessary. The same goes for permissions...

Only an automated sorting would automatically apply to every translation, and would not have to be redone after changes....

Thanks

The first issue is that I received the notice to approve the plugin even though I already approved the plugin at the site after editing the page. This is a regression.

The second issue is that the email message is malformed. It says:

"Plugin html is pending approval on Shared_t_o_footer."

And the text "Shared_t_o_footer" is supposed to be a link to that page, but it isn't a link. What should be the URL is actually the data from the body of the plugin, that is, the entire wiki page content in this case.

PluginLayout assumes there will be one content area in the foreground and one full-width background area behind the content. To create a full-width area for the page background image, PluginLayout changes -+div class="container"+- to -+div class="container-fluid"+-.

But for some page content layouts, the page backgrounds, etc. are full-width, but the text content is limited to the normal container width (1270px or whatever) in (vertically) alternating sections of the page, like on [http://demo.zukathemes.com/Happy+Scroll].

The layout on that page starts out with a full-width page to get the wide backgrounds behind the headings. Then -+div.container+- is used in the sections with columns of text. But with the plugin currently, ''every'' instance of -+container+- gets changed by the plugin to -+container-fluid+-.

Setting the "contentwidth" parameter to 80% or whatever doesn't help because this also limits the width of the section background images.

It would be good if only the outermost instances of -+div class="container"+- were changed by the plugin (not the nested or child instances), so any instances of -+div class="container"+- in the wiki text wouldn't be touched by the plugin - they would remain -+div class="container"+-. This would enable alternating sections of full-width backgrounds and container-limited content on the page.

(Of course I'm open to other ways of achieving the same result with this plugin, if there's a better/easier way.)

{syntax type="tiki" editor="plain"}
Possible to see admin "Advanced" options when the parent "Experimental" feature is not visible.

See the attached file (video screenshot)

That doesn't make sense.

Or all children should be hidden as well or, once enable, an optionis always visible. (and its children too)

(or, alternatively, wrong user input method) The admin UI for the facet feature describes, that the user shall enter a comma-separated list of categories, yet a multiselection window is presented.

Interestingly, in /lib/prefs/category, where this help string comes from, is text input specified ?! If that would be presented, the text would be right, but somehow it is not...

{CODE(Colors="Tiki")}
'category_custom_facets' => [
'name' => tr('Generate custom facets from categories'),
'description' => tr('Comma-separated list of category IDs.'),
'type' => 'text',
'size' => 15,
'filter' => 'int',
'separator' => ',',
'default' => '',
'profile_reference' => 'category',
],
{CODE}

cf. screenshot (attachment)

While dealing with tracker data, the preference "Sortable Chosen Multi-selects" seems to not work at all. The jquery seems fine, in that I can drag and drop items, but when I go to save the tracker, it ignores the order in which the fields were sorted in.

I have noticed this predominately while editing a tracker item.

When you install new Tiki 11.x and go to Features admin panel, you see only Watches fieldset when the Basic filter is on. When you choose Advanced, some more features appear, but still not the main global ones such as Wiki, Articles, Blogs, Forums features... Unless you check all the four filters (Experimental and Unavailable), you do not see them. Weird ? Instance showcase coming up. Hold on.

__Update:__ ~~#F00:__This bug is not reproducible on show.t.o 11.0 but on latest SVN branch 11.x__~~
I could demonstrate it on 11.2svn here:

{flash type="url" movie="display482" width="801" height="801"}

On a fresh install, I enabled image galleries without realizing that neither GD or ImageMagick libraries had been installed. I was able to create a gallery and attempt an upload of images, which failed with a vague "Upload can not be processed". It was only after visiting the second admin screen (http://localhost/tiki-admin.php?page=gal) that I was able to see that the proper libraries were not installed.

This code in db/tiki_1.8to1.9.sql used in upgrade script, is causing duplicate menu items.

{img src=images/code.png}%%% {CODE()} INSERT IGNORE INTO tiki_menu_options (menuId,type,name,url,position,section,perm,groupname) VALUES (42,'o','Mobile','tiki-mobile.php',37,'feature_mobile','','');
{CODE}

{img src=images/code.png}%%% {CODE()} INSERT INTO tiki_menu_options (menuId,type,name,url,position,section,perm,groupname) VALUES (42,'o','Users map','tiki-gmap_usermap.php',36,'feature_gmap','',''); {CODE}


Duplicates also happen for 187, and 188, 900, 1191, 1235, and in a minor way, 189, 780,

See screenshot attached.

{syntax type="tiki" editor="plain"}
When I cloned the system menu, the clone had many duplicate menu items (options). I posted some screenshots here: https://matrix.to/#/!SLEgqpTNTlGYAhzNvK:gitter.im/$fXaHIgU2lnDuxIUeyFASiRQNjsH_smpZyE5RDBwopP0?via=gitter.im&via=matrix.org&via=coeus.ca . I didn't check yet if smaller (few menu items) menus would clone correctly.

Also, when trying to preview the clone menu, only the top-level menu items displayed. There were "+" symbols to click to see the dropdown-menu items, but clicking them didn't work so the dropdown-items couldn't be seen.

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.