You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
https://github.com/collective/Solgema.fullcalendar/blob/master/Solgema/fullcalendar/events.py This event fires every time a profile is run and forces solgemafullcalendar_view to be an allowed view method for various types - why? I just spent a lot of time debugging where I tried to install a separate profile (to be run after this was installed) that existed solely to remove this view option from Folder and Event types, only to find that they weren't removed. I don't see a way to disable this view as an option without hacking your code to nullify this event listener, or manually editing TTP which doesn't fly when I need to be able setup a new portal with our profiles in one click.
Please consider removing this event listener. If this option needs to be applied to to older sites it should be done manually through a GenericSetup upgrade step in my opinion.
The text was updated successfully, but these errors were encountered:
https://github.com/collective/Solgema.fullcalendar/blob/master/Solgema/fullcalendar/events.py This event fires every time a profile is run and forces solgemafullcalendar_view to be an allowed view method for various types - why? I just spent a lot of time debugging where I tried to install a separate profile (to be run after this was installed) that existed solely to remove this view option from Folder and Event types, only to find that they weren't removed. I don't see a way to disable this view as an option without hacking your code to nullify this event listener, or manually editing TTP which doesn't fly when I need to be able setup a new portal with our profiles in one click.
Please consider removing this event listener. If this option needs to be applied to to older sites it should be done manually through a GenericSetup upgrade step in my opinion.
The text was updated successfully, but these errors were encountered: