Page 1 of 1

Updating blueprint of module generated with CTLModuleMaker

Posted: Thu Dec 30, 2010 7:33 pm
by rhiaro
Okay, so yesterday, I wanted to make a couple of small changes to a module I'd made with CLTModuleMaker, and manually tweaking the blueprint file worked just fine.

Today... no such luck.

I've triple checked I'm updating the right file, looking at the right module, etc.  I've tried restarting, logging in and out, different browsers, clearing cache...

I tried making really minor changes, like the names of fields.  The changes are being saved and can be seen in the Blueprint.php file... but are not being reflected in the module itself.

It's just more annoying that it was working fine yesterday...

Tearing my hair out, no idea what I'm doing wrong... Probably something obvious... Pointers greatly appreciated :)

Re: Updating blueprint of module generated with CTLModuleMaker

Posted: Fri Dec 31, 2010 9:20 am
by klenkes
Well, it depends on what you want to change. Not all of the items in Blueprint.php will have an effect on your already working module.

Changing field attributes work fine, switching things on and off, like WYSIWYG or
indexed' => '',
'allowedext' => 'jpg,jpeg',
'startdir' => 'yourmodule/moduleimages',
'resize' => '800x600',
'crop' => '1',
'thumbsize' => '300x225',
'thumbcrop' => '1',

even changing those work:
'options_value' => 'alias',
'options_label' => 'name',
'normal_user' => '1',
'fe_allow_new' => '1',

Adminfields are managed through templates and even theese can be edited.

This of course ends with database field names! You cannot change DB field names through the blueprint.

--
Bernd