Page 1 of 1

Migrate from CGBlog to LISE

Posted: Thu Mar 04, 2021 1:35 pm
by rotezecke
Hi, the module forking project page mentions that, among others, CGBlog could be replaced with LISE. I can probably figure out how to set up templates and hopefully pretty URLs but I don't see an easy way to migrate my existing blog articles to LISE. Seems like data needs injecting into two different tables, one line per blog article in modele_liseInstance_item table, and at least one line per field definition in modele_liseInstance_fieldval. Has anyone written a migration script and cares to share it? it would likely require modifications but a starting point would be nice. cheers

Re: Migrate from CGBlog to LISE

Posted: Thu Mar 04, 2021 1:46 pm
by Jo Morg
We are in the process of making a tutorial for that purpose, which will probably be useful for other modules too. Of course, one of the steps will be always the creation of the custom fields and that for now should be done manually. For most cases there won't be that many fields that would make that an impossible task. The rest of the steps would be to export via a custom smarty template the items (news or other) to a CSV file in a format that LISE can import.
Since the modules listed there won't just stop working I think it will be worthwhile to wait a bit for the tutorial :)

Re: Migrate from CGBlog to LISE

Posted: Thu Mar 04, 2021 10:54 pm
by JamesT
I'm interested in this too. I'd also like to replace Banners with LISE as the page suggests, but I have no experience of LISE and I'm having a hard time working out how to replicate the functionality of Banners in LISE.

Hopefully the tutorial will cover this too?

Re: Migrate from CGBlog to LISE

Posted: Thu Mar 11, 2021 12:42 pm
by JamesT
Update: I've managed to get to grips with LISE and replace Banners and CGBlog with it. Existing content was minimal and could be manually transferred.

Re: Migrate from CGBlog to LISE

Posted: Thu Mar 11, 2021 4:15 pm
by Rolf
I have a tutorial for moving Company Directory content to LISE 99% ready (others will follow)
Only need to port a few of my sites to test it.
After that is will become available for you at my https://cmscanbesimple.org

Re: Migrate from CGBlog to LISE

Posted: Sun Mar 28, 2021 8:52 pm
by Rolf

Re: Migrate from CGBlog to LISE

Posted: Wed Jul 05, 2023 1:30 pm
by creopard
On new installations it's not possible to install CGBlog any more:
The module CGSimpleSmarty (1.9) could not be found in the repository, but it is a dependency.
This module may no longer be available in the module repository, or may require manual installation.
Please ensure that it is installed correctly, then retry this operation.
Is there a guide on how to migrate from CGBlog to LISE yet?

Re: Migrate from CGBlog to LISE

Posted: Wed Jul 05, 2023 1:41 pm
by DIGI3
You can still get CGSimpleSmarty from the forge, http://dev.cmsmadesimple.org/projects/cgsimplesmarty
Modules that haven't been updated in 5 years are dropped from Module Manager.

There's no separate tutorial for CGBlog > LISE, but the one posted above for CD can be easily adapted.

Re: Migrate from CGBlog to LISE

Posted: Thu Jul 06, 2023 6:47 am
by creopard
Thanks for letting me know.

Maybe you want to reconsider adding "CGSimpleSmarty" to the Module Manager again, as this would improve the "onboarding process" for news users.
(It's not very intuitive to upload the module manually if you start freshly with CMSMS.)

Re: Migrate from CGBlog to LISE

Posted: Thu Jul 06, 2023 7:03 am
by JamesT
creopard wrote: Thu Jul 06, 2023 6:47 amMaybe you want to reconsider adding "CGSimpleSmarty" to the Module Manager again, as this would improve the "onboarding process" for news users.
Given that CGSimpleSmarty has been unsupported for years, it would make more sense to drop all packages from Module Manager which use it as a dependency.

Re: Migrate from CGBlog to LISE

Posted: Thu Jul 06, 2023 1:40 pm
by DIGI3
We don't pick and choose which third-party modules show in module manager, it's up to the developers who maintain them. CG did not give us permission to use or maintain his modules when he abandoned them. See https://www.cmsmadesimple.org/module-forking-project for related information.