Tiki RSS feed for the wiki pages

Where to commit

2026-08-25T21:17:13+00:00

-
2-div" class="table-responsive ts-wrapperdiv "> 2">

Name Currently this is git branch What is allowed in this branch Before commiting here, first commit to

Dev master (trunk) (future 31x) Functional [ENH]ancements and new features
[FIX]es and [TRA]nslations
Most development (new features) happens here
This is the place for [REF]actoring or cosmetic changes.
Features must be functional but don’t have to be fully complete.
In theory, should be releasable at any time. Also: 2-link" href="javascript:void(
)" class="plugin-mouseover-anchor">Update language strings2" class="plugin-mouseover" style="display: none; position: absolute; width: 4

px; height: 2

px; pointer-events: none;">If you must change the English version (but are not changing the meaning and so the translations are still valid, please use mass spelling correction. If you can't use that, just add to pending text corrections.. If you commit to master, and after you want to commit to a stable branch, please see how to git cherry-pick. This is the first place to propose a merge request (MR)

Next Stable (branched, unreleased) m/tikiwiki/tiki/-/tree/3
.x" rel="extern~~al">branch~~es/3
.x ~~src="img/icons/green_question.png" alt="Question" width="16" height="16" name="link-external" title="Question" class="icon" />~~ Exists only between the time Dev has been branched into the next stable, and the next stable .
release has been released. Bug fixes and Translations only Dev

Current Stable (released) 29.x" rel="external">branches/29.x Bug fixes and minor safe enhancements Dev, Next Stable (if any)

Previous Stable None Exists only until .1 release of Current Stable has been released. Then EoL or becomes the Previous Stable LTS Dev, Current Stable

Previous Stable LTS branches/27.x Minor safe enhancements, fixes and translations backported from Current Stable or Next Stable Dev, Current Stable or Next Stable

Security fixes only LTS (previous LTS) branches/24.x Security fixes only Dev, Current Stable or Next Stable, Previous Stable LTS

