CMS Made Simple Forums

Hi there.

I'm in the process of updating all the sites I build and manage and want to use the latest version(s). So I'm upgrading from 2.2.7 to 2.2.10 and php to version PHP 7.3.

I already upgraded several sites and I'm now upgrading the first site using Lise (it's my own site).

But it seems Lise is not PHP 7.3 compatible or/and not cmsms 2.2.10 compatible.

Is there an alternative to Lise ?

I'm using Lise to show the domains and the invoices from/for my customers. Customers can login using FriontEndUsers and click MySites. The they see the domains they own and al the invoices.

I realy like Lise. It is very flexible.

I'm in the proces of upgrade more sites that use Lise.
Would be nice if Lise was updated and was compatible with cmsms 2.2.10 and 2.3 and PHP 7.3.

Please advice.

TIA

For the moment LISE is not yet PHP 7.2+ compatible. LISE should however work perfectly with CMSMS 2.2.x.
Several events have conditioned the progress of LISE and other modules that I'm responsible or co-responsible for, but mainly my health issues. I had surgery a little over a fortnight ago, and things are looking good so I'm trying to pick up things from where I left them.
LISE has atm many private versions that need to be merged into a single one, needs to be CMSMS 2.3 ready and PHP 7.2+ ready. It's a single process encompassing those 3 steps. No release is going to be made prior to that process being complete. Also, there may be no backwards compatibility of LISE with CMSMS 2.2.x, although I'm not yet ready to say it wiht a reasonable amount of certainty.
The list of modules that I'm in the process of updating/improving is not small but I'll try to have releases of some of the most used ones as soon as humanly possible given the circumstances.
So I would recommend sticking to PHP 7.1.x for a while until new releases are available.

Thanks you for the quick answer. Take your time to recover. I Will wait for the next release.

Hello, is there an alternative for LISE at the time. I have two, my own templates http://serwer.compsoul.pl/kunstbau/ and http://serwer.compsoul.pl/motnet/ and I have to upgrade them. Form Builder module was replaced by CG module, but for LISE I can't find antthing. I think about Made Simple, WP have better suport and comunnity but it is sooooooo not simple. Package with best/needed modules will be a good ideas. Now when I am making templates (probably only me in Poland), I am not sure if I instal module will be actual after year when I update PHP version.

Why do you need a replacement for LISE, did you not read the author's response in the post directly above yours?

If I sells templates, I can't tell to my client: "Listen, we must wait to update LISE module". I need to have a package of modules compatible with latest CMS versions.

It is compatible with the latest version, I'm using it on dozens of 2.2.10 sites. It's not compatible with the beta yet, but you shouldn't be using the beta on your client sites.

I can't selling template in beta version, also I can't selling templates incompatible with latest PHP version.

Cyc wrote:If I sells templates, I can't tell to my client: "Listen, we must wait to update LISE module". I need to have a package of modules compatible with latest CMS versions.

You can also pay the module developer to speed up things...

CMSMS 2.3 will have a much improved method of distributing themes and templates.

Rolf wrote:

Cyc wrote:If I sells templates, I can't tell to my client: "Listen, we must wait to update LISE module". I need to have a package of modules compatible with latest CMS versions.

You can also pay the module developer to speed up things...

I thought CMSMS is free... If support will be worth, with good and supported module pack (like a PS or better) I will pay. Now when the most needed modules is not upgrade by two years, and this module is not replacment, how can I pay for this? Mniej pretensji więcej pracy a pieniądze będą.

It is free, but a lot of us who make money using it will sponsor the module developers to make improvements, add features, or just to keep maintaining their modules.

The CMSMS team can't force third-party module developers to do anything, we're just offering you a suggestion that may get you the result you want.

I know your situation is difficult. Core CMS MS is very good, to my mind its the best, but CMS need to have a module pack recommended and supported by DEV CORE. Other problem its bootstrap and jQuery cancer in default templates. DEV CORE need UX and UI and front end developer with good skills.

