Upgrade to 1.1.5 control panel not working after

  • Hi,
    I just upgraded to 1.1.5 and everything went well no errors. I'm trying to connect to my control panel and I get the following error:


    Warning: The Exception Writer `iMSCP_Exception_Writer_Browser` was unable to write the following message: `iMSCP_pTemplate::setRootDir expects a valid directory. - at line: 187 in file: /var/www/imscp/gui/library/iMSCP/pTemplate.php` Reason: Unable to find the message.tpl template file - at line: 533 in file: /var/www/imscp/gui/library/iMSCP/pTemplate.php in /var/www/imscp/gui/library/iMSCP/Exception/Handler.php on line 320


    Any ideas?
    Thanks,
    Rob

  • Could it be a file permission error on the /var/www/imscp/gui/library/iMSCP/pTemplate.php ? What permissions does it need by default?


    Thanks,

  • My file permission are:


    root@sosaria:/var/www/imscp/gui/themes/default# ls -alF
    total 44
    dr-xr-x--- 7 vu2000 vu2000 4096 Apr 7 15:10 ./
    dr-xr-x--- 3 vu2000 vu2000 4096 Apr 7 15:10 ../
    dr-xr-x--- 2 vu2000 vu2000 4096 Apr 7 15:10 admin/
    dr-xr-x--- 5 vu2000 vu2000 4096 Apr 7 15:10 assets/
    dr-xr-x--- 2 vu2000 vu2000 4096 Apr 7 15:10 client/
    -r--r----- 1 vu2000 vu2000 1031 Apr 7 15:10 index.tpl
    -r--r----- 1 vu2000 vu2000 1349 Apr 7 15:10 info.php
    -r--r----- 1 vu2000 vu2000 820 Apr 7 15:10 lostpassword.tpl
    -r--r----- 1 vu2000 vu2000 285 Apr 7 15:10 message.tpl
    dr-xr-x--- 2 vu2000 vu2000 4096 Apr 7 15:10 reseller/
    dr-xr-x--- 4 vu2000 vu2000 4096 Apr 7 15:10 shared/
    root@sosaria:/var/www/imscp/gui/themes/default#

  • Hello ;


    Teamviewer?

    badge.php?id=1239063037&bid=2518&key=1747635596&format=png&z=547451206

  • Thanks Nuxwin,
    Got it working. I had a custom theme declared and the upgrade seems to remove this but left the declaration.
    Working now...


    Would be good if the upgrade respected any customisations.

  • Hello ;


    I begin to be really tired to explain the same thing again and again... <X


    For any customization, you must use either (depending of your customization):

    • A plugin
    • A hook file


    We cannot infer and therefore, keep your own modification in place for the following reasons:

    • Sometime, a bugfix involves a template modification (such as in the service templates (postfix, proftpd, apache...)). This explains why during updates, all files are regenerated. If we don't do that, the old template will not be fixed (up to date) and so, the bug will still here. Even more, the installer will break if some needed changes are not in the old template which has been kept.
    • The installer cannot know what files were modified without a template checksum list which should be regenerated each time a template is modified by us, and which must be part of the release. It's something possible but this can lead to a fully broken system for the reasons explained in the first point. Some administrators (i-MSCP user) will argue that the installer should ask if changes must be overridden but I do not want add such option because too many administrators will rely on that option without take time to check if an upstream change / bugfix must be inserted in their own templates. Of course, it's their problem after all if they do something wrong but the problem is that after, they will complain on our forum, and therefore, we will lost a lot of time to finally say: You must know what you are doing if you modify i-MSCP templates...


    With a hook file or plugin, you can inject your own parts in the templates and even modify/remove some parts... To resume, it's not the task of i-MSCP developers to take care about exotic changes made by i-MSCP administrator. Administrator which are modifying i-MSCP should know what they are doing. Using a plugin or hook is the way to go for easy maintenance of exotic changes.

    badge.php?id=1239063037&bid=2518&key=1747635596&format=png&z=547451206

  • I'm not stressed ;)

    badge.php?id=1239063037&bid=2518&key=1747635596&format=png&z=547451206