Hi Guys,
About six months ago I inherited a site running a cms called Immerse (ICMS), it works great and has been a pleasure to work with since. However a number of problems are bugging me, with no support and very little online there is the constant worry of potential security issues that will be very difficult to plug.
I've noticed that Fruml looks to be similar in a lot of ways to Immerse and wanted to find out about the relationship between the systems and whether Fruml could be a potential upgrade path for my site.
Many thanks
Page 1 of 1
Fruml and Immerse
#2
Posted 17 February 2010 - 05:36 PM
Hi!
Fruml is a total rewrite and rethink of Immerse, and while they are superficially quite similar, the underlying code and way in which things work are quite different. While it's possible there may at some point be some sort of upgrade path/ conversion utility, any conversions will require a lot of manual work to rewrite components, plugins etc.
Having said that, Fruml is currently very much beta software, with a lot of functionality still incomplete or not implemented at all yet.
I think that once Fruml gets to a point where it can be used on public sites, it's probably a good idea to see what functionality (components and plugins) the existing site uses and then try to work out how much work it will be to convert it. At that point you could decide whether to (have someone) convert it, or to decide on an alternative solution.
Thanks!
Alex
Fruml is a total rewrite and rethink of Immerse, and while they are superficially quite similar, the underlying code and way in which things work are quite different. While it's possible there may at some point be some sort of upgrade path/ conversion utility, any conversions will require a lot of manual work to rewrite components, plugins etc.
Having said that, Fruml is currently very much beta software, with a lot of functionality still incomplete or not implemented at all yet.
I think that once Fruml gets to a point where it can be used on public sites, it's probably a good idea to see what functionality (components and plugins) the existing site uses and then try to work out how much work it will be to convert it. At that point you could decide whether to (have someone) convert it, or to decide on an alternative solution.
Thanks!
Alex
#3
Posted 17 February 2010 - 06:00 PM
Alex,
I appreciate the reply, how similar are the database structures? I would be happy to help develop/test anything when Fruml is more mature.
My site is fine using Immerse atm however I will need options in the future and anything that makes the migration smoother will be greatly appreciated.
Thanks
I appreciate the reply, how similar are the database structures? I would be happy to help develop/test anything when Fruml is more mature.
My site is fine using Immerse atm however I will need options in the future and anything that makes the migration smoother will be greatly appreciated.
Thanks
#4
Posted 17 February 2010 - 06:25 PM
I think that there are too few sites powered by Immerse to create migration tool. Immerse was good for small sites, so it shall not be a big problem to migrate Immerse site to Fruml. As soon as its functionalities are quite simular, it would be a good point to try to migrate.
#5
Posted 17 February 2010 - 07:40 PM
Hi guys,
The DB structures are very similar. The old icms db shouldn't be too hard to migrate to Fruml, although a migration script will be needed (a direct copy won't work). The problem lies in the differences in the way the content is parsed, how tags are rendered and internal api calls. Those will require rewriting, which could give some problems.
Another big change between the two systems is a move from a multi-lingual system to a multi-site system. Pages in Immerse could have multiple languages, pages in Fruml have no idea about what language they're in. In Fruml, however, we can host multiple sites (which inherently allows multi-lingual setups). The way this works is very different between the two systems. In the worst case scenario, it would mean duplicating sites in order to have multi-lingual stuff work.
If your site only uses one language, that's not a problem at all of course.
Of course, a manual migration is always possible, but it might be a bit time-consuming if you have a very large site with lots of plugins and components. Can you give a quick overview of the functionality in your site and the number of pages etc.?
I understand your need, and if you can indeed help to test any migration scripts, that would be great. However, I think it'll be a while before we're far enough to work on such scripts.
As Far rightly notes, there are not enough Immerse sites out there to warrant a full-blown converter, however it should be possible to write some tools that can aid in an eventual migration.
Thanks!
Alex
The DB structures are very similar. The old icms db shouldn't be too hard to migrate to Fruml, although a migration script will be needed (a direct copy won't work). The problem lies in the differences in the way the content is parsed, how tags are rendered and internal api calls. Those will require rewriting, which could give some problems.
Another big change between the two systems is a move from a multi-lingual system to a multi-site system. Pages in Immerse could have multiple languages, pages in Fruml have no idea about what language they're in. In Fruml, however, we can host multiple sites (which inherently allows multi-lingual setups). The way this works is very different between the two systems. In the worst case scenario, it would mean duplicating sites in order to have multi-lingual stuff work.
If your site only uses one language, that's not a problem at all of course.
Of course, a manual migration is always possible, but it might be a bit time-consuming if you have a very large site with lots of plugins and components. Can you give a quick overview of the functionality in your site and the number of pages etc.?
I understand your need, and if you can indeed help to test any migration scripts, that would be great. However, I think it'll be a while before we're far enough to work on such scripts.
As Far rightly notes, there are not enough Immerse sites out there to warrant a full-blown converter, however it should be possible to write some tools that can aid in an eventual migration.
Thanks!
Alex
#6
Posted 17 February 2010 - 08:05 PM
We use tags such as [link item=""] and I think [component folder=""] but otherwise its mainly just for serving up pages, menus and templates. (If these are no longer supported I can start phasing them out where possible).
We don't use the multi-lingual support (we have just setup a different cms for each language). There are just under 400 pages on the US site - other languages much less.
There is no rush, it's just good to know there is a way forward with Fruml. I would have happy to help with any migration tools or anything that would help the process along.
Many thanks
We don't use the multi-lingual support (we have just setup a different cms for each language). There are just under 400 pages on the US site - other languages much less.
There is no rush, it's just good to know there is a way forward with Fruml. I would have happy to help with any migration tools or anything that would help the process along.
Many thanks
Page 1 of 1

Sign In
Register
Help

MultiQuote
