Tiki RSS feed for the wiki pages

Creating or maintaining translations

2026-08-09T19:58:34+00:00

9" >Copy to clipboard

9" >php console.php translation:getstrings --lang=fr --skip-remove

1" >Copy to clipboard

1" >php console.php translation:getstrings --lang=fr --skip-remove

-
1
" >Copy to clipboard
1
" >// "Save" => "Save",

+
2" >Copy to clipboard
2" >// "Save" => "Save",

-
11" >Copy to clipboard
11" >"Save" => "Enregistrer",

+
3" >Copy to clipboard
3" >"Save" => "Enregistrer",

-
12" >Copy to clipboard
12" >php console.php translation:getstrings --lang=fr

4" >Copy to clipboard

4" >php console.php translation:getstrings --lang=fr

13" >Copy to clipboard

13" >php console.php translation:getstrings --lang=fr --skip-remove

5" >Copy to clipboard

5" >php console.php translation:getstrings --lang=fr --skip-remove

14" >Copy to clipboard

14" >php console.php translation:getstrings --custom --lang=fr --skip-remove

6" >Copy to clipboard

6" >php console.php translation:getstrings --custom --lang=fr --skip-remove

-
15" >Copy to clipboard
15" ><?php

+
7" >Copy to clipboard
7" ><?php

-
16" >Copy to clipboard
16" >php console.php translation:getstrings [options]

8" >Copy to clipboard

8" >php console.php translation:getstrings [options]

-
_custom

Endangered features

2026-08-07T13:02:16+00:00

-
3-link" class=> Details
3" class="wpfade-div-plain">
"The idea is to make the image galleries redundant, then obsolete, then nonexistant."

What is missing in File galleries?
Following the 2
14-11-
6 BBB meeting, Jyhem did a search of everything Image Galleries offer which is not in File Galleries.

+
1-link" class=> Details
1" class="wpfade-div-plain">
"The idea is to make the image galleries redundant, then obsolete, then nonexistant."

What is missing in File galleries?
Following the 2
14-11-
6 BBB meeting, Jyhem did a search of everything Image Galleries offer which is not in File Galleries.

-
5
~~e3c2~~">-1 I find the legacy (tabbed) insertion screen faster to use and appreciate being able to switch back and forth between tabs in some cases. The larger size for the form is also useful sometimes. 1.2. Release Steps
1.2.1. Checkout Tiki
1.2.2. Setup.sh
1.2.3. Update lib/setup/twversion.class.php ~~before the release~~
1.2.4. Run script
1.2.5. Create and test pre-release packages
1.2.5.1. Check the generated README file
1.2.6. Launch the release script again
1.2.6.1. Troubleshooting
1.2.6.1.1. Mysql credentials
1.2.7. Test the produced "tarballs" and share the testing
1.2.8. Upload tarballs to Sourceforge
1.3. After Release Steps
1.3.1. Update lib/setup/twversion.class.php
1.3.2. Update show2.t.o info (Skipped until note is resolved)
1.3.2.1. checkout that version in the local cache folder of tiki in show2.t.o
1.3.2.2. tell tim to manage also that branch to update tiki from that version also
1.3.2.3. make a tar.gz file from the new branch
1.3.2.4. update the field in tracker5 at dev.t.o to allow users to choose that version

+
1.2. Requirements
1.3. Release Steps
1.3.1. Checkout Tiki
1.3.2. Setup.sh
1.3.3. Update lib/setup/twversion.class.php
1.3.4. Run script
1.3.4.1. Check the generated README file
1.3.5. Test the produced "tarballs" and share the testing
1.3.6. Upload tarballs to Sourceforge
1.4. After Release Steps
1.4.1. Update lib/setup/twversion.class.php
1.4.2. Update show2.t.o info (Skipped until note is resolved)
1.4.2.1. checkout that version in the local cache folder of tiki in show2.t.o
1.4.2.2. tell tim to manage also that branch to update tiki from that version also
1.4.2.3. make a tar.gz file from the new branch
1.4.2.4. update the field in tracker5 at dev.t.o to allow users to choose that version

-
1.2. Release Steps

- 3 class="showhide_heading d-flex justify-content-start" id="Checkout_Tiki">1.2.1. Checkout Tiki

+ 2 class="showhide_heading d-flex justify-content-start" id="Requirements_2">1.2. Requirements
Unix shell environment, Linux or OSX suitable.
Git
PHP 7.x or 8.x CLI.
Note about php versions:

Use PHP 7.x for Tiki 25.x releases and lower

Use PHP 8.x for Tiki 26.x releases and upper.

PHP configuration must allow running external programs (like shell scripts)
Starting from Tiki 27.x and later versions release, Node.js and NPM are requiredtrong> for the JavasScript build system(for js and css compilation). Please check the required the versions in package.json at the root of the project in the "engines" property.
7za or 7z needed for creating 7zip archives. (may be installed in OSX through homebrew by typing brew install p7zip)
Plenty of disk space and memory 😉 - at least 64M of memory for php (in php.ini for php-cli)
The main packaging script is at blank" title="External link" href="https://gitlab.com/tikiwiki/tiki/-/blob/master/doc/devtools/release.php" rel="external">doc/devtools/release.php but releasing a Tiki version is a lot more than just running the packaging script 😊

1.3. Release Steps2>
1.3.1. Checkout Tiki

-
OPTION 1 Clone the branch you need to create the release for in a separate folder to separate it with your development instance by doing the following. Note that the bellow command is an example, so replace the branch value with that you want to work on, the reference repository by the path of your development instance to gain time when cloning and the target folder by that you want. Also remember to ensure that the reference repository is up to date and contains the required objects for successful cloning.
39" >Copy to clipboard
39" >
git clone --branch=29.x --shared --reference=./tiki https://gitlab.com/tikiwiki/tiki.git tiki29release
OPTION 2 checkout the correct branch, i.e the branch you want to create the release for and make sure your origin is https://gitlab.com/tikiwiki/tiki.git. For example, if you want to create the 29.1 release, do
Copy to clipboard
git checkout 29.x

OPTION 1	Clone the branch you need to create the release for in a separate folder to separate it with your development instance by doing the following. Note that the bellow command is an example, so replace the branch value with that you want to work on, the reference repository by the path of your development instance to gain time when cloning and the target folder by that you want. Also remember to ensure that the reference repository is up to date and contains the required objects for successful cloning. 39" >Copy to clipboard 39" > git clone --branch=29.x --shared --reference=./tiki https://gitlab.com/tikiwiki/tiki.git tiki29release
OPTION 2	checkout the correct branch, i.e the branch you want to create the release for and make sure your origin is https://gitlab.com/tikiwiki/tiki.git. For example, if you want to create the 29.1 release, do Copy to clipboard git checkout 29.x

+ No Tabs
Option 1
Option 2

>
OPTION 1 >
Clone the branch you need to create the release for in a separate folder to separate it with your development instance by doing the following. Note that the bellow command is an example, so replace the branch value with that you want to work on, the reference repository by the path of your development instance to gain time when cloning and the target folder by that you want. Also remember to ensure that the reference repository is up to date and contains the required objects for successful cloning.
21" >Copy to clipboard
21" >
git clone --branch=29.x --shared --reference=./tiki https://gitlab.com/tikiwiki/tiki.git tiki29release

OPTION 1 >
Clone the branch you need to create the release for in a separate folder to separate it with your development instance by doing the following. Note that the bellow command is an example, so replace the branch value with that you want to work on, the reference repository by the path of your development instance to gain time when cloning and the target folder by that you want. Also remember to ensure that the reference repository is up to date and contains the required objects for successful cloning. 21" >Copy to clipboard 21" > git clone --branch=29.x --shared --reference=./tiki https://gitlab.com/tikiwiki/tiki.git tiki29release

+

-
1.2.2. Setup.sh

+ OPTION 2
checkout the correct branch, i.e the branch you want to create the release for and make sure your origin is https://gitlab.com/tikiwiki/tiki.git. For example, if you want to create the 29.1 release, do
Copy to clipboard
git checkout 29.x

1.3.2. Setup.sh

OPTION 2
checkout the correct branch, i.e the branch you want to create the release for and make sure your origin is https://gitlab.com/tikiwiki/tiki.git. For example, if you want to create the 29.1 release, do Copy to clipboard git checkout 29.x

-
41" >Copy to clipboard
41" >
sh ./setup.sh

+
23" >Copy to clipboard
23" >
sh ./setup.sh

-
_before_the_release">1.2.3. Update lib/setup/twversion.class.php ~~before the release~~_before_the_release" class="heading-link" aria-label="heading link">

<~~p>Look for section with "Release Managers sho~~ul~~d update this array before release." of~~ >~~https://gitlab.com/tikiwiki/tiki/-/blob/master/lib/setup/twversion.class.php~~ (of your relevant branch)

increment the version number and the star name in the constructor. The star name only needs to be updated if it is a major release (Eg. Tiki 29.
alpha) but this is usually done during branching, it's done during release if it was not done during branching.
temporarily, remove the vcs from the branch number. E.g.

42" >Copy to clipboard
42" >
function TWVersion()

+
1.3.3. Update lib/setup/twversion.class.php

Increment the version number and the star name in the constructor. The star name only needs to be updated if it is a major release (Eg. Tiki 29.
alpha) but this is usually done during branching, it's done during release if it was not done during branching.
Temporarily, remove the vcs from the branch number.
E.g

