Forum Index   -   Topic Index
   Core Development
     migrate to Cube from XOOPS 2.0.13.2?
Register To Post

Threaded | Newest First Previous Topic | Next Topic | Bottom
Poster Thread
minahito
Posted on: 2006/8/10 23:41
Home away from home
Joined: 2005/10/6
From: Japan
Posts: 398
Re: migrate to Cube from XOOPS 2.0.13.2? Problem Solved
XOOPS2 JP and XOOPS Cube Legacy layer haven't changed the DB-Structure form XOOPS2.

I had not known that xoops.org has changed his DB-Structure. I had thought that the migration is easy. But, if xoops.org has changed his DB-Structure, it's no easy.

XOOPS Cube has the layer for the sub-core. Therefore, if anybody will develop new base module for compatibility with xoops.org, we'll be able to use it. But, that's not easy.

As the first method, we should think to migrate from xoops.org 2.0.x to XOOPS2 JP 2.0.16 JP. For this goal, we need each knowledge.

I had not thought about it before now. But, my stance is a wrong. Sorry.

I'll start to try to migrate from xoops.org to xoops2 JP. Please, let's try it together, and feedback out experience to this forum.


----------------
minahito
Homepage (poor English )

Shine
Posted on: 2006/8/11 0:14
Home away from home
Joined: 2005/12/30
From: Netherlands
Posts: 172
Re: migrate to Cube from XOOPS 2.0.13.2? Problem Solved
As far as I know the xoops version as of 2.0.x can be updraded (changed) to XoopsJP 2.0.x without any problems. There are no DB changes/differences between them.
As of xoops 2.0.14 the change to XoopsJP will not be possible anymore because XOOPS 2.0.14 has done some DB changes in this version. One of them is the way templates are handled.

So changing from xoops 2.0.x - 2.0.13.2 to XoopsJP 2.0.x.16 JP can be done without any problems.

Grtz., Shine
gigamaster
Posted on: 2006/8/12 0:16
Home away from home
Joined: 2005/12/30
From: Switzerland
Posts: 1227
Re: migrate to Cube from XOOPS 2.0.13.2? Problem Solved
Xoops.org is missing a legacy strategy which result in a problematic development
- alike 2.2.x - a misunderstood or lack of interoperability and dev knowledge.

Xoops Cube instead adopt what seems to be a legacy system (base).
And if it's a form of backward compatibility it would means that an application
created using an earlier version of xoops will run on a later version.

That way, in a near future, users may expect a friendly interface within XC 2.1 to upgrade
from old/other xoops versions. While that, Xoops Cube with its own and improved
delegate/preload mechanism, will be able to aim an automated business process.

But , just now its a messy situation, without modules working on 2.0.x, 2.2.x, 2.16 or 2.1
« 1 2 (3)
Threaded | Newest First Previous Topic | Next Topic | Top

Register To Post
 

Who's Online
26 user(s) are online (12 user(s) are browsing Forums)

Members: 0
Guests: 26

more...

Welcome | News | Overview | Documentation | Forum | Tutorialstop
Brasilian | French | German | Greek | Japanese | Korean | Russian | T-Chinese
Powered by XOOPS Cube © 2001-2011 The XOOPS Cube Project