Hi Luo
In the meantime I did a further try and this time It is only Toolset View without any Elementor usage, except for the Site Footer, with the following result:
The Content from a Single View with a child View appears, but all the CSS added to the Views are getting stripped off after updating Views to 2.7 - rolling back to 2.6.3 solves this issue.
Maybe you should escalate this ticket to Amir, as he mentioned recently in a post comment on your blog how important it is to him that upgrades work as painless as possible and how much he cares about stability.
For the new problem:
but all the CSS added to the Views are getting stripped off after updating Views to 2.7
Please check the new thread here:
https://toolset.com/forums/topic/all-the-css-added-to-the-views-are-getting-stripped-off-after-updating-views-to-2-7/
thanks
Hi Luo
thanks for looking into this ?
Indeed - this is a different issue - thanks for opening a new thread for this.
In the meantime I followed the new instructions and there where some content templates left over from the time the site wasn't using Elementor.
The Good news: After moving them to trash the Elementor Templates are working with Views 2.7 - except for the CSS issue which you moved to the new thread.
Hi Lou
thanks for this hint and your efforts to look into this 🙂
My first thought about this was: changes in the workflow like this should be better communicated to the Toolset users !
Then I followed the changes in the documentations and came across the following issue:
How conditional display of fields is handled ? It looks like this wasn't really thought out or is completely ignored in the documentation.
As for your point about the changes since the release of Views 2.6.3 a few updates happened but it looks very evident that this should be definitly addressed on the Toolset side as everything works fine when still using Views 2.6.3 even with the latest Elementor and WordPress Version.
I hope your dev's will come up with a great solution for solving this puzzle
Best regards, Peter