4" >Copy to clipboard
4" >
function TWVersion()

- // Set the development branch. Valid are:
// stable : Represents stable releases.
// unstable : Represents candidate and test/development releases.
// trunk : Represents next generation development version.
$this->branch = &#
39;stable&#
39;;

// Set everything else, including defaults.
$this->version = &#
39;22.1vcs&#
39;; ~~// needs to have no spaces for releases~~
$this->star = &#
39;Corona Borealis&#
39;;>

> Since we where to release 22.1, we need to remove the "vcs" from "22.1vcs", so this part will stay as:

43" >Copy to clipboard
43" >
// Set everything else, including defaults.

+ $this->version = &#
39;22.1vcs&#
39;;
$this->star = &#
39;Corona Borealis&#
39;; Since we where to release 22.1, we need to remove the "vcs" from "22.1vcs", so this part will stay as:

25" >Copy to clipboard
25" >
// Set everything else, including defaults.

-
update list of valid releases in tikiVersions()
<ul>
Make sure you add all Tiki versions (not just the one you are doing now). Ex.: when 5.
is released, 4.2 will probably exist, as this was added to branches/4.x but not merged by script.

+
Update list of valid releases in tikiVersions()
</li>
Make sure you add all Tiki versions (not just the one you are doing now). Ex.: when 5.
is released, 4.2 will probably exist, as this was added to branches/4.x but not merged by script.

-
Update the star name in the list in the function tikiStars() if it's not yet done.
i> ~~Comm~~i~~t your~~ cha~~nge~~s ~~with thi~~s c~~ommit m~~essage ~~(ch~~a~~nge \$VERSION~~ by the version of t~~he rele~~ase):

>
"codel~~isting_c~~ontain~~er"~~><~~div~~ class="~~ico~~n~~_co~~p~~y_code fa~~r ~~fa-cl~~i~~pbo~~ard" t~~abi~~n~~dex="~~
" ~~data-clipboard-~~target="~~#codebox44~~" >l~~ass~~="~~copy_code_~~t~~ool~~t~~iptext">C~~o~~py to clipboard~~n>
data-~~them~~e="off" data-syn~~tax~~="shell" data-wrap~~="1~~" dir="~~ltr"~~ st~~yle="wh~~ite~~-space:pre-wrap; o~~verflo~~w-wr~~ap: bre~~ak-w~~o~~rd;~~ wo~~rd-~~w~~rap: brea~~k-wo~~rd;"~~ i~~d="cod~~ebox44" >
as~~s="code">[RE~~L~~] Preparing \$V~~ERSION ~~rele~~asediv>>

</li>
Then push your commit to ank" class="~~wiki~~ ~~exter~~na~~l" href="h~~ttps~~://github.com/tikiwiki/tiki.git~~"~~>https://g~~i~~thub.com/tikiwiki/tiki.git~~="i~~mg/ic~~ons~~/green~~_~~ques~~t~~ion.png"~~ a~~lt="Qu~~est~~ion~~" wi~~dth="16"~~ ~~height~~="~~16"~~ na~~me="link~~-~~external" t~~itle~~="Question~~" class="~~ico~~n~~" />~~a> in ~~the corresponding br~~anc~~h (~~the ~~branc~~h ~~you a~~re doing the r~~elea~~s~~e for).~~
i>
on~~g>No~~tet~~rong>:~~ ~~Do no~~t pus~~h y~~o~~ur chan~~ge~~s if you~~ a~~re doing a p~~re-release ~~test.~~
p>
<hr />
<h3 class="~~showh~~i~~de_h~~ea~~ding~~ ~~d-f~~l~~ex ju~~s~~tify-content-~~s~~tart" id~~="Run~~_scr~~ipt"~~>1.2.4. Run script~~ href="#Run_script~~" cl~~as~~s="h~~e~~ading~~-~~link~~" aria-label="hea~~ding link~~">las~~s="~~icon ~~icon-link f~~a~~s fa-link "~~ >span>a>h3>
<~~p>The ma~~i~~n packaging script is at~~ class="~~wiki ex~~tern~~al"~~ t~~arg~~et~~="_blank~~" ti~~tle~~="~~Ext~~er~~nal l~~in~~k" href="h~~ttps~~://sourceforge.n~~et~~/p/t~~iki~~wiki/~~code~~/HEAD/~~tre~~e/t~~run~~k/doc/dev~~t~~ool~~s/release.p~~hp"~~ ~~rel="extern~~a~~l">do~~c~~/de~~v~~tools/r~~e~~lease.ph~~pa><~~img~~ sr~~c="img/ic~~ons/g~~ree~~n_questio~~n.p~~ng~~" alt="Qu~~estion" ~~width="16" h~~e~~ight="16" nam~~e="l~~ink-~~exte~~rnal"~~ t~~itle="Qu~~est~~ion" cla~~s~~s="ic~~on~~" /~~>

+
Update the star name in the list in the function tikiStars() if it's not yet done.
</ul>iv class="clearfix tabs" data-name="versions_tabset_2">
'float-end'><a class="btn btn-primary btn-sm" target="" role="button" data-role="button" data-inline="true" href="/tiki-wiki_rss.php" onclick="setCookie('versions_tabset_2','n', 'tabs', 'session', window.tikiCookieConstants.BUILTIN_COOKIE_CATEGORY_FUNCTIONAL);" >No Tabsa>
nav nav-tabs" id="nav-versions_tabset_2">i class="nav-item"> class="nav-link active" href="#contentversions_tabset_2-1" data-bs-toggle="tab">Pre-releasea>li><li class="nav-item"><a class="nav-link " href="#contentversions_tabset_2-2" data-bs-toggle="tab">Releasinga>li>ul>div><div class="tab-content" id="v-pills-versions_tabset_2">iv id='contentversions_tabset_2-1' class='tab-pane pt-3 active'> <p>
<br />trong>Do not push your changes in pre-release test.strong>

-
Go to ~~the~~ ~~newly~~ ~~create~~d directory and ~~run~~

+

div> <div id='contentversions_tabset_2-2' class='tab-pane pt-3 '>

- <div class="codeca~~ptio~~n~~">Displa~~y Basic Helpdiv>
45" >Copy to clipboard
45" >
php doc/devtools/release.php --helpdiv>re>

+ <ul>i> Commit your changes with this commit message (change \$VERSION by the version of the release):
<br />
26" >Copy to clipboard
26" >
[REL] Preparing \$VERSION release

Then push your commit to et="_blank" class="wiki external" href="https://github.com/tikiwiki/tiki.git">https://github.com/tikiwiki/tiki.gitsrc="img/icons/green_question.png" alt="Question" width="16" height="16" name="link-external" title="Question" class="icon" /> in the corresponding branch (the branch you are doing the release for).
<p>
<br />>

>

-
to get the command help and see different options that can be used.

-
To Run the release command:

+

1.3.4. Run script

Go to the tiki instance pointing to the branch you want to release and run:

Display Basic Help
Copy to clipboard
php doc/devtools/release.php --help
to get the command help and see different options that can be used.
To Run the pre-release or release command:

-
odelistin~~g_c~~ontainer">
"icon~~_copy_co~~d~~e f~~ar ~~fa-~~cl~~ipbo~~ard" tabindex="
" data-clipboard-target="~~#cod~~e~~box46~~" ><span cl~~ass~~="co~~py_c~~ode_tooltipte~~xt">~~Copy to ~~clipb~~oardspan>
<~~pre~~ class="~~codelisti~~ng" data~~-theme="off~~" data-synta~~x="~~shell" data~~-wr~~ap="1" dir="ltr" style="~~whi~~t~~e-sp~~a~~ce:p~~re-wr~~ap; ov~~erfl~~ow-wr~~a~~p: br~~ea~~k-word;~~ ~~word-wr~~a~~p: bre~~ak-~~word;"~~ i~~d="cod~~e~~box46~~" ><~~div~~ class="code"~~>php~~ d~~oc/dev~~tool~~s/r~~eleas~~e.php 26.1~~div>pre>

<~~p>(rep~~lace ~~26.1 wi~~th the corresponding release ve~~rsion)~~

+
earfix tabs" data-name="versions_tabset_3">
'float-end'><a class="btn btn-primary btn-sm" target="" role="button" data-role="button" data-inline="true" href="/tiki-wiki_rss.php" onclick="setCookie('versions_tabset_3','n', 'tabs', 'session', window.tikiCookieConstants.BUILTIN_COOKIE_CATEGORY_FUNCTIONAL);" >No Tabs
<ul class="nav nav-tabs" id="nav-versions_tabset_3"><li class="nav-item"><a class="nav-link active" href="#contentversions_tabset_3-1" data-bs-toggle="tab">Pre-releasea> class="nav-item"><a class="nav-link " href="#contentversions_tabset_3-2" data-bs-toggle="tab">Releasinga>i>ul>
<div class="tab-content" id="v-pills-versions_tabset_3"><div id='contentversions_tabset_3-1' class='tab-pane pt-3 active'>

-
Note: For Tiki 31 and later We don't need this anymore since Secdb got temporary disabled,

If the previous command fails at the secdb file creation step, you may need to run the release command providing your MySQL credentials for the script to successfully create the secdb file for you.

Unnecessary for Tiki31 and later
Copy to clipboard
php -d mysqli.default_host=HOST -d mysqli.default_user=USER -d mysqli.default_pw=PASS doc/devtools/release.php 28.2

