New in Tiki27, permitting to improve PluginList, and fixes/enhancements are being backported to the Tiki26 branch. Once it is more stable/robust, it may also be backported to Tiki24.

Parameters

This was one of the recommendations from this large project: FOSDEM 2024

Related Merge request: PluginList SUBLIST MR

Example Usage

PluginList SUBLIST gives the ability to join several trackers and get mixed results into a single array, greatly optimizing the performance when subqueries and sub-list plugins are needed.
Steps to follow:

1. Create a tracker called Region with ID, Name as fields (tracker_id = 1)
2. Create an other tracker called Hospital with ID, Name and Region (Item Link pointing to region tracker) (tracker_id = 2)
3. Fill all trackers with data as well
4. Apply this code:

!!! Stock table template
{LIST()}
  {filter type="trackeritem"}
  {filter field="tracker_id" exact="2"} 
  {SUBLIST(name="region")}
    {filter field="tracker_id" exact="1"} 
    {filter field="object_id" exact="$parent.tracker_field_hospitalRegion$"}
    {FORMAT(name="name")}{display name="tracker_field_regionName" default=""}{FORMAT}
  {SUBLIST}
  {OUTPUT(template="table")}
    {column field="hospital" label="Hospital" mode="raw"}
    {column field="region" label="Region" mode="raw"}
  {OUTPUT}
  {FORMAT(name="hospital")}{display name="tracker_field_hospitalName"  default="" }{FORMAT}
  {FORMAT(name="region")}{display name="region.name" default=""}{FORMAT}
{LIST}

First List Plugin joins tracker 1 (tracker Region) and tracker 2 (tracker Hospital) with an Item Link field in tracker 2 (tracker Hospital) pointing to tracker 1 (tracker Region) called tracker_field_hospitalRegion....Sublist filters the results by the ID of the record coming from the parent tracker(here tracker Region).

Output template is using the stock table template with wiki formatting the name field of tracker 1 (tracker Region) and then wiki formatting the table column for region name using nested keys like 'region.name'.
Region is the key name in SUBLIST block, so it adds an array of records in the parent row under the 'region' key. Then, it formats and adds the tracker 1 (tracker Region) field(s) to that key for each parent record.
The given above code in step 4, would produce (accordingly to the data filled in trackers...step 3 ):

Click to expand

Example Using Pivot table

You can use SUBLIST in pivottable as you normally would in a plugin list - define the SUBLIST and either format some of the columns there or leave all columns (skip formatting blocks in sublist). In order for the results to appear in the main pivottable array of data, you must include the fields in the display blocks in the main pivottable.
Assure that you have the two trackers as documented above, then apply this code:

{PIVOTTABLE(data="tracker:2" cols="region.regionName" vals="hospitalName" colOrder="key_a_to_z" rowOrder="key_a_to_z" rendererName="Table" aggregatorName="List Unique Values" inclusions="{}" menuLimit="500" aggregateDetails="object_type" highlightMine="n" highlightGroup="n" chartHoverBar="y")}
{display name="tracker_field_hospitalName"}
{display name="region.tracker_field_regionName"}
{SUBLIST(name="region" required="2")}
  {filter field="tracker_id" exact="1"}
  {filter field="object_id" exact="$parent.tracker_field_hospitalRegion$"}
{SUBLIST}
{PIVOTTABLE}

This example shows how to include 2 remote tracker fields (tracker_field_hospitalName, tracker_field_regionName) in the parent result set using the keys 'tracker_field_hospitalName' and 'region.tracker_field_regionName'. These 2 will appear as fields in the PluginPivotTable and you would be able to use them as normal fields.

The given above code would produce:

Click to expand

Related

See also:

• PluginTrackerList
• PluginTrackerList To PluginList Converter
• PluginTracker
• PluginList
• PluginPivotTable

Plugin List

If you are searching for the list of all plugins, see All Plugins. A graphical user interface (ListGUI) was added in Tiki18 and massively improved in Tiki19. Starting in Tiki21, it has been enhanced to use with Federated Search. And new in Tiki26: PluginList Sublist.

Introductory Remarks

LIST is a very powerful and flexible wiki plugin that can return and output data (a listing) of information using various sorts, filters, etc. It uses the search data provided by the improved search index so it should be emphasized that this means that only the data that has actually been indexed by the Search and List from Unified Index can be accessed. Good knowledge of how Unified Index works is therefore recommended.

By utilizing a full-text search across most major Tiki features, which is then enhanced by a programmable filter, OUTPUT, DISPLAY, and SORT control blocks, this combination can render almost any information in the database in any format desired. This means that LIST is similar in some respects to Pretty Trackers output of TrackerList plugin but it is not limited to just the Tracker data. When combined with the PluginCustomSearch plugin, LIST can replace TrackerList and TrackerFilter plugin usage and can considerably extend it!! Please also see PluginListExecute.

Please note you can use nested LIST.

Control blocks vs. Wiki Plugins

"Control blocks" are quite similar to "wiki plugins", as they use the very same syntax of parameters and values.
The positions of the parameters can be switched around in wiki plugins as well as in List control blocks. Both allow to leave out the quotation marks around the values of the parameters when the values contain no empty spaces.

However, for both, control blocks and wiki plugins, it makes sense to stick to some best practices in respect of consistent sort order. This is not mandatory but makes it easier to understand the principle, to read the own code, and to work together in teams. This is especially valid for the LIST control blocks, as there are usually a lot of control blocks used in one LIST plugin.

The difference between "control blocks" and "wiki plugins" is, that you cannot use a "control block" stand-alone outside one of the plugins, which use the "PluginList" syntax, as there are "PluginList", "PluginCustomSearch" and "PluginListExecute" (?). If you place a single List "control block" stand alone on a wiki page, either nothing happens or you'll get an error message.

"Wiki plugins", instead, can be used stand-alone anyplace where you can use wiki syntax and, to some extent, you can nest them as well.

Clarifying a potential confusion

Potentially confusing is the difference between a control block and a parameter both called "format":

The parameter "format" (in lower case) inside the control block "{display}" is responsible for how the displayed result is rendered. Maybe it also could have been named "render" instead of "format", but "format" was the naming decision of our coders and that makes sense as well, maybe even better sense for some reason.

The control block "{FORMAT(name=...)}" (in upper case) wraps around the control block "{display}" and is for example responsible for the reference to the control block column (when we consider the example of a tracker table display).

The other potentially confusing fact is, is the difference and same time similarity of the parameters "field" and "name", where we use always "field" in the {filter} and in the {column} inside the "{OUTPUT(template=table)})" control block.
Contrarily we use "name" in the optional ''{display} and {FORMAT()}'' control blocks.

When we use this ...

{filter field="tracker_id" content="10"}
  {OUTPUT(template="table")}
     {column field="tracker_field_permanent_name_1" label="columntitle" mode="raw"}
     {column field="tracker_field_permanent_name_2" label="columntitle" mode="raw"}
  {OUTPUT}

... then the "field"' parameter contains a "Unified Index field"'' - in this case a tracker field which we want to display.

But when we use this ...

{filter field="tracker_id" content="10"}
  {OUTPUT(template="table")}
     {column field="reference_1" label="columntitle" mode="raw"}
     {column field="reference_2" label="columntitle" mode="raw"}
  {OUTPUT}
     {FORMAT(name="reference_1")}{display name="tracker_field_permanent_name_1" format=trackerrender editable=inline default="n.a."}{FORMAT}
     {FORMAT(name="reference_2")}{display name="tracker_field_permanent_name_2" format=trackerrender editable=inline default="n.a."}{FORMAT}

... we referenced (passed) the actual value of the "field" parameter of control block "{column ...}" to the subcontrol block "{display ...}" inside the control block '"{FORMAT(...)", where we for some reason cannot use a parameter '"field"''.

When we reference the original content of "field" from one to another control block, both control blocks need to "know" about each other, which you see as obvious, when you have more than only one column.
So the content of the column's field parameter will be replaced with a reference string and this reference string has to be repeated in the FORMAT's name parameter. Now the column control block and the FORMAT control block are interlinked with each other. Finally, the original content of the columns field parameter (which is a "Unified Index field") has to be placed into the display's name parameter.

In other words:

"Unified Index field string" goes from "column field" to "display name"
And a "reference string" is added to "column field" and "FORMAT name"

Important to know is the content of the page Search and List from Unified Index, where you find a list of all available "Unified Index fields" for which you can filter and in respect of tracker based tables you can use to create columns.

Syntax Overview

The overall format is the same as any other plugin:

{LIST()}
body content
{LIST}

Any of the following control blocks with their own plugin-like syntax are placed in the body of the LIST plugin to define the search query that will be carried out and how the resulting list will be presented :

Parameters

While Plugin List is generally configured with plugins (some say control blocks) contained in the body as described above, there are a few standard parameters like other plugins, they are:

Additional parameter

Select fields

The syntax of the parameter is as follows: {select fields="tracker_field_permName1 tracker_field_permName2 ..."}.
This allows us to limit the number of fields actually fetched from the search index. It currently works for all 3 index types - Mysql, Manticore and Elasticsearch. It is especially useful when you want to do subtotal and calcs on a large number of results in an index that has thousands of fields. Note that object_type and object_id are always returned no matter what.

By design, title, object_type,object_id,score and row_index fields value will always be outputted. However, to benefit from the performance improvement of this additional parameter you must use it with at least one value. If you need only the title of the returned object, even if the title is always returned, you must use a value and {select fields="title"} is acceptable.

Work for the plugin List and on the plugin Customsearch

Introduced by this commit: https://gitlab.com/tikiwiki/tiki/-/commit/afc34f5c7fdea02f7c8f43b894d422b018a5eb7f

Using

{LIST()}
 {pagination max="1"}
 {filter type="trackeritem"}
 {filter field="object_id" content=""}
 {select fields="tracker_field_permName1 tracker_field_permName2 ..."}
{LIST}

Basic worked example

In the meantime, you can see a basic working example here: GeoLocation (or play in your tiki with a similar basic example after applying the profile Easy Geoblog, which is available at the Profiles Wizard ).

Body content elements of the LIST Plugin

Each of the principle plugin-like control blocks is described in more detail in the following set of child pages:

Additional General Notes on the Syntax

• The field argument in the content filter can contain multiple fields separated by commas.

Available Fields

All the fields that are indexed can be referenced by the various plugin-like control blocks e.g. filter , FORMAT, etc and a complete list of fields for each object type can be found in the Search and List from Unified Index documentation.

More Worked Examples

Example Tracker item with Comments

Item

{LIST()}
 {pagination max="1"}
 {filter type="trackeritem"}
 {filter field="object_id" content=""}
{LIST}

Comments

{LIST()}
 {filter type="comment"}
 {filter field="parent_object_id" content=""}
 {filter field="parent_object_type" content="trackeritem"}
{LIST}

Example Tracker item with a picture (file)

{LIST()}
  {filter field="tracker_id" content="1"}
{OUTPUT()}
  {display name="fathername"}%%%
  {display name="fatherpict"}%%%
  {display name="id"}
   {OUTPUT}
{FORMAT(name="fathername")}{display name="tracker_field_fatherName"}{FORMAT}
{FORMAT(name="fatherpict")}{display name="tracker_field_fatherPicture" format="trackerrender"}{FORMAT}
{FORMAT(name="id")}{display name="tracker_field_parentId"}{FORMAT}
{LIST}

Same Example as above within a table

(see: LIST - OUTPUT control block)

{LIST()}
{filter content="1" field="tracker_id"}
{filter type="trackeritem"}
{OUTPUT(template="table")}
  {column label="Father Name" field="fathername"}
  {column label="Picture" field="fatherpict" mode="raw"}
  {column label="ID" field="id"}
{OUTPUT}
{FORMAT(name="fathername")}{display name="tracker_field_fatherName"}{FORMAT}
{FORMAT(name="fatherpict")}{display name="tracker_field_fatherPicture" format="trackerrender"}{FORMAT}
{FORMAT(name="id")}{display name="tracker_field_parentId"}{FORMAT}
{LIST}

Example Blog Post List

This code:

{LIST()}
	{list max="10"}
	{filter type="blog post"}
	{filter content="1" field="blog_id"}
{LIST}

Would produce on this site:

• Blogs enabled, and blog created allowing post comments
• changes to perms and disabling forum
• site upgraded to the released tiki 2.0 stable
• DocContributors granted the perms to edit doc.tw.o homepage
• Wiki Structures re-enabled
• Copyright turned off
• Packages
• Disabled "Users can choose to stay in SSL mode after an HTTPS login" to have SSL login always on.
• Preference feature jquery validation disabled (Preference name: feature_jquery_validation)
• Comments enabled for registered users

  
  

Common Pitfalls and Mandatory Requirements when filtering Tracker fields with Plugin LIST

Tracker field configuration is critical

When using {LIST} with tracker fields, only fields indexed by the Unified Search can be filtered.
For any tracker field used inside a {filter} control block, the following options must be enabled in the tracker field configuration:

If Searchable is not enabled, {LIST} will always return No results for query for anonymous, even if:

• tracker items exist
• the filter value is correct
• permissions are correctly configured

Rebuild the search index after changes

After enabling Searchable on a tracker field:
Go to Admin → Search then Click Rebuild index

Without rebuilding the index, the field will not be available to the Unified Search, and {LIST} filters on that field will silently fail.

Using dynamic values (Smarty) in LIST filters

The content= parameter of {filter} accepts plain text or numeric values only.
Wiki plugins (such as {"now"}) are not evaluated inside content=.
To use dynamic values, a Smarty template context is required.

Practical example: filtering by day of the year

Option A — Server-side Smarty template

1. Create a Smarty template file (server-side)
File location (recommended, non-core): templates/modules/custom_daily_content.tpl

{assign var=daynum value=$smarty.now|date_format:"%j"}

{wikiplugin _name='list'}{literal}
{filter field="tracker_id" content="1"}
{filter field="tracker_field_dayNumber" content="{/literal}{$daynum}{literal}"}

{OUTPUT()}
{display name="tracker_field_dailyTitle"}
{display name="tracker_field_dailyMessage"}
{OUTPUT}
{/literal}{/wikiplugin}

2. Include it from the Custom Module
Module Name : Custom Daily Content
Module content (Wiki Markup):

{INCLUDE file="templates/modules/custom_daily_content.tpl"}

3. Call the module in a wiki page
Use the Module plugin to display the custom module on a page.
Wiki page content:

{module module="Custom Bible Plan" nobox="y"}

Option B — Wiki page used as a Smarty template (UI-managed, recommended)

1. Create a Wiki page used as a Smarty template

• Page name: Custom Daily Content Tpl
• Permissions required: tiki_p_use_as_template (Make it editable only by trusted users)
• Page content:

{assign var=daynum value=$smarty.now|date_format:"%j"}

{wikiplugin _name='list'}{literal}
{filter field="tracker_id" content="1"}
{filter field="tracker_field_dayNumber" content="{/literal}{$daynum}{literal}"}

{OUTPUT()}
{display name="tracker_field_dailyTitle"}
{display name="tracker_field_dailyMessage"}
{OUTPUT}
{/literal}{/wikiplugin}

