gophp5!
July 8th, 2007 by Ted KulpCMS Made Simple is gladly joining in the gophp5.org mission. On 5 February 2008, many PHP projects, including us, will not be releasing any more versions that will be compatible with anything less that PHP 5.2.0. This is to help push ISPs into supporting php5 finally… which has been out for 3 years already.
In actuality, we’ve already said that CMSMS 2.0 will only support php5, but this seals the deal on a version number (5.2.0) and also gives us leverage for this decision. CMSMS 2.0 will also be coming out before that date, but that just means we’ll be a few months ahead of the curve.
If you’re having trouble and worrying about a host supporting future releases, then you should probably check out the list of hosts on this page and get your migration plans ready.
Thanks to the folks at gophp5.org for giving us a reason to finally push php acceptance in forward and positive motion. It really is THAT much better that php 4.
July 8th, 2007 at 11:46 pm
Come on in the waters warm…
I’ve been using PHP5 servers with cmsms from v0.12. PHP5 gives me the tools to develop stable and memory frugal user defined tags within cmsms that with PHP4 would take double the amount of code.
gophp5? more like goCMSMS
July 9th, 2007 at 2:56 am
HOW ABOUT FULLY SUPPORTING SAFE_MODE???
WHY ARE YOU IGNORING SUCH BASICS IN SECURITY???
THE WAY IT IS GOING, WE WILL HAVE TO STOP USING YOUR CMS, BECAUSE YOU ARE JOINING THE HYPE WITHOUT SUBSTANCE MOVEMENT AKA JOOMLA, ETC.
July 9th, 2007 at 3:05 am
@ Draak,
First, using CAPS LOCK doesnt make your message more informative, nor does it make it any more important.
Second, I have 6 totally different websites running CMS Made Simple with Safe Mode on and no trouble at all, fine tune permission on a couple of folders and everything works fine, expect xml import in the module manager, but ftp’ing is just as quick.
So I would like to know what basics in security is CMSMS ignoring?
July 9th, 2007 at 4:31 am
Just to confirm: All our installations use SAFE MODE ON and CMSMS works well.
On topic: We upgraded all our systems just because CMSMS announced to switch to PHP5, as CMSMS is our preferred CMS by now.
Keep up the good work!
Cheers,
faglork
July 9th, 2007 at 8:37 am
Will we have any issues in upgrading to PHP5, Apache2 and MySQL5 from under existing installations of CMSMS?
July 9th, 2007 at 9:10 am
@MattJH: There shouldn’t be an issue. I’ve been developing CMSMS on that setup for about a year now. If anything, it’s the preferrred way to go even for current releases.
July 9th, 2007 at 8:56 pm
draak, safe_mode provides no security, only problems. it has never worked, get a clue for god sake and stop writting with CAPS ON.
Thank you.
July 10th, 2007 at 11:34 am
This means that if the server is not using php5 I cannot upgrade anymore my CMSMS?
July 10th, 2007 at 11:24 pm
This is bad news.
I use CMSMS to develop websites for other clients. I can’t force my clients to change their hosts. Lot of people prefer to stay with a single host and don’t want to change unless their current host goes down.
All this is going to achieve, is to force developers like me to dump CMSMS and start using some other CMS.
And what exactly is the need for forcing people to use PHP5? Even PHP.net themselves haven’t dumped PHP4, so why are you?
July 11th, 2007 at 4:17 am
@saltydog: You can continue to use the 1.0.x and 1.1.x versions. You just can’t upgrade to 2.0.
@Jatinder: It’s not like it’s an issue for existing sites… just new ones. And if you’re creating the site, can’t you suggest what hosts to use? Anyway, if you take a look at the list of CMS’s that are making the same change, you’re going to have an increasingly harder time finding another CMS to use that still works on PHP4 (drupal, typo3, website baker, etc).
PHP4 is a dinosaur and is getting increasingly harder to write decent programs with. As programmers, we want to start writing better software using ALL of the wonderful features that php5 gives us. Not just workaround php4’s limitations time after time again because hosting companies don’t want to deal with the upgrade. That’s the reason for the whole gophp5 initiative in the first place.
July 11th, 2007 at 1:19 pm
I guess it is time to finally update my test server. 5.0 isn’t gonna cut it anymore
July 13th, 2007 at 3:35 am
“…anything less _that_ PHP 5.2.0…”
July 15th, 2007 at 3:49 am
@Ted: I understand how programmers are eager to use new functionalities and new methods with PHP5, but the issues rised by Jatinder are real. I am in the same situation, managing CMS for 2 or 3 clients that really don’t want to put theris hands on the installation. Maybe is it too early for a full switch to PHP5? A smooth transition is more welcome!
July 15th, 2007 at 8:53 am
@saltydog: Take a look at http://php.net. They just announced the PHP4 end of life. Seems like I was only slightly ahead of the curve.
July 17th, 2007 at 10:26 am
sorry for the caps chaps, got the attention i wanted.
yes i also have SAFE MODE ON working OK together with REGISTER GLOBALS OFF. that is not the point. perhaps i should have made myself more clear.
what i was referring to was more of an installation procedure with after-install steppes and unnecessary messages in administration that cannot be switched off. also, SGID permissions on writeable directories are no longer working in more recent versions of CMSMS.
and i do understand the reasoning with PHP5, however i really would like to suggest that if you are going purely PHP5, then start urging users to use SAFE MODE in the installation procedure instead of suggesting that using SAFE MODE OFF is a good idea. this doesn’t educate, instead it promotes ignorance.
August 1st, 2007 at 6:11 pm
Draak,
You say that it has all been working find with safe mode on and register globals off - that is the scenario I’m working in (and yes, the client doesn’t want to change hosts as they have been with these hosts for years and are happy with them - even if I’m not :-)). Anyway, I’m wondering if you had problems uploading images and files via. the editor (I am using fckeditor) at all because of the safe mode problem? I seem to have most things working except this - which is unfortunately critical for my client - help?! heh
October 3rd, 2007 at 12:36 am
I am having problems with a CMS-MS install on a client’s site. It works fine on my testbed, but not theirs. It’s an issue apparently with safe mode. I cannot upload modules from the module manager nor from an XML file. The whole point of migrating these folks to CMS-MS was to make things easy for them to maintain. I wanted to keep them from having to upload things via http://FTP. This is a Civic Club and they will have PDF files and other documents to upload, and it would have been really nice to be able to do that from the admin panel.
So if you guys have sites running with safe mode on that have been able to get around the file upload issue (and it is a BIG issue, NOTHING can be uploaded from the admin panel on this live install), I’m all ears and I may even be persuaded to be all wallet too, if you get my drift.
Thanks for any help.
My prototype site is here: http://cmsms.mytestbed.com
The main site which I am working on this evening is here: http://idylwood-houston.org
Thanks!
April 18th, 2008 at 1:11 pm
[…] CMS Made Simple Accessible, flexible, simple open source content management. […]
August 27th, 2008 at 5:17 pm
[…] the moment there are already a couple of big projects associated such as Drupal, CMS Made Simple, phpMyAdmin and […]