(replace the version number with the corresponding release version)

Note: Do not run this command first. Before running it, please start with the creation of pre-release packages as described in the next step.

~~1.2.5.~~ Create and test pre-release packages

+
Create and test pre-release packages

-
48" >Copy to clipboard
48" >
php8.1 doc/devtools/release.php 29.
preRC1 --devmode

+
28" >Copy to clipboard
28" >
php8.1 doc/devtools/release.php 29.
preRC1 --devmode

-
49" >Copy to clipboard
49" >
php8.1 doc/devtools/release.php 29.1 pre --devmode

>

>Note: Use the command for the version of PHP which is the minimum spec for that branch. In this case we need PHP 7.1 for Tiki 19.x~~, 5.6~~ for ~~18.x~~ and ~~15.x~~ and 5.3 for 12.x, for instanceem>

+
29" >Copy to clipboard
29" >
php8.1 doc/devtools/release.php 29.1 pre --devmode

Note: Use the command for the version of PHP which is the minimum spec for that branch. In this case we need PHP 7.4 for Tiki 24.x for instance

div>

ong>Note: Do not run this command first. Before running it, please start with the creation of pre-release packages as described in the first tab.strong>

-
The release script has an interactive mode, enabled by default, that will ask you if you really want to do each step. It also asks for a confirmation before committing any changes. You can have a look at them with another shell by using this command:

-

-
Check for changes made by the release script before validating commits
Copy to clipboard
git status

- git diff

- <h4 class="sho~~whi~~de~~_head~~i~~ng d-flex ju~~sti~~fy-~~conte~~nt-sta~~rt" id="~~Che~~c~~k_the_ge~~n~~erated~~_~~README~~_~~file">1.2.5.1. Che~~c~~k th~~e ~~gener~~a~~ted~~ ~~README~~ fi~~le<~~a hr~~ef=~~"~~#Check_~~t~~he_ge~~n~~erate~~d~~_README_fil~~e" cla~~ss="he~~a~~ding~~-li~~nk"~~ aria-label="he~~ading~~ ~~link"~~>ico~~n i~~con-link ~~fas~~ ~~fa-~~li~~nk " >~~a>
>ro~~ng>Not~~estrong>: For ~~Tiki 3~~
and later, thi~~s s~~tep can be skipped. The ~~README~~ is no longer generated per release; the ve~~rsion~~ fro~~m maste~~r (trunk) is ~~sha~~red a~~cros~~s versions.

+ <div class="codelisting_container"><div class="icon_copy_code far fa-clipboard" tabindex="
" data-clipboard-target="#codebox3
" >py_code_tooltiptext">Copy to clipboarddiv>e class="codelisting" data-theme="off" data-syntax="shell" data-wrap="1" dir="ltr" style="white-space:pre-wrap; overflow-wrap: break-word; word-wrap: break-word;" id="codebox3
" >iv class="code">php doc/devtools/release.php 26.1pre>
(replace 26.1 with the corresponding release version)

- <ul><li> ~~Chec~~k lin~~ks/con~~tent in the gene~~rat~~ed ~~README~~ file
li><~~/ul>~~r />
<h3 clas~~s="s~~h~~owhid~~e_head~~ing~~ d-flex ~~jus~~ti~~fy-c~~on~~tent-~~sta~~rt"~~ id~~="La~~un~~ch_~~the_release_scri~~pt_aga~~in~~">1.2.6.~~ L~~aun~~c~~h the~~ release script~~&nb~~s~~p;again~~ef~~="#La~~unc~~h_the_~~release_scrip~~t_aga~~in" class="headin~~g-link~~" aria-label="~~hea~~ding link"><~~span~~ class="icon ico~~n-link~~ fas fa-link " ></span>h3>
>After testing, launch the release script again, now without "pre":

+ <p>Note: <strong>For Tiki 31 and later We don't need this anymore since Secdb got temporary disabled,strong>
<br />If the previous command fails at the secdb file creation step, you may need to run the release command providing your MySQL credentials for the script to successfully create the secdb file for you.
p>

iv class="codecaption">Unnecessary for Tiki31 and later
lass="codelisting_container"><div class="icon_copy_code far fa-clipboard" tabindex="
" data-clipboard-target="#codebox31" > class="copy_code_tooltiptext">Copy to clipboardspan>div>e class="codelisting" data-theme="off" data-syntax="shell" data-wrap="1" dir="ltr" style="white-space:pre-wrap; overflow-wrap: break-word; word-wrap: break-word;" id="codebox31" >
lass="code">php -d mysqli.default_host=HOST -d mysqli.default_user=USER -d mysqli.default_pw=PASS doc/devtools/release.php 28.2iv>pre>
(replace the version number with the corresponding release version)
or

-
Unnecessary for Tiki31 and later, use simplified command instead
51" >Copy to clipboard
51" >
php -d mysqli.default_host=HOST -d mysqli.default_user=USER -d mysqli.default_pw=PASS doc/devtools/release.php 29.
RC1

+
Unnecessary for Tiki31 and later, use simplified command instead
32" >Copy to clipboard
32" >
php -d mysqli.default_host=HOST -d mysqli.default_user=USER -d mysqli.default_pw=PASS doc/devtools/release.php 29.
RC1

-
Or

+
The release script has an interactive mode, enabled by default, that will ask you if you really want to do each step. It also asks for a confirmation before committing any changes. You can have a look at them with another shell by using this command:

-
~~Unn~~ec~~essary~~ for ~~Tiki31~~ and later, use simplified comm~~and~~ inst~~ead~~
52" >Copy to clipboard
52" >
~~php -d mysql~~i~~.defaul~~t~~_host=HOST~~ -d mys~~qli.def~~ault_us~~er=USER~~ -d ~~mysql~~i~~.de~~f~~ault_pw=PASS doc/devtools/release.php 29.1~~

Note: If you run the php command without specifying explitely the version as in the above commands, please make sure your CLI php version is set to the required one of the branch you are making the release for.

+
Check for changes made by the release script before validating commits
33" >Copy to clipboard
33" >
git status
git diff

>

>Note: If you run the php command without specifying explitely the version as in the above commands, please make sure your CLI php version is set to the required one of the branch you are making the release for.

- ~~class="showhide_heading~~ ~~d-flex~~ ~~justify-content-start"~~ ~~id="Troubleshooting">1.2.6.1.~~ ~~Troubleshooting~~ ~~href="#Troubleshooting"~~ ~~class="heading-link"~~ ~~aria-label="heading~~ ~~link">~~ ~~class="icon~~ ~~icon-link~~ ~~fas~~ ~~fa-link~~ " >
~~class="showhide_heading~~ ~~d-flex justify-content-start" id="Mysql_credentials">1.2.6.1.1. Mysql credentials~~<~~a href="#Mysql_cre~~d~~ent~~i~~als" class="heading-link" aria-label="heading link">~~>span>
Note: For Tiki 31 and ~~later We don't need th~~i~~s anymore since Secdb got temporary disabled,~~
<~~br />In ste~~p ~~11 (or 8 ?) of the release script ("~~>8) Generate SecDB file 'db/tiki-secdb_12.1_mysql.sql'?"), you might see this type of error:

~~SecDB step failed because some filenames need escaping but no MySQL connection has been found.~~

~~Try this command line instead (replace HOST, USER and PASS by a valid MySQL host, user and password) :~~

+ </div>v>

- <~~div~~ class="codecaption~~">Unnec~~essary ~~for T~~iki31 ~~and~~ later, use simplifie~~d comm~~and ~~inst~~ead
="code~~listin~~g~~_co~~ntainer"> class="icon~~_copy_code far fa~~-cli~~pboard~~" tabindex="
" data-clipb~~oard-targ~~et="~~#co~~d~~ebox53~~" >py_co~~de_too~~lti~~ptext">Copy~~ to cli~~pboard~~div>e class="codelisting" dat~~a-th~~e~~me="off"~~ data-synt~~ax="sh~~e~~ll"~~ da~~ta-li~~n~~e-num~~bers="
" ~~data-wrap="1"~~ di~~r="ltr"~~ ~~sty~~le~~="whi~~te-space:pr~~e-w~~rap; overflo~~w-wr~~ap: break~~-word;~~ ~~word-wr~~a~~p: b~~re~~ak-wor~~d;" ~~id="~~codebo~~x53"~~ ><div clas~~s="~~code~~">/usr/b~~in~~/php~~ ~~-d mysql.defaul~~t_h~~ost=HOST~~ ~~-d mysql.d~~efault~~_us~~e~~r=US~~ER ~~-d mysql.de~~faul~~t_password=PASS doc/d~~e~~vtools~~/~~relea~~s~~e.php 12.1 be~~ta
re>>

+ <h4 class="showhide_heading d-flex justify-content-start" id="Check_the_generated_README_file">1.3.4.1. Check the generated README&nbsp;file<a href="#Check_the_generated_README_file" class="heading-link" aria-label="heading link">icon icon-link fas fa-link " >a>>
>rong>Notestrong>: For Tiki 3
and later, this step can be skipped. The README is no longer generated per release; the version from master (trunk) is shared across versions.

><li> Check links/content in the generated README file</strong>

-
If so, provide your own HOST, USER and PASS for your MySQL from the machine where you are running the release script, and you should be fine, then.

-

1.2.7. Test the produced "tarballs" and share the testing

Test on your server. Ideally, you have 1-2 other people trying on different servers. In case of a major version (x.
), you need at least 3 installations from 3 different people