2. Include the Wiki template in a Wiki page

{includetpl filename="tplwiki:Custom Daily Content Tpl" values=""}

For more details: PluginIncludeTpl

Tutorials

• Tutorial - Display Tracker Data with Plugin List
• LIST plugin demo and nesting tracker items - Youtube

Additional child pages of the LIST documentation

Related

See also:

• PluginList Sublist
• PluginTrackerList
• PluginTrackerList To PluginList Converter
• PluginTracker
• PLuginModule
• PluginIncludeTpl

• Plugin List

Permits you to become temporarily the member of a group. This is useful for admins to "emulate" what other groups are seeing/doing.

Usage

{MODULE(module=groups_emulation, showallgroups=n, showyourgroups=y)}{MODULE}

Parameters

Related Pages

See these pages for information that applies for all modules:

• Module — Overall introduction and overview
• Module Admin — Introduction to the module admin pages for site-wide and individual module settings
  • Assigning Modules — How to select a module to configure it
  • Module Settings Interface — Interface for configuring individual module settings
  • Module Settings Parameters — Explanation of standard parameter settings for modules
  • Creating Custom Modules — How to create user modules
• Index of Modules — Links to the documentation of individual modules
• User Modules — How (if the feature is active) users can choose and place their modules
• Mods Type Modules — Links to modules that are installed as components

This Tiki feature allows users to use the content of a Wiki Page to create a slideshow (presentation). Introduced in Tiki7 and improved later, the feature was Revamped in Tiki19 and a complementary plugin, the SlideShowSlide plugin was added to allow fine tuning per slide.

Plugin Slideshow is an existing Tiki Plugin to create a slideshow of a page. The Plugin was updated in the Tiki 19.0 and now has moved on to use Reveal.js. The PluginSlideShow is now more powerful than ever before. It has better transitions and control over individual slides.

Admin Settings

Go to Admin Control Panels and search for "Slideshow" and enable the Slideshow features mentioning Reveal.js the updated Slideshow component.

Click to expand

Parameters

Create a slideshow from the content of a wiki page
Introduced in Tiki 7.
Go to the source code
Preferences required: wikiplugin_slideshow, feature_slideshow

Parameters	Accepted Values	Description	Default	Since
parallaxBackgroundHorizontal		Number of pixels to move the parallax background per slide, Calculated automatically unless specified. Set to 0 to disable movement along an axis		19.0
parallaxBackgroundSize		syntax, e.g. "2100px 900px" - currently only pixels are supported (don't use % or auto)		19.0
parallaxBackgroundVertical				19.0
autoSlide	digits	Number of milliseconds between automatically proceeding to the next slide, disabled when set to 0, this value can be overwritten by using a data-autoslide attribute on your slides	0	19.0
autoSlideStoppable	y n	Stop auto-sliding after user input	y	19.0
alignImage	n y	Automatically move images to left hand side of slide text, will only align images greater than 200px in width	n	19.0
backgroundTransition	none fade slide convex concave zoom	Transition style for full page slide backgrounds	fade	19.0
controls	y n	Display presentation control arrows	y	19.0
controlsBackArrows	faded hidden visible	Visibility rule for backwards navigation arrows; "faded", "hidden" or "visible"	faded	19.0
controlsLayout	bottom-right edges	Determines where controls appear, "edges" or "bottom-right"	bottom-right	19.0
fragmentClass	grow shrink fade-out fade-up current-visible		grow	19.0
fragmentHighlightColor	none red green blue		blue	19.0
fragments	y n	Turns fragments on and off globally	y	19.0
parallaxBackgroundImage		URL of the background image to use in your slideshow, overrides backgroundcolor		19.0
progress	y n	Display a presentation progress bar	y	19.0
slideNumber	y n	Display the page number of the current slide	n	19.0
theme	black blood beige league moon night serif simple sky solarized	The theme you want to use for the slideshow, default will be what you choose from the admin panel under Look and Feel for jQuery UI	black	19.0
headingLevelSlideSeparator	1 2 3 4 5 6	Allows you to specify the heading levels to use to trigger a new slide (Included between h1 and h6)	3	26.0
transition	zoom fade slide convex concave (blank)	Transition style	zoom	19.0
transitionSpeed	default fast slow	Transition Speed		19.0

 Change of behavior from Tiki26

From Tiki26 it is possible to set precisely the Heading level from which will be created the slide with the parameter "headingLevelSlideSeparator". However this addition changed the default behavior when this parameter is not set to use only H1. As previously it was set from H1 to H3, if you need, add the "headingLevelSlideSeparator" with a value of 3 (for headings3)

Tiki Page to a Slideshow

The Plugin Slideshow converts a Tiki page to a slide show , every H1, H2, and H3 tag starts a new slide.

First, you must create a new Wiki page and save it. You can name it as you wish.
See Wiki and Using Wiki Pages for more information about wiki pages.
After creating the page, add the sections to it, each section must start with either an H1, H2 or H3 tag since each H1, H2 or H3 tag is the beginning of a new slide.
This is an example of a page with four H1 tags, each of which is a slide, the overview and code of which are shown below.

Speaker's notes

PluginSlideshow can include speaker's notes to support the presenter during a slideshow.

Enable this feature with `speakerNotes="y"` in `PluginSlideshow`.

After enabling it, add notes in the page content with `{NOTES()}...{NOTES}` after the visible content of a slide. These notes can be used for reminders, extra explanations, timing cues, examples to mention, or transitions between slides.

During the slideshow, press `S` to open the speaker view. The speaker view can help the presenter follow the talk while keeping the main slide content clean and concise for the audience.

Overview

Click to expand

Code

Copy to clipboard

! Email and Calendar
{img type="fileId" fileId="1"}
The Universal Communication Tool
* Calendar
* Newsletter
* Webmail
* Address Book
* IMAP / CardDAV / CalDAV
* Notifications of Changes
* Anti-Spam
* Filters

! OS and Network
{img type="fileId" fileId="4"}
The Underlying Infrastructure
* Router / Gateway / Firewall / VPN
* Virtualization (Any Client OS)
* Unified Index / Search
* Server / Network
* Desktop / Mobile
* Natural Language Processing (NLP)
* Federated Search

! Commerce
Sell Memberships, Products or~hs~Services
{img type="fileId" fileId="2"}
* Customer / Membership Management (CRM)
* Shopping Cart / Payment
* Sales Force Management
* Advertising / Social Networks
* Event Management
* Digital Signage
* Accounting (Alpha)

! Web and Intranet
{img type="fileId" fileId="3"}
Your Public and Private Web Content
* Website / CMS / Blog
* Wiki / Knowledge Base / Book
* Enterprise Social Networking
* Customer Support / Issue Tracker
* Web Framework / Workflows
* E-Learning / Quizzes
* Video Management
* Forums

Now it is time to transform the content of the page into SlideShow.
In edit mode, click on the help icon, when the window appears, click on the Plugin help tab then use the filter to find the Slideshow more quickly and click on it.

Click to expand

By clicking on the Slideshow icon, a window will appear.
At this step, customize the presentation of the Slideshow by changing the values of parameters such as Theme, Transition, Controls, etc. Then click on the Save button.

Click to expand

A code will appear in the Wiki page, save the page.

Copy to clipboard

{slideshow theme="black" transition="zoom" transitionSpeed="default" backgroundTransition="none" controls="y" controlsLayout="bottom-right" controlsBackArrows="faded" progress="y" slideNumber="y" fragments="y" fragmentClass="grow" fragmentHighlightColor="none" autoSlideStoppable="y" alignImage="n"}

After saving the page, a button Start Slideshow Presentation will appear, click on it to start the slide.

Click to expand

This is the appearance of the Slideshow

Click to expand

You can then customize it, by changing the Theme or the Transition as shown in the image below

Click to expand

Slides Thumbnail View

On the desktop you can reach the Slides Thumbnail View by hitting ESC on the keyboard. Use arrow keys to choose the slide you want to show.

Change the parameters

You can choose to directly modify the parameters of the Slideshow Plugin.
This code:

Copy to clipboard

{slideshow theme="serif" transition="concave" transitionSpeed="fast" backgroundTransition="convex" controls="y" controlsLayout="bottom-right" controlsBackArrows="visible" progress="y" slideNumber="y" fragments="y" fragmentClass="fade-up" fragmentHighlightColor="none" autoSlideStoppable="y" alignImage="n"}

Will produce:

Click to expand

Custom Backgrounds

Plugin Slideshow enables you setup different types of backgrounds as follows:

1. Static background image for all slides
2. Different background images for individual slides using Plugin Slide
3. Parallax background image
4. Video backgrounds

Mobile touch enabled

The slideshow is optimised for smart phones and tablets. It’s touch gestures enable you to easily browse the slideshow or jump to a screen.

Go to next or previous slides
Simply drag right or left to move forward or backwards in the slideshow.

View thumbnails of all the slides and choose a slide to browse
Use two fingers zoom in and zoom out gestures to view slide thumbnails or browse a slide you choose.

Different behaviour for each slide

The slideShow plugin allow a global configuration for the slides behaviour or design (all slide will look and do the same). In case you need to specify options or design element per slide You can use the (PluginSlideshowSlide|SlideShowSlide plugin)).

Related Pages

• PluginSlideshowSlide
• Using Wiki Pages
• Wiki

Use this wiki plugin to configure a Slideshow in Tiki from the content of the wiki page using the headings in it. It extends the existing wiki page slideshow with notes & styles.

1.1. Setup

You need to enable it by means of marking these two checkboxes:

1. "Settings > Control Panels > Wiki > Features > Slideshow"
2. "Settings > Control Panels> Editing and plugins > Plugins > Slideshow"

1.1.1. Avoid images being resized and relocated

This s5 slideshow engine in Tiki resizes and relocates images automagically by default, in order to allow quickly show content, and a small thumbnail of the image at the upper right corner of the slide.

If you prefer to have the image shown at its original size and position, you can add the parameter class="fixedSize" to your img call. Example:

This code would show the image as a small thumnail in the upper right corner of the slide: code to allow resizing and relocating the image Copy to clipboard {img src="display2" rel="box[g]" width="500"}

But this code would allow the image to be shown at the original size of 500px and at the same position where this code was written. code to keep original size and position Copy to clipboard {img src="display2" rel="box[g]" width="500" class="fixedSize"}

1.1.2. Tutorial

See this presentation as example, create with the JQuery S5 Slideshow Feature in Tiki7 in a localhost, and then converted into pdf in a later stage, as seen here:
http://ueb.ir.vhebron.net/UseR+2011

1.1.2.1. Source Wiki page

This is the wiki page created in the local tiki site:

Identify these 3 areas, since they are specially relevant and take different roles when the page is shown as a slideshow:

(1) Wiki page title
(2) First section between headings
(3) Second Section between headings

1.1.2.1.1. Title of the wiki page

In this case, this is "2011 UseR"

1.1.2.1.2. First section between headings

