search

jweiland-net / sync_crop_areas

git@github.com:jweiland-net/sync-crop-areas.git
Other
0 stars 2 forks source link

How to add sync_crop_areas to custom content elements? #8

Closed Treupo closed 3 years ago

Treupo commented 3 years ago

I have a (custom) content element. Card Group from the EXT:bootstrap_package. I'd like to have the sync_crop_areas function there too. Is it somehow possible? Do I have to override the TCA for this element by myself? Thank's in advance.

froemken commented 3 years ago

Good Morning @Treupo,

I have extended the sys_file_reference. If your content element is using the public API for file relations our sync_crop_areas will also work for your element.

As it should work for you out of the box I'm wondering about your ticket. Is this a ticket before installing sync_crop_areas or more a ticket like: I've installed sync_crop_areas, but it doesn't does its job?

Nice greetings

Stefan

PhilippKuhlmay commented 3 years ago

Hi I use a content element from the bootstrap package called "card group". There I don't habe the switch for synchronizing the crop areas. I was wondering how to add it to this content element.

If your content element is using the public API for file relations our sync_crop_areas will also work for your element. So the issue is not in this extension, but in the bootstrap package?

Philipp (I just realize that I asked the question with an different GitHub account)

froemken commented 3 years ago

Hello @Treupo @PhilippKuhlmay

thank you for the hint "card group". That helps me a lot understanding your problem in more detail. The bootstrap_package does not use the default palette of columns to show cropping feature.

I have added a new section into documentation of sync_crop_areas why this is a problem and how to solve that:

https://github.com/jweiland-net/sync_crop_areas/blob/master/Documentation/KnownProblems/Index.rst#sync_crop_areas-does-not-work-for-columns-of-extension-xy

I can't add that feature to sync_crop_areas as I have to be sure that my extension MUST BE loaded AFTER all other extensions and that is nearly impossible. So you have to add these lines of code into your site_package extensions