Results 1 to 10 of 10

Thread: How would I install the evolution skin?

  1. #1
    Join Date
    Dec 2017
    Posts
    2

    How would I install the evolution skin?

    I grabbed the latest Evolution skin (3 december 2017) and tried to install it both automatically and manually.

    Via the Web-interface, trying to upload the skin (.tar.gz file as downloaded), I got this message:

    Error untarring the archive: gzip: stdin: not in gzip format /bin/tar: Child returned status 1 /bin/tar: Error is not recoverable: exiting now
    The skin package did not install properly. Either there were files missing, or their permissions were incorrectly set
    when I copied all skin files into admin/skins/evo3dec/ , I was able to install the skin and select it in the web interface. However, after loading the skin I got a full blank page..

    So both ways seem to fail me.

    What is the correct way to install the skin successfully?

  2. #2
    Join Date
    Dec 2017
    Posts
    2
    Seriously, no reply in a week..?

  3. #3
    Join Date
    Apr 2005
    Location
    GMT +7.00
    Posts
    11,680
    Feel free to open a ticket with Directadmin support then: https://tickets.directadmin.com/

  4. #4
    Join Date
    Nov 2012
    Posts
    38
    To be fair it does state on the Evolution page that the DA team are discouraging submitting tickets for the Evolution skin at this point.

    I am also experiencing the same issue as OP with the blank white page. Looking at console its not able to load several JS scripts. They are present on the file system and permissions for diradmin set accordingly on the whole evolution skin dir, but these scripts return a 404 when loaded with HTTP or in my case forced HTTPS login.

    assets/login.js
    assets/vendors.js

    The skin worked when I applied it while already logged in, but once I logged out and then tried to login again, I just get the white page when trying to auth.

  5. #5
    Thanks for the report.
    We did address an /assets load issue for both Two-Factor Auth, and Security Questions 3 days ago.
    Ensure you've got the latest binaries, and let us know if the problem persists.

    I'd recommend running DA in debug mode to let us know what errors DA is throwing to generate the 404.

    John

  6. #6
    Join Date
    Nov 2012
    Posts
    38
    Thanks. Running the pre-release binaries fixes the 404 errors on those paths.

    I am however still getting console errors when logging in, I do have 2FA enabled.

    Code:
    TypeError: Cannot read property 'LOST_PASSWORD' of undefined
        at a.n (login.js?ver=1fae57397f35e5c3a84dbd12c488186a28487195:1)
        at a.e._render (vendors.js?ver=1fae57397f35e5c3a84dbd12c488186a28487195:1)
        at a.r (vendors.js?ver=1fae57397f35e5c3a84dbd12c488186a28487195:1)
        at ge.get (vendors.js?ver=1fae57397f35e5c3a84dbd12c488186a28487195:1)
        at new ge (vendors.js?ver=1fae57397f35e5c3a84dbd12c488186a28487195:1)
        at mountComponent (vendors.js?ver=1fae57397f35e5c3a84dbd12c488186a28487195:1)
        at a.Vue$3.$mount (vendors.js?ver=1fae57397f35e5c3a84dbd12c488186a28487195:1)
        at a.Vue$3.$mount (vendors.js?ver=1fae57397f35e5c3a84dbd12c488186a28487195:1)
        at init (vendors.js?ver=1fae57397f35e5c3a84dbd12c488186a28487195:1)
        at createComponent (vendors.js?ver=1fae57397f35e5c3a84dbd12c488186a28487195:1)
    I'm running the Evolution skin that has timestamps of 6th January. The skins works if you can get past the login part.

    Interestingly, I don't see the login form displayed on the demo site? Do I need to make any further config changes to set this login page?
    Last edited by James2k; 01-07-2018 at 03:41 AM.

  7. #7
    Join Date
    Aug 2015
    Posts
    164
    You need to address some rules in Directadmin.conf from enhanced to evolution.

    demodocsroot=./data/skins/evolution
    docsroot=./data/skins/evolution
    Then it works (maybe hit shift+F5 in your browser once).

    Kind regards, Fred

  8. #8
    Join Date
    Nov 2012
    Posts
    38
    Already set, still shows old login, cached cleared:

    Code:
    grep docsroot* /usr/local/directadmin/conf/directadmin.conf
    demodocsroot=./data/skins/evolution
    docsroot=./data/skins/evolution
    Edit for some reason the old path of ./data/skins/enhanced was still set on the input field in /admin/settings, changing that finally makes the new login page show up!
    Last edited by James2k; 01-07-2018 at 03:52 AM.

  9. #9
    Join Date
    Aug 2015
    Posts
    164
    Did you install the latest DA pre-release binaries?
    To install it or update it:
    https://help.directadmin.com/item.php?id=408

  10. #10
    Join Date
    Nov 2012
    Posts
    38
    Yes I did. I've just found the problem, even though evolution path was set in the directadmin.conf the field in the GUI still had ./data/skins/enhanced set within the /admin/settings page. Changing that sets the correct login form and fixes the issue with the LOST_PASSWORD variable because it was using a mixture of the old login page and new skin.

    Thanks for the help.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •