RSS

Boss Ibrahim Mussa Gregoire (50ae76a3) at 15 Jul 12:27 Merge branch 'duplucate_save_config' into 'master' ... and 1 more commit

Related to !65

Related to !65

It's have been reported that tiki could not read preferences set on the configuration file. For some use case Tiki instance used to load some preferences form the ini file and prevent to be edited but was not working. The issue come from an update that did not use the previous method to save data of the file. Related the commit 46b7f5af Related task

Victor Emanouilov (3d57e95a) at 15 Jul 12:03 Merge branch 'missing_preference_config' into 'master' ... and 1 more commit

It's have been reported that tiki could not read preferences set on the configuration file. For some use case Tiki instance used to load some preferences form the ini file and prevent to be edited but was not working. The issue come from an update that did not use the previous method to save data of the file. Related the commit 46b7f5af Related task

Ah, then I get the point, I used to face the same issue with log files. Thanks.

No, the key reason is: Tiki Manager, in its current state expects to be executed always with the user who has permissions in the Tiki Manager folder, so switching to the domain user causes Tiki Manager to fail due to permission issues. All commands write to log files, check the database, etc. So need to run as the user owning tiki manager, that in wikisuite is root. Either way, curious, why the question?

Can't we only allow run detect command as root, and other command can remain as it is?

SoftStart Code (4575bbfd) at 21 May 08:09 Merge branch 'item130775-virtualmin-fix-log-write-permission' into ... ... and 1 more commit