May 20, 2019 at 12:54 pm #1102465May 21, 2019 at 9:04 am #1102738
No, please leave it there in the database since it’s needed.
You can refer on Kriesi’s answer on this thread: https://kriesi.at/support/topic/_avialayoutbuildercleandata-keeping-data-old/#post-320684
NikkoJuly 23, 2020 at 8:25 pm #1232795
I hate to say it but this record in the postmeta table is redundant. There is a specific process that is well documented to avoid the autop method in the wp_posts content entries and it appears that enfold is simply unaware of this and not using it correctly.July 23, 2020 at 8:46 pm #1232802
Thanks for your input!
I have shared your messages with our devs :)
YigitJuly 25, 2020 at 2:35 pm #1233204
I heard back from our devs. They have worked on a fix for this however it was not added because Kriesi and our devs decided it was too risky as it could break something else. Main concerns are special characters and broken HTML (many users use invalid HTML and that breaks ALB). For special characters, we have a plugin – https://github.com/KriesiMedia/enfold-library/tree/master/integration%20plugins/Enfold/Special%20Character%20Translation/avia-special-characters however we do not have a solution for broken HTML so far. So it is still needed.
YigitJuly 28, 2020 at 5:32 am #1233657
1. why aren’t you guys sanitizing/accommodating the special characters in your saving process?
2. why aren’t you spitting back the changes that the users are using, and highlighting the special characters so they can make changes?
3. or, why aren’t you notifying the users of special characters as they create the page??
You should be using a discovery process here, and your shortcode parser should be more robust here. This is why other page builders are more successful and why I use other page builders with all of my other clients. I am stuck using this theme due to the client’s willingness to learn something different.
First: you notify and block all special characters as they enter them.
Second: you allow people to send recommendations for specific characters they need, this will happen a lot at the beginning, and less over the course of time.
You should be building your code in iterations that instead of trying to accommodate all of them at the beginning.
By slowly adding them over time, you allow yourself to acclimate to the special characters that people use.July 28, 2020 at 5:37 pm #1233777
Thanks a lot for your input and suggestions.
I checked with our dev team again and they will try to implement proposed steps in future development stages if possible. But for the time being, we can only ask our users to use the workaround we provided for special characters.
- The topic ‘Can I delete _aviaLayoutBuilderCleanData in postmeta table?’ is closed to new replies.