Name	Currently this is git branch	What is allowed in this branch	Before commiting here, first commit to
Dev	master (trunk) (future 31x)	Functional [ENH]ancements and new features [FIX]es and [TRA]nslations Most development (new features) happens here This is the place for [REF]actoring or cosmetic changes. Features must be functional but don’t have to be fully complete. In theory, should be releasable at any time. Also: 2-link" href="javascript:void( )" class="plugin-mouseover-anchor">Update language strings2" class="plugin-mouseover" style="display: none; position: absolute; width: 4 px; height: 2 px; pointer-events: none;">If you must change the English version (but are not changing the meaning and so the translations are still valid, please use mass spelling correction. If you can't use that, just add to pending text corrections.. If you commit to master, and after you want to commit to a stable branch, please see how to git cherry-pick.	This is the first place to propose a merge request (MR)
Next Stable (branched, unreleased)	m/tikiwiki/tiki/-/tree/3 .x" rel="extern~~al">branch~~es/3 .x ~~src="img/icons/green_question.png" alt="Question" width="16" height="16" name="link-external" title="Question" class="icon" />~~	Exists only between the time Dev has been branched into the next stable, and the next stable . release has been released. Bug fixes and Translations only	Dev
Current Stable (released)	29.x" rel="external">branches/29.x	Bug fixes and minor safe enhancements	Dev, Next Stable (if any)
Previous Stable	None	Exists only until .1 release of Current Stable has been released. Then EoL or becomes the Previous Stable LTS	Dev, Current Stable
Previous Stable LTS	branches/27.x	Minor safe enhancements, fixes and translations backported from Current Stable or Next Stable	Dev, Current Stable or Next Stable
Security fixes only LTS (previous LTS)	branches/24.x	Security fixes only	Dev, Current Stable or Next Stable, Previous Stable LTS

+
1-div" class="table-responsive ts-wrapperdiv "> 1">

Name Currently this is git branch What is allowed in this branch Before commiting here, first commit to

Dev master (trunk) (future 31x) Functional [ENH]ancements and new features
[FIX]es and [TRA]nslations
Most development (new features) happens here
This is the place for [REF]actoring or cosmetic changes.
Features must be functional but don’t have to be fully complete.
In theory, should be releasable at any time. Also: 1-link" href="javascript:void(
)" class="plugin-mouseover-anchor">Update language strings1" class="plugin-mouseover" style="display: none; position: absolute; width: 4

px; height: 2

px; pointer-events: none;">If you must change the English version (but are not changing the meaning and so the translations are still valid, please use mass spelling correction. If you can't use that, just add to pending text corrections.. If you commit to master, and after you want to commit to a stable branch, please see how to git cherry-pick. This is the first place to propose a merge request (MR)

Next Stable (branched, unreleased) None Exists only between the time Dev has been branched into the next stable, and the next stable .
release has been released. Bug fixes and Translations only Dev

Current Stable (released) 3
.x" rel="external">branches/3
.x Bug fixes and minor safe enhancements Dev, Next Stable (if any)

Previous Stable None Exists only until .1 release of Current Stable has been released. Then EoL or becomes the Previous Stable LTS Dev, Current Stable

Previous Stable LTS branches/27.x Minor safe enhancements, fixes and translations backported from Current Stable or Next Stable Dev, Current Stable or Next Stable

Security fixes only LTS (previous LTS) branches/24.x Security fixes only Dev, Current Stable or Next Stable, Previous Stable LTS

Name	Currently this is git branch	What is allowed in this branch	Before commiting here, first commit to
Dev	master (trunk) (future 31x)	Functional [ENH]ancements and new features [FIX]es and [TRA]nslations Most development (new features) happens here This is the place for [REF]actoring or cosmetic changes. Features must be functional but don’t have to be fully complete. In theory, should be releasable at any time. Also: 1-link" href="javascript:void( )" class="plugin-mouseover-anchor">Update language strings1" class="plugin-mouseover" style="display: none; position: absolute; width: 4 px; height: 2 px; pointer-events: none;">If you must change the English version (but are not changing the meaning and so the translations are still valid, please use mass spelling correction. If you can't use that, just add to pending text corrections.. If you commit to master, and after you want to commit to a stable branch, please see how to git cherry-pick.	This is the first place to propose a merge request (MR)
Next Stable (branched, unreleased)	None	Exists only between the time Dev has been branched into the next stable, and the next stable . release has been released. Bug fixes and Translations only	Dev
Current Stable (released)	3 .x" rel="external">branches/3 .x	Bug fixes and minor safe enhancements	Dev, Next Stable (if any)
Previous Stable	None	Exists only until .1 release of Current Stable has been released. Then EoL or becomes the Previous Stable LTS	Dev, Current Stable
Previous Stable LTS	branches/27.x	Minor safe enhancements, fixes and translations backported from Current Stable or Next Stable	Dev, Current Stable or Next Stable
Security fixes only LTS (previous LTS)	branches/24.x	Security fixes only	Dev, Current Stable or Next Stable, Previous Stable LTS

Major Features Missing In Tiki

2026-08-25T20:54:51+00:00

-
2
24-12 : What's new in Tiki 28.
~~LTS?~~
2
25-
9 : What's new in Tiki 29.
~~LTS?~~

+
2
24-12 : What's new in Tiki 28.

2
25-
9 : What's new in Tiki 29.

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

1" class="table normal table-hover table-striped" data-count="11">

Daily Build

2026-08-25T20:49:07+00:00

-
Content
+
Content
>
Current
Future
End of life>
-
-
-
29.x
-
29.x — The ../branches/29.x/.. branch from Git
-
MD5

DevMenu

2026-08-25T20:07:37+00:00

-
Tiki29

How to release

2026-08-24T22:46:21+00:00

- 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
1.2.1. Checkout Tiki
1.2.2. Setup.sh
1.2.3. Update lib/setup/twversion.class.php
1.2.4. Run script
1.2.4.1. Check the generated README file
1.2.5. Test the produced "tarballs" and share the testing
1.2.6. 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.1. Requirements
-
Unix shell environment, Linux or OSX suitable.
-
Git
-
PHP 7.x or 8.x CLI with MySQL, iconv, DOM and SimpleXML extensions. Note about php versions: Use PHP 7.x for Tiki 25.x releases and lower, and 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 😊
-
-
_2">1.2. Requirements_2" class="heading-link" aria-label="heading link">
+

1.1. Requirements
-
1.3. Release Steps

1.3.1. Checkout Tiki
+
1.2. Release Steps

1.2.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.
9" >Copy to clipboard
9" >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. 9" >Copy to clipboard 9" > 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.
Copy to clipboard
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. 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

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 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 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

+
1.2.2. Setup.sh

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

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

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

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

-
22" >Copy to clipboard
22" >
function TWVersion()

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

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

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

-

24" >Copy to clipboard
24" >
[REL] Preparing \$VERSION release

+

6" >Copy to clipboard
6" >
[REL] Preparing \$VERSION release

-
1.3.4. Run script

+
1.2.4. Run script

-
Display Basic Help
25" >Copy to clipboard
25" >
php doc/devtools/release.php --help
to get the command help and see different options that can be used.

+
Display Basic Help
7" >Copy to clipboard
7" >
php doc/devtools/release.php --help
to get the command help and see different options that can be used.

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

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

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

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

-
28" >Copy to clipboard
28" >
php doc/devtools/release.php 26.1

+
1
" >Copy to clipboard
1
" >
php doc/devtools/release.php 26.1

-
Unnecessary for Tiki31 and later
29" >Copy to clipboard
29" >
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)

+
Unnecessary for Tiki31 and later
11" >Copy to clipboard
11" >
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)