+

1.3.5. Test the produced "tarballs" and share the testing

>

>Test on your server. Ideally, you have 1-2 other people trying on different servers. In case of a major version (x.
), you need at least 3 installations from 3 different people

-
Make sure to do a file integrity check with tiki-admin_security.php?check_files

+
Make sure to do a file integrity check with tiki-admin_security.php?check_files (Only applies on tiki 3
and lower)

-
One tester should test an upgrade

+
One tester should test an upgrade (from previous to newer minor version and previous to newer major )

+

-
1.2.8. Upload tarballs to Sourceforge

+
1.3.6. Upload tarballs to Sourceforge

-
1">
1','n', 'tabs', 'session', window.tikiCookieConstants.BUILTIN_COOKIE_CATEGORY_FUNCTIONAL);" >No Tabs
1">
1-1" data-bs-toggle="tab">Web Interface
1-2" data-bs-toggle="tab">SCP
1-3" data-bs-toggle="tab">SFTP
1">

+
4">
4','n', 'tabs', 'session', window.tikiCookieConstants.BUILTIN_COOKIE_CATEGORY_FUNCTIONAL);" >No Tabs
4">
4-1" data-bs-toggle="tab">Web Interface
4-2" data-bs-toggle="tab">SCP
4-3" data-bs-toggle="tab">SFTP
4">

-

+

-
54" >Copy to clipboard
54" >
cd ~/tikipack/$VERSION

+
34" >Copy to clipboard
34" >
cd ~/tikipack/$VERSION

-
Real example
Copy to clipboard
#since 15.0 :

-

- scp *bz2 *gz *zip *7z username,tikiwiki@frs.sourceforge.net:/home/pfs/project/t/ti/tikiwiki/Tiki_XX.x_Starname/XX.Y

-

+

-
6" >Copy to clipboard
6" >
User jsmith seeks to put tiki-12.1.* .7z .zip .tgz .bz2 to the 12.1 directory of his project, tikiwiki:

+
35" >Copy to clipboard
35" >
User jsmith seeks to put tiki-12.1.* .7z .zip .tgz .bz2 to the 12.1 directory of his project, tikiwiki:

+
1.4. After Release Steps

- ~~1.3. After Release Steps~~

1.3.1. Update lib/setup/twversion.class.php

change $this->version = '23.1'; to '23.2vcs';

+
_2">1.4.1. Update lib/setup/twversion.class.php_2" class="heading-link" aria-label="heading link">

change $this->version = '23.1'; to '23.2vcs';

-
57" >Copy to clipboard
57" >
[REL]Closing release 12.1beta

+
36" >Copy to clipboard
36" >
[REL]Closing release 12.1beta
>
>

-
1.3.2. Update show2.t.o info (Skipped until note is resolved)

+
1.4.2. Update show2.t.o info (Skipped until note is resolved)

-
1.3.2.1. checkout that version in the local cache folder of tiki in show2.t.o

+
1.4.2.1. checkout that version in the local cache folder of tiki in show2.t.o

-
1.3.2.2. tell tim to manage also that branch to update tiki from that version also

+
1.4.2.2. tell tim to manage also that branch to update tiki from that version also

-
58" >Copy to clipboard
58" >
BRANCHES="trunk 23.x 22.x 21.x 2
.x 19.x 18.x"

+
37" >Copy to clipboard
37" >
BRANCHES="trunk 23.x 22.x 21.x 2
.x 19.x 18.x"

-
1.3.2.3. make a tar.gz file from the new branch

+
1.4.2.3. make a tar.gz file from the new branch

-
59" >Copy to clipboard
59" >
cd /usr/local/src/tiki/

+
38" >Copy to clipboard
38" >
cd /usr/local/src/tiki/

-
1.3.2.4. update the field in tracker5 at dev.t.o to allow users to choose that version

+
1.4.2.4. update the field in tracker5 at dev.t.o to allow users to choose that version

How to Release requirements section

2026-08-01T21:29:36+00:00

+
Requirements
+
Unix shell environment, Linux or OSX suitable.
+
Git
+
PHP 7.x or 8.x CLI.
Note about php versions:
+
Use PHP 7.x for Tiki 25.x releases and lower
+
Use PHP 8.x for Tiki 26.x releases and upper.
+
+
+
PHP configuration must allow running external programs (like shell scripts)
+
Starting from Tiki 27.x and later versions release, Node.js and NPM are required for the JavasScript build system(for js and css compilation). Please check the required the versions in package.json at the root of the project in the "engines" property.
+
7za or 7z needed for creating 7zip archives. (may be installed in OSX through homebrew by typing brew install p7zip)
+
Plenty of disk space and memory 😉 - at least 64M of memory for php (in php.ini for php-cli)
+
The main packaging script is at doc/devtools/release.php but releasing a Tiki version is a lot more than just running the packaging script 😊

Release Steps

2026-08-01T21:27:35+00:00

+
Release Steps
+
1.1.1. Checkout Tiki
+
For this step we have 2 options, so you can use one of your choice but the first is recommended.
+
+
No Tabs
Option 1
Option 2

+
+
OPTION 1
Clone the branch you need to create the release for in a separate folder to separate it with your development instance by doing the following. Note that the bellow command is an example, so replace the branch value with that you want to work on, the reference repository by the path of your development instance to gain time when cloning and the target folder by that you want. Also remember to ensure that the reference repository is up to date and contains the required objects for successful cloning.
Copy to clipboard
git clone --branch=29.x --shared --reference=./tiki https://gitlab.com/tikiwiki/tiki.git tiki29release
+
+

+
+
OPTION 2
checkout the correct branch, i.e the branch you want to create the release for and make sure your origin is https://gitlab.com/tikiwiki/tiki.git. For example, if you want to create the 29.1 release, do
Copy to clipboard
git checkout 29.x

