Used the Akeeba pro backup to move site to new server....

Items and k2 menus do not work on new server when the Joomla "sef" is enabled...

Mod-rewrite is on,and the .htaccess file is in place (default) joomla, with no editing...

Is there some additional process that must be done for updating? Do I need to manually rewrite the "alias" for items and menus?

gertrudezachary.com

 

...sefs urls are off....mod-rerite on...add url suffixes off...

Try to set real livesite parameter in configuration.php, if you didn´t done that.

and clean your cache (even better, don't include it in your Akeeba backup, solves many problems).

The cache is never included in the backup set ;) One of the magic tricks Akeeba Backup does, for your convenience, is to automatically exclude the files and directories inside your cache and tmp directories.

Damn you Nikos and your Google Alerts.   You just can't ignore it when I say stupid things can you! ;-)

 

I had forgotten that you had pre-excluded these folders (I now see the red vs. yellow selection).

 

--Olivier

 
Nicholas K. Dionysopoulos said:

The cache is never included in the backup set ;) One of the magic tricks Akeeba Backup does, for your convenience, is to automatically exclude the files and directories inside your cache and tmp directories.

thanks for the responses...I have updated the "livesite" for three or four of the moved joomla sites on the new server...

However, the sites still will not function correctly when the sef url option is enabled...apparently it has nothing to do with K2 menus or K2 items...I can open the homepage, but when selecting ANY menu item, whether it is joomla article or K2 item, or blog category (whatever) it will give me a 404 error...

Only unique thing that i can spot is that the config.php file is 444 permission and not 644 like every other file on the site...is this default and is this configured this way through the backup (i know this is not akeeba), but I have a thread going here, and maybe nicholas will just appear, gazing at my dilemma...

Rochen is the host

I don't think that the file being 444 should affect the way your site runs (I've checked and some of my sites have it also in 444, some in 644 without issues).  

 

Sorry to ask the obvious question but since your config.php file is indeed 444, are you sure that when you saved your livesite var, it was actually updated correctly? (you can check in Help->System Info->Configuration File

 

--Olivier

yes, i had to change permissions first to edit, then re-change back to 444...

Where is one of those greek genius guys when you need them...

Wait, i'm sorry, apparently you are of greek heritage also. (if not so, please take no offense)

Thanks for your responses. Rochen has no answer for this either....

No sweat, I'm 1/2 French, 1/2 Greek so I guess I'm just a demi-genius ;-)

 

Can you show us an example of the URL on your local working site vs. the one that the live site is giving you?

 

Not sure why this is happening but couple of thoughts:

 

* Can you do a hardcoded redirect in the .htaccess file to see if mod_rewrite is actually working?

* Try to move the Akeeba archive that you used on that server to another server to see if this was server related or maybe something to do with the backup itself?

 

--Olivier

Can you explain "hardcoded redirect in the .htaccess file to see if mod_rewrite is actually working?" ??

Would that be a "?" added to the htaccess file? Please give me an example and I will try this on a not important site...

url for joomla sites that has sef url disabled...studiosevenproductions.com...douglasmagnus.com...

See what you think for those...

Do this on the server that you have a problem with:

 

1. Create a valid html page, call it testredirect.html and upload it to the root of your Joomla install

2. in your .htaccess file (backup first), type the following at the bottom of the file:

 

Redirect 301 /test123.html http://www.[yourdomainname]/testredirect.html

 

3. Save

4. In your browser, enter: 
http://www.[yourdomainname]/test123.html and see if you get redirected to 

http://www.[yourdomainname]/testredirect.html

 

If that works, at least we know that your mod_rewrite works in that directory (and you can delete the file + changes)

 

When I was asking for the url, I meant on the home page of the local site that works, hover over a link and copy the URL then on the same live site that you have problems with, do the same thing.  Are these URLs exactly the same?

 

--Olivier

Thanks for the test...I tried it and it worked fine....so I guess the mod-rewrite is working...have a good weekend....

Olivier Karfis said:
Do this on the server that you have a problem with:

 

1. Create a valid html page, call it testredirect.html and upload it to the root of your Joomla install

2. in your .htaccess file (backup first), type the following at the bottom of the file:

 

Redirect 301 /test123.html http://www.[yourdomainname]/testredirect.html

 

3. Save

4. In your browser, enter:  http://www.[yourdomainname]/test123.html and see if you get redirected to 

http://www.[yourdomainname]/testredirect.html

 

If that works, at least we know that your mod_rewrite works in that directory (and you can delete the file + changes)

 

When I was asking for the url, I meant on the home page of the local site that works, hover over a link and copy the URL then on the same live site that you have problems with, do the same thing.  Are these URLs exactly the same?

 

--Olivier

I have found the problem...

Thanks "BBC", for your response, because that was the correct thing to do...but I set the "livesite parameter" with http://mysite.com...this was not working... when I added the "www", making the parameter "http://www.mysite.com"...it worked...well sorta.

But, not until I realized that the default rochen "new account" will leave a .htaccess file that is all "frontpage directives"...??? I discovered this when trying the "redirect" test suggested by Oliver Karfis, the demi-genius...I did get the re-direct to work, and replaced the .htaccess files, but it took some backtracking to realize I needed the "www" in the 'live site".

The restoration process did not overwrite that file...

Thanks for all the suggestions and insights...