[Fixed in r1709] Importing Joomfish data

Hello

the SPupgrade is for J1.5 --> J2.5
but it also maintains IDs

no direct/indirect relation between FLEXIcontent and SP-upgrade

Ok but hang on... you're saying Jupgrade changes article IDs, but I don't think that's right. As far as I can see in my upgrade, they stay the same.

As I understood, the problem was in the fact that importing content to flexicontent changes article IDs, in joomla 1.5, so it's flexicontent that can't connect articles to joomfish translations?

Hello,

-- during J1.5 import procedure new content items are created , so new content ids can not be related to Joomfish data

-- about JUpgrade it does change the IDs , there is a newer version that does not ?

Hm, I don't know, I'm using JUpgrade version 2.5.2. I've used it on many sites, it never changed any article IDs?

It is actually even possible to use the new version of joomfish on an upgraded joomla 2.5 site - with old joomfish tables, in a so-called "old mode". That would never work if IDs changed.

(unfortunately the new joomfish is too buggy otherwise to be used for real, which is why I'm trying to get rid of it)

ggppdk wrote: -- about JUpgrade it does change the IDs , there is a newer version that does not ?

Yes, I read in a different forum that they have fixed this! I think even in the JoomFish forum.
Rooney

teapot wrote: I'm not sure I understood what you mean.
SP upgrade is something like JUpgrade, except commercial?

Where does flexicontent come in all that?

Yes. SPUpgrade is a migration tool like JUpgrade and has been much better than JUpgrade. Don't know ho it is now.

FlexiContent comes in if you make translations. It looks which translations are available in the Joomfish tables for a given item id and creates an new article that is associated with the original item as translation.

Am I right ggppdk?

Rooney