Category: Admin Interface (UI)

The Site layout selector doesn't have any options. This is a regression from Tiki 14. I thought the problem might have been caused by my changing the names of the layout options, but now I think maybe this isn't the case (that is, I don't see code that would be edited similar to how I edited to make the layout name changes).

(I don't know how many people would change the layout template via the setup wizard, but the broken selector isn't good for user confidence.)
---
Thanks Gary for reporting!
I leave it as pending ad please retest for you Gary, in case you can confirm it somewhere else too; it's fixed for me, at least, in this show.t.o instance. {sign user="xavi" datetime="2016-04-20T08:03:49+00:00"}

With 19.1, the LDAP and LDAP external items in the Admin->Log In 'option' is a bit (for lack of a better word) confusing and two check boxes are in the wrong place.

1) As mentioned in ticket 7035, the LDAP user field settings is in both the LDAP section and the LDAP external group section. If the LDAP user field settings do the same thing, I would believe the LDAP user field should be in the "external group section".

2) Relatedly, the "LDAP External group" I believe it really should be renamed "LDAP external source". (Though I would hazard a guess that even this isn't right... just putting it out here as a suggestion).

3) Under LDAP external group, in the "LDAP user" settings, the checkbox is wrong "Synchronize Tiki groups with a directory". This really moved to the "LDAP group" part.

4) Under LDAP external group, in the "LDAP group" settings, the checkbox for "Synchronize Tiki users with a directory" should be in the "LDAP user" part.

In line 520, lib/prefs/feature.php containts text (a hint) that cannot be translated into any language, because it doesn't call tra():

{CODE(colors=tiki)}
'feature_contact' => [
'name' => tra('Contact us'),
'description' => tra('A basic contact form a visitor can use to contact the site admin'),
'hint' => 'You can use Trackers to create custom Contact Us forms.',
'help' => 'Contact+us',
'type' => 'flag',
'default' => 'n',
'dependencies' => [
'feature_messages',
'sender_email',
],
'tags' => ['basic'],
'admin' => 'general',
'view' => 'tiki-contact.php',
],
{CODE}

In lib/prefs/permission.php is a help text that resists all trials to translate it. It __does__ get pumped through tra(), but I cannot translate it even if I copy exactly the string from the PHP source code. I have also tried to substitute the line break that is contained by \n, the newline character. To no avail.

The code in question is this:

