• Home
  • Get help
  • Ask a question
Last post 4 hours 44 min ago
Posts last week 81
Average response time last week 44 min
All time posts 70378
All time tickets 10862
All time avg. posts per day 20

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.

#9326 – Upgrade to 4sef with k2 component

Posted in ‘Pre-sale questions’
This is a public ticket. Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.
Friday, 16 December 2022 10:31 UTC
lifeintravel

Hi, i'm an happy user of sh404sef and in the process of migrating to joomla 4 i would like to switch from sh404sef to 4sef but i am currently using the k2 component for article management.

Since now k2 has not been updated for years and there is no news of its release for joomla 4, in the future I would like to switch to the native component of joomla but having thousands of articles the process is slow and complex. If I want to install 4sef now, to start migrating urls from sh404sef, can I do that? Or is it not compatible with k2?

Also then with 4sef will I be able to manage the redirect from the k2 url to the joomla one?

Thanks

Friday, 16 December 2022 11:18 UTC
wb_weeblr

Hi

K2 is indeed a very specific case because K2 comes with a dedicated sh404SEF plugin. So it's in fact K2 itself building SEF URLs, and sh404SEF is just recording them. But 4SEF does not use the same plugin format at all, and so K2 would have to update their sh404SEF plugin to the new format. Not sure that's going to happen more than K2 being available for Joomla 4.

If I want to install 4sef now, to start migrating urls from sh404sef, can I do that? Or is it not compatible with k2?

So moving to 4SEF with K2 in itself would be fine, in that 4SEF will definitely build SEF URLs for K2, however these URLs are not going to be the same as those K2 would have built using its sh404SEF plugin.

The way I'd suggest to handle this as follows:

- Using K2, switch to 4SEF. 4SEF will import all existing SEF URLs from your sh404SEF database, therefore all existing URL, for your existing K2 content, will be preserved. As long as you do not purge URLs in 4SEF, you'll be fine. Even if you do so, you can still import again from the sh404SEF tables, and you'll get your existing sh404SEF/K2 URLs in 4SEF.

At this point, if you create new content in K2, they will get URLs, but not using the same URLs pattern as with sh404SEF. The URLs created will be the exact same as if you only had Joomla SEF URLs. Remember, that's just for new content added after switching to 4SEF.

So aside from having less "sexy" URLs, generally that would be fine.

Now moving to regular Joomla content is something else. I don't know how you plan on doing that exactly. Do you have an automated way? some kind of importer? or just manually creating articles and copy/pasting content from K2 to Joomla?

Also then with 4sef will I be able to manage the redirect from the k2 url to the joomla one?

No, 4SEF can't help. 4SEF does only one single thing: create/manage SEF URLs. It has no other feature than that. Its first and foremost purpose is to allow a transition for sh404SEF URLs from J3 to J4.

4SEO - not 4SEF - is what you need to do all SEO work, including redirects. 

Now redirecting from K2 URLs to Joomla URLs may be simple or complicated, it depends on how the content transfer will happen between K2 and Joomla. 

The worst case is if you get totally different URLs and have to do one-to-one redirects for each item.

To avoid that, I'd suggest trying:

- build the same category structure in Joomla than in K2: using 4SEF, you may just obtain about the same Joomla articles SEF URLS as the K2 URLs, meaning you'll just have to delete the K2 URLs for the Joomla article one to take over.

- if not possible to have exactlty the same structure, you could put your transferred articles into a specific top category, such as /new/[redacted]

And therefore you could have just one single redirect for all K2 content, or one per category, similar to:

from: /k2-cat-1/{*}  // K2 URLs

to: /new/k2-cat-1/{*}  // Joomla content URLs with similar name as K2 content

With one rule, or a few, you'll be able to redirect many articles in one go.

Now if you create each joomla article by hand, copying the content, I would then suggest a different approach: 

- create the Joomla article

- view it on the frontend, so that 4SEF creates a URL for it

- go to 4SEF admin, locate the corresponding K2 URL, take not of it and delete it

- manually customize th new article URL to be exactly the same as the corresponding K2 URLs for the same content

That last method is the best by far, because the URLs simply won't change between K2 and Joomla articles and you won't need any redirect. If you can, from an SEO standpoint, this is what you want to do.

Best regards

Yannick Gaultier

weeblr.com / @weeblr

 

 

 

 

 
Friday, 16 December 2022 17:58 UTC
lifeintravel

