• Home
  • Get help
  • Ask a question
Last post 2 hours 28 min ago
Posts last week 110
Average response time last week 29 min
All time posts 67418
All time tickets 10424
All time avg. posts per day 21

Helpdesk is open from Monday through Friday CET

Please create an (free) account to post any question in the support area.
Please check the development versions area. Look at the changelog, maybe your specific problem has been resolved already!
All tickets are private and they cannot be viewed by anyone. We have made public only a few tickets that we found helpful, after removing private information from them.

#4297 – Migration from Joomla 2.5 to 3.5

Posted in ‘sh404SEF’
This is a public ticket. Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.
Thursday, 09 November 2017 08:15 UTC
[email protected]
Hello,

I have a Joomla installation with SH404 Urls in Joomal 2.5.

Now I transferred all arrticles to a new installation (new DB) with Joomla 3.5.
All articels and menus have the same id like before.

How can I migrate SH404?

Thanks! 
Thursday, 09 November 2017 09:04 UTC
wb_weeblr
Hi

What do you want to migrate? do you have custom URLs, custom metadata?

As Joomla 2.5 -> Joomla 3.5 is not a migration but just an update, normally this situation does not occur.

Rgds
 
Thursday, 09 November 2017 09:26 UTC
[email protected]
Hi,

the whole old SH404 database, custom urls, custom metadata... yes!

Thursday, 09 November 2017 09:57 UTC
wb_weeblr
Hi

There are 2 ways to do that, depending on your skills with database handling

1 - DB copies

- copy the DB tables
- install latest sh404SEF
- set exactly the same parameters

2 - Import/export

- install sh404SEF
- set exactly same parameters
- In source site, use export buttons on SEF URLs, Short URLs and Aliases to create export files
- on target site, use import buttons on the same pages to import back the data.

1 is probably faster.

Rgds
 
Friday, 24 November 2017 05:34 UTC
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.
This ticket is closed, therefore read-only. You can no longer reply to it. If you need to provide more information, please open a new ticket and mention this ticket's number.