Hi felixkat,
I've done a migration yesterday, using your very helpful steps in post#27.
I've started a wiki based on your post as long as the impressions are present.
http://fabrikar.com/wiki/index.php/3.x_Migrating_from_Joomla1.5.20+/Fabrik2.1
jUpgrade has some issues but fabrik upgrade is running very well (including joined tables, repeated groups, multiple content plugins).
But I'm still testing.
One issue I found is migrating visualisations, params aren't converted to json.
Thanks for this Troester, I'll started editing it and modifying where necessary.
I'll look into the visualisations params as well.
the main problem I see with your tutorial, troester, is that it will probably take days (at least...) before one figures everything up and has a working site once again.
Which I guess is the point of jupgrade creating a new site oppose to upgrading the existing one. It allows you to make all the tweaks, set permissions for the 2.5 standard, modify templates.. etc etc.
No one should ever be upgrading live sites, they should always have at least a development site and optionally a test site as well.
I think Fabrik will be one of the very few products that jupgrade will never be 100% with. This is simply due to the type of product Fabrik is and not a fault with either products.
The main issue arises because of the prefixes, Fabrik has to store your 'full backend table names' as it is interacting with them. If anybody has a site that is linking to any table with a prefix it's going to fail on upgrade. An example of this is the Joomla user table, Joomla 1.5 will always have this as jos_users unless it has been changed. When you migrate to 2.5 it will have a different prefix, thereby Fabrik will no longer find it.
I don't think there is anyway around this as the Fabrik doesn't know about any upgrade and simply uses it's stored information. This is why it's recommended to change your prefix before the migration and then migrate to the prefix of jos_
felix, besides the tutorial to update joomla/fabrik, maybe you or someone would make a tutorial about transferring custom templates to the new Fabrik3 model?
The template format is different as well as you have discovered but again there's not too much we can do with that. Unless people are using a completely standard J! 1.5 template which has a 2.5 version there are always going to be tweaks needed. The same works with Fabrik, I believe the way forward would be to use the default Fabrik templates to test everything works and then gradually migrate your Fabrik 2.x templates across.
I have taken the comment on board though and will include this in the documentation.
Another thing to bear in mind is that Fabrik 3.x is still at Beta stage and there are still a lot of code changes taking place. These changes are in the core and plugins. All these changes may or may not impact the Fabrik upgrade script but we can only rely on user feedback to correct where necessary. So with that said I do appreicate all the feedback so far.
)
