Category: Installer (profiles, upgrades and server-related issues)

I installed a tiki3.3 on a server ( pangea.org ) with no remarkable issues, and the tikis seem to work fine:
http://d-recerca.org


However, I attempted to install a spare tiki4.0 for testing on the same server, and I can't install it:
http://xavidp.pangea.org/tiki40/

I guess the server doesn't have pdo installed. I added the line in local.php to force tiki to use adodb instead (copied from tw.o forums, message from sylvie). With this change I can bo a bit further, but I cannot finish the installation proces. After the sql are run, I'm sent to the authentication page of tiki-install.php, instead of to the step of locking the installer and proceeding to tiki.

I went to the tiki-index.php then. and i could see it, and changed password for admin. But I can't login after that step neither with admin admin or with new admin pass..

This error was seen when using PHP4

Tiki should detect and provide better error message

Good:

Since Tiki4, in tiki-admin_include_sefurl.php, Tiki detects if .htaccess is there and if contains tiki-index.php?page=$1

But:
If Tiki is upgraded, by installing over, there may be issues because Tiki is still using the old .htaccess without informing tiki admin


Proposal:
Have Tiki version number in _htaccess (and thus updated as part of the release procedure)
Test on this, and inform users when they forgot to upgrade their .htaccess file.

Please add to tiki-check.php in a (new) Composer section

Also, when sh setup.sh is executed, it runs Composer, but it should 1st check if .phar is available on the server

I went to http://demo.tiki.org/12x/tiki-install.php to proceed to a test of the installer (for an upgrade, not fresh install) and I saw: "Database `d01863d1` was created" which doesn't make sense with ''Tiki found an existing database connection in your local.php file. Database name: "d01863d1"''

{img fileId="441"}

At tiki-admin.php?page=general when "Server Fitness" is activated or clicked, the page never loads, and the rest of the tiki site stalls as well.
A browser reboot must be performed or browser clear cache in order to access the tiki site.

A show instance will be created to test if this issue persists here as well.

My own instance:
Tiki 18.2svn
innoDB
PHPv 7.0

The install script says to run the 1.8to1.9 SQL upgrade when upgrading from a 1.9.x to another 1.9.x release.

I have and error in that script while creating the tiki_score table, which is normal because it already exists. Then, I have a bunch of errors in the following INSERT statements because the category column is missing (along ith the desription and ordd columns). Here is the output of the failed statements:

CREATE TABLE tiki_score (
event varchar(40) NOT NULL default '',
score int(11) NOT NULL default '0',
expiration int(11) NOT NULL default '0',
category text NOT NULL,
description text NOT NULL,
ord int(11) NOT NULL default '0',
PRIMARY KEY (event),
KEY ord (ord)
) TYPE=MyISAM
Message: Table 'tiki_score' already exists


Command: INSERT INTO tiki_score (event,score,expiration,category,description,ord) VALUES ('login',1,0,'General','Login',1)
Message: Unknown column 'category' in 'field list'

.... other similar failed INSERT


Here is the tiki_score table definition that is currently in my 1.9.1 database (extracted from a mysqldump):
CREATE TABLE tiki_score (
event varchar(40) NOT NULL default '',
score int(11) NOT NULL default '0',
expiration int(11) NOT NULL default '0',
PRIMARY KEY (event)
) TYPE=MyISAM;

Upgrading a previous 1.10 site with current cvs code (from August 1st, 2007) I get, while using
tiki_1.9to1.10.sql with -f param from command line:

^
(...)
ERROR 1071 at line 561: Specified key was too long. Max key length is 500
ERROR 1071 at line 585: Specified key was too long. Max key length is 500
(...)
ERROR 1074 at line 620: Too big column length for column 'value' (max = 255). Use BLOB instead
ERROR 1074 at line 627: Too big column length for column 'fieldname' (max = 255). Use BLOB instead
(...)
^

