-
Victor Emanouilov accepted merge request !65: [FIX] Missing default system configuration preference setting. at WikiSuite / Virtualmin Tiki Manager
()
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 pushed to project branch master at WikiSuite / Virtualmin Tiki Manager
()
Victor Emanouilov (3d57e95a) at 15 Jul 12:03 Merge branch 'missing_preference_config' into 'master' ... and 1 more commit
-
Boss Ibrahim Mussa Gregoire opened merge request !65: [FIX] Missing default system configuration preference setting. at WikiSuite / Virtualmin Tiki Manager
()
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
-
Boss Ibrahim Mussa Gregoire commented on merge request !63 at WikiSuite / Virtualmin Tiki Manager
()
Ah, then I get the point, I used to face the same issue with log files. Thanks.
-
SoftStart Code commented on merge request !63 at WikiSuite / Virtualmin Tiki Manager
()
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?
-
Boss Ibrahim Mussa Gregoire commented on merge request !63 at WikiSuite / Virtualmin Tiki Manager
()
Can't we only allow run detect command as root, and other command can remain as it is?
-
SoftStart Code pushed to project branch master at WikiSuite / Virtualmin Tiki Manager
()
SoftStart Code (4575bbfd) at 21 May 08:09 Merge branch 'item130775-virtualmin-fix-log-write-permission' into ... ... and 1 more commit
-
SoftStart Code accepted merge request !63: [FIX] Run Global Tiki Manager CLI as Root to Avoid Log Write Permission Issues in Virtualmin at WikiSuite / Virtua...
()
This MR fixes the issue where running tiki-manager under Virtualmin fails with log permission errors due to user switching. 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. There is a work in progress to allow Tiki-Manager to execute some operations as other users, but it is still not merged. That would allow some commands to be executed impersonating the domain user in the future. Ref: https://avan.tech/item130775
-
SoftStart Code pushed to project branch master at WikiSuite / Virtualmin Tiki Manager
()
SoftStart Code (b3d4e8e8) at 21 May 08:05 Merge branch 'item131133-skip-remaining-steps-on-install-error' int... ... and 1 more commit
-
SoftStart Code accepted merge request !64: [ENH] Skip Remaining Configuration Steps on Instance Creation Failure at WikiSuite / Virtualmin Tiki Manager
()
Context: Enhances stability by ensuring that no additional configuration steps (e.g., setting preferences, changing ownership) are run if instance creation fails via Tiki Manager. Changes: tikimanager_tiki_install_and_config now checks for ERROR string in the output of tikimanager_tiki_install(). If an error is detected, the process logs a message and skips remaining steps gracefully. Ref: https://avan.tech/item131133