Support

Site Restoration

#24322 Site Move Using KickStart - System Requirements

Posted in ‘Site restoration’
This is a public ticket

Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.

Environment Information

PHP version
n/a
CMS Type
Other
CMS Version
n/a
Backup Tool Version
n/a
Kickstart version
n/a

Latest post by on Thursday, 03 March 2016 17:20 CST

kentmorrison
 Nicholas,
I wanted to be sure that you were aware of this issue:

In the course of developing a new site at one location, then moving it to new hosting, I ran int this issue.
I restored to the new server and the kickstart requirements page indicated that all parameters were OK.
The files extracted, the database restored.
There were some configuration elements that had to be changed regarding db and host names, of course, but I paid attention to those per the site move instructions.

The restored (moved) site did not display correctly, and I spent hours trying to figure it out.
And there was precious little info in the debug to help with diagnosing it.
One module was displaying, and no other elements of the template, though I could login to the backend OK.
I spent many hours reading your troubleshooting docs, and others as well.

It appeared to be a PHP configuration issue, but I could not track it down.
Finally I started a support ticket with the hosting techs, and overnight they worked on it.

This morning I awoke to find their response: GD was not installed.
I was frustrated of course, since this cost me 6 hours of banging my head on the problem.

Do you think that it would be appropriate to have the GD as one of the system requirements in the kickstart checklist ?
I know that, for my part, I would have been grateful if it notified me of that deficiency in my new server config.

Thanks for all of your excellent products, and for you very professional and congenial support.
Regards,
Kent

nicholas
Akeeba Staff
Manager
No, it shouldn't be in ANGIE's list of required parameters. Please keep in mind that the required and suggested PHP settings we display in ANGIE are the same ones Joomla! itself required. The GD library is not a core requirement. Most likely it's a requirement of a third party software you have installed (presumably a plugin that performs image resizing?).

We just can't put any third party extension's requirements as an ANGIE required setting. If we did that we'd end up with pretty much all PHP extensions being required – not quite a helpful or even meaningful situation for our users :(

Nicholas K. Dionysopoulos

Lead Developer and Director

πŸ‡¬πŸ‡·Greek: native πŸ‡¬πŸ‡§English: excellent πŸ‡«πŸ‡·French: basic β€’ πŸ• My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

kentmorrison
ALSO just found out that PHP mbstring module was not installed at time of server build.
This was vexing because after 3 re-installs of Akeeba Backup Pro, I was still getting the "complexifier.php" error in backup.

FOUND that diagnostic in the forum, so THANKS for keeping a good set of trouble docs posted.

Regards,
Kent

nicholas
Akeeba Staff
Manager
Hehe! The mbstring requirement is displayed in ANGIE. This further proves the point made by UX designers, i.e. that a long list of stuff is ultimately ignored by users.

FWIW I've forked the Complexify package and made a version that doesn't rely on mbstring to work. It's up for inclusion in the next version of Akeeba Backup.

Nicholas K. Dionysopoulos

Lead Developer and Director

πŸ‡¬πŸ‡·Greek: native πŸ‡¬πŸ‡§English: excellent πŸ‡«πŸ‡·French: basic β€’ πŸ• My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

kentmorrison
I believe you, and do not doubt that I failed to see mbstring in Angie.
The reason that I did not see it is because it was green, I guess.

That does not make any sense though, since I restored to the new server BEFORE adding mbstring, and the flags were green.
Then I restored and Akeeba Admin Tools worked.
But when I went to the Akeeba Backup Pro menu, I got the white screen and had to turn on the full system error reporting to see the complexify error.

I guess I am saying that Site Move using Akeeba Backup Pro is not as straightforward as indicated.
Perhaps the problem is with the HOWTO for restoring to a new server. (site move)

I'm a pretty good technical writer, would you like to trade some license credit for a fresh write-up a HOWTO:
"Site Move Using Akeeba Backup Pro and KickStart"

Regards,
Kent

nicholas
Akeeba Staff
Manager
It is absolutely straightforward BUT do keep in mind that we cannot possibly tell you what are the minimum requirements of every single version of each of the 15,000+ extensions that have been published on the JED in the last ten years, all the third party PHP scripts they integrate with or, even worse, all the custom code ever written and not JED listed.

I would like to remind you that despite what you think you just didn't see the mbstring requirement being RED and a message above it telling you that even though it's red some clients reported that Joomla! runs, therefore we are NOT going to block the restoration. So the information you need is right there, in front of your eyes, you just have to read the information on your screen.


Do you really need a how-to to tell you to read the information presented to you in the first page of ANGIE? If you do, please watch our video tutorial on transferring a site.

Nicholas K. Dionysopoulos

Lead Developer and Director

πŸ‡¬πŸ‡·Greek: native πŸ‡¬πŸ‡§English: excellent πŸ‡«πŸ‡·French: basic β€’ πŸ• My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

System Task
system
This ticket has been automatically closed. All tickets which have been inactive for a long time are automatically closed. If you believe that this ticket was closed in error, please contact us.

Support Information

Working hours: We are open Monday to Friday, 9am to 7pm Cyprus timezone (EET / EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets outside of our working hours, but we cannot respond to them until we're back at the office.

Support policy: We would like to kindly inform you that when using our support you have already agreed to the Support Policy which is part of our Terms of Service. Thank you for your understanding and for helping us help you!