Announcing CMS Made Simple 1.2 Beta 2

calguy1000 · **Posted:** Sun Sep 30, 2007 2:27 pm

after only 48 hours we've managed to fix any of the outstanding issues that have been reported with the 1.2Beta1 release and provide yet another version for your testing.

Keep up the good work.

stopsatgreen · **Posted:** Sun Sep 30, 2007 3:29 pm

Have installed it, I'm looking at it now.

Couple of quick points/questions re: the new file manager:

1. The Current Path has a backslash in front of it which looks a little weird with a forward slash after it:

Current path: \/uploads/

2. Will it be possible in the future to be able to rename and move files with the file manager? That would be VERY useful.

calguy1000 · **Posted:** Sun Sep 30, 2007 3:32 pm

Well, in the future we may either look at expanding this module or using another PHP driven GPL based file manager. but I agree, rename, copy, change permissions would all be very cool.

GDS · **Posted:** Sun Sep 30, 2007 5:15 pm

Edit Content - Options
Notice: Undefined variable: entries in c:\phpdev\www\sff\modules\FileManager\fileview.php on line 157

FileManager - File view
Notice: Only variables should be assigned by reference in c:\phpdev\www\sff\lib\classes\class.content.inc.php on line 1481

And i do see some untranslated strings. (Norwegian)
Is there a way I could do these translations?

GDS

RonnyK · **Posted:** Sun Sep 30, 2007 5:43 pm

GDS,

for translations, you can go to translations.cmsmadesimple.org make an account there and sign up for doing translations.

Ronny

GDS · **Posted:** Sun Sep 30, 2007 6:22 pm

I have alreade registered, but as far as I can see,
News 2.5.1 and Core 1.2 is not in the Translation center yet.

GDS

jce76350 · **Posted:** Sun Sep 30, 2007 6:43 pm

Hi,

Quote:

News 2.5.1 and Core 1.2 is not in the Translation center yet.

for Core 1.2 use Core
But I confirm News is not at the good version
and also Printer Friendly pages(Printing) and Filemanager for me into French/Français

moorezilla · **Posted:** Sun Sep 30, 2007 9:46 pm

I just tried to take an existing database from the latest stable release and update it with beta2. Everything seems to work, except I get a

"You are now running schema version 28 and you need to be upgraded to version 29."

in the admin section despite having gone through the update process... ie. running install/upgrade.php. When I run install/upgrade.php, it says that all is fine, so I'm a little confused.

Any idea why it is still thinking it's on schema 28 instead of 29?

update: I just changed the 28 to a 29 in the database and the error goes away, but it seems a bit odd that it says it has successfully updated the schema but it doesn't change the schema number. Is there a quick place to check in the database to see if it really has made the changes from 28 to 29?

Also, in trying to make a database completely utf8, there's a problem with table cms_module_template having two varchars of 200. If you lower them both to 150, you can successfully import an existing database into a mysql database with utf8 default text and utf8 collation. I suppose this could have an impact on module templates down the road. I'm not sure if this is important, but I did run across it.

moorezilla · **Posted:** Mon Oct 01, 2007 1:09 am

Ok... I think this might be a bug in beta2 as I did not run into it in beta1.

When I upload all of beta2 to an existing database and try to upgrade, I can't properly get rid of this in the admin area:

Code:

Warning: CMSMS is in need of an upgrade.

You are now running schema version 28 and you need to be upgraded to version 29.

Please click the following link: Start upgrade process.

If I trigger the install/upgrade.php it says that it has updated the schema, but it doesn't seem to change the 28 to a 29 in the database. If I go into the database and change the 28 to a 29 manually, it gets rid of the error, but it's unclear to me if the database has been updated correctly aside from the 28 being updated to 29.

The site seems to work fine after I update the 28 to a 29, but I don't know where to look to see if the schema is actually updated.

Any ideas?

tsw · **Posted:** Mon Oct 01, 2007 4:54 am

Sorry, my bad. I forgot to re-enable the actual change of the db after my tests.

This is fixed in svn rev 4209 and its a oneline fix in install/upgrades/upgrade.28.to.29.php line 32 change from

Code:

#$query = 'UPDATE '.cms_db_prefix().'version SET version = 29';

to

Code:

$query = 'UPDATE '.cms_db_prefix().'version SET version = 29';

Sorry folks.

GDS · **Posted:** Mon Oct 01, 2007 7:46 am

Site Admin - Page Defaults

Notice: Only variables should be assigned by reference in c:\phpdev\www\sff\lib\classes\class.content.inc.php on line 1481

Add New Content - Options:

Notice: Only variables should be assigned by reference in c:\phpdev\www\sff\lib\classes\class.content.inc.php on line 1481

Notice: strtotime() [function.strtotime]: Called with empty time parameter in c:\phpdev\www\sff\lib\classes\contenttypes\Content.inc.php on line 270

GDS

stopsatgreen · **Posted:** Mon Oct 01, 2007 10:49 am

I've just noticed that version.php still has 1.2-beta1

stopsatgreen · **Posted:** Mon Oct 01, 2007 11:53 am

Also, this is just a suggestion, but I don't think the Printing module is ready to be included as a core module yet. There are no settings, no default templates, very little help; I'd say it needs more development before going out. It's a useful module, for sure, but a bit too rough at the moment.

GDS · **Posted:** Mon Oct 01, 2007 12:30 pm

All Notices mentioned in my earlier postings disappears when uninstalling the truetypetext module.

GDS

GDS · **Posted:** Mon Oct 01, 2007 2:59 pm

I would like to keep the old print plugin, and leave the Printing module out of the Core
(Aat least until converting to pdf works properly).

Just my opinion.

GDS

Announcing CMS Made Simple 1.2 Beta 2

Who is online