Support

 Hi there.

I have just switched to a new host on a fully configurable Cloud Rack service by the biggest provider in Denmark, TDC.

I have created a LAMP server running same specs as our old server.

We have a site at www.fazeday.dk wich is a joomla site with a jomsocial extension.
We have backed it all up using Akeeba Backup professional 4.4.3.

We installed kickstart on new server and the restoration process worked fine with all requirements met.
Database and all was input correct.
However, the site is missing the complete CSS structure.

We have tried to restore the site on managed hosts by other providers, here it worked fine - but we need to make it work on our own new server wich is much faster and larger.

I fear that something is missing in the setup of our new server.
I have NO experience in server setup - i HAVE seen in the support tickets that some have had the same problem and they were resolved - but i don't understand the command lines you are talking about.

Can you please help me setting this up ? I will of course provide you with all the access you need.

You can visit our current site at www.fazeday.dk to see what it is supposed to look like.

Our akeeba clone where the site is restores is located at 178.23.244.44.

As you can see - the CSS is not applied.

Thank you.

Best regards,

Danny Grønbech.
Fazeday Corporation Inc.

Danny,

Your restored site is not there, just the jpa file. I think I know what you were seeing. You need to check the $live_site variable in your configuration.php file. Normally it is blank:

public $live_site = '';

But some servers require the url to the root of the site. You should include the protocol (http:// or https://) but not include the trailing slash. You should also include any folder names required for your site, http://www.mysite.com/joomla.

Hi Dale.

Please look again on 178.23.244.44.

i was making backup with the new akeeba pro i just purchased to see if that improved over the free version.

Perhaps files were not uploaded 100% as you looked.

We have the index in the root directory, not in /joomla and so on - just as you see on www.fazeday.dk.

That is what I expected. Check your $live_site variable. To change it you will need to edit the configuration.php file directly, you can not get to it from within Joomla!.

If it is already blank, try it with

public $live_site = 'https://178.23.244.44';

You will need to update this again when you take your site live with the domain name.

The RewriteBase setting in .htaccess can do this too. Mostly RewriteBase will affect your menu and links, it usually leaves the home page intact.

This is not a backup or restore error, it is simply an adjustment that needs to be made between the two servers.

Hi Dale.

I now found at updated the blank variable to: public $live_site = 'https://178.23.244.44';

This had no effect.

I don't undertand what you mean by RewriteBase in .htacess - what do you mean i have to alter there ?

I found this in the Developer tools console in Chrome:

http://178.23.244.44/media/plg_jchoptimize/assets3/nz/30/0/813b2b047cab4433a01d4bd99689973e.css Failed to load resource: the server responded with a status of 404 (Not Found)

It appears to be related to JCH Optimize. Let's temporarily disable that plugin and see if that fixes the problem.

I disabled JCH Optimize and there is no effect.

If i press one of the links on the restored site - for example "level 1" the page setup somewhat better - and the html banners are there - but the banners stored in joomla/images folder are not there - could this be an issue of not changing the paths or so ?

The $live_site variable should start with http:// not https://.

I thought I saw https:// on the site, but that is not working. Now I can't figure out why I thought it should be https://.

Hi Dale.

We do run https but that is first after we log in, the frontpage is just http.

Anyway, i changed it to public $live_site = 'http://178.23.244.44';

It has no effect.

I just tried to see what is happening - to upload the same configuration.php from the old site to the new and overwrite it - and now it works.

This is strange - should the original configuration.php not be preserved through akeeba and be exactly the same ?

Wow! There are elements of the configuration.php file that are updated by the restore process because the paths would be wrong for the new server. For example, the log and tmp folder locations should be updated. But I can't see anything in there that would do what we were seeing.

I'm glad you got it working, but I can't explain why.

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.