Legacy Views Deprecation | Need More Info

Hi @generosus,

I wanted to take the time to answer your questions surrounding our Legacy Views and clarify a couple of things on communication from our side.

On that article we talk about two specific dates.

August 3, 2021
Which was the date we stopped offering support for customers using Legacy Views, so we are no longer doing bug fixes on those views since that date.

February 1, 2022
Is the date we are planning to remove code from our plugins regarding Legacy Views, which means that if you have PHP customization that use methods, classes or functions from V1 there might be problems when updating.

Now to answer your questions to make sure we have all explained.

• We will only offer security fixes for the latest version prior to the release of version 6.0.0 which will be the version number that removes all of the Legacy Views codebase, that is for Free and Pro versions, some of the other pro plugins will receive a major bump X.0.0 too but it might not be 6.0.0
• We are planning on adding as many fail-safes as we can, but the way third-party customizations work might prevent us from catching all the edge cases.
• Our team is working to work out any particular problems with the new views as much as possible but I cannot guarantee all Avada problems will be squared out, do you have any particular reports that you have in mind that you feel like we should take a closer look into?
• Yes, like on answer 1 we intend to keep releasing security patches for a while, we are still working out exactly how long that will be since we want to make sure the amount of time makes sense to everyone, we are leaning on something like 2 years maybe more
• Our team is working on a much much more extensive FAQ answering all questions about the Legacy Views deprecation and removal. Also our development team that is working on the removal of the Legacy views is working on a list of all methods, functions, Classes and views that will be either removed, deprecated or modified.

Hopefully I was able to answer all your questions.

If you have any other questions please let me know, my goal is to answer as much as possible to allow all of our customers to properly prepare.

On the FAQ and communication leading up to the date which might change due to other related projects that will be launching on 6.0.0.

Best Regards,

• This reply was modified 2 years, 10 months ago by Gustavo Bordoni. Reason: headings were poorly formatted

Hi @bordoni,

Wow! Thank you so much for your answers. Very helpful.

To answer your question about issues with Avada, well, most of them are styling (CSS) related.

Specifically:

(1) Ensure your plugin’s code loads scripts and styles ONLY where a calendar is shown (page or widget). Currently, we are dequeuing many scripts and styles that we don’t need or use and/or are loaded within pages where we don’t have a calendar.

(2) Add a CSS Customization box in the Settings section of your plugin and ensure the custom CSS we add or apply only loads where a calendar is shown (page or widget). As it stands now, we have to add custom CSS to Avada’s general CSS customization section which means it loads on all of our pages. Many times, this causes an “Unused CSS” condition which is usually flagged by Google Lighthouse or PageSpeed Insights.

Other than the above, we’re good to go. Thank you for your continued support.

Cheers!

Hi @generosus,
Perfect I will take a look into that particular problem of Unused CSS and/or JS files being loaded without being used.

It might be a super simple case of some conditionals not applying correctly, because that is for sure not our intentions, we don’t want our stuff loading on pages that it shouldn’t.

I would love if you have the time to share which one are you deactivating on your case? Might help speed up the development of a fix from our side too.

Best Regards,