{CODE(colors="Tiki")}
function prefs_permission_list()
{
return [
'permission_denied_url' => [
'name' => tra('Send to URL'),
'description' => tra('URL to redirect to on "permission denied"'),
'type' => 'text',
'size' => '50',
'default' => '',
'tags' => ['basic'],
],
'permission_denied_login_box' => [
'name' => tra('On permission denied, display login module'),
'description' => tra('If an anonymous visitor attempts to access a page for which permission is not granted, Tiki will automatically display the Log-in module.
Alternatively, use the Send to URL field to display a specific page (relative to your Tiki installation) instead.'),
'type' => 'flag',
'default' => 'n',
'tags' => ['basic'],
],
];
}
{CODE}

The string in 'description' cannot be translated. And when I grep through the entirety of Tiki 18.6, in __no language__ has anyone managed to translate this part, because in all of the 58 languages that are available in /lang, not a single one custom.php or language.php contains a string starting with "If an anonymous visitor"...

Tiki website admins probably expect page hits to be recorded and shown on List Pages, but they aren't unless the Stats feature is activated. (It seems to me they used to be, long ago, but maybe memory is failing me ;-) .) If recording/displaying page hits can't be separated from the Stats feature, so it's on by default even if Stats isn't activated, then at least there should be a notice on List Pages like "To have page hits recorded and displayed here, activate the Stats feature."

The live support system does not have a function to delete support requests, chats or messages. The one delete that is offered deletes an operator. With the operator also all support data is lost, which might be undesirable. Reinstating an operator does not reinstate the data.

Two tracker properties, "Template to display an item" and "Template to edit an item", are currently under "Section Format" of the tracker "Properties" form. This isn't an intuitive location for them IMO. I think they should be under "Display" since they are related to the tracker item interface. They aren't related to tracker item sections as far as I can tell.

While some issues have been fixed around logo image, brand icon and classic bootstrap layout, it's still necessary to go to L&F admin to turn on "site logo and title" (IIRC) before the logo module is available to be assigned on the admin modules page. That should be a separate wish.

See related ticket

Five of the plugins in 18.7 cannot be activated. Simply, because there is NO checkbox for "activate"! How come? Have they been withdrawn? If so, why wasn't their heading removed? Headings are there, hints also, but no "activate".

The non-activateable are

- footnotearea (cf note: footnote is there!)
- paymentlist
- pdfbookmark
- pdfpage
- pdfpagebreak

/lib/prefs/feature.php contains 11 instances of quote characters that are wrongly escaped. To my understanding of PHP they shouldn't be escaped with a backslash if they are in single quote strings, which they are.

Example:
{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}

The description string is enclosed in single quotes, yet the double quotes that are part of the string were escaped with backslashes. And the strings are fed into tra().

This leads to the backslashes being visible to the user in English language, and making translating really hard: The only way that tra() will catch these with a content from custom.php is double escaping like this:

{CODE(Colors="Tiki")}
"Enables zoom in images on mouseover or click. Used in Plugin Img with the parameter \\\"thumb=zoombox\\\"" => "Emöglicht, in Bilder hineinzuzoomen bei Mouseover oder Klick. Im Img-Plugin mit dem Parameter \"thumb=zoombox\" verwendet",
{CODE}

I'm not sure if many writers of other translations out there know about this implication...

Not all strings in feature.php have been escaped like this, actually there are 11 instances of \" in there. Some, actually many, strings were written the right way like this example:

{CODE(Colors="Tiki")}
'feature_jquery_reflection' => [
'name' => tra('Reflection'),
'description' => tra('Creates a reflection under an image. Used in Plugin Img with the parameter "class=reflect"'),
'type' => 'flag',
'help' => 'JQuery#Reflection',
'default' => 'n', // reflection effects on images
],
{CODE}

The 11 instances are on lines 1526 (2), 1841 (2), 2084 (2), 2191 (2), 2928 (2). Line 2496 uses \" for something else.

Related:
((MemoryConsumption))


Here is a very famous error: "Fatal error: Allowed memory size of 8388608 bytes exhausted"
http://tikiwiki.org/art82

And they often cause blank pages. How can we can catch them and render a simple & descriptive error page (not enough memory) instead of a blank page?


__Maybe useful?__
Smarty validation class
http://www.phpriot.com/d/code/smarty/smarty-validator/index.html



Related:
Better protection against accidental site breakage with improper use of code in modules + template
http://dev.tikiwiki.org/tiki-view_tracker_item.php?itemId=1065

This feature isn't internationalized.

The usage of quicktags is hardcoded in the PHP, like

$quicktags = $quicktagslib->list_quicktags(0,-1,'taglabel_desc','','trackers');

for the trackers. The french translation e.g. reads

Catégorie : wiki, formulaires, etc.

So a french user would enter "formulaires", but never see his Quicktags in the Trackers feature.

{syntax type="tiki" editor="plain"}
In barebones profile and in featured profiles, there is intro text about 1st login being necessary with u: admin p: admin (good)

However, this message stays and needs to be deleted by admin (bad)

Perhaps we should have a module with is only visible if admin password has not yet been set.

Many people use the wiki without structures. It should be optional, like the rest.

During the last few weeks before launch of 1.9.8, many fixes were introduced. They need to all be evaluated and ported to 1.10



Needed in 1.10 script: change password -> 999 days and 1999 days, needs to become -1 (and a warning in tpl not to use these values) 999 become 1000 and 1999 becomes 2000 if you try.

ref: [http://tikiwiki.cvs.sourceforge.net/tikiwiki/tiki/db/tiki_1.8to1.9.sql?revision=1.79.2.194&view=markup&sortby=date&pathrev=BRANCH-1-9]

Making tiki-admin_modules.php more intuitive (last few commits):
http://tikiwiki.cvs.sourceforge.net/tikiwiki/tiki/templates/tiki-admin_modules.tpl?view=log&pathrev=BRANCH-1-9

Related:
[wish1887|Modules use should be restrictable with standard permissions]


Read from bottom up:

2008-05-27 00:46:33 Norrin_Rrr mmh
2008-05-27 00:45:57 prozaq you could probably modify that
2008-05-27 00:45:39 prozaq that displays all categories
2008-05-27 00:45:32 prozaq Norrin_Rrr: in 1.10 there is a module called "categories"
2008-05-27 00:41:25 Norrin_Rrr will try it
2008-05-27 00:41:16 Norrin_Rrr the example in the documentation says its for features not sections that s weird
2008-05-27 00:40:51 prozaq oh - yes I think so, but Ive never tried it
2008-05-27 00:40:34 prozaq beg your pardon?
2008-05-27 00:39:45 Norrin_Rrr the section parameter in the menu its to set wich section (wiki/cms/forums) will display the menu ?
2008-05-27 00:38:54 Norrin_Rrr that should be doable
2008-05-27 00:38:19 prozaq so you should be able to copy some of the code from the tiki-browse_categories pages
2008-05-27 00:34:38 Norrin_Rrr yes
2008-05-27 00:34:16 prozaq but isnät that when you are creating a module from scratch?
2008-05-27 00:34:07 Norrin_Rrr i am not sure but there seems a possibility for hacking ?
2008-05-27 00:33:44 Norrin_Rrr "So if you know about Smarty template editing you can use any Smarty tag in your user modules."
2008-05-27 00:33:05 Norrin_Rrr ah okay i am at the module documentation, and its seems there are some conditionals with TW1.10 for modules but unfortunatly none for specific category
2008-05-27 00:32:56 *** franck has left #tikiwikin
2008-05-27 00:29:43 *** kiilo_ has quit IRCn
2008-05-27 00:28:34 Suprano even more if you paste in in a formular :D
2008-05-27 00:28:15 Suprano hmmm copying 4mb text slows down the pc
2008-05-27 00:28:10 Norrin_Rrr and display a menu that gather the various item of this category
2008-05-27 00:27:59 prozaq marclaporte: earlier I posted a bug to the tracker item Bugs & Wish list on dev.tikiwiki.org but how do I post to the "All Bugs" section or the "Release 110 taged bugs" ? section
2008-05-27 00:27:38 Norrin_Rrr yes
2008-05-27 00:27:30 marclaporte the goal would be to show a certain module only if current item (page, etc) is in category X ?
2008-05-27 00:26:07 prozaq eek...
2008-05-27 00:25:45 Norrin_Rrr its seems it works for feature enabled on the site but not for category (?)
2008-05-27 00:25:16 Norrin_Rrr yep i have the doc about the menu under my nose but i don't understand the section parameter
2008-05-27 00:24:39 marclaporte hi prozaq
2008-05-27 00:24:24 prozaq marclaporte: hi
2008-05-27 00:24:19 prozaq but Iäm not sure a specific category would fall under that
2008-05-27 00:23:57 prozaq it seems that you can tell a module which "section" it should appear in
2008-05-27 00:22:37 Norrin_Rrr for now 1.9.9 but 1.10 soon i hope :)
2008-05-27 00:21:20 *** marclaporte has joined #tikiwikin
2008-05-27 00:20:45 prozaq which version are you using norrin?
2008-05-27 00:18:38 Norrin_Rrr i am not sure, a module with a menu would be nice
2008-05-27 00:18:08 prozaq a menu item or a module with menus?
2008-05-27 00:17:29 Norrin_Rrr and hello everybody ;)
2008-05-27 00:16:39 Norrin_Rrr Is it possible to show a menu only when a user reach an item belonging to a given category ?
2008-05-27 00:15:24 *** Norrin_Rrr has joined #tikiwikin