Thanks Yannick for your super complete answer.

I know K2 is complicated and i hope to find the best solution to migrate. 

It's not that big problem having new urls different from old ones, the important thing is to keep the old ones.

And for sure i will use 4seo with 4sef to have redirects. I don't know how i will switch from k2 to joomla content but manually moving around 5000 articles will be tough... 

Thanks for all the clarifications, now I'm thinking about it a bit and trying to find the courage to start this migration. ;)

Friday, 16 December 2022 18:09 UTC
wb_weeblr

Hi

It's not that big problem having new urls different from old ones, the important thing is to keep the old ones.

That will work as long as you keep using K2. But that won't take you into J4 so yes, there must be a way to move on to Joomla content.

I suggest you search for K2 to Joomla converter. I'm pretty sure I have heard about that. Not sure how comprehensive such a tool is, but at least will get you started.

Best regards

Yannick Gaultier

weeblr.com / @weeblr

 

 
Saturday, 17 December 2022 08:30 UTC
lifeintravel

That will work as long as you keep using K2. But that won't take you into J4 so yes, there must be a way to move on to Joomla content.

Yes, for sure i will migrate from k2 to joomla content using some automations. I'm already speaking with someone about that. 

I got another question: in sh404sef i have a lot of customisation. I mean: i have aliases, i have custom tag Title and tag Description, i use sometimes Social image tag and i put in the raw content code for paywall indexing and FAQ structured data.

Is there a way to migrate them to, i guess, 4seo?

Monday, 19 December 2022 08:53 UTC
wb_weeblr

Hi

Yes, for sure i will migrate from k2 to joomla content using some automations. I'm already speaking with someone about that. 

Just saw a reference to a K2 to Joomla content plugin. It's by Joomlart, available here. Not a recommendation, I have no opinion on it, but someone shared a link to it over the weekend. May be an option.

I got another question: in sh404sef i have a lot of customisation. I mean: i have aliases, i have custom tag Title and tag Description, i use sometimes Social image tag and i put in the raw content code for paywall indexing and FAQ structured data.

Yes, aliases, custom title and descrption and custom sharing image will be imported by 4SEO.

4SEO has raw content code, actually easier and more flexible to use.

The FAQ structured data can either be done using raw content code (not imported), or you can directly use 4SEO structured data rules, something sh404SEF does not have and one of the major reasons to stop sh404SEF and create 4SEO.

Best regards

Yannick Gaultier

weeblr.com / @weeblr

 

 

 
Monday, 19 December 2022 14:39 UTC
lifeintravel

Hi Yannik,

Just saw a reference to a K2 to Joomla content plugin. It's by Joomlart, available here. Not a recommendation, I have no opinion on it, but someone shared a link to it over the weekend. May be an option.

thanks for the suggestion. I'm actually already speaking with joomlart team to understand if they can help me with the migration.

The FAQ structured data can either be done using raw content code (not imported), or you can directly use 4SEO structured data rules, something sh404SEF does not have and one of the major reasons to stop sh404SEF and create 4SEO.

so if i understand correctly from sh404sef everything would be imported except the raw code which i would have to import manually, right? (Or use 4seo structured data rules)

Thanks

Leonardo

Monday, 19 December 2022 14:43 UTC
wb_weeblr

Hi

so if i understand correctly from sh404sef everything would be imported except the raw code which i would have to import manually, right? (Or use 4seo structured data rules)

Pretty much. The most important difference between the two in terms of data is likely to be that sh404SEF can have a description for meta tag and one for social sharing, while 4SEO use the same for both at the moment.

Best regards

Yannick Gaultier

weeblr.com / @weeblr

 

 
Tuesday, 20 December 2022 09:07 UTC
lifeintravel

Pretty much. The most important difference between the two in terms of data is likely to be that sh404SEF can have a description for meta tag and one for social sharing, while 4SEO use the same for both at the moment.

Ok, thanks for your clear explanation. I will move forward and try this migration with the help of joomlart team and using 4sef and 4seo.

 

 

Tuesday, 20 December 2022 09:27 UTC
wb_weeblr

Hi

Cool, hope it'll work out fine. Closing this ticket now, feel free to open a new one as needed. If you do so, please mention this ticket number in the new one.

Best regards

Yannick Gaultier

weeblr.com / @weeblr

 

 
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.