-
Unnecessary for Tiki31 and later, use simplified command instead
3
" >Copy to clipboard
3
" >
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
12" >Copy to clipboard
12" >
php -d mysqli.default_host=HOST -d mysqli.default_user=USER -d mysqli.default_pw=PASS doc/devtools/release.php 29.
RC1

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

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

-
1.3.4.1. Check the generated README file

+
1.2.4.1. Check the generated README file

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

+
1.2.5. Test the produced "tarballs" and share the testing

-
1.3.6. Upload tarballs to Sourceforge

+
1.2.6. Upload tarballs to Sourceforge

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

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

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

+
15" >Copy to clipboard
15" >
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.4.1. Update lib/setup/twversion.class.php

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

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

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

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

+
1.3.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.3.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.3.2.2. tell tim to manage also that branch to update tiki from that version also

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

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

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

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

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

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

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

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

Tiki-End-to-End-Testing

2026-08-21T20:32:47+00:00

-
Test suites
+ The bootstrap
Wiring a fixture to a spec
Test suites
-
53" >Copy to clipboard
53" >
tests/e2e/bin/e2e-setup.sh # setup + smoke run
+
7" >Copy to clipboard
7" >
tests/e2e/bin/e2e-setup.sh # setup + smoke run
-
54" >Copy to clipboard
54" >
npm install # @playwright/test is a root devDependency
+
38" >Copy to clipboard
38" >
npm install # @playwright/test is a root devDependency
-
55" >Copy to clipboard
55" >
cp tests/e2e/.env.template tests/e2e/.env
+
39" >Copy to clipboard
39" >
cp tests/e2e/.env.template tests/e2e/.env
-
56" >Copy to clipboard
56" >
php tests/e2e/fixtures/create_test_users.php
+
4
" >Copy to clipboard
4
" >
php tests/e2e/fixtures/bootstrap.php create_test_users.php
-
Adapt the PHP invocation to your environment: ddev exec php, docker exec, or plain php.
+
Every PHP fixture is run this way: bootstrap.php first, then the script path relative to tests/e2e/fixtures/. Adapt the PHP invocation to your environment: ddev exec php, docker exec, or plain php.
-
57" >Copy to clipboard
57" >
npm run test:e2e # all suites
+
41" >Copy to clipboard
41" >
npm run test:e2e # all suites
-
58" >Copy to clipboard
58" >
cd tests/e2e
+
42" >Copy to clipboard
42" >
cd tests/e2e
-
59" >Copy to clipboard
59" >
# Open Playwright UI: browse, filter, and re-run tests interactively
+
43" >Copy to clipboard
43" >
# Open Playwright UI: browse, filter, and re-run tests interactively
-
6
" >Copy to clipboard
6
" >
cd tests/e2e
+
44" >Copy to clipboard
44" >
cd tests/e2e
-
61" >Copy to clipboard
61" >
npx playwright test --reporter=list # terminal only
+
45" >Copy to clipboard
45" >
npx playwright test --reporter=list # terminal only
-
2" >Copy to clipboard
2" >
tests/e2e/
+
46" >Copy to clipboard
46" >
tests/e2e/
+ │ ├── bootstrap.php Runs every fixture: CLI guard, Tiki + admin, JSON in/out
-
If PHP fixtures are needed, add a fixtures/<domain-name>/ subfolder.
+
If PHP fixtures are needed, add a fixtures/<domain-name>/ subfolder and write each script to the fixture contract below: a return function (array $input): array { ... }, with no bootstrap code of its own.
- <~~p>Per-test~~case fixtures are wired <strong>by naming conventionng>. A spec never writes its own beforeAll / afterAll plumbing; it adds one line at the top:
+ <h3 class="showhide_heading d-flex justify-content-start" id="The_bootstrap"> The bootstrapotstrap" class="heading-link" aria-label="heading link">an class="icon icon-link fas fa-link " >pan>

