Legacy view not supported with version 6.0
-
Hello,
as I know you will fully remove the legacy view with version 6.0, right?
The calendar page of all the websites that we made with the legacy view will have a broken layout. I can already see it now if I switch to the updated views.
Nowhere in the backend of your plugin was written that view was deprecated.
Are you sure you want to do a so drastic removal without first declaring the legacy view as deprecated in the backend? The warning should be very big and clear in the backend, and the users should have the time to take action after seeing the warning. I think version 6 would be too early for something like this that will break a lot of websites.To be honest, I was very disappointed with this news. I totally understand that you want to improve the plugin, but I don’t think this is the way to deprecate a feature. We are speaking about the most important thing of your plugin, the calendar view. Please rethink how you can deprecate the legacy view in a much less drastic way.
Will you offer a filter hook to keep the legacy view? Or is avoiding future updates of the plugin the only solution to don’t break the layout?
- The topic ‘Legacy view not supported with version 6.0’ is closed to new replies.