Made today a sample installation.
What is fine the installation process is easy and simple . good for endusers.
But what I have seen is - installation is made in a local XAMPP:
1. the ongoing process needed approx. 20 seconds - only the spinning wheel was visible.
I thought first, the process hangs, but was finally okay.
Instead of having only this speinning wheel, I would recommend some dynamic timeline or percent
2. automatic delete of the install folder
The folder itself could be not deleted, but is already fixed at GitHub - okay.
But from ym point of view (as dev) I do not like to delete this folder.
More to rename (e.g. _install or _install_and_timestamp) and setting permissions to 0644
With this I can get back whenever i need it (and can check on customers installation what was used).
3. store and login details: the installer should have the possibility to get these by email (during the last 17 years with unlimited Joomla installations - and other - I got several help cries: I forgot my login data .. or they did not knew what they have written .. or a typo during install
4. installation language: same as with OC - only English!
should have a select or choice option to select which language for installation.
Could be automated via API from Crowdin - for example - if we do not want to make the package too big.
Just a few assumptions ..
What is fine the installation process is easy and simple . good for endusers.
But what I have seen is - installation is made in a local XAMPP:
1. the ongoing process needed approx. 20 seconds - only the spinning wheel was visible.
I thought first, the process hangs, but was finally okay.
Instead of having only this speinning wheel, I would recommend some dynamic timeline or percent
2. automatic delete of the install folder
The folder itself could be not deleted, but is already fixed at GitHub - okay.
But from ym point of view (as dev) I do not like to delete this folder.
More to rename (e.g. _install or _install_and_timestamp) and setting permissions to 0644
With this I can get back whenever i need it (and can check on customers installation what was used).
3. store and login details: the installer should have the possibility to get these by email (during the last 17 years with unlimited Joomla installations - and other - I got several help cries: I forgot my login data .. or they did not knew what they have written .. or a typo during install
4. installation language: same as with OC - only English!
should have a select or choice option to select which language for installation.
Could be automated via API from Crowdin - for example - if we do not want to make the package too big.
Just a few assumptions ..
Share this post:
Responses (1)
-
Accepted Answer
Hi Michael,
1) The speed depends on the speed of the server, local or web, but improving the process line must be considered.
2) I agree with you from a dev point of view but not as user. I mean users want to install and let it go.
3) Yes for username but not for password, especially in 2015. Today, serious web sites don't send the password even in the reminder email, they send you a link.
4) Totally agree. It should be a task of the Translation Team
Regards
Your Reply
Please login to post a reply
You will need to be logged in to be able to post a reply. Login using the form on the right or register an account if you are new here.
Register Here »