Plus some:
{CODE(wrap=>1)}
(...)
ERROR 1064 at line 497: You have an error in your SQL syntax. Check the manual that corresponds to your MySQL server version for the right syntax to use near 'user(100),serverId,groupName(100))' at line 1
ERROR 1064 at line 500: You have an error in your SQL syntax. Check the manual that corresponds to your MySQL server version for the right syntax to use near 'user(150),pageName(100))' at line 1
ERROR 1064 at line 506: You have an error in your SQL syntax. Check the manual that corresponds to your MySQL server version for the right syntax to use near 'user(100),id(100))' at line 1
ERROR 1064 at line 509: You have an error in your SQL syntax. Check the manual that corresponds to your MySQL server version for the right syntax to use near 'user(100),event,object(50))' at line 1
ERROR 1064 at line 513: You have an error in your SQL syntax. Check the manual that corresponds to your MySQL server version for the right syntax to use near 'user(120),friend(120))' at line 1
(...)
ERROR 1064 at line 597: You have an error in your SQL syntax. Check the manual that corresponds to your MySQL server version for the right syntax to use near 'user(120))' at line 1
(...)
ERROR 1064 at line 638: You have an error in your SQL syntax. Check the manual that corresponds to your MySQL server version for the right syntax to use near 'SELECT `fieldId` FROM `tiki_webmail_contacts_fields` WHERE `fie
(...)
{CODE}

Sylvieg, if you review this, you can see it your own at ourproject.org server, uniwiki project, updating uniwiki2 database (the one for http://uniwiki.ourproject.org ).

Also, there is a DB error on a fresh install of 10.2 I can't test in show.tiki.org to see if it's fixed in 10.4 --because 10.4 is not available on show.tiki.org-- 10.4 is now available {sign user="marclaporte" datetime="2013-08-14T23:29:31+00:00"}

{img fileId="340"}

---

In latest 11.x: "Version 0.0 is still supported. However, a major upgrade to 9.0 is available."
{img fileId="359"}

On another site:
{img fileId="371"}

On another site:
{CODE()}A new version of Tiki, , is available. You are currently running SVN pre 8.4. Please visit tiki.org/Download.{CODE}

On another sites:
"A new version of Tiki, , is available. You are currently running SVN proposals pre 6.6. Please visit tiki.org/Download." Seen on http://info.tiki.org Last update from SVN (SVN proposals pre 6.6): Friday, January 13, 2012 11:52:30 GMT-5 - REV 39480 Theme: Fivealive - Akebi

On another site:
[http://irc.tiki.org/irclogger_log/tikiwiki?date=2013-02-26,Tue&sel=150#l146]

If Trackers had the "tracker template" feature, it would allow for better pre-made extended features for Tiki at install time.
In tw.o forums, some people requested like: address books (imagine with the same basic fields as Mozilla Thunderbird & Evolution, etc. address books, ... Export from you local program (through csv), and import to your address book in Tiki (through csv).

The same for "Offers & Demands (linked or linkable)", that many people/communities would like to use like "out of the box" feature. I do have that kind of trackers made (basic, but working for production already: http://valldelcorb.org/trackers - http://valldelcorb.org/Comparteix (1.9.x) or http://intercanvis.net (1.10.x) using tracker plugins in a general Wiki page).

Since duplicate tracker is already coded in 1.10, and templates concept already exists in Tiki, Tracker templates would be a nice MUST in the MID and LONG run.

Tracker templates should be selectable at install time (in the new installer devs. are thinking/designing -> ((Install)) ), or at a later stage through Mods, maybe?

{CODE()}[root@tikisuite 12]# sh setup.sh

Tiki setup.sh - your options
============================

c run composer and exit (recommended to be done first)

f fix (classic default) o open (classic option)
S clear screen

predefined Tiki Permission Check models:
----------------------------------------

1 paranoia
2 paranoia-suphp w suphp workaround
3 sbox W sbox workaround
4 mixed
5 worry 6 moreworry
7 pain 8 morepain
9 risky a insane

q quit x exit

There are some other commands recommended for advanced users only.
More documentation about this: http://doc.tiki.org/Permission+Check

Your choice [c]?
#!/usr/bin/env php
Some settings on your machine may cause stability issues with Composer.
If you encounter issues, try to change the following:

Your PHP (5.3.3) is quite old, upgrading to PHP 5.3.4 or higher is recommended.
Composer works with 5.3.2+ for most people, but there might be edge case issues.

Downloading...

Composer successfully installed to: /var/www/html/12/temp/composer.phar
Use it: php temp/composer.phar
Loading composer repositories with package information
Installing dependencies (including require-dev) from lock file
Your requirements could not be resolved to an installable set of packages.

Problem 1
- phpunit/phpunit 3.7.28 requires ext-dom * -> the requested PHP extension d om is missing from your system.
- phpunit/phpunit 3.7.28 requires ext-dom * -> the requested PHP extension d om is missing from your system.
- Installation request for phpunit/phpunit 3.7.28 -> satisfiable by phpunit/ phpunit[3.7.28].

Composer failed, retrying in 5 seconds, for a few times. Hit Ctrl-C to cancel.
Loading composer repositories with package information
Installing dependencies (including require-dev) from lock file
Your requirements could not be resolved to an installable set of packages.

Problem 1
- phpunit/phpunit 3.7.28 requires ext-dom * -> the requested PHP extension dom is missing from your system.
- phpunit/phpunit 3.7.28 requires ext-dom * -> the requested PHP extension dom is missing from your system.
- Installation request for phpunit/phpunit 3.7.28 -> satisfiable by phpunit/phpunit[3.7.28].

Composer failed, retrying in 5 seconds, for a few times. Hit Ctrl-C to cancel.
Loading composer repositories with package information
Installing dependencies (including require-dev) from lock file
Your requirements could not be resolved to an installable set of packages.

Problem 1
- phpunit/phpunit 3.7.28 requires ext-dom * -> the requested PHP extension dom is missing from your system.
- phpunit/phpunit 3.7.28 requires ext-dom * -> the requested PHP extension dom is missing from your system.
- Installation request for phpunit/phpunit 3.7.28 -> satisfiable by phpunit/phpunit[3.7.28].

Composer failed, retrying in 5 seconds, for a few times. Hit Ctrl-C to cancel.
Loading composer repositories with package information
Installing dependencies (including require-dev) from lock file
Your requirements could not be resolved to an installable set of packages.

Problem 1
- phpunit/phpunit 3.7.28 requires ext-dom * -> the requested PHP extension dom is missing from your system.
- phpunit/phpunit 3.7.28 requires ext-dom * -> the requested PHP extension dom is missing from your system.
- Installation request for phpunit/phpunit 3.7.28 -> satisfiable by phpunit/phpunit[3.7.28].

Composer failed, retrying in 5 seconds, for a few times. Hit Ctrl-C to cancel.
Loading composer repositories with package information
Installing dependencies (including require-dev) from lock file
Your requirements could not be resolved to an installable set of packages.

Problem 1
- phpunit/phpunit 3.7.28 requires ext-dom * -> the requested PHP extension dom is missing from your system.
- phpunit/phpunit 3.7.28 requires ext-dom * -> the requested PHP extension dom is missing from your system.
- Installation request for phpunit/phpunit 3.7.28 -> satisfiable by phpunit/phpunit[3.7.28].

Composer failed, retrying in 5 seconds, for a few times. Hit Ctrl-C to cancel.
Loading composer repositories with package information
Installing dependencies (including require-dev) from lock file
Your requirements could not be resolved to an installable set of packages.

Problem 1
- phpunit/phpunit 3.7.28 requires ext-dom * -> the requested PHP extension dom is missing from your system.
- phpunit/phpunit 3.7.28 requires ext-dom * -> the requested PHP extension dom is missing from your system.
- Installation request for phpunit/phpunit 3.7.28 -> satisfiable by phpunit/phpunit[3.7.28].

Composer failed, retrying in 5 seconds, for a few times. Hit Ctrl-C to cancel.
Loading composer repositories with package information
Installing dependencies (including require-dev) from lock file
Your requirements could not be resolved to an installable set of packages.

Problem 1
- phpunit/phpunit 3.7.28 requires ext-dom * -> the requested PHP extension dom is missing from your system.
- phpunit/phpunit 3.7.28 requires ext-dom * -> the requested PHP extension dom is missing from your system.
- Installation request for phpunit/phpunit 3.7.28 -> satisfiable by phpunit/phpunit[3.7.28].{CODE}

--Need to test latest 12.x and 13.x--

It's fixed in latest 12.x

I applied current profile related to spreadsheets (as of September 2015) in profiles.t.o:

... https://profiles.tiki.org/Spreadsheet_Test_Profiles

and it does enable the spreadsheet feature and create the intended spreadsheet indeed, but the indicated contents do not seem to get added.

Syntax in that profile page is:
{CODE()}
objects:
-
type: sheet
data:
-
title: Test Title
- [ Test, =A1 ]
- [ =B2, =B1 + A1 ]
{CODE}

I tried with 12.x and 14.x with same results.

Maybe something needs to be tweaked in the profile handler code?:
{CODE()}
/lib/core/Tiki/Profile/InstallHandler/Sheet.php
{CODE}

In trunk (future tiki15) it also fails to add the data to the sheet. Help is needed. {sign user="xavi" datetime="2015-12-31T14:33:57+00:00"}

After I upgraded a site from 10.x to 12.x, and cleared caches, I got this error when attempting to see or login at the site:

12.x: Fatal error: Unsupported operand types in lib/setup/prefs.php on line 406

using 12.x svn (r53316)

The site uses LDAP, so maybe some pref in LDAP settings interferes somewhere?

our server uses PHP Version 5.3.5-1ubuntu7.2ppa1~lucid1

This was working in Tiki9, as far as I know.

12.x: profile data defined for item link field do not get stored in local tiki where profile was applied

Example: apply profile "Time_Sheet" ( https://profiles.tiki.org/Time_Sheet ), and notice that items "Watch TV" or "Setup of Tiki TimeSheet" had defined "General" in the field "Associated project", which is an item link field.

The field seems to have been well defined, since it allows the admin (once the profile has been applied) to edit a tracker "Time Sheet" item, and select the project from the drop down list (so far it only contains "General").

To be reproduced in short in a show.t.o instance associated with this item.
http://xavi-9794-4983.show.tikiwiki.org/tiki-view_tracker.php?trackerId=2
u: admin
p: 12345

FF26.0
after reaching the step 'install' in the installer, I was asked in a never ending loop for my db credentials

my work-around solution was to add
$_SESSION[['accessible'] = true;
to
db\local.php

and then the install went on

Seen here: http://next.tiki.org/tiki-admin.php?page=general

13.x: applying a profile from Profiles Wizard doesn't send the user to the "Step2" indicated in the url (some steps anchors gone?)

13.x: Default feature 'Contact us' (used in featured profiles) has broken display (too narrow fields and below column in right-hand-side)

{img fileId="839" thumb="y" rel="box[g]" width="600"}

You can see it reproduced here:
http://xavi-9794-5369.show.tikiwiki.org/tiki-contact.php

u: admin
p: 12345

13.x: Profiles with "random header images" stopped working as expected compared to 12.x

See it reproduced with profile Easy GeoBlog, which doesn't display any images in the header (images aren't saved in the local tiki instance).
See it reproduced here:
http://xavi-9794-5064.show.tikiwiki.org/tiki-list_file_gallery.php?galleryId=5

-----
It currently works as expected (only small issues with surrounding box).

Who knows what happened. Maybe temporary network issue to display images from tiki.org or similar.
Closing the report {sign user="xavi" datetime="2014-07-13T11:35:12+00:00"}

15.x Regression: Profile Voting System can't create the instructions page.
IT works as expected from 12.x to 14.x, but not using trunk (future 15.x)

It may happen with other profiles in the Profiles Wizard: I just havent' tested them yet. {sign user="xavi" datetime="2016-01-19T21:35:25+00:00"}
---
Tested other profile: Collaborative_Community_12x (one of the 4 featured) and it fails to assign the trackerId or tracker fields in the "... Members Homepage", which used to work.{sign user="xavi" datetime="2016-01-21T07:35:32+00:00"}

Reproduced in a show.t.o instance linked to this bug report.
See:
http://xavi-9794-5794.show.tikiwiki.org/tiki-index.php?page=Community+Members+HomePage
u: admin
p: 12345

The tracker & items were created properly, but not the references to those objects in the Community+Members+HomePage

Something similar with the "Voting System" profile. The page "Voting" is not created in trunk (but everything works as expected up to 14.x).
--
Update on the error message for profile Voting system:
__An error occurred: Cannot add user user1 to nonexistent group Group1__
{CODE()}
root@penguinbookpro:/var/www/html/trunk# php console.php d:i --force;php console.php cache:clear --all;php console.php profile:apply Voting_System
Installation completed.
Queries executed successfully: 1392
Clearing all caches
Installation failed:
Applying profile: Voting_System
Preference set: feature_trackers=y
Preference set: feature_wiki_argvariable=y
Preference set: useGroupHome=y
Preference set: limitedGoGroupHome=y
Preference set: trackerfield_autoincrement=y
Preference set: trackerfield_dropdownother=y
Preference set: wikiplugin_jq=y
Preference set: instructions=Profile_Voting_System_voting_page
Added (or modified): tracker "Tracker for the Voting System"
Added (or modified): tracker_field "Note from the Voting System"
Added (or modified): tracker_field "Presidency"
Added (or modified): tracker_field "Vicepresidency"
Added (or modified): tracker_field "Secretarial"
Added (or modified): tracker_field "Treasury"
Added (or modified): tracker_field "Extra Membership 1"
Added (or modified): tracker_field "Extra Membership 2"
Added (or modified): tracker_field "Extra Membership 3"
Added (or modified): tracker_field "Extra Membership 4"
Added (or modified): tracker_field "Username"
Added (or modified): tracker_field "Vote #"
An error occurred: Cannot add user user1 to nonexistent group Group1
root@penguinbookpro:/var/www/html/trunk#
{CODE}

Hi:

I've set up an R script (.Rmd: with R markdown to be run through Knitr) to check the application of all Tiki Profiles (the ones available in the Profiles Wizard since Tiki12, at least) on several tiki branches on your own localhost, to search for error messages, and aggregate that information for easy monitoring. It can be extended to send an email when regressions show up, etc.
I developed that over the weekend from home, and even if in beta stage, it currently works.
See: https://github.com/xavidp/TikiProfilesTester

However, I cloned the git repo at work, where we are behind a proxy, and console.php cannot apply profiles from there through the commandline. Through the GUI I always have to add the proxy info to Tiki first in order to be able to list profiles and apply them , etc.

{CODE()}
root@pentinella:/var/www/html/trunk# php console.php p:a Voting_System
Profile not found.
root@pentinella:/var/www/html/trunk#
{CODE}

proxy info seem to be defined at ./trunk/lib/tikilib.php (line 185 onwards)

This script does not work with http servers that run under UNcommon user ID/GID. There is one good http server example in the Debian repos called yaws where the script becomes a problem. yaws runs under user ID/GID yaws/yaws. If one attempts to run setup.sh with a yaws http server, the script does not work.

1.Clicking on "Admin mods" after installation returns this error.
You need to run setup.sh :
./setup.sh $APACHEUSER all
Common Apache users are www-data, apache or nobody

2. Going to the command line and running setup.sh yaws all (because the username/gid is yaws, not the usual) returns no messages when in fact the script has already decided that the user will be www-data because I'm on Debian. About line 27 of the script. if [ -f /etc/debian_version]; ....

There's no message that says how the ownership has been changed after running the script. There's no message saying the user has been chosen for me because I'm on Debian either. In both cases, I'd still have problems because the userID/GID needs to be yaws/yaws in order to make tikiwiki work right.

Perhaps another way to address the problem is to check and see who owns the server process with an lsof -p :portNumber?

I was willing to test some feature in recent 18.x compared to trunk. Trunk worked fine, but 18.x complained with:
"Data too long for column 'log' at row 1"

The query was:
insert into `tiki_actionlog` (`action`, `object`, `lastModif`, `user`, `ip`, `comment`, `objectType`, `client`, `log`) values(?,?,?,?,?,?,?,?,?)

Steps to reproduce in 18.x: brand new install (r67615). MyISAM in db type.
* Login as admin, change pass
* Profiles Wizard > Demo of Interesting Use Cases > Bug Tracker
* click again in the profiles manager, since the profiles wizard didn't succeed showing you the button to apply the profile.
* next page shows that error message:
{CODE()}
The query was:
insert into `tiki_actionlog` (`action`, `object`, `lastModif`, `user`, `ip`, `comment`, `objectType`, `client`, `log`) values(?,?,?,?,?,?,?,?,?)

Values:

profile apply
Bug_Tracker_16
1537742078
admin
127.0.0.1
profile applied
system
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0
a:76:{i:0;a:4:{s:4:"type";s:10:"preference";s:3:"new";s:1:"y";s:3:"old";s:1:"n";s:11:"description";s:16:"feature_trackers";}i:1;a:4:{s:4:"type";s:10:"preference";s:3:"new";s:1:"y";s:3:"old";s:1:"n";s:11:"description";s:20:"feature_user_watches";}i:2;a:4:{s:4:"type";s:10:"preference";s:3:"new";s:1:"y";s:3:"old";s:1:"n";s:11:"description";s:26:"feature_syntax_highlighter";}i:3;a:4:{s:4:"type";s:10:"preference";s:3:"new";s:7:"default";s:3:"old";s:3:"off";s:11:"description";s:32:"feature_syntax_highlighter_theme";}i:4;a:4:{s:4:"type";s:10:"preference";s:3:"new";s:1:"y";s:3:"old";s:1:"n";s:11:"description";s:16:"ajax_inline_edit";}i:5;a:4:{s:4:"type";s:10:"preference";s:3:"new";s:1:"y";s:3:"old";s:1:"n";s:11:"description";s:26:"feature_jquery_tablesorter";}i:6;a:4:{s:4:"type";s:10:"preference";s:3:"new";s:1:"y";s:3:"old";s:1:"n";s:11:"description";s:24:"feature_wiki_argvariable";}i:7;a:4:{s:4:"type";s:10:"preference";s:3:"new";s:1:"y";s:3:"old";s:1:"n";s:11:"description";s:25:"tracker_change_field_type";}i:8;a:4:{s:4:"type";s:10:"preference";s:3:"new";s:1:"y";s:3:"old";s:1:"n";s:11:"description";s:18:"tracker_clone_item";}i:9;a:4:{s:4:"type";s:10:"preference";s:3:"new";s:1:"y";s:3:"old";s:1:"n";s:11:"description";s:27:"tracker_show_comments_below";}i:10;a:4:{s:4:"type";s:10:"preference";s:3:"new";s:1:"y";s:3:"old";s:1:"n";s:11:"description";s:26:"trackerfield_dropdownother";}i:11;a:4:{s:4:"type";s:10:"preference";s:3:"new";s:1:"y";s:3:"old";s:1:"n";s:11:"description";s:26:"trackerfield_groupselector";}i:12;a:4:{s:4:"type";s:10:"preference";s:3:"new";s:1:"y";s:3:"old";s:1:"n";s:11:"description";s:21:"wikiplugin_pivottable";}i:13;a:4:{s:4:"type";s:10:"preference";s:3:"new";s:1:"y";s:3:"old";s:1:"n";s:11:"description";s:12:"useGroupHome";}i:14;a:4:{s:4:"type";s:10:"preference";s:3:"new";s:1:"y";s:3:"old";s:1:"n";s:11:"description";s:18:"limitedGoGroupHome";}i:15;a:4:{s:4:"type";s:10:"preference";s:3:"new";s:1:"y";s:3:"old";s:1:"n";s:11:"description";s:8:"log_mail";}i:16;a:4:{s:4:"type";s:10:"preference";s:3:"new";s:21:"YourEmail@example.com";s:3:"old";s:13:"xavi@tiki.org";s:11:"description";s:12:"sender_email";}i:17;a:4:{s:4:"type";s:10:"preference";s:3:"new";s:1:"y";s:3:"old";s:1:"n";s:11:"description";s:21:"feature_wiki_comments";}i:18;a:4:{s:4:"type";s:10:"preference";s:3:"new";s:1:"y";s:3:"old";s:1:"n";s:11:"description";s:23:"feature_inline_comments";}i:19;a:4:{s:4:"type";s:10:"preference";s:3:"new";s:1:"y";s:3:"old";s:1:"n";s:11:"description";s:20:"comments_field_email";}i:20;a:4:{s:4:"type";s:10:"preference";s:3:"new";s:1:"y";s:3:"old";s:1:"n";s:11:"description";s:22:"comments_field_website";}i:21;a:4:{s:4:"type";s:10:"preference";s:3:"new";s:1:"y";s:3:"old";s:1:"n";s:11:"description";s:18:"wikiplugin_comment";}i:22;a:4:{s:4:"type";s:9:"installer";s:3:"new";b:0;s:3:"old";b:0;s:11:"description";s:14:"tracker "Bugs"";}i:23;a:4:{s:4:"type";s:9:"installer";s:3:"new";b:0;s:3:"old";b:0;s:11:"description";s:26:"tracker_field "Bug status"";}i:24;a:4:{s:4:"type";s:9:"installer";s:3:"new";b:0;s:3:"old";b:0;s:11:"description";s:24:"tracker_field "Severity"";}i:25;a:4:{s:4:"type";s:9:"installer";s:3:"new";b:0;s:3:"old";b:0;s:11:"description";s:24:"tracker_field "Priority"";}i:26;a:4:{s:4:"type";s:9:"installer";s:3:"new";b:0;s:3:"old";b:0;s:11:"description";s:23:"tracker_field "Summary"";}i:27;a:4:{s:4:"type";s:9:"installer";s:3:"new";b:0;s:3:"old";b:0;s:11:"description";s:23:"tracker_field "Version"";}i:28;a:4:{s:4:"type";s:9:"installer";s:3:"new";b:0;s:3:"old";b:0;s:11:"description";s:27:"tracker_field "Description"";}i:29;a:4:{s:4:"type";s:9:"installer";s:3:"new";b:0;s:3:"old";b:0;s:11:"description";s:34:"tracker_field "Expected behaviour"";}i:30;a:4:{s:4:"type";s:9:"installer";s:3:"new";b:0;s:3:"old";b:0;s:11:"description";s:28:"tracker_field "Submitted by"";}i:31;a:4:{s:4:"type";s:9:"installer";s:3:"new";b:0;s:3:"old";b:0;s:11:"description";s:27:"tracker_field "Assigned to"";}i:32;a:4:{s:4:"type";s:9:"installer";s:3:"new";b:0;s:3:"old";b:0;s:11:"description";s:24:"tracker_field "Alert to"";}i:33;a:4:{s:4:"type";s:9:"installer";s:3:"new";b:0;s:3:"old";b:0;s:11:"description";s:35:"tracker_option "sort_default_field"";}i:34;a:4:{s:4:"type";s:9:"installer";s:3:"new";b:0;s:3:"old";b:0;s:11:"description";s:29:"tracker_option "popup_fields"";}i:35;a:4:{s:4:"type";s:4:"user";s:3:"new";O:19:"Tiki_Profile_Object":4:{s:25:"Tiki_Profile_Objectdata";a:2:{s:4:"type";s:4:"user";s:4:"data";a:5:

(...)

{CODE}

Btw, profile seems to have been applied successfully.{sign user="xavi" datetime="2018-09-23T22:51:34+00:00"}

This should be migrated to the community site, and handled with ((doc:Organic groups)) and ((doc:User Trackers))