+
+
+
+
+
+
+
1.1.2. Setup.sh
+
Run:
+
+
Copy to clipboard
sh ./setup.sh
+
+
And choose 'b' option to install all necessary setup and exit (composer, npm, etc) instead of 'f', which is not needed for release.
+
+
+
1.1.3. Update lib/setup/twversion.class.php
+
Increment the version number and the star name in the constructor. The star name only needs to be updated if it is a major release (Eg. Tiki 29.0alpha) but this is usually done during branching, it's done during release if it was not done during branching.
+
Temporarily, remove the vcs from the branch number.
E.g
+
Copy to clipboard
function TWVersion()
+ {
+ $this->version = '22.1vcs';
+ $this->star = 'Corona Borealis'; Since we where to release 22.1, we need to remove the "vcs" from "22.1vcs", so this part will stay as:
+
Copy to clipboard
// Set everything else, including defaults.
+ $this->version = '22.1'; // needs to have no spaces for releases
+
Update list of valid releases in tikiVersions()
+
Make sure you add all Tiki versions (not just the one you are doing now). Ex.: when 5.0 is released, 4.2 will probably exist, as this was added to branches/4.x but not merged by script.
+
change the version branch to "unstable", "stable", or "trunk" as explained in that file
+
Update the star name in the list in the function tikiStars() if it's not yet done.
+
No Tabs
Pre-release
Releasing

+
Do not push your changes in pre-release test.
+
+
+
+

+
+
+
Commit your changes with this commit message (change \$VERSION by the version of the release):
+

Copy to clipboard
[REL] Preparing \$VERSION release
+
Then push your commit to https://github.com/tikiwiki/tiki.git in the corresponding branch (the branch you are doing the release for).
+
+
+
+
+
+
+
+
1.1.4. Run script
+
Go to the tiki instance pointing to the branch you want to release and run:
+
Display Basic Help
Copy to clipboard
php doc/devtools/release.php --help
to get the command help and see different options that can be used.
+
To Run the pre-release or release command:
+
+
+
No Tabs
Pre-release
Releasing

+
+
Create and test pre-release packages
+
This is done by executing the release script with the release version as argument, using the format major.minor preXYZ (XYZ can be RC1, RC2, alpha, beta1, beta2, etc.)
+
Use the --help option of the release script for advanced help on options (like using a web proxy)
+
+
E.g.
+
+
Copy to clipboard
php8.1 doc/devtools/release.php 29.0 preRC1 --devmode
+
+
+
Copy to clipboard
php8.1 doc/devtools/release.php 29.1 pre --devmode
+
Note: Use the command for the version of PHP which is the minimum spec for that branch. In this case we need PHP 7.4 for Tiki 24.x for instance
+
+

+
Note: Do not run this command first. Before running it, please start with the creation of pre-release packages as described in the first tab.
+
+
+
+
+
Copy to clipboard
php doc/devtools/release.php 26.1
+
(replace 26.1 with the corresponding release version)
+
+
+
Note: For Tiki 31 and later We don't need this anymore since Secdb got temporary disabled,
+
If the previous command fails at the secdb file creation step, you may need to run the release command providing your MySQL credentials for the script to successfully create the secdb file for you.
+
+
+
Unnecessary for Tiki31 and later
Copy to clipboard
php -d mysqli.default_host=HOST -d mysqli.default_user=USER -d mysqli.default_pw=PASS doc/devtools/release.php 28.2
(replace the version number with the corresponding release version)
+
or
+
+
Unnecessary for Tiki31 and later, use simplified command instead
Copy to clipboard
php -d mysqli.default_host=HOST -d mysqli.default_user=USER -d mysqli.default_pw=PASS doc/devtools/release.php 29.0 RC1
+
+
The release script has an interactive mode, enabled by default, that will ask you if you really want to do each step. It also asks for a confirmation before committing any changes. You can have a look at them with another shell by using this command:
+
+
Check for changes made by the release script before validating commits
Copy to clipboard
git status
+ git diff
+
+
Note: If you run the php command without specifying explitely the version as in the above commands, please make sure your CLI php version is set to the required one of the branch you are making the release for.
+
+
+
+
+
+
+
+
1.1.4.1. Check the generated README file
+
Note: For Tiki 30 and later, this step can be skipped. The README is no longer generated per release; the version from master (trunk) is shared across versions.
+
+
Check links/content in the generated README file
+
+
+
+
1.1.5. Test the produced "tarballs" and share the testing
+
+
Test on your server. Ideally, you have 1-2 other people trying on different servers. In case of a major version (x.0), you need at least 3 installations from 3 different people
+
+
Make sure to do a file integrity check with tiki-admin_security.php?check_files (Only applies on tiki 30 and lower)
+
There are 4 featured profiles in the installer and these are great tests.
+
One tester should test an upgrade (from previous to newer minor version and previous to newer major )
+
The other tester should test a fresh install
+
this can help you to make test: http://dev.tiki.org/Tiki-Test-Plan-for-new-site-admin
+
+
+
+
1.1.6. Upload tarballs to Sourceforge
+
When the "tarballs" are tested, the next step is to upload them to sourceforge. For that we have 3 options:
+
+
+
No Tabs
Web Interface
SCP
SFTP

+
+
Follow the steps to upload on SourceForge:
+
+
http://sourceforge.net/p/forge/documentation/Files/
+
+
+

+
To upload the 'tarballs', copy-paste and execute the following line (and change '$SF_LOGIN' by your SF.net login and $VERSION with the version, which may look like "7.0.rc1" ):
+
+
Copy to clipboard
cd ~/tikipack/$VERSION
+ scp *bz2 *gz *zip *7z $SF_LOGIN@frs.sourceforge.net:/home/pfs/project/t/ti/tikiwiki/$RELEASEFOLDER$
+
+

+
Alternatively, you can do it with sftp
+
+
Copy to clipboard
User jsmith seeks to put tiki-12.1.* .7z .zip .tgz .bz2 to the 12.1 directory of his project, tikiwiki:
+
+ $ sftp jsmith@frs.sourceforge.net
+ Connecting to frs.sourceforge.net...
+ jsmith,fooproject@frs.sourceforge.net's password:
+ sftp> cd /home/frs/project/tikiwiki/Tiki_12.x_Altair/
+ sftp> mkdir 12.1
+ sftp> cd 12.1
+ sftp> mput tiki*.*
+ Uploading tiki-12.1.7z to /home/pfs/project/tikiwiki/Tiki_12.x_Altair/12.1/tiki-12.1.7z
+ tiki-12.1.7z 100% 27MB 2.3MB/s 00:12
+ Uploading tiki-12.1.tar.bz2 to /home/pfs/project/tikiwiki/Tiki_12.x_Altair/12.1/tiki-12.1.tar.bz2
+ tiki-12.1.tar.bz2 100% 38MB 2.9MB/s 00:13
+ Uploading tiki-12.1.tar.gz to /home/pfs/project/tikiwiki/Tiki_12.x_Altair/12.1/tiki-12.1.tar.gz
+ tiki-12.1.tar.gz 100% 43MB 2.7MB/s 00:16
+ Uploading tiki-12.1.zip to /home/pfs/project/tikiwiki/Tiki_12.x_Altair/12.1/tiki-12.1.zip
+ tiki-12.1.zip 100% 52MB 2.9MB/s 00:18
+ sftp>
+
You need to have "release technician" status on SourceForge. Ask an Admin if you don't have it.
+
+
Update default download version on Sourceforge:
+
This needs to be done only if you are releasing a new major version or a minor version of the latest stable branch. To do so:
+
+
Go to the Files page while logged in to access the File Manager
+
From the File Manager navigate to the directory that contains the file
+
Select the "i" icon for the file you wish to set as the default download
+
On the bottom right check the boxes for the operating systems which you wish the file to be the default download for.
+
Select save
+
+
+
+
+
+
+
1.2. After Release Steps
+
+
+
1.2.1. Update lib/setup/twversion.class.php
+
change $this->version = '23.1'; to '23.2vcs';
+
+
Needs to have no spaces and use the format X.YabcZ see tikiVersions fn below for examples
+
+
+
You can add a commit message like this one:
+
+
Copy to clipboard
[REL]Closing release 12.1beta
+

Tiki Test Plan for new site admin

2026-07-31T13:07:56+00:00

Testing Checklist

2026-07-31T13:02:59+00:00

-
Save and verify the theme
+
Save and verify the theme in Unified Admin Backend Mode and Non-Unified Admin Backend

Tiki30

2026-07-29T18:21:17+00:00

-
6-link" class=> SOLVED list of release blockers added manually
6" class="wpfade-div-plain">
Reported by Details Status
@luci The UAB pref (theme_unified_admin_backend) is still optional (just added it to Endangered features; too late to remove the pref for 3
.x?) and when it gets disabled all the admin pages are broken/unusable (due to the sections refactoring) in master/3
.x Fix MRs: !1
622 and !1
719 Completed/Merged
@luci ~~After the latest fixes and due to the sections refactoring some admin/management pages fell off the UAB again~~ Fix MRs (same as above) Completed/Merged
@luci ~~Custom Modules regression~~ Completed/Merged
@luci ~~UAB needs to be perfectly usable (e.g., no transparent top bar on tiki-admin.php control panels!)~~ Completed/Merged
@bienvenu ushindi ~~Fix Too late to modify headers in templates~~
~~Too later to modify in calendar new module~~ Completed/Merged
@Jonny Bradley ~~Prevent output_headers() from throwing when service broker catches an error and output_headers() has already been attempted~~ Completed / Closed
@Gary Cunningham-Lee ~~revamp of the page header/navbar~~ Completed/Merged
@Gary Cunningham-Lee ~~Smartmenus are broken with an inner scroll inside dropdown menu~~ Completed/Merged

+
5-link" class=> SOLVED list of release blockers added manually
5" class="wpfade-div-plain">
Reported by Details Status
@luci The UAB pref (theme_unified_admin_backend) is still optional (just added it to Endangered features; too late to remove the pref for 3
.x?) and when it gets disabled all the admin pages are broken/unusable (due to the sections refactoring) in master/3
.x Fix MRs: !1
622 and !1
719 Completed/Merged
@luci ~~After the latest fixes and due to the sections refactoring some admin/management pages fell off the UAB again~~ Fix MRs (same as above) Completed/Merged
@luci ~~Custom Modules regression~~ Completed/Merged
@luci ~~UAB needs to be perfectly usable (e.g., no transparent top bar on tiki-admin.php control panels!)~~ Completed/Merged
@bienvenu ushindi ~~Fix Too late to modify headers in templates~~
~~Too later to modify in calendar new module~~ Completed/Merged
@Jonny Bradley ~~Prevent output_headers() from throwing when service broker catches an error and output_headers() has already been attempted~~ Completed / Closed
@Gary Cunningham-Lee ~~revamp of the page header/navbar~~ Completed/Merged
@Gary Cunningham-Lee ~~Smartmenus are broken with an inner scroll inside dropdown menu~~ Completed/Merged

-
4-div" class="table-responsive ts-wrapperdiv " >
4" class="table normal table-hover table-striped" data-count="32">
+
2-div" class="table-responsive ts-wrapperdiv " >

2" class="table normal table-hover table-striped" data-count="32">
-
Planned What Completed Note
Monday 2
26-
2-23 Slush
Monday 2
26-
3-
2 Freeze
Saturday 2
26-
3-14 Branching of 3
.x Monday 2
26-
3-16
Saturday 2
26-
3-16 Upgrade of https://themes.tiki.org
Tuesday 2
26-
3-17 Alpha Tue, Mar 31 2
26 A known Too late to modify headers error may occur in some modules(Quick adminbar, contributors, calendar_new). This is a known issue in 3
.
-alpha and will be fixed before the beta release.
Saturday 2
26-
3-21 Upgrade of https://doc.tiki.org Frid, Mar 27 2
26
Friday 2
26-
3-27 Upgrade of https://dev.tiki.org Thursday, April
9 2
26
Thursday 2
26-
4-
2 Beta Tuesday 2
26-
7-14
Monday 2
26-
4-
6 Upgrade of https://tiki.org Wednesday 2
26-
7-15
Saturday 2
26-
4-11 3
.
RC1
Saturday 2
26-
4-18 Release of Tiki 3
.

Monday 2
26-
6-15 (approx) Release of 3
.1 - -
+
Planned What Completed Note
Monday 2
26-
2-23 Slush
Monday 2
26-
3-
2 Freeze
Saturday 2
26-
3-14 Branching of 3
.x Monday 2
26-
3-16
Saturday 2
26-
3-16 Upgrade of https://themes.tiki.org
Tuesday 2
26-
3-17 Alpha Tue, Mar 31 2
26 A known Too late to modify headers error may occur in some modules(Quick adminbar, contributors, calendar_new). This is a known issue in 3
.
-alpha and will be fixed before the beta release.
Saturday 2
26-
3-21 Upgrade of https://doc.tiki.org Frid, Mar 27 2
26
Friday 2
26-
3-27 Upgrade of https://dev.tiki.org Thursday, April
9 2
26
Thursday 2
26-
4-
2 Beta Tuesday 2
26-
7-14
Monday 2
26-
4-
6 Upgrade of https://tiki.org Wednesday 2
26-
7-15
Saturday 2
26-
4-11 3
.
RC1 Wednesday 2
26-
7-22
Saturday 2
26-
4-18 Release of Tiki 3
.
Sunday 2
26-
7-26
Monday 2
26-
6-15 (approx) Release of 3
.1 - -

MenuPageBanner

2026-07-26T11:04:12+00:00

+
+
+
+
+ id="community-promotion-carousel"
+ class="carousel slide mb-3"
+ data-bs-ride="carousel"
+ data-bs-interval="8000"
+ data-bs-pause="hover"
+ role="region"
+ aria-roledescription="carousel"
+ aria-label="Upcoming event and EvoluData promotion"
+ >
+
+
+ id="calendar-event-slide"
+ class="carousel-item active"
+ role="group"
+ aria-roledescription="slide"
+ aria-label="1 of 2"
+ >
+
+
+
-
+ >

id="evoludata-promotion-slide"
class="carousel-item"
role="group"
aria-roledescription="slide"
aria-label="2 of 2"
>
id="evoludata-promotion-panel"
class="alert alert-light bg-white border overflow-hidden d-flex align-items-center"
aria-labelledby="evoludata-promotion-title"
>

id="evoludata-promotion-logo"
href="https://evoludata.com/?utm_source=dev-tiki&utm_medium=carousel&utm_campaign=open-source-sites"
target="_blank"
rel="noopener noreferrer"
class="d-flex align-items-center justify-content-center rounded bg-light"
aria-label="Visit EvoluData"
>
src="https://evoludata.com/display22"
alt="EvoluData"
width="11
"
height="1

"
decoding="async"
>

id="evoludata-promotion-copy"
class="flex-grow-1 text-start"
>
id="evoludata-promotion-title"
class="text-primary fw-bold"
>
Open Source solutions

Custom development, consulting, and reliable support for critical Open Source platforms

id="evoludata-promotion-products"
class="fw-semibold"
>
TikiWiki · Cypht · Dolibarr

id="evoludata-promotion-actions"
class="d-flex flex-wrap gap-2"
>
class="btn btn-primary"
href="https://evoludata.com/en/Solutions?utm_source=dev-tiki&utm_medium=carousel&utm_campaign=open-source-sites&utm_content=solutions"
target="_blank"
rel="noopener noreferrer"
>
Explore our solutions

class="btn btn-outline-primary"
href="https://evoludata.com/en/Contact-Us?utm_source=dev-tiki&utm_medium=carousel&utm_campaign=open-source-sites&utm_content=contact"
target="_blank"
rel="noopener noreferrer"
>
Contact us

class="carousel-control-prev"
type="button"
data-bs-target="#community-promotion-carousel"
data-bs-slide="prev"
aria-label="Previous slide"
>
class="carousel-control-prev-icon"
aria-hidden="true"
>

class="carousel-control-next"
type="button"
data-bs-target="#community-promotion-carousel"
data-bs-slide="next"
aria-label="Next slide"
>
class="carousel-control-next-icon"
aria-hidden="true"
>

>

Tiki-End-to-End-Testing

2026-07-23T13:19:51+00:00

-
Table of contents
+
Table of contents
>
End-to-End Tests
Prerequisites
First-time setup
Environment variables
Test users
Automatic environment seeding
Running the tests
Interactive and debug modes
Viewing the HTML report
Overriding the reporter
Directory structure
Adding a new test domain
Fixtures
Test suites
shared-secrets/: Shared Secrets and Tracker Encryption
wiki-pages/: Wiki Page Management
smoke/: Framework and Environment Smoke Tests
Self-Contained Mode
CI integration
Accessing the HTML report artifact
Troubleshooting
Related pages
>
-
89" >Copy to clipboard
89" >
tests/e2e/bin/e2e-setup.sh # setup + smoke run
+
76" >Copy to clipboard
76" >
tests/e2e/bin/e2e-setup.sh # setup + smoke run
-
9
" >Copy to clipboard
9
" >
npm install # @playwright/test is a root devDependency
+
77" >Copy to clipboard
77" >
npm install # @playwright/test is a root devDependency
-
91" >Copy to clipboard
91" >
cp tests/e2e/.env.template tests/e2e/.env
+
78" >Copy to clipboard
78" >
cp tests/e2e/.env.template tests/e2e/.env
-
Variable Default Purpose
-+TIKI_BASE_URL+- -+http://localhost+- Base URL of your Tiki instance
-+TIKI_FIXTURE_CMD+- auto-detected PHP invocation prefix for fixture scripts
-+TIKI_ADMIN_USER+- -+admin+- Admin username for tests requiring admin access
-+TIKI_ADMIN_PASS+- -+admin1234+- Admin password
-+TIKI_TEST_USER+- -+Test1+- Registered non-admin username for permission tests
-+TIKI_TEST_PASS+- -+test1pass+- Registered user password
-+TIKI_E2E_WEBSERVER+- unset Set to 1 for self-contained mode: serve this checkout via php -S
-+TIKI_E2E_PORT+- -+8686+- Port for the built-in web server in self-contained mode
-+TIKI_E2E_DB_*+- -+tiki_e2e+- on 127. . .1 Dedicated test DB host, name, user and password (self-contained mode)
+
Variable Default Purpose
TIKI_BASE_URL http://localhost Base URL of your Tiki instance
TIKI_FIXTURE_CMD auto-detected PHP invocation prefix for fixture scripts
TIKI_ADMIN_USER admin Admin username for tests requiring admin access
TIKI_ADMIN_PASS admin1234 Admin password
TIKI_TEST_USER Test1 Registered non-admin username for permission tests
TIKI_TEST_PASS test1pass Registered user password
TIKI_E2E_WEBSERVER unset Set to 1 for self-contained mode: serve this checkout via php -S
TIKI_E2E_PORT 8686 Port for the built-in web server in self-contained mode
TIKI_E2E_DB_* tiki_e2e on 127. . .1 Dedicated test DB host, name, user and password (self-contained mode)
-
User Password Role
Test1 -+test1pass+- Registered, primary tester
Test2 -+test2pass+- Registered, secondary
admin -+admin1234+- Administrator
+
User Password Role
Test1 test1pass Registered, primary tester
Test2 test2pass Registered, secondary
admin admin1234 Administrator
-
2" >Copy to clipboard
2" >
php tests/e2e/fixtures/create_test_users.php
+
79" >Copy to clipboard
79" >
php tests/e2e/fixtures/create_test_users.php
-
Adapt the PHP invocation to your environment ~~(-+~~ddev exec php+-, docker exec, plain php).
+
Adapt the PHP invocation to your environment: ddev exec php, docker exec, or plain php.
-
enable_encryption.php persists the User Encryption security fe~~atu~~re ~~(-+~~feature_user_encryption='y'~~+-)~~ in the database.
+
enable_encryption.php persists the User Encryption security preference feature_user_encryption='y' in the database.
-
93" >Copy to clipboard
93" >
npm run test:e2e # all suites
+
8
" >Copy to clipboard
8
" >
npm run test:e2e # all suites
-
94" >Copy to clipboard
94" >
cd tests/e2e
+
81" >Copy to clipboard
81" >
cd tests/e2e
-
95" >Copy to clipboard
95" >
# Open Playwright UI: browse, filter, and re-run tests interactively
+
82" >Copy to clipboard
82" >
# Open Playwright UI: browse, filter, and re-run tests interactively
-
96" >Copy to clipboard
96" >
cd tests/e2e
+
83" >Copy to clipboard
83" >
cd tests/e2e
-
97" >Copy to clipboard
97" >
npx playwright test --reporter=list # terminal only
+
84" >Copy to clipboard
84" >
npx playwright test --reporter=list # terminal only
-
98" >Copy to clipboard
98" >
tests/e2e/
+
5" >Copy to clipboard
5" >
tests/e2e/
-
99" >Copy to clipboard
99" >
import { useSuiteFixtures } from "../../common/fixtures";
+
86" >Copy to clipboard
86" >
import { useSuiteFixtures } from "../../common/fixtures";
-
Script Used by Purpose
-+create_test_users.php+- Global setup Ensure Test1/Test2 exist with known passwords
-+enable_encryption.php+- Global setup Persist feature_user_encryption='y' in the DB, idempotent
-+clean_baseline.php+- Maintenance Wipe all TC-prefixed keys and trackers from the DB, for recovery after a killed run in existing-instance mode
-+provision_admin.php+- Provisioning Set admin password and pass_confirm on a fresh install, called by e2e-provision.sh
-+provision_defaults.php+- Provisioning Test-friendly prefs on a fresh install, for example no admin wizard, called by e2e-provision.sh
-+shared-secrets/tc
4_setup.php+- shared-secrets Create tracker, encrypted field and key
-+shared-secrets/tc
4_teardown.php+- shared-secrets Remove TC-
4 tracker and key
-+shared-secrets/tc
6_setup.php+- shared-secrets Create tracker and key, return Test1 share string
-+shared-secrets/tc
6_teardown.php+- shared-secrets Remove TC-
6 tracker and key
-+shared-secrets/tc1
_setup.php+- shared-secrets Create tracker and key with share string
-+shared-secrets/tc1
_teardown.php+- shared-secrets Remove TC-1
tracker and key
-+shared-secrets/tc11_setup.php+- shared-secrets Create key for the regeneration test
-+shared-secrets/tc11_teardown.php+- shared-secrets Remove TC-11 key
+
Script Used by Purpose
create_test_users.php Global setup Ensure Test1/Test2 exist with known passwords
enable_encryption.php Global setup Persist feature_user_encryption='y' in the DB, idempotent
clean_baseline.php Maintenance Wipe all TC-prefixed keys and trackers from the DB, for recovery after a killed run in existing-instance mode
provision_admin.php Provisioning Set admin password and pass_confirm on a fresh install, called by e2e-provision.sh
provision_defaults.php Provisioning Test-friendly prefs on a fresh install, for example no admin wizard, called by e2e-provision.sh
shared-secrets/tc 4_setup.php shared-secrets Create tracker, encrypted field and key
shared-secrets/tc 4_teardown.php shared-secrets Remove TC-
4 tracker and key
shared-secrets/tc 6_setup.php shared-secrets Create tracker and key, return Test1 share string
shared-secrets/tc 6_teardown.php shared-secrets Remove TC-
6 tracker and key
shared-secrets/tc1 _setup.php shared-secrets Create tracker and key with share string
shared-secrets/tc1 _teardown.php shared-secrets Remove TC-1
tracker and key
shared-secrets/tc11_setup.php shared-secrets Create key for the regeneration test
shared-secrets/tc11_teardown.php shared-secrets Remove TC-11 key
-
File Coverage
-+tc
1-encryption-tab.spec.ts+- Encryption tab visible and accessible
-+tc
2-create-key.spec.ts+- Key creation with one shared user
-+tc
3-create-key-with-users.spec.ts+- Key creation with shared users
-+tc
4-tracker-field-encryption.spec.ts+- Write and read an encrypted tracker field
-+tc
5-edit-key.spec.ts+- Edit key metadata: rename, description, duplicate guard
-+tc
6-unlock-flow.spec.ts+- Encrypted field unlock flow: share entry, session unlock
-+tc
7-delete-key.spec.ts+- Key deletion flow
-+tc
8-security.spec.ts+- Unauthorized access is blocked
-+tc
9-algorithm.spec.ts+- Algorithm dropdown, absent on 27.x and future-proofed
-+tc1
-manual-key-entry.spec.ts+- Manual share entry via the UI modal
-+tc11-key-regeneration.spec.ts+- Key regeneration flow
+
File Coverage
tc 1-encryption-tab.spec.ts Encryption tab visible and accessible
tc 2-create-key.spec.ts Key creation with one shared user
tc 3-create-key-with-users.spec.ts Key creation with shared users
tc 4-tracker-field-encryption.spec.ts Write and read an encrypted tracker field
tc 5-edit-key.spec.ts Edit key metadata: rename, description, duplicate guard
tc 6-unlock-flow.spec.ts Encrypted field unlock flow: share entry, session unlock
tc 7-delete-key.spec.ts Key deletion flow
tc 8-security.spec.ts Unauthorized access is blocked
tc 9-algorithm.spec.ts Algorithm dropdown, absent on 27.x and future-proofed
tc1 -manual-key-entry.spec.ts Manual share entry via the UI modal
tc11-key-regeneration.spec.ts Key regeneration flow
-
File Coverage
-+tc
1-page-lifecycle.spec.ts+- Create, view content and delete a wiki page
-+tc
2-page-access.spec.ts+- Page listing accessible, nonexistent page prompts creation
+
File Coverage
tc 1-page-lifecycle.spec.ts Create, view content and delete a wiki page
tc 2-page-access.spec.ts Page listing accessible, nonexistent page prompts creation
-
File Needs live Tiki Coverage
-+tc

-subpath-routing.spec.ts+- no -+page.goto+- subpath prefixing: prepends BASE_PATH to leading-slash URLs, leaves absolute and relative paths untouched
-+tc
1-environment.spec.ts+- yes Environment readiness: instance reachable, admin credentials log in, User Encryption feature enabled
+
File Needs live Tiki Coverage
tc -subpath-routing.spec.ts no page.goto subpath prefixing: prepends BASE_PATH to leading-slash URLs, leaves absolute and relative paths untouched
tc 1-environment.spec.ts yes Environment readiness: instance reachable, admin credentials log in, User Encryption feature enabled
-
1

" >Copy to clipboard
1

" >
# 1. Provision once (writes db/local.php, installs the schema, sets the admin password).
+
87" >Copy to clipboard
87" >
# 1. Provision once (writes db/local.php, installs the schema, sets the admin password).
-
Job Runs
-+e2e-all+- Every suite under suites/
-+e2e-suite: ~~" rel="">sm~~oke>+- Framework and environment smoke checks
-+e2e-suite: ~~" rel="">share~~d-se~~crets~~>+- The Shared Secrets domain
-+e2e-suite: wiki-pagesa>+- The wiki-pages domain
+
Job Runs
e2e-all Every suite under suites/
e2e-suite: [smoke]ode> Framework and environment smoke checks
e2e-suite: [shared-secrets]de> The Shared Secrets domain
e2e-suite: [wiki-pages]code> The wiki-pages domain
-
1
1" >Copy to clipboard
1
1" >
https://gitlab.com/tikiwiki/tiki/-/jobs/<job-id>/artifacts/file/tests/e2e/playwright-report/index.html
+
88" >Copy to clipboard
88" >
https://gitlab.com/tikiwiki/tiki/-/jobs/<job-id>/artifacts/file/tests/e2e/playwright-report/index.html
-
Symptom Likely cause and fix
Global setup warns that fixtures could not run -+TIKI_FIXTURE_CMD+- does not match your environment. Set it to php, ddev exec php, or your Docker equivalent.
A spec file is skipped with a fixture warning Its tcNN_setup.php failed. Run the script manually from the Tiki root to see the PHP error.
Tabs or modals time out The frontend bundles are missing. Run npm run build so public/generated/ exists, otherwise Bootstrap JS never loads.
Key creation fails with a math error -+bcmath+- is not installed. The Shamir secret-sharing library behind shared secrets requires it.
Leftover TC-prefixed keys or trackers after a killed run Run php tests/e2e/fixtures/clean_baseline.php from the Tiki root, in existing-instance mode only.
-+e2e-provision.sh+- refuses to run A db/local.php already exists. Use a fresh checkout or worktree, or pass --force to reset.
+
Symptom Likely cause and fix
Global setup warns that fixtures could not run TIKI_FIXTURE_CMD does not match your environment. Set it to php, ddev exec php, or your Docker equivalent.
A spec file is skipped with a fixture warning Its tcNN_setup.php failed. Run the script manually from the Tiki root to see the PHP error.
Tabs or modals time out The frontend bundles are missing. Run npm run build so public/generated/ exists, otherwise Bootstrap JS never loads.
Key creation fails with a math error bcmath is not installed. The Shamir secret-sharing library behind shared secrets requires it.
Leftover TC-prefixed keys or trackers after a killed run Run php tests/e2e/fixtures/clean_baseline.php from the Tiki root, in existing-instance mode only.
e2e-provision.sh refuses to run A db/local.php already exists. Use a fresh checkout or worktree, or pass --force to reset.

Reported by	Details	Status
@luci	The UAB pref (theme_unified_admin_backend) is still optional (just added it to Endangered features; too late to remove the pref for 3 .x?) and when it gets disabled all the admin pages are broken/unusable (due to the sections refactoring) in master/3 .x Fix MRs: !1 622 and !1 719	Completed/Merged
@luci	~~After the latest fixes and due to the sections refactoring some admin/management pages fell off the UAB again~~ Fix MRs (same as above)	Completed/Merged
@luci	~~Custom Modules regression~~	Completed/Merged
@luci	~~UAB needs to be perfectly usable (e.g., no transparent top bar on tiki-admin.php control panels!)~~	Completed/Merged
@bienvenu ushindi	~~Fix Too late to modify headers in templates~~ ~~Too later to modify in calendar new module~~	Completed/Merged
@Jonny Bradley	~~Prevent output_headers() from throwing when service broker catches an error and output_headers() has already been attempted~~	Completed / Closed
@Gary Cunningham-Lee	~~revamp of the page header/navbar~~	Completed/Merged
@Gary Cunningham-Lee	~~Smartmenus are broken with an inner scroll inside dropdown menu~~	Completed/Merged

Planned	What	Completed	Note
Monday 2 26- 2-23	Slush
Monday 2 26- 3- 2	Freeze
Saturday 2 26- 3-14	Branching of 3 .x	Monday 2 26- 3-16
Saturday 2 26- 3-16	Upgrade of https://themes.tiki.org
Tuesday 2 26- 3-17	Alpha	Tue, Mar 31 2 26	A known Too late to modify headers error may occur in some modules(Quick adminbar, contributors, calendar_new). This is a known issue in 3 . -alpha and will be fixed before the beta release.
Saturday 2 26- 3-21	Upgrade of https://doc.tiki.org	Frid, Mar 27 2 26
Friday 2 26- 3-27	Upgrade of https://dev.tiki.org	Thursday, April 9 2 26
Thursday 2 26- 4- 2	Beta	Tuesday 2 26- 7-14
Monday 2 26- 4- 6	Upgrade of https://tiki.org	Wednesday 2 26- 7-15
Saturday 2 26- 4-11	3 . RC1
Saturday 2 26- 4-18	Release of Tiki 3 .
Monday 2 26- 6-15 (approx)	Release of 3 .1	-	-

Variable	Default	Purpose
-+TIKI_BASE_URL+-	-+http://localhost+-	Base URL of your Tiki instance
-+TIKI_FIXTURE_CMD+-	auto-detected	PHP invocation prefix for fixture scripts
-+TIKI_ADMIN_USER+-	-+admin+-	Admin username for tests requiring admin access
-+TIKI_ADMIN_PASS+-	-+admin1234+-	Admin password
-+TIKI_TEST_USER+-	-+Test1+-	Registered non-admin username for permission tests
-+TIKI_TEST_PASS+-	-+test1pass+-	Registered user password
-+TIKI_E2E_WEBSERVER+-	unset	Set to `1` for self-contained mode: serve this checkout via `php -S`
-+TIKI_E2E_PORT+-	-+8686+-	Port for the built-in web server in self-contained mode
-+TIKI_E2E_DB_*+-	-+tiki_e2e+- on `127. . .1`	Dedicated test DB host, name, user and password (self-contained mode)

User	Password	Role
Test1	-+test1pass+-	Registered, primary tester
Test2	-+test2pass+-	Registered, secondary
admin	-+admin1234+-	Administrator

Script	Used by	Purpose
-+create_test_users.php+-	Global setup	Ensure Test1/Test2 exist with known passwords
-+enable_encryption.php+-	Global setup	Persist `feature_user_encryption='y'` in the DB, idempotent
-+clean_baseline.php+-	Maintenance	Wipe all TC-prefixed keys and trackers from the DB, for recovery after a killed run in existing-instance mode
-+provision_admin.php+-	Provisioning	Set admin password and `pass_confirm` on a fresh install, called by `e2e-provision.sh`
-+provision_defaults.php+-	Provisioning	Test-friendly prefs on a fresh install, for example no admin wizard, called by `e2e-provision.sh`
-+shared-secrets/tc 4_setup.php+-	shared-secrets	Create tracker, encrypted field and key
-+shared-secrets/tc 4_teardown.php+-	shared-secrets	Remove TC- 4 tracker and key
-+shared-secrets/tc 6_setup.php+-	shared-secrets	Create tracker and key, return Test1 share string
-+shared-secrets/tc 6_teardown.php+-	shared-secrets	Remove TC- 6 tracker and key
-+shared-secrets/tc1 _setup.php+-	shared-secrets	Create tracker and key with share string
-+shared-secrets/tc1 _teardown.php+-	shared-secrets	Remove TC-1 tracker and key
-+shared-secrets/tc11_setup.php+-	shared-secrets	Create key for the regeneration test
-+shared-secrets/tc11_teardown.php+-	shared-secrets	Remove TC-11 key

File	Coverage
-+tc 1-encryption-tab.spec.ts+-	Encryption tab visible and accessible
-+tc 2-create-key.spec.ts+-	Key creation with one shared user
-+tc 3-create-key-with-users.spec.ts+-	Key creation with shared users
-+tc 4-tracker-field-encryption.spec.ts+-	Write and read an encrypted tracker field
-+tc 5-edit-key.spec.ts+-	Edit key metadata: rename, description, duplicate guard
-+tc 6-unlock-flow.spec.ts+-	Encrypted field unlock flow: share entry, session unlock
-+tc 7-delete-key.spec.ts+-	Key deletion flow
-+tc 8-security.spec.ts+-	Unauthorized access is blocked
-+tc 9-algorithm.spec.ts+-	Algorithm dropdown, absent on 27.x and future-proofed
-+tc1 -manual-key-entry.spec.ts+-	Manual share entry via the UI modal
-+tc11-key-regeneration.spec.ts+-	Key regeneration flow

File	Coverage
`tc 1-encryption-tab.spec.ts`	Encryption tab visible and accessible
`tc 2-create-key.spec.ts`	Key creation with one shared user
`tc 3-create-key-with-users.spec.ts`	Key creation with shared users
`tc 4-tracker-field-encryption.spec.ts`	Write and read an encrypted tracker field
`tc 5-edit-key.spec.ts`	Edit key metadata: rename, description, duplicate guard
`tc 6-unlock-flow.spec.ts`	Encrypted field unlock flow: share entry, session unlock
`tc 7-delete-key.spec.ts`	Key deletion flow
`tc 8-security.spec.ts`	Unauthorized access is blocked
`tc 9-algorithm.spec.ts`	Algorithm dropdown, absent on 27.x and future-proofed
`tc1 -manual-key-entry.spec.ts`	Manual share entry via the UI modal
`tc11-key-regeneration.spec.ts`	Key regeneration flow

File	Coverage
-+tc 1-page-lifecycle.spec.ts+-	Create, view content and delete a wiki page
-+tc 2-page-access.spec.ts+-	Page listing accessible, nonexistent page prompts creation

File	Coverage
`tc 1-page-lifecycle.spec.ts`	Create, view content and delete a wiki page
`tc 2-page-access.spec.ts`	Page listing accessible, nonexistent page prompts creation

File	Needs live Tiki	Coverage
-+tc -subpath-routing.spec.ts+-	no	-+page.goto+- subpath prefixing: prepends `BASE_PATH` to leading-slash URLs, leaves absolute and relative paths untouched
-+tc 1-environment.spec.ts+-	yes	Environment readiness: instance reachable, admin credentials log in, User Encryption feature enabled

Job	Runs
-+e2e-all+-	Every suite under `suites/`
-+e2e-suite: ~~" rel="">sm~~oke>+-	Framework and environment smoke checks
-+e2e-suite: ~~" rel="">share~~d-se~~crets~~>+-	The Shared Secrets domain
-+e2e-suite: wiki-pagesa>+-	The wiki-pages domain

Job	Runs
`e2e-all`	Every suite under `suites/`
`e2e-suite: [smoke]ode>`	Framework and environment smoke checks
`e2e-suite: [shared-secrets]de>`	The Shared Secrets domain
`e2e-suite: [wiki-pages]code>`	The wiki-pages domain

Symptom	Likely cause and fix
Global setup warns that fixtures could not run	-+TIKI_FIXTURE_CMD+- does not match your environment. Set it to `php`, `ddev exec php`, or your Docker equivalent.
A spec file is skipped with a fixture warning	Its `tcNN_setup.php` failed. Run the script manually from the Tiki root to see the PHP error.
Tabs or modals time out	The frontend bundles are missing. Run `npm run build` so `public/generated/` exists, otherwise Bootstrap JS never loads.
Key creation fails with a math error	-+bcmath+- is not installed. The Shamir secret-sharing library behind shared secrets requires it.
Leftover TC-prefixed keys or trackers after a killed run	Run `php tests/e2e/fixtures/clean_baseline.php` from the Tiki root, in existing-instance mode only.
-+e2e-provision.sh+- refuses to run	A `db/local.php` already exists. Use a fresh checkout or worktree, or pass `--force` to reset.

Tiki RSS feed for the wiki pages

Creating or maintaining translations

Endangered features

1.2. Release Steps

1.3. Release Steps2>1.3.1. Checkout Tiki

1.3.1. Checkout Tiki

1.2.2. Setup.sh

1.3.2. Setup.sh

_before_the_release">1.2.3. Update lib/setup/twversion.class.php before the release_before_the_release" class="heading-link" aria-label="heading link">

1.3.3. Update lib/setup/twversion.class.php

1.3.4. Run script

1.2.5. Create and test pre-release packages

Create and test pre-release packages

1.2.7. Test the produced "tarballs" and share the testing

1.3.5. Test the produced "tarballs" and share the testing

1.2.8. Upload tarballs to Sourceforge

1.3.6. Upload tarballs to Sourceforge

1.4. After Release Steps

1.3. After Release Steps

1.3.1. Update lib/setup/twversion.class.php

_2">1.4.1. Update lib/setup/twversion.class.php_2" class="heading-link" aria-label="heading link">

1.3.2. Update show2.t.o info (Skipped until note is resolved)

1.4.2. Update show2.t.o info (Skipped until note is resolved)

1.3.2.1. checkout that version in the local cache folder of tiki in show2.t.o

1.4.2.1. checkout that version in the local cache folder of tiki in show2.t.o

1.3.2.2. tell tim to manage also that branch to update tiki from that version also

1.4.2.2. tell tim to manage also that branch to update tiki from that version also

1.3.2.3. make a tar.gz file from the new branch

1.4.2.3. make a tar.gz file from the new branch

1.3.2.4. update the field in tracker5 at dev.t.o to allow users to choose that version

1.4.2.4. update the field in tracker5 at dev.t.o to allow users to choose that version

How to Release requirements section

Requirements

Release Steps

Release Steps

1.1.1. Checkout Tiki

1.1.2. Setup.sh

1.1.3. Update lib/setup/twversion.class.php

1.1.4. Run script

Create and test pre-release packages

1.1.4.1. Check the generated README file

1.1.5. Test the produced "tarballs" and share the testing

1.1.6. Upload tarballs to Sourceforge

Update default download version on Sourceforge:

1.2. After Release Steps

1.2.1. Update lib/setup/twversion.class.php

Tiki Test Plan for new site admin

Testing Checklist

Tiki30

MenuPageBanner

Tiki-End-to-End-Testing

Table of contents

Table of contents

1.3. Release Steps2>
1.3.1. Checkout Tiki