https://developers.google.com/speed/pag ... tab=mobile - RLY?

The best system with people who do not have time. I know what I am telling, I was the head of the team who was responsible for making sites using CMSMS completely rebuilt by the dev team. We had to change CMS through the lack of modules.

I tend to disagree.

CMSMS is a great foundation for professionals to build applications. It is small, fast and extremely configurable. The dev team is not in the business of providing a huge variety of solutions to the community. It is in the business of developing a content management system and application foundation so that you can build your applications faster than writing them from scratch, or using other solutions.

For example: If your application needs a login system, a registration system, facebook and twitter integration, etc. it is NOT the business of the CMSMS core to provide that for you. You can either write them yourself, or if your requirements are compatible with the features of some third party modules... maybe you can use those to get you further along. But it is not the responsibility of the core or the core team. Even if some members of the core team do share modules.

Third party developers are typically application builders that share modules so that you CAN use some modules to make your application building process faster, but there is no way that these modules are applicable to every application or can provide all the functionality that your applications will ever need.

So, no. The dev team does NOT need to maintain a core package of modules. We need to only provide a system whereby YOU can build applications quickly and relatively easily. And to build applications you will most likely need proficiency in HTML, CSS, Javascript (and at least familiarity with jQuery) and at some point proficiency in PHP.

Your comments about "jquery cancer" is just a religious argument. You are entitled to your opinion, but I tend to like JQuery when I am writing applications so I probably won't be changing for a while.

calguy1000 wrote:I tend to disagree.

CMSMS is a great foundation for professionals to build applications. It is small, fast and extremely configurable. The dev team is not in the business of providing a huge variety of solutions to the community. It is in the business of developing a content management system and application foundation so that you can build your applications faster than writing them from scratch, or using other solutions.

I agree with you, it is very good working system. Good working and without popularity. Why? Because when I want doing website I have to looking module for gallery, blog, contact form, users, comments ect... Why so good solutions isn't exist in website templates market? Have a look at PrestaShop team modules, still you thinking is not a good solutions?

calguy1000 wrote: For example: If your application needs a login system, a registration system, facebook and twitter integration, etc. it is NOT the business of the CMSMS core to provide that for you. You can either write them yourself, or if your requirements are compatible with the features of some third party modules... maybe you can use those to get you further along. But it is not the responsibility of the core or the core team. Even if some members of the core team do share modules.

Writing own applications isn't main thing in CMS. Core team have to must care about modules, because usually users need to basic modules for doing website. For example, I making cars and I doing car bodies, wheels, steering wheels and seats and thats all. I don't care about air conditioning, radio, windows ect.

calguy1000 wrote: Third party developers are typically application builders that share modules so that you CAN use some modules to make your application building process faster, but there is no way that these modules are applicable to every application or can provide all the functionality that your applications will ever need.

Ok, I installing new official version and I wanna use LISE module, module not working... Ok I think: "You have to replace this module another". Sorry we dont have... Ok, I will use Gallery module... Now I wanna use Form Builder ah shit, here we go again. Its not only my problem, I wrote you I menaged over 10 000 sites basic in your solutions.

calguy1000 wrote: So, no. The dev team does NOT need to maintain a core package of modules. We need to only provide a system whereby YOU can build applications quickly and relatively easily. And to build applications you will most likely need proficiency in HTML, CSS, Javascript (and at least familiarity with jQuery) and at some point proficiency in PHP.

Well why core CMS have news module? It is special module?

calguy1000 wrote: Your comments about "jquery cancer" is just a religious argument. You are entitled to your opinion, but I tend to like JQuery when I am writing applications so I probably won't be changing for a while.

Just because I like something doesn't mean it's a good solution.
https://soanvig.github.io/dlaczego-nie- ... ootstrapa/
http://youmightnotneedjquery.com/

https://developers.google.com/speed/pag ... tab=mobile - my website

https://developers.google.com/speed/pag ... tab=mobile - yours

Do not get me wrong, I like using CMSMS but I wanna improve CMS.