First section between headings of levels 1 to 3 (of level 2 in the case shown at the previous screenshot (created with standard !! syntax).

Limited text is added here since this first heading and its content until the next heading will be used as a footer for the presentation when in slideshow mode.

1.1.2.1.3. Second section between headings

Second section between headings, of second level in this case (created with standard !! syntax). This will be used as the entry point for the presentation.

At this point, you click at the "slideshow" button that will show up in the bottom of the wiki page, which will lead you to an url similar tiki-slideshow.php

1.1.2.2. Second slide used as official presentation of the slideshow

As seen in the previous slideshow, a few areas can be recognized from the source wiki page:

(2) First section between headings
(3) Second Section between headings

1.1.2.2.1. Wiki page title

"2011 UseR" is the text shown in the top bar of the browser (not seen in the previous screenshot)

1.1.2.2.2. First section between headings

Content of the first heading is shown as footer in the slideshow for all slides.

1.1.2.2.3. Second Section between headings

Content of the second heading can be used as a normal presentation of the slideshow. Next headings will be used as indicators of new slides.

Control bar at the bottom

When you pass your mouse over the footer of any slide, a control bar will be shown at the footer instead:

In this bar you will find some buttons and controls that will allow you to manage the play, forward, reverse, etc. of the presentation, plus a few other things:

(4). Slideshow Theme style
(5). Notes
(6). Slide list for quick jumps
(7). Close the presentation and back to wiki page
(8). (Missing in screenshot). Since Tiki9, there is also an option to generate a PDF from the presentation (if the experimental feature is enabled).

1.1.2.2.4. Slideshow Theme style

You can change the theme style for the presentation ( redmond style shown in the previous screenshot).

1.1.2.2.5. Notes

You can show the notes for the slides, that will appear in a spare browser window, so that when used in a multi-monitor environment, they can be shown in the local monitor while the presentation is shown in the public screen.

1.1.2.2.6. Slide list for quick jumps

You show the slide list, which allows you to click in any of them and jump into it straight away.

1.1.2.2.7. Close the presentation and back to wiki page

You can also close the presentation and return to the wiki page which acted as a source of the presentation.

Related pages

• For more information, see Slideshow

Aliases

Plugin Slideshow

Overview

The InterTiki feature allows different Tikis to communicate user data with each other.

To access

Click the InterTiki icon on the Admin Panel
or
Access http://example.org/tiki-admin.php?page=intertiki

Tabs

This page contains the following tabs:Intertiki Client & Intertiki Master Server

Note

The information below pertains to using and administering the InterTiki feature. Eventually it will be moved to the new User and Administrator Guides

Introduction

The InterTiki feature allows Tikis to communicate user data with each other. It's based on xmlrpc protocol. It can be extended to several applications if those applications can communicate via XMLRPC. It was introduced to allow cross site authentication in all the tiki.org subdomains.

Assumptions:

• The client IP must be fixed to have this feature working
• The InterTiki master must not exist behind an Apache authorization barrier. (htpasswd)
• The InterTiki Master must not use the Web authorization method.

  
  

Key Function and sub-features

InterTiki's primary design is meant to achieve master-slave authentication relationships between multiple Tiki sites. It's designed to allow several satellite sites authenticate against one central source for user data.

Additionally InterTiki can be used to transfer user profiles from the primary user source and their corresponding groups. Both of these choices are configurable and allow for a wide range of authentication and user data share paradigms.

InterTiki can be extended for several other purposes with additional custom development utilizing XMLRPC's ability to query just about any asset of user data in a tiki.

Configuration example

In order to enable InterTiki for proper configuration, four key steps are required:

1. Enable "InterTiki" in the Tiki feature controls on both the master and slave(s)
2. On the "client" Tiki (the Tiki that will be requesting to authenticate against a master) change the "Authentication Method" to "Web Server" in the Log-in feature page.
3. Configure the server and client(s) based on the example information below making changes for your deployment where necessary.

Explanation of fields

Server Setup

On the machine you will configure to be the primary authentication server (a Master that other Tiki's will request user data from) these are the fields that matter on the InterTiki feature page:

• InterTiki Server Enabled: Check this to make this machine an InterTiki Server
• InterTiki shared cookie for sliding auth under same domain: When enabled a user who logs into or out of any site(slaves or master) is automatically logged into or out of all other sites. (feature rememberme must be on)
• Access Log File: location, from your tiki root dir, where you want the access log file stored.
  • a few examples here would be nice. Does this path start with "/" or not. Is it a URL or a direct path to a file from the root of the server?
• Error Log File: location, from your tiki root dir, where you want the error log file stored

The table after allows you to define multiple clients. Only clients on this list will be allowed to make requests against the server. This is useful, and necessary, security feature:

• Name: Arbitrary name used to uniquely identify this configuration (does not effect operation). Recommend use of a name that indicates the client server (ex: doc.tw.o)
• Key: This is the shared key you define. It has to match the client configuration for your server. It can be as short or as long as you like. It is recommended you follow the same kind of password policies your organization would have for something like a wireless WEP key.
• IP: The physical IP address the client machine will be making requests to the server from. If the client is on the same machine, you should be able to use 127.0.0.1
• Contact: username of primary contact on client machine. Useful for adminstration

Client Setup

IMPORTANT: On your client machine (machine that will request auth from the master server) you MUST have set the Authentication Type to "Web Server" on the Log In admin control page or InterTiki will not work.

It is useful to start by first entering the InterTiki Server fields first.

The InterTiki Server fields are for defining for every master server you want to have access to from this client

• Name: Set the name of your target server as defined in the server name field of the master. Use a distinct, but easily understood value.
• host: The full URL of the master servers primary Tiki (ex: https://tiki.org).
  • Note, even if your Tiki is not at the top level of your web directory, you will still use the site's URL per the ex. above.
• port: The port number the master tiki responds to HTTP on (usually 80).
  • Note: HTTP is the assumed method for XML_RPC interchange.
• path: the full path (from the URL root) to the PHP file containing the XMLRPC handler on the server
  • EX 1: If the master tiki resides at the root of the site, you would enter "/remote.php"
  • EX 2: Say the master tiki is found at http://www.mydomain.com/tiki/mytiki, you would enter "/tiki/mytiki/remote.php" in this field.
• Groups: Groups on the master to authenticate to (only auth users in the groups defined, case-sensitive).
  • is this required, or can it be blank?

• Tiki Unique Key: This must match the shared key entered in the Master's key field.
• xxxxx As Master: Use the drop down list to select the master server you just setup.
• Import User Preferences: Check this box if you want your client Tiki to copy the user preferences from the master server (NOTE: This will overwrite local user preferences every time the user logs in)
• Import User Groups: Check this box if you want the groups the user belongs to on the master server to be imported (along with their security defintions). NOTE: This will overwrite local groups every time a user logs in.
• Limit Group Import: A comma separated list of case-sensitive group names. This list will limit the group import feature to only those groups listed here.
• InterTiki shared cookie for sliding auth under same domain: When enabled a user who logs into or out of any site(slaves or master) is automatically logged into or out of all other sites. (feature rememberme must be on).

  
  

Pictoral Examples

You can see below an example of two Tiki clients (doc.tiki.org, edu.tiki.org]) configuration using InterTiki against tiki.org as a master server.

InterTiki client 1: doc.tiki.org

InterTiki client 2: edu.tiki.org

InterTiki Server: tiki.org

Hosting example

Please find below an example of successful setup at a hosting environment (siteground)

_{gezzaz notes:}

• the setup below is not so much different than above but I was struggling a while to get it right, so I decided to share it. I was stuck with error message saying that the key is not valid but it was entered correctly >> I think I got this error because changing the key on the master side is not performed correctly. You will get the above error if you decide to change your key on the master and make a save. So you have to delete the whole config row on the master and enter the values again if you wish to make changes. On the client side you can change the key without removing the old entry, it got updated for me
• Please interpret mydomain.com to your domain name

InterTiki internal details

Get version : intertiki:get_version

Used for debugging at this time. Future plans include the ability to limit requests based on a minimally defined Tiki version.

Remote login : intertiki.validate

This enables the ability to use a tiki account created on one tiki, at another tiki. One tiki is server, the other is client (client will authenticate against the server). The server has to identify a url where the xmlrpc requests can be reached. The client uses that url to reach server and send xmlrpc requests. (Typically this is: http://yourtiki/remote.php, as the XMLRPC server handler code is located in the remote.php file in your tiki root directory).

The idea is to avoid creating a local account such remote logins. At this time, a local account is automatically created on the client Tiki when a client succesfully authenticates against an InterTiki master server if that account does not already exist. InterTiki clients support the use of the @ as a delimiter for specifying the 'realm' the login belongs to when a user is logging in. This feature is primarily useful if a client Tiki can authenticate against more than one master tiki allowing for complex InterTiki relationships between Tiki sites. Some changes are made here and there to avoid a new client login containing a @ access certain features (like preferences and such).

Upon successful login from a remote intertiki server, the client will log the user into the local client Tiki. If the options are chosen it will also transfer the users preferences and group security settings from the master Interiki server.

Each validation request also sends a hash key that sort of identifies the client server. Eventually the use of that key will be optional. However a good security practice will be to keep it in place, especially if your Tiki is publicly available on the web.

Future enhancements

In the login box a new menu is proposed with that when enabled via login features will list the possible master auth locations, either local or remote. The user could also type login@remote directly it will be processed correctly.

Trouble shooting

• check the IP is the right one by checking the tiki Logs
• check that the error log and the access log are writeable by the server
• if your client does not have a static IP and you need to specify an IP range in the server settings check out a temp fix here: http://dev.tiki.org/tiki-view_tracker_item.php?itemId=1878

Changed client host

When moving a client instance to another host, the client login will not work properly and the access to admin will be not possible. In this situation, just update the new client IP on Tiki master (The address should be something like this: https://example.com/tiki-admin.php?page=intertiki#contentadmin_interwiki-2).

Changed client key and host

When hosting several Tiki instances on one host is common to use a single client key for all instances (not recommended). So, when you need to move a single Tiki instance to another host, it is not possible just update IP for that instance, because it will break all other instances using the same key and old IP.

In this situation, admin is unaccessible and is not possible login on client to fix it. A new key is needed for this Tiki instance and the follow step may solve this situation:

1. Open a MySQL client

2. Select the Tiki database

USE tiki_example;

3. Create another key for your client

UPDATE tiki_preferences SET value=MD5(CONCAT(RAND(), 'example.com')) WHERE name='tiki_key';

4. Check and copy your new key

SELECT * FROM tiki_preferences WHERE name='tiki_key';

A box like below will appear as result of previous command. Copy the value field from it.

+----------+----------------------------------+
| name     | value                            |
+----------+----------------------------------+
| tiki_key | 61d96346b08f9f6633618b8fb678f0c4 |
+----------+----------------------------------+

5. Open browser at keys config page on your Tiki master (Something like https://example.com/tiki-admin.php?page=intertiki#contentadmin_interwiki-2)

6. Scroll down until you see field to a new entry

7. Fulfill it with a meaningful name, paste new key and the new host IP and click on Apply

8. Delete Tiki client cache on new host (-+/var/www/html/+- is the Tiki root folder, change it to reflect you installation)

find /var/www/html/temp/cache -type f -type f -not -name "*.php" -not -name ".htaccess" -delete

9. Now you should be able to login in Tiki client

Major changes have been applied since Tiki 24

Starting in May 2026, InterTiki has been updated, and the following Tiki versions will continue to work with InterTiki: Tiki 24.13 and above, Tiki 27.6 and above, Tiki 29.3 and above, and Tiki 30.x Other versions will stop working due to those changes!

Also, make sure the interTiki master server and interTiki Client are on the above versions or above, so interTiki can still work!

• http://www.xmlrpc.com/
• http://phpxmlrpc.sourceforge.net/ (on which is based the xmlrpc pear lib used in tiki)
• http://tiki.org/InterTiki
• TRIM to manage many Tikis!

  
  

• InterTiki Config

Punxant sobre la icona de Funcionalitats en el Panell d'Administració ("Admin > Funcionalitats") et porta a la pantalla de Funcionalitats, on pots habilitar o deshabilitar funcionalitats del Tiki.

Una mostra de la Plana de Funcionalitats

Empra aquesta finestra per escollir quines funcionalitats seran accessibles en el teu Tiki. Així, pots adaptar Tiki a les teves necessitats específiques sense haver de configurar l'aplicació sencera. La instal·lació per defecte de Tiki habilita molt poques funcionalitats, mentre que el perfil d'instal·lació "Basic enbled for easy use" n'habilita per defecte moltes més de les habituals.

Recorda, quan deshabilitis una funcionalitat, que totes les pantalles i mòduls relacionats amb aquella funcionalitat mostraran una pantalla error quan s'intenti accedir a elles. Si està s rebent una pantalla d'error quan intentes accedir a una funcionalitat, consulta la informació d'aquesta plana primer.

La taula inferior mostra els noms de les principals funcionalitats de Tiki. Segueix els enllaços de sota per dirigir-te a la plana de la documentació sobre cada una de les funcionalitats.

Les funcionalitats es poden habilitar i deshabilitar des d'aquesta pnatalla. Addicionalment, quan estiguis a la pantalla d'Administració, pots clicar sobre qualsevol terme per llegir l'ajuda!

Seccions del Tiki i funcionalitats

Aquí tens la taula de les funcionalitats en anglès, amb els enllaços a les seves respectives planes de documentació. Les planes de documentació en català , a mesura que hi siguin, tindran el mateix nom que la plana en anglès però acabades en ",ca" (convenció de documentació de Tikiwiki per a les planes traduïdes).

Noves funcionalitats que vnen amb Tikiwiki 1.10

Funcionalitats de Contingut

La Secció de Funcionalitats de Contingut

Funcionalitats d'Administració

La secció de Funcionalitats d'Administració

Les Funcionalitats de les persones usuà ries

La secció de les Funcionalitats de les persones usuà ries

Aquests parà metres s'apliquen només a usuaris enregistrats

Opcions generals de format

La secció d'opcions Generals de Format

Aquesta part de la secció de funcionalitats pot ser emprada per controlar l'aspecete i la sensació (la disposició) del seu lloc Tiki. Bà sicament, pots habilitar/deshabilitar les columnes, la barra superior (on s'indica la versió Tiki) i la barra inferior (al peu de pà gina). Si vols una disposició d'una columna sense canviar alguna cosa en el codi, aquesta és la manera de fer-ho.

Alguns usuaris pregunten si hi ha una necessitat de mostrar el missatge de copyright del Tiki. La resposta és un NO rotund. Pots emprar Tiki per al que vulguis i pots personalitzar-ho per a que tingui l'aspecte que tu vulguis.

Tingues en compte que pots voler habilitar l'opció de Format per secció. Quan aquesta és habilitada, el disseny de pà gina pot ser configurat individualment per a seccions Tiki diferents. Per exemple, pots voler treure la columna dreta només en els fòrums. De ser així, habilita l'opció de format per secció i empra la pantalla de administra format per tal de seleccionar disposicions individuals per a les diferents seccions. (Pots accedir a la pantalla d'administració de format fent clic sobre l'enllaç a Administra Format per secció.)

Opcions de format-per-secció

Pots seleccionar una disposició individual per a les següents seccions:

• I enrecorda't de punxar en el botó Actualitza que hagis fet canvis.

  
  

Erste Konfiguration

Diese Seite bietet einen Überblick über alles, was Sie als Tiki Admin am Anfang tun sollten. Wir gehen davon aus, dass Sie die Installation bereits abgeschlossen haben und als Admin auf Ihrer Site eingeloggt sind.

Nicht-Administratoren, also Endbenutzer, die lernen möchten, wie Sie die verschiedenen Funktionen in TikiWiki nutzen können, sollten die Seite Features lesen.

Administration der Funktionen

Nach dem Installieren können Sie die Funktionen de, die Sie in Ihrem Tiki nutzen möchten, auswählen. Tiki bietet eine breite Auswahl an Funktionen; Wiki, Artikel, Blog, Workflow Management, Foren und vieles mehr. Seien Sie gewarnt: Die Vielzahl an Auswahlmöglichkeiten kann schnell dazu führen, dass Sie sich alsbald der TikiWiki Gemeinschaft anschließen möchten, um einen Mentor zu finden, der Sie bei der Implementierung berät und Ihnen eine helfende Hand reicht in Ihrem Einarbeitungsprozess.

Weitere Infos: Features Admin

Die wichtigsten Funktionen haben ihr eigenes Administrationspanel um die spezielle Funktion zu verwalten. Wenn Sie einmal die Funktionen ausgewählt haben, gehen Sie auf die entsprechende Admin-Seite featurename admin für die Funktion, auf der alle verfügbaren Konfigurationsoptionen beschrieben sind.

Wie stellt man eine Image Gallery oder File Gallery ein ?.

Optional: Speichern Sie Anhänge oder Bilder in Ordnern statt in der Datenbank.

Standardmäßig speichert Tiki die Datei aus Wiki-Anhängen, Bildergalerien, Tracker, Benutzerdateien usw. in der Datenbank.
Sie können es aber so einrichten, dass die Speicherung in Ihrem Verzeichnisbaum auf dem Server erfolgt um die Datenbank für Backups o.ä. möglichst klein zu halten.

Erzeugen Sie Ordner und setzen Sie Berechtigungen

Tiki Bereiche:

• Wiki-Anhänge
• Foren-Anhänge
• Bildergalerien
• Dateigalerien
• Tracker
• Benutzerdateien

Wir empfehlen das Präfix "tiki_" den Ordnernamen voranzustellen, damit Sie sie schneller zuordnen können.
Zum Beispiel könnten Ihre Ordnernamen folgendermaßen vergeben werden:

• tiki_anhaenge --> Wiki Anhänge
• tiki_dateien --> Dateien aus den Dateigalerien,
• tiki_bilder --> Bilder aus denBildergalerien ,
• tiki_tracker --> Tracker ,
• tiki_benutzerdateien --> Benutzerdateien ,
• tiki_forum1 , tiki_forum2 , ... --> Anhänge aus den Foren, falls benötigt.

(Beachten Sie: Beim Erzeugen des Ordners, müssen Sie die Berechtigungen auf 755 setzen oder einen höheren Wert, je nachdem was Ihr Webhost verlangt.)

Richten Sie in Ihrem Tiki die Pfade zu diesen Ordnern ein

Dabei gehen wir davon aus, dass Sie sich im Verzeichnis /home/username/ befinden, wenn Sie sich per ftp auf dem Server angemeldet haben.

Loggen Sie sich als Admin mit Ihrem Browser in Ihr Tiki ein und richten Sie den Pfad an folgenden Stellen ein:

1. Wiki Anhänge:
2. * Gehen Sie zu "Admin > Wiki > Wiki Administration > Verwalten der Anhangeinstellungen".
3. * Wählen Sie "Wiki Anhangeinstellungen > Benutze Verzeichnis zum Speichern der Dateien:", und "Verzeichnispfad": /home/username/tiki_anhaenge/
4. Dateigalerien:
5. * Gehen Sie zu "Admin > Dateigalerien > Galeriefunktionen "
6. * Wählen Sie: "Benutze Verzeichnis zum Speichern der Dateien:", und als "Verzeichnispfad": /home/username/tiki_dateien/
7. Bildergalerien:
8. * Gehen Sie zu"Admin > Bildergalerien> Galeriefunktionen"
9. * Wählen Sie "Benutze Verzeichnis zum Speichern der Bilder:", und als "Verzeichnispfad": /home/username/tiki_bilder/
10. Tracker:
11. * Gehen Sie zu "Admin > Tracker > Tracker Anhangeinstellungen"
12. * Wählen Sie: "Benutze Verzeichnis zum Speichern der Dateien:", und als "Verzeichnispfad": /home/username/tiki_tracker/
13. Benutzerdateien:
14. * Gehen Sie zu"Admin > Benutzerdateien"
15. * Wählen Sie: "Benutze Verzeichnis zum Speichern der Dateien:", und al "Verzeichnispfad": /home/username/tiki_benutzerdateien/

• Gehen Sie zu "Foren > Admin foren > (Wählen Sie ein Forum, zum Beispiel "Forum01") > Anhänge"
• Wählen Sie: " Speichere Anhänge nach:", und setzen Sie den "Pfad:": /home/username/tiki_Forum01/
• Das wiederholen Sie so oft, bis Sie für alle Foren in den Sie Anhänge zulassen, einen Pfad eingerichtet haben.

Ändern Sie weitere Parametereinstellungen für Ihre Website

• "Admin > Allgemein",
  • "Server Name (für absolute URIs):" -> http://yourserver.com/yoursite/
    
  • "Titel (Browser Titel):" -> Hier können Sie den Namen Ihrer Gruppe, Vereinigung, Unternehmens ... einsetzen
  • "Versende Email:" -> Ihr E-Mail-Postfach auf dem gleichen Server, falls vorhanden
• "Admin > (Login)"
  • "HTTP server name:" -> yourserver.com
  • "HTTP Prefix for URL:" -> yoursite/
    
  • "Remember me name:" -> yourserver.com
  • "Remember me domain:" -> domain_name_set_when_using_setup.sh
  • "Remember me path:" -> yoursite/

Erstellen Sie Gruppen und Benutzer

Nachdem Sie festgelegt haben für was Sie ihr Tiki nutzen möchten; sollten Sie nun angeben, wer es nutzt.

Registrationseinstellungen

Soll Ihr Tiki öffentlich sein oder nur einem bestimmten Personenkreis zugänglich (auch zur Ansicht) ? Hier ist die gesamte Bandbreite auswählbar. Die meisten Tiki Installationen beginnen mit drei Standardbenutzertypen:

• Admin - Jede Site hat zunächst einen "allmächtigen" Administrator, der alles erstellen/anpassen/löschen kann. (Standardmäßig gibt es nur einen solchen Administrator.Sie können später anderen Benutzern ebenfalls diese Rechte einräumen. Tun Sie das aber zu Ihrer eigenen Sicherheit wirklich nur dann, wenn sie ganz, ganz sicher sind, dass die Benutzer vertrauenswürdig sind und wissen, was sie tun.)
• Registrierte - Registrierte Benutzer sind eine der beiden Benutzergruppen die standardmäßig erzeugt werden. Hier können Sie globale Rechte für diese Gruppe einrichten, die alle Funktionen Ihres Tikis betreffen.
• Anonyme - Anonyme User können entweder sein:
  • Benutzer, die sich bislang nicht eingeloggt haben - in diesem Fall haben sie nur eingeschränkte Rechte (Lesen und Einloggen/Registrieren)
  • Benutzer, die anonym bleiben möchten - in diesem Fall gewähren Sie der Gruppe minimale Rechte an allen Funktionen, die für anonyme Benutzer freigegeben sind.
  • faule/unerfahrene Benutzer - Admins die Ihre Beitragsanzahl maximieren möchten unterstützen häufig Benutzer, die entweder zu faul oder zu ungeschickt sind sich einzuloggen. (Das ist ein nicht zu vernachlässigender Teil der Besucher). In diesem Fall sollten Sie sich gewahr sein, dass sie hier einen "Wilden Westen" erschaffen und müssen die Änderungen auf Ihrer Seite einer permanenten Überwachung unterziehen.

Weitere Gruppen erstellen

Zusätzlich zu den drei oben genannten Gruppen können Sie weitere Gruppen erstellen, in der Regel aus folgenden Gründen:

• Junior Administratoren / Site Editoren - erfahrenen Benutzer können eigene Rechte eingeräumt werden, so dass sie bei dem Design und der Wartung der Site mithelfen können.
• Private Benutzergruppen - Tiki ermöglicht die Benutzung eines Kategoriensystems, um private Seiten und Bereiche zu erstellen, die nur für Benutzer einer bestimmten Gruppe zugänglich sind.

Ändern des Aussehens.

Wählen Sie ein Design oder Theme

Themes sind die "Haut" Ihres Tikis. Themes nutzen ein CSS framework umd das Aussehen aller Elemente Ihrer Site zu verändern. Tiki bringt von Haus aus eine Vielzahl an Stile und Themes mit, so dass sich für jeden Geschmack etwas findet (Nicht alle Themes eignen sich für alle Funktionen).

Themes können global angelegt werden oder für spezielle Seitenkategorien (abhängig von der Benutzergruppe). Mit den entsprechenden Einstellungen können sich die Benutzer ihr Lieblingsdesign aussuchen.

Es ist möglich, Tiki so einzustellen, dass die .tpl-Dateien beschreibbar sind, die meisten nutzen jedoch ein Webdesignprogramm um mittels FTP Templateänderungen vorzunehmen.
Siehe Themes anpassen

Hinzufügen und Organisieren der Module

Module sind Boxen, die den Hauptinhaltsbereich der Site umgeben. In jedem Modul findet sich ein spezieller Inhalt, z.Bsp. ein Menü, ein Suchfeld, ein Bild, Werbung, usw. Tiki platziert die Module im Allgemeinen links und rechts an den Rand, aber mit einem kleinen bisschen Programmierkenntnissen können die Module nahezu überall eingerichtet werden. Die Module können in beliebiger Reihenfolge angeordnet werden und für unterschiedlich Benutzergruppen sichtbar oder unsichtbar sein.

Um Ihr eigenes Menü zu erstellen und es den Spalten zuzuweisen lesen Sie Menu HOWTO.

Inhalt erzeugen

Nachdem alles Obenstehende angelegt ist, können Sie und (Ihre Benutzer) die Site mit Inhalt füllen.

Siehe: Funktionen de Seite mit Informationen wie Sie Inhalt hinzufügen oder bearbeiten in allen Funktionen, die Sie eingerichtet haben.

Um zu erfahren wie Sie Wiki-Seiten verwenden, lesen Sie bitteUsing Wiki Pages

Entwerfen Sie Ihre Navigation

Benutzen Sie Menu, Structures, Categories und Tags um Ihren Inhalt zu organisieren.

Module to show public/friends Twitter timeline

Introduced in Tiki10. See https://sourceforge.net/p/tikiwiki/code/42459

Parameters

Configuration

1.1.1. Creating the Twitter / X Application

Go to the Twitter/X Developer Portal:

https://developer.x.com/

Log in with your Twitter/X account and create a Developer account if you do not already have one.

Create a new Project and App.

Once the application is created, locate the following information in the application settings:

• API Key (Consumer Key)
• API Key Secret (Consumer Secret)

Configure the application's callback URL.

Replace:

https://your-domain.com

by:

https://your-domain.example/tiki/tiki-login_hybridauth.php?provider=Twitter

1.1.2. Configuration in Tiki

Log in to Tiki as an administrator.

Go to:

Administration → Features

or directly:

/tiki-admin.php?page=features

Enable:

Social Networks

and click 'Apply'.

Go to:

Administration → Users & Community → Social Networks

or directly:

/tiki-admin.php?page=socialnetworks

In the 'General' tab, select:

Twitter

from the list of available social networks and click 'Apply'.

Open the 'Settings' tab and locate the 'Twitter' section.

Fill the following fields:

Consumer Key

Enter the API Key provided by Twitter/X.

Example:

ABCDEF123456789XYZ

Consumer Secret

Enter the API Secret provided by Twitter/X.

Example:

1234567890abcdef1234567890abcdef

Social networks login base URL

Enter the URL used by Tiki to receive the authentication callback.

Example:

https://your-domain.example/tiki/tiki-login_hybridauth.php?provider=

For example:

https://your-domain.example/tiki/tiki-login_hybridauth.php?provider=

If Tiki is installed at the web root:

https://your-domain.example/tiki-login_hybridauth.php?provider=

An incorrect value may result in errors such as:

No route found

or

Not Found

during the authentication process.

Twitter login allowed?

Check:

Twitter login allowed?

Twitter auto-create user?

Check:

Twitter auto-create user?

This allows Tiki to automatically create a local user account when a user logs in with Twitter/X for the first time.

Click 'Apply'.

Administration → Users & Community → Social Networks → Settings → Twitter

Testing the Configuration

Log out of Tiki.

Open:

tiki-login.php

You should see a button similar to:

Login via Twitter

or

Login via X

Click the button and authorize the application on Twitter/X.

If authentication succeeds:

• The user is logged into Tiki.
• A local Tiki account is automatically created (if auto-create is enabled).
• Subsequent logins will use the same Tiki account.

Troubleshooting

Error: No route found

This usually indicates that the callback URL is incorrect.

Verify:

Social networks login base URL

matches the actual installation path of your Tiki instance.

Example:

https://example.org/tiki/tiki-login_hybridauth.php?provider=

instead of:

https://example.org/tiki-login_hybridauth.php?provider=

when Tiki is installed in a /tiki subdirectory.

Error: Not Found

Verify:

• The file tiki-login_hybridauth.php exists.
• The callback URL is correct.
• Apache rewrite rules are properly configured.
• The Twitter/X callback URL exactly matches the one configured in Tiki.

Error: Authentication succeeds but login fails

Verify:

• PHP sessions are working correctly.
• HTTPS is consistently used.
• Social Networks feature is enabled.
• Twitter auto-create user is enabled if new users should be created automatically.

• Module Facebook
• Social Networks

On this page, you'll learn how to format text on Wiki pages and other areas that support Wiki formatting (including articles, forums, and blogs).

The Markup Language Wiki-Syntax

The markup language used on a Wiki page is most commonly called Wiki Syntax. It uses common characters in uncommon ways (or character combinations that are not normally used together) and provides them with a special meaning. Some of the character combinations only work at the beginning of a line, while others can be inserted anywhere in the text and are active until they are turned off.

Wiki-Syntax uses a character repeated twice for most functions, but it also has a few 2-character combinations. With a 2-character combination, the characters are reversed when the function is turned off. MonoSpaced Text provides a good example of this; the Minus (-) and Plus (+) characters are used to start the using MonoSpaced Text and a Plus (+) and Minus (-) characters specify the end of it.

The following sections explain most of this.

Quick Reference - Basic Text Formatting

Toggle textarea with headline + / -

''(click the [+]to open)''
!!!- Hidden by default 
Text text text text
Text text text text
Text text text text

!!!+ Visible by default 
''(click the [-]to close)''
Text text text text
Text text text text
Text text text text

Hint: enclose the [+] and [-] in np (noparse) tags when using - they cannot be shown here in the CODE Plugin, as noparse tags conflict with the CODE Plugin

creates this:

''(click the [+]to open)''

Hidden by default

Visible by default

Basic Text Formatting

The Wiki-Syntax given in this section can be located anywhere in the text so that specific characters, words, or sentences can be emphasized.

Color Font

Text can be any color you want it to be. Two Tildes (~) are used followed by the name of a color and a Colon (:) to specify the start of the Colored Text. Two other Tildes (~) are used to end the Colored Text.

Color font can also be specified using HTML colors. HTML colors use 3 pairs of Hex numbers; one for Red, Blue, & Green so that 00 00 00 would produce white. The syntax is two Tildes (~) followed by the Pound (#) character and the Hex Numbers with a Colon (:) followed by the text to be colored. Two Tildes (~) mark the end of the Colored Text.

As of 3.0, the syntax was enhanced to also support background color changing.

(click the [+] to open)

Web-Safe HTML Colors

Bold Text

Two Underscore (_) characters are used to make text Bold.

Italic Text

Two Single Quote (') characters are used to make text Italic.

Underlined Text

Three Equal (=) characters are used to underline text.

Strikethrough text

Centered Text

Two Colon (:) characters are used to Center text. The Centered Text can be centered within a Box, a Table, or almost anything else.

Monospaced Text for Code

Monospaced Text is useful when displaying Code and can be created in two ways. The easiest is to start a new line with one or more spaces. The Minus (-) and Plus (+) character combination can also be used to specify a Monospaced Text. See also PluginMono for another way to apply the Monospace font.

If using a Monospaced Font, be sure to keep the line length short. If the lines are too long, they will push the right column out of the browser display area.
❗ The Leading Space Monospaced Font is disabled on many sites.

Superscript and subscript

Use the {TAG} plugin (also see PluginTag).

Another alternative is to use the {SUB} and {SUP} plugins which are documented at PluginSub and PluginSup.

Text box

Apply one caret at the start and end of the text to be in a box.

Example: ^This Text is in a box^ produces:

NOTE: This CSS style is called "simplebox" and may look different or may not exist, depending on your theme CSS.

Plain Text

To turn off tiki formatting, surround your text with 'np' a.k.a. 'no processing' tags

Example: ~np~This ''text'' is __not__ being ===formatted===~/np~ produces:

This ''text'' is __not__ being ===formatted===

NOTE: np tags cannot be used within an np block. To display an unprocessed ~np~ tag, escape all the characters (not just the tildes) while in normal processing mode:

~126~~110~~112~~126~ produces: ~np~
~126~~47~~110~~112~~126~ produces: ~/np~

Headings

Headings are formed by starting the line with one, two, or three exclamation marks ("!", "!!", or "!!!").

Numbered Headings

In tiki 2.0 and above, you can create numbered headings using a combination of the ! and # characters

• !# My Heading will produce "1.0 My Heading"
• !!# My Secondary Heading will produce "1.1 My Secondary Heading"
• !!!# My Tertiary Heading will produce "1.1.1 My Tertiary Heading"

See: Headings

LineBreak (forced)

Basic WIKI markup language doesn't include "linebreak" element.
Nevertheless, with Tiki you can use a special command to force linebreaks into a text :
line break code (%%%), like so:
;:text %%% text %%% text
will look like this:

text
text
text

Note: There must be printable text after the linebreak. A space is not sufficient to introduce a blank line.

Indent

Indent is formed by the combination of the ; and : characters. ; must appear at the beginning of a line and : must appear between introduction text and the indented text. The introduction text portion is useful for forming definition type indention like Example 1 below. However, the introduction text can be eliminated by simply including ;: together followed by the text as shown in Example 2.

Using Square Brackets

If you wish to include square brackets in your text (i.e. as regular text and not a link) simply add an additional open bracket to start. E.g.

[[this would not be a link]

Would render like this...

[this would not be a link]

Non-breaking space

Use ~hs~ to add the HTML " " for a non-breaking space.

Comments

Wiki Comments

~tc~ this is a tiki comment ~/tc~

Will be kept in the Wiki source file but not seen when the HTML page is generated or HTML page source is viewed.

HTML Comments

~hc~ this is an HTML comment ~/hc~

Will be kept in the Wiki source file and will generate an HTML comment of the form

<!-- this is an HTML comment -->

An HTML comment will not be seen when the page is viewed but will be seen when the HTML page source is viewed.

Displaying code

{CODE()} and {CODE}

This is a WikiPlugin, which extends the WikiSyntax.

Citation-style blockquotes

When Pluginquote is enabled, use this Tiki syntax code to make a simple blockquote properly:

{QUOTE()}
One of the hardest lessons of GUI programming is that hard coding behavior can be the Right Thing. Programmers are taught to make everything generic and infinitely flexible. The problem is that the more generic and infinitely flexible your UI is, the more similar it is to a programming language.
— [https://www.joelonsoftware.com/uibook/chapters/fog0000000059.html | Joel Spolsky], April 2000
{QUOTE}

…which will render like this:

See PluginQuote for additional parameters that can be used as metadata for the quote.

You can also accomplish this using Markdown syntax, like this example:

{MARKDOWN()}
> As Joel points out, advanced users do not want a million (…) preferences when things should just work on their own. The point rings true in my experience.
> 
> — Havoc Pennington
{MARKDOWN}

…which will render like this:

As Joel points out, advanced users do not want a million (…) preferences when things should just work on their own. The point rings true in my experience.

— Havoc Pennington

Other Ways to Indent a Text Block

You can use the div module if it's enabled like so:

{div(type="blockquote")}Bananas
Apples
Oranges{div}

Will result in:

Apples

Useful Links

• The Color Picker II is located at http://www.pagetutor.com/colorpicker/index.html
• Web-Developer extension for Mozilla Firefox
• The wiki syntax is not standardized across applications. There is an initiative to publish the Wiki-Syntax as an RFC from the IETF. See RFCWiki.

Plugin Map

Use this wiki plugin to display a map on a wiki page with a wide range of customisation options.

See also Geolocation for how other Tiki objects, e.g. wiki pages, blog posts etc. can be geolocated.

Historical overview of Maps integration in Tiki

Parameters

More detail for the controls display options

controls : basic pan and zoom control positioned left top of map
layers : clickable tool right top of map that opens a pop-up where the different map options can be selected, e.g., OpenStreetMaps, Google Street, etc.
search_location : adds a 'Search Location' link beneath the map on the left, to allow a post code or address to be entered to search for a specific location
levels : displays zoom levels, positioned below the basic zoom control on the left of the map
current_location : adds a 'To My Location' link beneath the map on the left
scale : adds the map scale at the bottom left of the map
streetview : https://en.wikipedia.org/wiki/Google_Street_View
navigation : adds two icons below the zoom levels on the left of the map to select a grab tool to move the map and a box tool to zoom down to the selected box area
coordinates : displays the cursor coordinates at the top right of the map
overview : displays the current location in the context of the wider geographic area in a box at the bottom right of the map where the box can be toggled to be open/closed

More detail for the center parameter

Note that this (x,y,z) order means longitude and latitude are the opposite way round to some map applications, such as Google Maps and Earth.

Examples

Simple Example

This map shows all the tracker items from tracker #10. In its simplest form, the only thing a tracker item needs to appear on a map is a Location field with the "Use as item location" option set to "yes".

{MAP(controls="controls,layers,levels,navigation,scale,coordinates" width="500" height="350" center="-1.305,51.487,8" tooltips="y" library="ol2")}
    {searchlayer tracker_id="10"}
{MAP}

Slightly less simple real world example

This one combines the items from three trackers, #10 (for the points), #11 (paths and trails) and #12 (boundaries and zones. They each have the following fields:

• "theRidgewayMap" this is from type name, it contains a useful name for the displayed item
• "publishBoundaryZoneSeparately" is from type checkbox
• "publishPathsSeparately" also type checkbox
• "publishPOISeparately" also type checkbox

This code:

{MAP(controls="controls,layers,levels,navigation,scale,coordinates" width="630" height="500" center="-1.305,51.487,9" popupstyle="bubble" tooltips="y" library="ol2")}

    {searchlayer tracker_field_theRidgewayMap="y" tracker_field_publishBoundaryZoneSeparately="yes" maxRecords="200" popup_height="300"  popup_width="480"}

    {searchlayer tracker_field_theRidgewayMap="y" tracker_field_publishPathsSeparately="yes" maxRecords="200" load_delay="2" popup_height="300"  popup_width="300"}

    {searchlayer tracker_field_theRidgewayMap="y" tracker_field_publishPOISeparately="yes" maxRecords="200"   load_delay="3"  popup_height="300"  popup_width="360"}
{MAP}

Would produce on this site:

Note: load_delay help with the order (what should be display in the back and what should be in the front) of the layers.

You'll need several trackers to store the information you'll need (Boundaries, Point Of Interest and/or Path) with a few fields.
Note: I used the information below from a different simpler project.

• Boundaries: A name field, a files field (option index as maplayer GeoJSON) and a yes/no field (so the plugin know you want it displayed)
• POI (Point Of Interest): A name field, an icon, a field a location field and a yes/no field (so the plugin know you want it displayed)
• Path: A name field, a files field (option index as maplayer GeoJSON) and a yes/no field (so the plugin know you want it displayed)

{MAP(scope="Center" controls="yourselection" center="yourcoord,yourzoompref")}
{searchlayer tracker_field_theRidgewayMap="y"}
{searchlayer tracker_field_theRidgewayMap="y"}
{searchlayer tracker_field_theRidgewayMap="y"}
{MAP}

Using {searchlayer}

Since Tiki9
The {searchlayer} function allows objects to be displayed on maps and for logic to be applied for when and how they are displayed. It should be noted however that this is a 'search' function so only objects that have been properly indexed with Unified Search can be 'worked on'.

Individual {searchlayer} items are put in the body of the map plugin where the generic format is:

{MAP(mapfile="" extents="" size="" width="" height="" etc)}
{searchlayer parameter1="xx" parameter2="yy" layer="foo" etc }
{searchlayer parameter1="aa" parameter2="bb" layer="bar" etc }
etc
{MAP}

More detail on the {searchlayer} parameters:

suffix : will add a value from the incoming items as a suffix to the layer name, essentially creating multiple layers from a single search query. For example, in the CartoGraf demo case, it fetches the elements from the other students in the same workgroup and creates one layer per student, so other's results can be hidden or displayed.
refresh : is the refresh delay in seconds after which the query will be re-executed to update the map.
fields is the list of fields to take along with the results. The unified index indexes more data than the index returns with the results by default. This allows to provide a list of fields to be fetched before sending the result.
maxRecords : (Tiki 11+) Search results are limited by the "Maximum number of records in listings" setting (Look & Feel => Pagination) maxRecords bypass this setting and indicates how many results will be taken from the query. Be aware that it is important to give a reasonable value to this to make sure errors in a query won't take down your server and still the results you need to be displayed.
tracker_field_XXXXX : where XXXXX is the tracker field permanent name, allows conditional logic to be applied to the overall searchlayer request. If multiple tracker_field parameters are used then AND logic applies, e.g., if both tracker_field_XXXX="y" and tracker_field_YYYY="y" then both conditions will need to be true for the searchlayer action to be carried out
sort_mode : (Tiki 11+) order for the search results (e.g., tracker_id_desc )
load_delay : (Tiki 12+) delay in seconds to wait before loading the layer (can help in ordering layers with features loaded from files)
popup_width : (Tiki 12.2+) width of popups for features on this layer - plain numeric xx for pixels or xx% for percentage (percentage size only on dialog popups)
popup_height : (Tiki 12.2+) height of popups
layer : name of the layer
tracker_status : filtering results based on tracker status (ie: tracker_status="o")

Layers usage example 1

{MAP()}
{searchlayer tracker_field_fieldname="something" refresh="3600" maxRecords="50" fields="tracker_field_fieldname01,tracker_field_filedname02"}
{MAP}

{MAP()}
{colorpicker colors="ff0,69c,c96,6c9,ffffff,black,f0f,0ff,96c"}
{MAP}

Layers usage example 2

Imagine that you want to allow an external web site (blogspot, or anywhere where iframes are accepted) to show a map generated in a tiki site, in a similar way to how you would add a google map. You could embed the external wiki page with the geolocated tracker items in a map through an iframe at the remote site.

This type content below added to the wiki page will display a map in the page without showing the list of items (from tracker 16 in this example) below the map. And since the PluginAppframe is also used, no side columns will be displayed either, so that you could make an iframe with just the map of the page:

{MAP(scope="center" width="600" height="400" center="1.7282503,41.2257581,14")} {searchlayer geo_located="y" maxRecords="100" tracker_id="16" type="trackeritem"}
{MAP}

{appframe min="0" hideleft="y" hideright="y" fullpage="n" absolute="n"}

Then, if the wiki page was called "MyMap", then the url to be used in the iframe could be this one: http://example.com/tiki-index_p.php?page=MyPage

Creating map objects with the File option

Map objects can be defined in Tracker records: a simple POI can be defined using the Icon field type and the CartoGraf project then introduced the Geographic feature Tracker Field that allows paths (LineString) and boundaries (Polygon) to be drawn on a map and saved.

Whilst the 'Geographic feature Tracker Field' method is very powerful it does have limitation so in 12.1 a new "Index As Map Layer" option (defaults to No) was added to the Files Tracker Field for an uploaded file (scroll to the end of the Options list in the tracker field set up screen to find this new one). This allows a file to be uploaded that is is then indexed and can therefore be added to a map. The file does have to very carefully conform to a standard XML-like format and a drop down list allows the selection of the file format to be either geoJSON or GPX - however the map projection must (at present) be EPSG:4326. This new capability overcomes the previous limitations with the Geographic feature Tracker Field. A tracker should either have the Files field or the Geographic feature Tracker Field. Note you may have to use "load_delay" to tweak the order of the "searchlayer" to display the elements that will be on the foreground and those on the background (IE: POI should be displayed over opaque or color filled boundaries).

Using this File method any of the standard OpenLayer object types, LineString, MultiLineString, Polygon, MultPolygon, etc. can be used.

Worked example with map objects

Since Tiki12
This example displays a zoomed in section of the same map as the the 'Simple worked example' above, but uses 'searchlayer' logic to display different types of map objects (POIs, paths and boundaries) where POIs have been defined using the 'Icon' field and paths and boundaries have both been defined using the File field method described above.

Some detailed notes on how the above worked example is created

The following is the 'code' used:

{MAP(controls="controls,layers,levels,navigation,scale,coordinates", center="-1.305,51.487,9", width="630" height="500" tooltips="y" library="ol2")}
    {searchlayer tracker_field_theRidgewayMap="y" tracker_field_publishBoundaryZoneSeparately="yes" maxRecords="200" popup_height="300"  popup_width="480" }
    {searchlayer tracker_field_theRidgewayMap="y" tracker_field_publishPathsSeparately="yes" maxRecords="200" load_delay="2" popup_height="300"  popup_width="300"}
    {searchlayer tracker_field_theRidgewayMap="y" tracker_field_publishPOISeparately="yes" maxRecords="200" load_delay="3"  popup_height="300"  popup_width="360"}
{MAP}

In addition the following custom javascript is used to 'adjust' how OpenLayers displays the path 'lines'

/* 
 * this section of the custom js amends the way that OpenLayers 'spaces out' dot and dot/dash markings for paths etc
*/
  OpenLayers.Renderer.SVG.prototype.dashStyle = function(style, widthFactor) {
        var w = style.strokeWidth * widthFactor;
        var str = style.strokeDashstyle;
        switch (str) {
            case 'solid':
                return 'none';
            case 'dot':
                return [1, 4 * w].join();
            case 'dash':
                return [4 * w, 2 * w].join();
            case 'dashdot':
                return [4 * w, 2 * w, 1, 2 * w].join();
            case 'longdash':
                return [8 * w, 2 * w].join();
            case 'longdashdot':
                return [8 * w, 2 * w, 1, 2 * w].join();
            default:
                return OpenLayers.String.trim(str).replace(/\s+/g, ",");
        }
    }

Also:

• The tracker field "theRidgewayMap" allows the same tracker mapobjects to be displayed on a variety of different maps (or not)
• The tracker fields: "publishBoundaryZoneSeparately", "publishPathsSeparately", and "publishPOISeparately" - allow individual map objects to be displayed (or not) by changing their value in the appropriate tracker
• The 'popup_height' and 'popup_width' parameters allow the pop-ups for individual map objects to be resized dependent upon what tracker field data is being displayed (set in the main tracker parameters), and
• More customisation of the pop-up box can be achieved than is shown in this example by creating custom .tpl files:

/templates/styles/yourstyle/object/infobox.tpl
and
/templates/styles/yourstyle/object/infobox/trackeritem.tpl

Some other tips

Globally change stroke width

For instance

$(document).ready(function () {
	$(".map-container").on('initialized', function () {
		$(".map-container")[0].defaultStyleMap.styles.default.context.getStrokeWidth = function () { return 4; };
	});
});

Hide location field when location is not set

In some case you may have some items with a map location set and some items without.
Those without will display a map and you may prefer this not to happen.
You can hide the field using a Javascript plugin and some code on the page:

{JQ()}
  var map = $('input[name="location"]').val();
  if (map == "0,0,2") {
    $('#openlayers1').hide();
  }
{JQ}

New OpenLayers Library Support (Tiki 20+)

In Tiki 20.1 support for newer OpenLayers versions has been added, now updated to ol5. A very experimental version was introduced in earlier Tikis but it wasn't reliable or usable. There is a preference for this on the maps control panel.

This introduced:

• new parameters library and cluster which can be seen:
  • in this page: PluginMap ol3 Demo
  • applying this profile in your tiki site: GeoCMS_Maps_18
• new tilesets allowed, coming from:
  • Stamen (no api key required). Tileset param names:
    • tilesets="stamen_watercolor"
    • tilesets="stamen_terrain"
    • tilesets="stamen_toner-hybrid"
      (see the full list at http://maps.stamen.com )
  • Nextzen (Vector Tiles, & free api key required): https://www.nextzen.org
    • tilesets="nextzen"

Related pages

• PluginList
• Maps
• Geolocation
• PluginGoogleMap

Aliases

Plugin Map | PluginMaps | Plugin Maps

Introduced in Tiki31

This field type stores sensitive values such as API keys, credentials, and tokens.
The value is masked in the user interface and is never inlined in the rendered HTML: both edit and view modes display a masked placeholder, and the real value is fetched on demand over a POST request when the user clicks the reveal (eye) button.
Secret field values are excluded from the unified search index.

For team password management with encryption, the Secret field integrates with Shared Secrets (Shamir's Shared Secret) encryption keys.

Overview

• Edit mode renders a masked password input with a show/hide (eye) toggle. The browser is instructed not to autofill it (autocomplete="new-password").
• View mode shows ●●●●●● with a reveal button. The actual value is fetched on demand and never appears in the page source, browser history, or proxy logs.
• Values are excluded from the unified search index, so secrets can never leak through search results.
• When a Shared Secrets encryption key is assigned to the field, the value is stored encrypted. It can only be revealed after the key has been unlocked in the current session.
• Submitting the form with the field left empty keeps the stored value. This protects against accidental wipes when editing other fields of an item.

To Access

From the tracker administration page, click Add Field and select Secret Field in the field type selector.

Click to expand

Parameters

Using the field

Edit mode

When creating or editing a tracker item, the Secret field renders as a masked input with an eye button.

Click to expand

• On a new item, the eye button simply toggles between masked and visible text.
• On an existing item that already stores a value, the input shows a "Value stored" placeholder. The first click on the eye button fetches the stored value from the server, then the button toggles visibility locally.
• Leaving the field empty and saving keeps the previously stored value.

Click to expand

View mode

When viewing a tracker item, the Secret field always displays six bullets, regardless of the stored value length, together with a reveal button.

Click to expand

Clicking the reveal button fetches the value and displays it. Clicking again masks it.

Click to expand

With encryption (Shared Secrets)

To store the value encrypted, assign an encryption key to the field: "Advanced Options" > "Advanced" tab > "Encryption key".
See Shared Secrets for how to create and distribute encryption keys.

When an encryption key is assigned:

• The value is encrypted before being written to the database.
• The field stays locked until the user unlocks the encryption key in the current session.
• The reveal button only works once the key is unlocked. Before that, the server refuses to serve the value (HTTP 403).

Security model

• The plaintext value never appears in the rendered HTML. It travels only in the response of an on-demand POST request.
• The retrieval endpoint only serves Secret fields. It cannot be used to read any other field type.
• Field-level view permissions (including item-level visibility) are enforced on the server for every retrieval request.
• For encrypted fields, the server checks that the encryption key is accessible in the current session before decrypting.

• Tracker Field Types
• Trackers
• Shared Secrets
• User Encryption
• Text Tracker Field

Tiki 30.0 LTS is planned for May June 2026.

It is a Long Term Support (LTS) version and will be supported until March 2031 as per the Tiki lifecycle policy. This release is more about refining features than major changes. After this release, there will be major changes in Tiki31.

You can see the development page at: https://dev.tiki.org/Tiki30 and all the code commits here: https://gitlab.com/tikiwiki/tiki/-/commits/30.x/ once it will be created (in 2026-01).

1. Infrastructure

1.1. Major Changes

• [+] Admin Page Language – Refactored Section Handling
  • Admin pages now correctly respect the "admin_language" preference.
    Ensures consistent section initialization, centralized handling, and improved architecture across admin interfaces.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/8658

• [+] Background Job Queue for Asynchronous Task Execution
  • A new general-purpose background job queue has been introduced to offload long-running operations such as PDF generation and instance creation.
    The queue supports task serialization, user association, type filtering, and full lifecycle tracking (pending, running, completed, failed).
    A new queue:process CLI command executes queued tasks in single-run or continuous polling mode and records outputs and results in the database.
    API and CLI endpoints are available to enqueue tasks, retrieve status, and fetch results.
    This foundational system enables scalable background processing and removes heavy workloads from HTTP requests.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/8581
  • Client-Side Queue Processing
    A "queued_tasks_js_processing_disabled" preference allows disabling web-based queue processing while keeping task status polling for user feedback.
    Smart polling automatically stops when users have no active tasks, reducing unnecessary server requests.
    Early-return checks prevent polling and processing when "feature_queued_tasks" is disabled.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/9353

1.2. Dependency & Tools Updates

These changes include library upgrades, replacements of deprecated or unmaintained packages,
and tooling improvements to ensure compatibility with modern PHP, JavaScript, and build environments.
The updates aim to improve security, maintainability, and long-term sustainability, while minimizing
impact on existing installations.

1.2.1. Application Integrations

• Converse.js dependency has been upgraded from version 11 to version 12
  https://gitlab.com/tikiwiki/tiki/-/merge_requests/8586
• DOMPurify dependency has been upgraded from version 2 to version 3
  https://gitlab.com/tikiwiki/tiki/-/merge_requests/8674
• Element Plus dependency has been upgraded from version 2.8 to version 2.11
  https://gitlab.com/tikiwiki/tiki/-/merge_requests/8674
• html2canvas Upgrade dependency has been upgraded from version 1.0.0-RC.5 to version 1.4
  https://gitlab.com/tikiwiki/tiki/-/merge_requests/7711
• jsPDF upgraded dependency has been upgraded from version 2 to version 3
  https://gitlab.com/tikiwiki/tiki/-/merge_requests/8701
• kaltura/api-client-library dependency has been upgraded from version 21 to version 22
  https://gitlab.com/tikiwiki/tiki/-/merge_requests/8663
• Plotly.js dependency has been upgraded from version 1 to version 3
  https://gitlab.com/tikiwiki/tiki/-/merge_requests/8101
• Sentry Browser dependency has been upgraded to version 10
  https://gitlab.com/tikiwiki/tiki/-/merge_requests/8315

1.2.2. Core Libraries

• [+] CAS Authentication Library Modernization
  • The deprecated and unmaintained jasig/phpCAS library has been replaced with ecphp/cas-lib.
    A backward-compatible wrapper was introduced to preserve existing phpCAS calls while ensuring continued CAS authentication support with a maintained library.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/8071
• [+] HTML Purifier Migration to HTML5-Compatible Fork
  • Migration to an HTML5-compatible fork of HTML Purifier ensures cleaner, more robust, and standards-compliant output throughout Tiki.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/8350
• [+] jsPDF and SVG-Edit Libraries updated
  • jsPDF has been upgraded from version 3 to version 4.
    SVG-Edit has been updated from version 7.4.0 to 7.4.1 to maintain compatibility with the newer jsPDF version.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/9408
• [+] jQuery Reflection Plugin Replacement
  • The jQuery Reflection plugin has been removed and replaced with native CSS-based reflection effects in PluginImg.
    This reduces dependency overhead and uses modern, performant browser features.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/7561
• [+] MediaAlchemyst Package Migration
  • The abandoned media-alchemyst/media-alchemyst Composer package has been replaced with the official Tiki-maintained fork tikiwiki/media-alchemyst. All references, runtime checks, and CI configurations were updated to ensure continued support for document preview and OCR features, improving long-term compatibility and stability.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/8411
• [+] melbahja/seo Library has been upgraded to version 3.
  • https://gitlab.com/tikiwiki/tiki/-/merge_requests/9516
• [+] Laminas\Config replaced with Native Tiki\Config
  • Tiki now uses its native INI-based Tiki\Config system for all configuration parsing and merge logic.
    The external laminas-config dependency has been removed.
    The new system introduces improved merge order handling, overlays, configuration locking, and proper y/n string support.
    Core tests have been updated to validate the new configuration behavior.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/8574
• [+] Plotly.d3 and d3-color Replacement
  • The Plotly.d3 and d3-color libraries have been replaced with native DOM methods.
    This change ensures long-term compatibility with the updated Plotly.js API.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/8101
• [+] pragmarx/google2fa dependency has been upgraded from version 8 to version 9
  • https://gitlab.com/tikiwiki/tiki/-/merge_requests/8664
• [+] Symfony Polyfills support for PHP 8.4 and 8.5 added
  • Tiki now bundles symfony/polyfill-php84 and symfony/polyfill-php85 to ensure forward compatibility with upcoming PHP language features.
    These polyfills provide implementations for new PHP core functions and language constructs expected in PHP 8.4 and 8.5.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/8504
• [+] Unoserver Support for Document Conversion
  • Support for "Unoserver" has been added as a modern alternative to the deprecated "Unoconv".
    Administrators can select the converter using a new configuration option.
    Includes automatic binary detection, improved diagnostics, and environment checks in tiki-check.php.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/9370
• [+] XMPP and Logging Core Libraries Updated
  • Backend dependencies related to XMPP and logging have been updated for modernization and improved compatibility.
    The montefuscolo/xmpp library has been upgraded to version ~0.8, adding support for PHP ^8.1 and PSR-3.
    This update enables compatibility with Monolog 3, which can now be used by Tiki.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/8472

1.2.3. Dev Tools

• [+] CI Check for Alphabetical Ordering of Source Lists
  • Tiki’s CI pipeline now includes a test that verifies alphabetical ordering of selected lists in the source code, such as in composer.json and package.json.
    The check is designed to be easily extendable to additional lists in the future.
    This improvement strengthens code quality checks and enforces established contributor conventions.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/8720
• [+] CI Check for External Links in Source Code
  • A new CI check detects external URLs present in the source code.
    Links are categorized by severity to identify potential external dependencies.
    Helps ensure Tiki remains usable in environments without internet access.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/9139
• [+] CI Safeguard for npm Lockfiles
  • A new CI check verifies that platform-specific binaries required by dependencies (such as @parcel/watcher) are present in package-lock.json.
    This prevents incomplete lockfiles from being committed and avoids installation failures across different operating systems.
    The safeguard improves reliability and consistency of Node.js dependency management.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/8792
• [+] Cross-Platform BOM and Line-Ending Handling
  • Tiki’s BOM and line-ending maintenance tools have been modernized to improve cross-platform support and remove external dependencies.
    A new mechanism now automatically detects and removes byte‑order marks, while an updated component natively manages the different types of line endings (CR, LF, and CRLF).
    FixBOMandUnixCommand now supports --report-only and no longer depends on external tools like dos2unix.
    These enhancements make Tiki’s maintenance commands more reliable and fully cross-platform for developers.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/9142
• [+] Database Schema Checks Enhanced
  • tiki-check.php now performs deeper database schema validation by detecting mismatches in column types, sizes, and index definitions between the live database and db/tiki.sql.
    Previously undetected issues—such as incorrect column lengths (for example, "tinyint size mismatches") and outdated field size limits (such as "filename length constraints")—are now reported.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/8546
• [+] happy-dom Library dependency has been upgraded from version 18 to version 20
  • https://gitlab.com/tikiwiki/tiki/-/merge_requests/8782
• [+] Husky was added as a pre-commit hook to check the formatting of the commit messages
  • https://gitlab.com/tikiwiki/tiki/-/merge_requests/8582
• [+] MariaDB and MySQL Versions updated in CI
  • The CI configuration has been updated to use current supported versions of MariaDB and MySQL.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/9345
• [+] mohlsen/check-engine replaces deprecated check-engines
  • Replacement of the deprecated check-engines package with mohlsen/check-engine to maintain compatibility and ensure continued tooling support.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/8131
• [+] PHP CodeSniffer Updated for PHP 8.5 Deprecations
  • The PHP CodeSniffer (phpcs) ruleset has been updated to detect PHP 8.5 deprecation warnings more accurately.
    Support for polyfills has been added, and outdated manual exceptions were removed to improve overall code quality checks for developers.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/9089
• [+] PHPStan Static Analysis Integrated into CI
  • Static analysis using "PHPStan" has been integrated into the CI workflow.
    Enables automated detection of potential issues and regressions during development.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/9265
• [+] Squizlabs/php_codesniffer dependency has been upgraded from version 3 to version 4
  • https://gitlab.com/tikiwiki/tiki/-/merge_requests/8592
• [+] Vitest Upgraded has been upgraded to version 4.0.16.
  • https://gitlab.com/tikiwiki/tiki/-/merge_requests/9270

1.3. Tiki 27+ Build System

• [+] Build System Updated for Node.js 24 Support
  • The build system has been updated to ensure compatibility with Node.js 24 (current LTS).
    Keeps the development and asset build workflow aligned with the latest supported Node.js environment.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/9385
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/9281
• [+] FieldsLinker Migrated to the New Build System
  • The FieldsLinker component has been fully migrated to the Tiki 27+ build system.
    This refactoring improves consistency with the modern asset pipeline and frontend tooling.
    Benefits include cleaner builds, easier maintenance and updates, and better long-term compatibility with Tiki’s current JavaScript infrastructure.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/8188

2. New Features and Improvements

2.1. Accessibility and UI

• [+] Asset Caching & Headers Improvements
  • Tiki now applies precise HTTP caching headers to files served via its PHP-based download system.
    Public assets can be cached with an admin-configurable max-age to improve performance.
    Restricted assets are marked as private, no-store, no-cache to prevent any form of caching and ensure strict access control.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/7088

• [+] Audio and Video Recording – Responsive Enhancements
  • The recording interface now better adapts to mobile devices and responsive layouts.
    Mobile environments are detected to optimize the recording experience on smaller screens.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/8889

• [+] Blog Comments Page UX Improved
  • The blog comments page has received several usability enhancements to improve clarity and predictability.
    Search filters are preserved when users start typing, blogs without comments no longer show unrelated entries, and non-existent blog IDs behave like empty blogs.
    Comment action buttons are now hidden when blogs have no posts.
    These improvements make the blog comments interface easier and more intuitive to use.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/8145

• [+] Bulk Removal for Scheduler Jobs
  • Administrators can now delete multiple scheduled jobs at once in the Scheduler interface.
    Previously, jobs had to be removed individually; the new multi-remove option streamlines cleanup and management of scheduled tasks.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/9066

• [+] Collapsible Sidebar Restored in Admin Settings
  • The collapsible sidebar feature in the Admin Settings has been restored and fully implemented.
    The collapsed state is persisted between page loads, and the sidebar can temporarily expand on hover for easier navigation.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/9181

• [+] Custom CSS for PDF Export
  • PDF exports can now use a theme-specific custom CSS file, allowing styling to be adjusted independently from the site theme.
    This is currently supported when using mPDF for PDF generation.
    The enhancement provides greater control over the appearance of exported PDFs and attached documents.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/9062

• [+] Custom Module Configuration Improvements
  • Custom user-defined modules now support structured parameter forms during module assignment, similar to standard Tiki modules.
    This improves usability and makes module configuration more reliable and intuitive for administrators.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/9658

• [+] Dynamic Modal Backdrop Configuration
  • Tiki’s modal system now supports dynamic backdrop options, allowing runtime control over whether clicking outside a modal closes it or not.
    This enhancement improves UI flexibility and gives developers and theme designers finer control over modal interaction behavior.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/9168

• [+] Improved Mobile Dropdown Positioning
  • The Tiki menu system now provides enhanced dropdown positioning on mobile devices to ensure proper alignment and visibility within the viewport.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/9145

• [+] Improved Usability in Admin Notifications
  • The tiki-admin_notifications.php interface has been enhanced to make it easier for administrators to locate configuration options related to email notifications for tracker changes.
    This includes clearer access to settings such as Copy activity to email for a whole tracker.
    The improvement streamlines notification configuration and reduces friction when managing tracker-related emails.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/8216

• [+] Menu Usability for Long Dropdowns
  • SmartMenus dropdowns now support scrolling when they exceed the viewport height.
    This ensures all submenu items remain accessible, even for menus displayed near the bottom of the screen, such as the Settings menu.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/8600

• [+] Minichat UI Improvements
  • The Minichat module interface has been improved with updated chat bubble styling and a clearer message layout.
    Minichat messages are now strictly confined to the Minichat module and no longer appear in admin alert areas.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/8801

• [+] Modal Dialogs – Improved Resizable Windows
  • Resizable modals now better handle dynamic content such as expanding sections and dropdown menus.
    Conditional resizing logic allows modals to grow with their content while preserving proper scrolling when reduced.
    Fixes layout issues introduced after the migration from jQuery UI to Interact.js.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/9524

• [+] Module Preference Error Display in Modules Admin
  • The Modules Admin interface now highlights missing or invalid preferences directly during module configuration.
    Error messages include clickable links that take administrators straight to the corresponding preference in the admin panel.
    These improvements streamline module setup, reduce configuration errors, and make troubleshooting significantly faster.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/8855

• [+] Profiles Wizard UI Simplified
  • The Installer’s Profiles Wizard has been streamlined to prevent access to outdated and non-functional steps.
    The left-side menu has been removed, the content area now uses full width, and navigation buttons have been adjusted (the Next button hidden and Back retained where applicable).
    Only the first functional step remains visible, with non-working steps commented out for potential future restructuring.
    These changes improve clarity and reduce confusion during installation.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/8500

• [+] Support for Prefers-Reduced-Motion
  • Tiki now honors the prefers-reduced-motion system setting, disabling non-essential animations across the interface while preserving user-initiated interactions.
    This improves accessibility for users with motion sensitivity and also benefits low-end devices or users looking to reduce battery usage.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/7433

• [+] Syntax Help Display on Widescreens Improved
  • The Wiki Syntax Help overlay is now responsive and automatically arranges its content into columns on wider screens.
    This reduces excessive vertical scrolling and improves readability, especially on landscape and large displays.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/8139

• [+] Tikiben Theme – New Bento-Style Layout
  • Introduces the Tikiben theme featuring a modern bento-style layout based on modular content blocks.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/9318

• [+] User Info Tooltips Enabled by Default
  • User hovercards are now displayed automatically for users who allow their information to be public.
    The related preference has been removed to simplify configuration.
    The “Public” vs “Private” profile setting has been clarified to ensure consistent behavior for hovercards and username links.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/9419

• [+] Username Validation – Improved Registration Page Checks

  • Username validation now provides clearer guidance when spaces are used, suggesting alternatives such as ".", "-", or "_".
    Client-side validation prevents submission when the username format is invalid.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/9564

• [+] User Task List Template – Refactored Structure
  • The template used to display the user task list has been refactored and cleaned up.
    Improves code structure, maintainability, and interface consistency.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/9395

• [+] Webmail Module Showing Unread Emails
  • A new module, Unread emails, displays the number of unread Webmail messages even when users are not on the Webmail page.
    Unread counts can be shown on home pages or dashboards and work with IMAP folders as well as Email Folders stored in tracker fields.
    This is especially useful when Webmail (Cypht) is integrated into Tiki but not used as the home page.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/8650

2.2. Calendars & Event

• [+] Calendar Module and Plugin Refactoring for Consistency
  • The calendar_new module has been refactored to rely on the main Tiki calendar library as its core implementation.
    This refactor aligns the module and the wiki calendar plugin with the default calendar page, ensuring consistent behavior, rendering, and feature support across all calendar entry points.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/8626

• [+] Checkbox-Based Calendar Selection for calendar_new and PluginCalendar
  • Added a checkbox-based calendar selection form to calendar_new and wikiplugin-calendar for easier filtering and display of multiple calendars.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/9678

• [+] Cypht Calendar Invitations – Archive Confirmed Emails
  • When a calendar invitation received by email is confirmed and added to the Calendar, the original email is now archived instead of being discarded.
    This ensures the invitation and its attachments remain available for future reference alongside the calendar event.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/8329

• [+] “Copy to New Event” Calendar Workflow
  • The calendar Copy to New Event action now opens a pre-filled event creation form instead of immediately creating a duplicate event.
    This provides a safer and more user-friendly workflow by allowing users to review and adjust event details before saving.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/9667

• [+] Event Descriptions for Calendar Invitations via Email
  • When creating calendar events from email invitations via Cypht, Tiki now prefers a suitable HTML version of the email body when available.
    This results in event descriptions that more closely match the original invitation email and avoids multipart-MIME artifacts from calendar attachments.
    HTML content is sanitized to prevent security issues and remove inappropriate interactive elements.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/8620

• [+] Streamlined Calendar UI and Improved Event Dialog Behavior
  • Redundant calendar views have been consolidated to simplify navigation, replacing separate List day/week/month/year views with a single unified list-style view.
    This reduces UI complexity and makes calendar browsing more intuitive.
    Event dialogs now close reliably, ensuring more predictable and user-friendly interaction.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/8427

• [+] Tracker Calendar Auto-Sync Improvements
  • The Tracker Calendar plugin now supports automatic synchronization of event dates with tracker fields, including the ability to use multiple calendar item fields within a single tracker item.
    This enables managing different expiry dates or variations under the same item.
    Improvements also include better handling of date vs. datetime fields and proper support for all-day event settings.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/8432

• [+] Tracker Calendar Items Now Link to Tracker Entries
  • Calendar views displaying tracker-based events now include a direct link back to the original tracker item.
    This makes it easier to navigate from the calendar interface to the underlying record, improving workflow efficiency.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/8510

• [+] Unified Calendar Rendering for Plugin and Module
  • The wiki Calendar plugin and the calendar_new module now use the main Tiki calendar rendering library.
    This provides a unified look, consistent behavior, and shared feature support across the main calendar, plugins, and modules.
    Two new display options have been added:
    • A List View mode, in addition to the traditional calendar grid view.
    • An option to display calendar legends for improved readability.
    
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/8359

2.3. Communications & Messaging

• [+] Webmail Contact Search
  • Webmail contact search has been enhanced to support recipient lookup by nickname and company name while composing emails.
    This improves usability and makes it easier to quickly find contacts using alternative identifiers.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/9718

2.4. Developer Tools & APIs

• [+] AttachmentsMigrateCommand Command
  • The attachments:migrate console command now better handles missing files when migrating wiki attachments to file galleries.
    Attachments whose physical files cannot be found are skipped to prevent inconsistent records.
    The command generates a report listing missing files and suggesting verification of the `w_use_dir` configuration.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/9538
• [+] ExportPDF
  • A new ListExecute action and console command ( php console.php page:print "PageName" ) have been introduced to export wiki pages as PDF.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/7767

• [+] Git Commit Information in Admin General Panel
  • When Tiki is installed from a Git clone, the Admin General panel now displays detailed Git repository information.
    The extended version banner shows the current Git branch, the short commit hash (linked to the full commit on GitLab), and the commit date formatted with tiki_short_datetime.
    This provides clearer version tracking and improves administration of Git-based deployments.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/9030

• [+] GlitchTip – Performance Tracing Support
  • The GlitchTip integration now supports performance tracing and transaction grouping.
    Enables monitoring of PHP and JavaScript operations through structured transactions and spans.
    New preferences allow configuring tracing and sampling rates.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/9143

• [+] Object Categorization – API Improvements
  • The object categorization API now supports assigning multiple categories to multiple objects in a single request, enabling more efficient bulk operations.
    Legacy single-category requests remain supported for backward compatibility with existing integrations.
    Correct action handling has been restored after recent refactoring.
    API responses now consistently include `message` and `count` fields for clearer feedback.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/9387

• [+] Scheduler Monitoring
  • The scheduler monitoring system has been improved to help administrators detect failures earlier and integrate with external monitoring tools.
    The CLI commands scheduler:monitor and scheduler:stats allow checking scheduler health, retrieving runtime statistics, and integrating with monitoring systems such as Zabbix.
    New admin preferences allow detecting failures from the last run or within a configurable time window.
    The admin interface can display warnings for tasks with recent failures.
    Scheduler errors can optionally be reported to external tracking systems such as GlitchTip.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/8005
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/9473

• [+] Security Auditing Tool Improved
  • Enhancements to doc/devtools/securitycheck.php expand CLI-only validations to strengthen detection of potentially unsafe PHP files.
    The tool now classifies execution-safe files, identifying scripts that contain only class or function declarations and do not expose executable entry points.
    Missing or improper CLI checks are flagged, while exception cases are validated based on explicit and documented rationale.
    These provide more accurate auditing of exposed PHP entry points and help developers maintain clear and secure code boundaries.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/8548

• [+] Transition Diagrams Migrated to Mermaid
  • The Tiki transition diagram system has been migrated from Dracula/Raphael to Mermaid using stateDiagram-v2.
    This modernizes the rendering of transition and event chain diagrams and improves maintainability.
    The change aligns diagram rendering with Tiki’s new JavaScript build system and provides more consistent, easier-to-manage visualizations for administrators.
    Diagram functionality in the admin interface remains unchanged while simplifying generation and upkeep.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/8623

• [+] Wiki API PATCH Endpoint for Partial Page Updates
  • A new Wiki API PATCH endpoint allows partial updates of wiki page fields without resubmitting the full page content.
    Supported updates include SEO title, SEO description, categories, and tags.
    This improves safety and efficiency for integrations, automation workflows, and AI-assisted content management.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/9702

2.5. Editors

• [+] Markdown – Expanded Help in Editor
  • The Markdown help menu in the editor now includes more comprehensive information about supported syntax.
    Based on reference material from the Markdown Guide, providing clearer guidance for formatting options.
    Improves consistency with the help available for Wiki syntax.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/9511
• [+] Page Edit Form Layout Improvements
  • The page edit form has been updated so the Describe the change you made field is displayed outside the Edit/Categories/Properties tabs, clarifying that it applies to all modifications.
    The redundant Monitor this page checkbox has been removed, as page monitoring is already available via the page menu.
    These changes improve clarity, consistency, and reduce confusion in the page editing interface.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/8495
• [+] Summernote – LanguageTool Integration for Grammar and Spell Checking
  • Summernote now supports optional real-time grammar and spell checking via LanguageTool.
    Highlights issues and provides suggestions directly in the editor.
    Configurable preferences allow defining the LanguageTool server URL and related options.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/8269
• [+] ToastUI Editor
  • Resizable Editor in Edit Mode
    The ToastUI editor now supports resizing directly while editing content, without the need for changes in editor configuration settings.
    This enhances usability and flexibility, particularly when working with long or complex content.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/8654
  • Preview Now Uses Tab Mode by Default
    The ToastUI editor now displays the preview panel in a separate tab by default.
    Previously the preview appeared beside the editor, which could lead users to try editing the rendered content.
    Improves clarity by separating editable content from the rendered preview.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/8655
• [+] wysiwyg Parameter for Editable Block Fields
  • Added a new wysiwyg parameter to decouple textarea editing from automatic WYSIWYG editor initialization in editable block fields.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/9740

2.6. External Services Integrations

• [+] BigBlueButton Integration
  • Tiki now uses the official bigbluebutton-api-php library, replacing legacy custom code.
    The integration is more robust and maintained in line with upstream development.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/7794
  • The BigBlueButton plugin now uses consistent shared secret terminology across all settings and error handling.
    The bigbluebutton_server_salt preference has been renamed to bigbluebutton_shared_secret, and ServerSaltKeyException is now SharedSecretKeyException.
    A migration script updates existing installations automatically.
    These changes improve clarity and consistency in configuring and troubleshooting the integration.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/9122
  • Meetings can now be marked as public or private, providing more control over access.
    A new bigbluebutton_use_iframe option allows meetings to open inside an embedded iframe within Tiki.
    Improved interface styling, error handling, and user feedback enhance the overall meeting experience.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/8551

• [+] CryptPad Integration for Editing Office Documents
  • A new integration allows editing Office and OpenDocument files from file galleries using CryptPad.
    An “Edit in CryptPad” option opens supported files (DOCX, XLSX, PPTX, ODT, ODS, ODP) in an embedded collaborative editor.
    Changes are automatically saved back to the file gallery.
    Requires enabling feature_cryptpad_docs and configuring cryptpad_base_url.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/9190

• [+] HybridAuth Plugin: Facebook Integration Fix
  • The HybridAuth plugin has been updated to fix issues with Facebook authentication.
    Corrections were made to the Facebook module, and a data retrieval library was added to improve integration reliability.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/8910

• [+] PeerTube Integration
  • Tiki now supports PeerTube as an external video backend for upload, storage, streaming, and embedding.
    Integration uses OAuth2-based authentication and introduces new preferences and schema updates to configure PeerTube connectivity.
    A new dedicated library (peertubelib) provides API interactions for video listing, uploading, and token management.
    Authorized users can manage PeerTube-hosted videos directly from Tiki via a new video listing page and upload interface.
    Includes a new PeerTube tracker field type , a wiki plugin for embedding PeerTube videos, and updates to the video administration panel and related UI templates.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/8109
• [+] Prosody and Converse.js Integration with Tiki as Identity Provider
  • Adds initial integration enabling real-time chat using Prosody and Converse.js.
    Tiki acts as the XMPP identity provider and synchronizes chatrooms with Tiki groups.
    Supports anonymous chat access, automatic login for registered users, and optional external XMPP clients.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/8631
• [+] Webmail Tracker Folders – Restore Option for Deleted Emails
  • Emails deleted from tracker-based Webmail folders can now be restored from the trash.
    A new Restore action allows moving messages back to their original location.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/9015

2.7. File Galleries & Attachments

• [+] File Gallery List Display
  • The file gallery listing now displays the category assigned to each file, improving visibility and organization.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/8170

• [+] Flexible Rules for Display Names
  • Tiki now provides flexible control over how file display names are generated during upload, replacing the previous single fixed behavior.
    A new global default preference has been introduced, now set to preserve original filenames exactly as uploaded.
    Administrators can override the global rule on a per-gallery basis, allowing different naming styles depending on context.
    For example, a Marketing Photos gallery may apply Title Case for consistency, while a Technical Documents gallery can preserve exact filenames.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/8015

• [+] Long-Format File Modification Date/Time Preference
  • A new fgal_show_modtimedate preference allows administrators to display file modification timestamps in long format (date and time) within File Galleries.
    This addresses previous limitations where long-format timestamps could not be configured through the UI or stored in the database.
    The option is now available in File Gallery settings, enabling consistent long-format display across file listings.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/8330

• [+] Tiki API File Version Upload Support
  • The Tiki API now supports uploading new file versions while respecting the file gallery archive limit.
    This prevents uncontrolled storage growth and enables reliable use in IoT and other high-frequency update scenarios.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/8049
• [+] ZIP Downloads Preserve Original File Timestamps
  • ZIP downloads from file galleries now retain the original file modification timestamps.
    Previously, files inside the archive showed the download time instead of their actual modification date.
    Ensures accurate metadata and consistent behavior with the Tiki file manager.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/9292

2.8. Maps, Geolocation & Internationalization

• [+] Interactive Translation Now Supports Modals and Dropdown Menus
  • The interactive translation tool can now translate strings displayed inside modal dialogs and dropdown menus.
    Several UI and UX blockers that previously prevented translation in overlay elements have been fixed.
    This significantly improves the translator workflow, especially when working with modern UI components on i18n.tiki.org.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/8580

• [+] Timezone Mismatch Detection and Update
  • Tiki now detects when a user’s profile-configured timezone does not match the timezone reported by their web browser.
    When a mismatch is found, a clear notification is displayed with a one-click option to resolve it.
    Users can choose to:
    + Temporarily apply the browser’s timezone for the current session, or
    + Permanently update their profile timezone to match the detected setting.
    This helps prevent confusion when viewing dates, calendar events, logs, or tracker timestamps across different devices or locations.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/8079

• [+] Timezone Synchronization Option in User Preferences
  • A new option in the User Preferences page allows users to synchronize their timezone with their environment.
    This helps ensure accurate time display for features such as calendars, events, and timestamps.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/8529

2.9. Menus and Navigation

• [+] Dropdown Menu Dynamic Opening Direction
  • Submenus now automatically adjust their opening direction based on available screen space, improving navigation usability on all devices.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/8044

• [+] Pagetop Hero Module – Enhanced Breadcrumb Options
  • The Pagetop Hero module now allows configuring custom breadcrumb text and URLs.
    Provides greater flexibility for defining navigation paths displayed in breadcrumb trails.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/9307

• [+] Sidebar Behavior on Small Screens
  • The sidebar display has been improved to correctly respect user preferences on smaller viewports, resolving cases where collapsed sidebars rendered improperly.
    This update ensures consistent behavior across responsive and split-screen layouts.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/7951
• [+] Transitive Relations Module
  • A new module, `relations_transitive`, displays multi-level relationships between objects (for example A → B → C).
    Supports configurable search depth and optional exclusion of specific levels.
    Helps explore indirect relationships between tracker items and other linked objects.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/9317

2.10. Miscellaneous

• [+] Copy Link Action for Comments
  • A new “Copy Comment Link” action allows users to copy the direct URL of a comment to the clipboard.
    This simplifies sharing or referencing specific comments without manually copying the page URL.
    Improves usability when linking to discussions across pages, trackers, and other comment-enabled areas.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/8926
• [+] Custom WebSocket Base URL Support
  • Tiki now supports configuring a custom WebSocket base URL via realtime preferences.
    This allows instances to function correctly behind reverse proxies or in advanced deployment setups where the default WebSocket endpoint is not suitable.
    The enhancement improves flexibility and reliability for realtime features in complex infrastructures.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/8621

• [+] Email Threading for Notifications – Improved Handling
  • Email notifications now include standard headers such as "In-Reply-To" and "References".
    Enables proper conversation threading in mail clients for monitored comments and related activity.
    Improves organization of notification emails when multiple updates occur on the same content.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/9108

• [+] Mail Queue Management Interface and Retry Limit
  • A new administration page provides visibility into the mail queue, including a full list of queued messages and a summary of the current queue status.
    A new preference, mailer_queue_max_retries (default: 10), defines the maximum number of retry attempts for sending emails.
    Messages that exceed the retry limit are automatically ignored by the queue processor.
    This improves reliability, prevents endless retry loops, and makes failed email delivery handling safer and more predictable.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/8549

• [+] Notifications with End-of-Life Alerts
  • The update notification system now includes optional End-of-Life (EoL) alerts via the `feature_eol_date_notifier` preference.
    Administrators receive warnings when the installed LTS version is approaching or has reached its EoL date.
    Notifications now use color-coded indicators to highlight upgrade priority and importance.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/8784

• [+] Scheduler
  • Improved Notifications and Reliability
    The scheduler notification system has been enhanced with multiple improvements:
    • Consolidated preferences for better management.
    • Introduced an admin notification option for key alerts.
    • Added a stalled jobs banner with filtering capabilities.
    • Fixed issues with scheduler_users_to_notify_on_stalled to ensure alerts reach only the intended recipients.
    
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/7717
  • Scheduler Admin: Consolidated Logs and Status Overview
    The Scheduler Admin interface now includes a consolidated logs view to simplify monitoring and troubleshooting.
    A new Consolidated Logs tab displays total runs, last run status, and stalled status for each scheduled task.
    Logs are paginated for easier navigation, and deleted schedulers are handled gracefully with a Scheduler Deleted indicator.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/8921
• [+] System Menu Visual Consistency
  • Icons are now displayed by default for all System Menu dropdown items, aligning their appearance with the admin side menu.
    The icons are implemented in a vendor-neutral way to ensure compatibility with different icon sets.
    This change improves visual consistency and usability across administrative navigation.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/8636

• [+] Tiki Manager Instance Deletion Confirmation
  • The Tiki Manager interface now requires explicit user confirmation before deleting a Tiki instance.
    This critical-action prompt helps prevent accidental deletions and potential data loss.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/9045

• [+] Upgrade Notices – Improved Handling for VCS Versions
  • The upgrade notification system now detects when Tiki is running a VCS (development) version.
    Displays clearer notices indicating when a stable release is available.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/7166

• [+] User Avatar
  • The User Avatar has been replaced with a FontAwesome icon.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/8765

    
    

2.11. Plugins

• [+] Contributions Dashboard Plugin Uses Mermaid for Graphs
  • The Contributions Dashboard plugin now uses Mermaid for graph rendering, replacing the previous Raphaël-based implementation.
    This modernizes graph visualization and simplifies long-term maintenance, aligns the plugin with other parts of Tiki that use Mermaid for diagrams and visualizations.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/9546

• [+] Lottie Plugin for Displaying Animations
  • A new lottie wiki plugin allows embedding Lottie animations in pages.
    Animations can be loaded from a File Gallery file or an external URL.
    Supports options such as autoplay and custom dimensions.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/9333

• [+] Model3DViewer Plugin to display 3D objects on the page
  • A new model3dviewer plugin allows embedding interactive 3D models in pages.
    Supports models from File Galleries or external URLs (GLB, glTF, STL, OBJ, FBX).
    Provides camera controls, optional auto-rotation, animation playback, and visual customization.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/8212

• [+] Newsletter Subscription Plugin – Improved Feedback and Email Confirmation
  • The newsletter subscription plugin now provides clearer status messages during the subscription process.
    Improves handling of email confirmation workflows to ensure subscriptions are properly validated before activation.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/9134
• [+] PluginImg Reflection Update
  • Image reflections can now be enabled directly through PluginImg options, using a modern CSS-based reflection feature.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/7561

• [+] PluginList
  • Advanced Filtering with AND / OR / NOT
    PluginList now supports advanced filtering logic when using multiple selections.
    Filters can be combined using AND, OR, or NOT operators on fields that allow multiple values.
    The enhancement brings PluginList filtering closer to advanced search capabilities and improves flexibility when building complex lists.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/5416
  • Filter Tracker Items by Creator
    PluginList now supports filtering tracker items by their creator using the "created_by" filter.
    Enables more precise queries and personalized views when listing tracker items.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/9291

• [+] RSS Plugin
  • The RSS plugin now fully supports the max, sortBy, and sortOrder parameters when used with URL-based feeds.
    • max: Controls the number of feed items displayed.
    • sortBy: Defines the field used for sorting items.
    • sortOrder: Specifies sorting direction (ascending or descending).
    
    These enhancements apply directly to URL-based feeds, not only database-stored items.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/8303
• [+] PluginList Sublist Plugin: Memory Optimization with limitfields
  • A new limitfields parameter has been added to the Sublist plugin.
    When enabled (limitfields="y"), the sublist result set is limited to only the formatted columns actually displayed.
    This reduces memory usage and improves performance, especially for large datasets.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/8821
• [+] Teleprompter Plugin for Auto-Scrolling Presentations
  • A new teleprompter wiki plugin provides a customizable auto-scrolling teleprompter for presentations, speeches, recordings, and guided reading.
    Supports configurable scrolling behavior, mirror modes, playback controls, timers, and display customization.
    Content can be displayed from wiki text or File Gallery images.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/9302
• [+] YouTube Plugin – Responsive Video Support
  • The YouTube plugin now supports responsive video embeds that adapt to the container width.
    The correct aspect ratio is determined using YouTube oEmbed data.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/8579

2.12. Search and Files

• [+] ElasticSearch Configurable max_result_window
  • Tiki now allows administrators to configure the ElasticSearch max_result_window setting.
    This makes it possible to retrieve result sets larger than the default 10,000 record limit, such as when using PluginList with large datasets.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/8982
• [+] mPDF PDF Generation Improvements
  • Improvements to the mPDF rendering pipeline increase reliability of PDF generation.
    A new debug preference allows administrators to save the generated HTML used for PDF rendering.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/9320
• [+] robots.txt – Improved Handling and SEF URL Indexing
  • robots.txt handling has been improved with a dedicated parser following RFC 9309.
    Supports proper user-agent matching, wildcard rules, and Allow/Disallow precedence.
    Prevents incorrect NOINDEX directives when SEF URLs are enabled and improves search engine indexing behavior.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/9346
• [+] Sitemap Generation – Improvements
  • The sitemap generation system has been refined to improve reliability and maintainability.
    Updates include implementation adjustments and compliance with current coding standards.
    Helps ensure consistent sitemap generation for search engine indexing.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/9487
• [+] SEO and Sitemap Management Enhancements
  • Enhanced SEO and sitemap management with automatic sitemap generation support.
    Administrators can now choose between automatic and manual sitemap generation modes.
    Advanced sitemap splitting options improve scalability and handling of large websites.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/9573

2.13. Security & Access Control

• [+] 2FA
  • Administration Improvements
    Site administrators can now reset or disable Two-Factor Authentication (2FA) for individual users.
    This supports secure account recovery scenarios, such as when users lose access to their authentication devices.
    The enhancement complements group-based 2FA enforcement and grace-period policies in organizational environments.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/8723
  • Enforcement with Per-User and Per-Group Grace Periods
    Tiki now supports enforcing Two-Factor Authentication (2FA) using configurable grace periods applied per group and per user.
    Administrators can define enforcement policies with grace periods (for example 3, 7, 14, or 30 days), calculated per user based on enforcement date or account creation.
    Clear reminders are shown to users during the grace period, and optional notifications can be sent to users who have not yet enabled 2FA.
    A grace period of 0 days enforces immediate 2FA, and accounts are automatically locked once the grace period expires.
    An admin interface allows granting, revoking, or extending grace periods for individual users, supporting scalable and secure 2FA rollout.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/8710
• [+] Batch Lock/Unlock for User Accounts
  • Administrators can now lock or unlock multiple user accounts at once from the user administration interface.
    Multiple users can be selected and the lock or unlock action applied via the dropdown menu.
    This enhancement reduces manual effort and significantly speeds up account management on sites with large user bases.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/8733

• [+] Blending Permission Scope System
  • A new preference introduces flexible permission scope handling.
    Administrators can choose between the traditional strict scope (nearest defined scope wins) or the new blending scope, which merges permissions from nearest to farthest using an additive model.
    This provides more granular control over permission inheritance and enforcement.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/7181

• [+] Brute Force Protection (Experimental)
  • A new experimental brute force protection system has been introduced to mitigate automated attacks on authentication-related workflows.
    The new BruteForceProtection service applies exponential backoff throttling to login attempts, user registration, and password reset requests.
    Attempts are tracked in a new tiki_bruteforce_attempts database table with automatic, time-based cleanup.
    New experimental admin preferences allow enabling or disabling the feature, configuring the initial delay, growth rate multiplier, and forget time window.
    Users receive clear retry messages indicating when the next attempt is allowed.
    The system includes full unit test coverage for timing, attempt tracking, and expiry behavior.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/8588

• [+] Email-to-Tracker Safety Preference
  • A new preference has been added ( email_to_tracker_mode ) to control whether emails are moved or copied when creating tracker items from IMAP.
    The enhancement is especially useful in test or pre-production environments where email retention is critical.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/8646

• [+] Expanded HTTP Security Headers and CORS Support
  • Tiki now supports a full set of configurable CORS and cross-origin policy headers, including credential handling, allowed methods and headers, and modern browser isolation controls (COOP, COEP, CORP).
    All headers are configurable from the Admin → Security interface and follow MDN specifications.
    Smart validation prevents unsafe configurations, and all options are disabled by default to preserve backward compatibility.
    This enhancement strengthens security while giving administrators fine-grained control over cross-origin behavior.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/8639

• [+] Forum Email Masking Option
  • A new privacy feature allows forums to automatically hide email addresses from public view.
    A new forum_mask_emails preference controls masking behavior, and a maskFields method in the Comments class ensures sensitive fields are safely masked.
    A new forummaskemail template modifier is used across forum views, and admin settings have been updated to manage email masking.
    This enhancement helps prevent email harvesting and strengthens privacy on forums open to anonymous visitors.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/9159

• [+] Password Reset Security with Cryptographic Tokens Improved
  • The password reset process has been modernized to use cryptographically secure random tokens instead of the previous MD5-based validation.
    This significantly reduces the risk of token prediction, forgery, or replay attacks.
    Key improvements include:
    • Replacement of insecure MD5 hashes with secure, randomly generated reset tokens.
    • Introduction of PasswordResetLib for token creation, validation, and expiration handling.
    • Addition of a new database table, tiki_password_reset_tokens, to safely store and manage reset tokens.
    
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/8426
• [+] Retry-After Header for Load Threshold Protection
  • When "use_load_threshold" protection is triggered, Tiki now sends a "Retry-After" HTTP header.
    Informs clients and bots how long to wait before retrying requests when the server is under high load.
    Improves behavior of search engines and automated clients during temporary overload situations.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/9349
• [+] SAML Authentication: Admin Fallback Login
  • When SAML authentication is enabled, all users with Admin privileges can now log in using Tiki’s fallback authentication method.
    This improves flexibility while preserving a secure login flow and simplifies access for administrators.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/8214

• [+] Security Checks in tiki-check Enhanced
  • tiki-check.php and its dashboard have been extended with additional security verifications to help administrators quickly identify potential risks.
    New checks include:
    • Detection of exposed or misconfigured phpMyAdmin installations.
    • Detection of leftover or publicly accessible Adminer / AdminerEvo files.
    • Verification of unsafe, world-readable permissions on db/local.php.
    • Additional warnings for other common insecure deployment conditions.
    
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/7986
• [+] Trusted Proxy Restriction for Load Balancer Access
  • Support for trusted proxies has been added to improve security when Tiki is deployed behind a load balancer.
    The feature_loadbalancer_header preference enables handling of load balancer headers.
    The feature_loadbalancer_trusted_proxies preference allows restricting accepted proxy IP addresses to a trusted list.
    Helps prevent spoofed headers and unauthorized access through proxy infrastructure.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/9484
• [+] Usernames Cannot Contain Spaces
  • Tiki now strictly enforces that usernames cannot contain spaces and must follow a single contiguous pattern.
    This prevents ambiguities between usernames and page content or other identifiers.
    The rule applies system-wide and improves compatibility with features such as feature_tag_users.
    https://gitlab.com/tikiwiki/tiki/-/merge_requests/9040