Sylvie has recently added some useful code in BRANCH-1-10 so we can use categories as conditions in templates (.tpl)

[http://dev.tikiwiki.org/Hello+World#To_do_something_specific_in_a_template_ex_tiki_tpl_conditional_to_the_current_item_being_in_a_category_Ex_different_header_picture_|related info in Hello World]

If use Bootstrap menu is set to "y", the menu is vertical instead of horizontal even if the type is set to horiz. If "bootstrap=y" is not explicitly set (left empty, since it's the default), then type=horiz has the expected effect.

If I recall correctly, in the past when you're making a menu and adding menu options, the options' position incremented automatically by 10, so it wasn't something you needed to pay attention to. Making a menu in Tiki 15.2, with this assumption, I didn't edit the position number, and found that sometimes the number increased by 10 and sometimes it didn't. I don't see a pattern for when it increments and when it doesn't.

{syntax type="tiki" editor="plain"}
I have a menu with a third-level dropdown, followed by another link in the second level, as shown in the attached screenshot. The menu is saved, including the last option, "One more link", but the menu doesn't show the item "One more link" in the second-level dropdown, or anywhere. Another master instance here on my localhost also has the same problem. The second-level dropdown items just get truncated after the link with the dropdown. This obviously doesn't happen with first-level links, but is happening with second-level links (and probably with third-level, etc. links).

This is a regression maybe linked to the change in Smartmenus versions.

On tiki-admin_menu_options.php?menuId=n, although you can choose horizontal or vertical and there's a "CSS" checkbox, the only preview is the old type of vertical menu with folder icons. This is helpful to show that the basic structure of the menu is correct, but isn't responsive to the type selector and CSS checkbox.

Add a feature to move files in between the file system and the database

This feature:
tiki-admin.php?page=trackers
tiki-admin.php?page=fgal
tiki-admin.php?page=wikiatt

should be added here:
tiki-admin.php?page=gal

(In fact, it should be backported from 1.10) "Move images from filesystem storage to database storage"

1) Forms where only a single option can be selected have the Select2 gadget for multi-select options. For example, in the Switch Theme module, there can be only one theme selected for the site. But the selected item has the "x" icon (with tooltip: "Remove all items"). According to the examples on [https://select2.org/getting-started/basic-usage] and [https://apalfrey.github.io/select2-bootstrap-5-theme/examples/single-select/] , this icon shouldn't be here, and UI-wise it is redundant.

2) Actually this is related/caused by the first issue: the "x" icon is mis-located when used with a single-option selector: it's at the far right of the selector rather than being to the left of the option name. But this will be fixed when the "x" icon no longer displays in single-option selectors.

In lib/prefs/feature.php a couple of help texts were begun during programming, but never finished (they remain empty shells consisting only of a heading ("name"), but lacking description and/or hint).

These are feature_action_calendar, feature_contacts, feature_forum_content_search, feature_forum_parse, feature_forum_quickjump, feature_forum_topics_archiving, feature_gal_slideshow, feature_groupalert, feature_integrator, feature_notepad, feature_score_expday, feature_tasks, feature_user_bookmarks, feature_userPreferences, feature_user_watches_languages, feature_user_watches_translations, feature_userfiles, feature_usermenu, feature_wiki_import_page, feature_wiki_undo, feature_xmlrpc, feature_hotwords, feature_community_mouseover_country, feature_community_mouseover_distance, feature_community_mouseover_email, feature_community_mouseover_gender, feature_community_mouseover_lastlogin, feature_community_list_country, feature_community_list_distance, feature_community_list_score, feature_community_list_name, feature_community_mouseover_score,

If these features are not meant to have help texts, then please remove the empty shells altogether, because the they really make for inconsistent look and feel of the admin UI. If a slightly more verbose version of the feature's name is to be transported, then this should be done in the name section and really have at least a couple words more than the name displayed.

{syntax type="tiki" editor="plain"}
Using mobile mode, from a PC with Chrome (on GNU/Linux, in case it matters).

I clicked on "Switch to mobile site" in nextdev.tiki.org, and then when you go to "Admin home > Look & Feel", the theme style shown there is "abse" and not fivealive, so that if you save any setting there in L&F, you are switching the theme for the non-mobile mode (and you will not notice since you as admin are still in mobile mode).

Google changed their formula. module should now deal with:
google_ad_client = "pub-xxxxxxxx";
google_ad_slot = "02353245";
google_ad_width = 468;
google_ad_height = 15;


While we are playing here, the module should be re-organized and default should be a public service advertisement

Current Adsense module is too complicated to set-up as we can read here:
http://tikiwiki.org/Module+Adsense

There are way too many forum posts for something which should be really simple to set up:
http://tikiwiki.org/tiki-searchindex.php?highlight=adsense&where=forums

So, I suggest:

The public service advertisement should appear instead of the current "You forgot your Google ad_client number !" message. So people would know right away that the connection with Google is OK.

By default, it should be a fairly small ad so it fits nicely in a module.

And if the user is admin level (check for tiki_p_admin), then, add a link to documentation on how to set pub-xxxxxxxxxxxx and others...
http://doc.tikiwiki.org/tiki-index.php?page=Module+adsense

So, if no pub-xxx number is set, use pub-xxxxxxxxxxxx (which provides the public service advertisement) with a warning for admins.

If the admin specifically wants a public service advertisement, he can set the pub number as pub-xxxxxxxxxxxx. In which case, there should not be a warning to admins on how to set.

Finally, if the pub number is set normally (ex.: pub-1234...), no admin warning should appear.