No fixture script bootstraps itself. They all run through fixtures/bootstrap.phpe>, which owns every step they would otherwise repeat: routing errors to stderr, the CLI-only guard, tiki-setup.phpode> and helpers.php, bootstrap_admin(), decoding the input argument, printing the result as JSON on stdout, and turning a thrown exception into a stderr message and a non-zero exit.
- 3" >Copy to clipboard 63" >import { useSuiteFixtures } from "../../common/fixtures";
+ 47" >Copy to clipboard php tests/e2e/fixtures/bootstrap.php <script> [base64(JSON input)] The script path is relative to fixtures/, so no caller has to know where the Tiki root sits inside a container. A fixture therefore contains only its own logic. It returns a callable: Copy to clipboard php" data-wrap="1" dir="ltr" style="white-space:pre-wrap; overflow-wrap: break-word; word-wrap: break-word;" id="codebox48" >ss="code"><?php // TC-11 setup: creates an encryption key assigned to Test1. return function (array $input): array { delete_keys_by_name(&# 39;TC11-EncKey&# 39;); $key = create_encryption_key(&# 39;TC11-EncKey&# 39;, &# 39;Test1&# 39;); return [&# 39;keyId&# 39; => $key[&# 39;keyId&# 39;], &# 39;share&# 39; => $key[&# 39;shares&# 39;][ ]]; }; The returned array is printed as JSON on stdout, the only thing ever written there. $input is the decoded argument: for a tcNN_teardown.php that is whatever tcNN_setup.php printed. Failures throw, and common/fixtures.ts surfaces the message and skips the suite. A fixture that needs a different environment says so instead of hand-rolling one: Copy to clipboard 49" >return [ &# 39;tiki&# 39; => false, // skip tiki-setup.php, raw PDO access only &# 39;admin&# 39; => false, // skip bootstrap_admin(), defaults to the &# 39;tiki&# 39; value &# 39;run&# 39; => function (array $input): array { ... }, ]; Wiring a fixture to a spec Per-testcase fixtures are wired by naming convention. A spec never writes its own beforeAll / afterAll plumbing; it adds one line at the top: Copy to clipboard import { useSuiteFixtures } from "../../common/fixtures";
- teardown runs in afterAll and receives the setup's JSON output <strong>base64-encoded as its first CLI argument, which is shell-safe through ddev exec, Docker or plain PHP, so it can read back the IDs setup created.
+ teardown runs in afterAll and receives that same JSON as its ode>$input</code>, handed over base64-encoded so it is shell-safe through ddev exec, Docker or plain PHP, and can read back the IDs setup created.
- <br />Most scripts >require_once tiki-setup.php and must be invoked with the Tiki web root as the working directory. The exception is create_test_users.php, which connects to the database through PDO directly using db/local.php. It needs no Tiki bootstrap and works with plain PHP CLI. 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 bootstrap.php Every fixture Runs a fixture script: CLI guard, Tiki bootstrap, admin permissions, JSON in and out 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
- 64" >Copy to clipboard 64" ># 1. Provision once (writes db/local.php, installs the schema, sets the admin password).
+ 51" >Copy to clipboard 51" ># 1. Provision once (writes db/local.php, installs the schema, sets the admin password).
- 65" >Copy to clipboard 65" >https://gitlab.com/tikiwiki/tiki/-/jobs/<job-id>/artifacts/file/tests/e2e/playwright-report/index.html
+ 2" >Copy to clipboard 2" >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 e>php tests/e2e/fixtures/bootstrap.php <suite>/tcNN_setup.php 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/bootstrap.php 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.
- Playwright documentation
+ Playwright documentation
Testing Checklist 2026-08-18T19:25:42+00:00 - Log in + Log in ** Local login ** Logout ** Password reset ** Failed-login/lockout ** 2FA ** Remember-me/session ** Permissions after login Decision Analysis for Image Editing Library in Tiki 2026-08-17T10:22:42+00:00 + Status + + This comparison is still a draft. The Cropper.js version in merge request !10413 is part of this evaluation, not a final decision. + + + Related links: + + Image manipulation request:https://dev.tiki.org/item1767 + Merge request !10413 + How to pick a software library + + + 1. What we need + + The goal is to let someone make basic changes to an image before uploading it to a Tiki File Gallery. + + + The first version should: + + work with JPEG, PNG, and WebP files; + crop, rotate, and flip images, with a few basic effects; + work inside the existing Vue uploader and Bootstrap interface; + return a normal File to the current upload process; + keep useful image quality and resolution; + be usable on desktop and mobile; and + use a Tiki-compatible license and be reasonably maintainable. + + + 2. What to compare + + The main points are the license, project activity, bundle size, browser and mobile support, accessibility, Vue compatibility, image quality, integration effort, and long-term maintenance. Existing use in Tiki or WikiSuite should also count in an option's favor. + + + 3. Options + + + Cropper.js 2.1.1 + + Cropper.js is focused on cropping and image transforms. It handles the difficult selection and transform logic, works independently of a particular framework, and is MIT licensed. The current MR shows that it can be integrated with the File Gallery uploader. + + + The tradeoff is that it would be a new Tiki dependency. Tiki still needs to provide the modal, controls, mobile layout, accessibility, effects, and upload integration. Canvas is also still used to render the final image and turn it back into a file. + + + Tiki's H5P image editor + + The H5P integration already ships image-editing code based on Darkroom.js and Fabric.js. However, that code expects the H5P editor environment and its globals and assets. It is not a standalone component that the Vue uploader can import directly, so reusing it would require separating and maintaining the H5P-specific parts. + + + Native Canvas + + Canvas works well for effects and for exporting the edited image, and it does not add a dependency. The downside is that Tiki would have to maintain all crop selection, transform, mouse, touch, and preview behavior itself. That is much more custom code than using Canvas only for final rendering. + + + + + 4. Current view + + Cropper.js looks like the strongest option so far. It removes most of the custom crop logic and is easier to reuse here than the H5P editor. This remains a preliminary view until the remaining alternatives and bundle impact are checked and the Tiki developer community has had a chance to comment. + Creating or maintaining translations 2026-08-09T19:58:34+00:00 - 74" >Copy to clipboard 74" >php console.php translation:getstrings --lang=fr --skip-remove + 66" >Copy to clipboard 66" >php console.php translation:getstrings --lang=fr --skip-remove - 5" >Copy to clipboard 5" >// "Save" => "Save", + 67" >Copy to clipboard 67" >// "Save" => "Save", - 76" >Copy to clipboard 76" >"Save" => "Enregistrer", + 8" >Copy to clipboard 8" >"Save" => "Enregistrer", - 77" >Copy to clipboard 77" >php console.php translation:getstrings --lang=fr + 69" >Copy to clipboard 69" >php console.php translation:getstrings --lang=fr - 8" >Copy to clipboard 8" >php console.php translation:getstrings --lang=fr --skip-remove + " >Copy to clipboard " >php console.php translation:getstrings --lang=fr --skip-remove - 9" >Copy to clipboard 9" >php console.php translation:getstrings --custom --lang=fr --skip-remove + 1" >Copy to clipboard 1" >php console.php translation:getstrings --custom --lang=fr --skip-remove - 8 " >Copy to clipboard 8 " ><?php + 72" >Copy to clipboard 72" ><?php - 81" >Copy to clipboard 81" >php console.php translation:getstrings [options] + 73" >Copy to clipboard 73" >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.

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 ~~man~~ually 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 e>php tests/e2e/fixtures/bootstrap.php <suite>/tcNN_setup.php 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/bootstrap.php 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.

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