Werner Krauß

I think it's bad practice, that the main category (aka ParentID) isn't added to ProductCategories manymany relation. This makes it harder to find e.g. all products of a given category...

E.g. a Product should also delete/duplicate its ProductVariations, the image etc... Use named params for better customisation Also go through other silvershop modules and look where cascade_* can be useful...

When deploying sites to a staging server it'd be nice to disallow robots either by Environment dev or test or even by a `.env` setting. An extension point to modify...

Hi @unclecheese, any plans to upgrade this module for SS4? Or any alternative modules you know of?

I stumbled across a problem with my Gallery implementation: ``` PageTypes: ImageGalleryPage: Fields: {} Components: ImageGalleryAlbum: Type: many Interface: Type: grid Tab: GalleryAlbum ProjektPage: Parent: ImageGalleryPage Fields: {} Components: ImageGalleryAlbum:...

Decorating e.g. Page in different modules with Silversmith results in many classes with the same name "PageDecorator". If we prefix this classname with the module name it should work.

$belongs_to is the opposite part of a has_one in 1:1 relations

So instead of MyDataObject.HELLOWORLD MyDataObject.db_MyField or MyDataObject.has_one_RelationName So we can use the same entities for generateCMSFields and Scaffolding, e.g. getFrontEndFields() This would need a tweak in all form templates or...

For designing the whole db schema with silversmith this could be useful

Why not generate Frontendfields? Maybe with a switch to enable per dataobject.