Normann

wrong working place, I am jumping around diff workingplacing. so lost my way. 🙂

Normann

The 'Type' column is actually also not seachable, it is kinda human-readable English word to describe the ClassName, e.g SilverStripe\UserForms\Model\UserDefinedForm is marked as 'page'

Normann

@Firesphere thanks. I will try to shorten the module name then.

Normann

got a question about composer.json -> extra -> installer-name, recently we developed a vendor module which has a really long name, e.g. mycompany/silverstripe-several-words-very-long and for installation, I want the directory name to be a little shorter than silverstripe-several-words-very-long. I thought the installer-name under extra in composer.json is the place I could customize the directory name, but I am wrong, as I give it a short name there, but it doesn't affect. Anyone knows what do I need to do, instead of using the installer-name.

Normann

@webbower I think I am going to go with @nightjarnz the LastEdited datetime field is managed / updated by the system automatically and is used in many many different ways and other legacy modules, in you case, why not make another field to hold your origin / source data's similar field, maybe `OrginalLastUpdated' and use it just meet your purpose of IA?

Normann

@Nightcrawler though I am not sure what composer require will behave in that project-files-installed light spot.

Normann

@Nightcrawler can you confirm that Page.php file exist in the host server that you works on? if you run composer create-project in local, there are bunch of files like Page.php / PageController.php, etc will be created for you and awaiting you add the meat to the bone, but if you you run composer install or 'composer update` in the server, the block mentioned by @Joe will be not effect hence will not create those files for you.