I created some pages on umbraco and it works correctly. But i added some datagrids to main page and now, main page's tabs is loading too slow because umbraco is trying to load all data of page on tabs on first call.
我在umbraco上创建了一些页面，它运行得很好。但是我在主页上添加了一些datagrid，现在主页的制表符加载速度太慢了，因为umbraco试图在第一次调用的制表符上加载页面的所有数据。
So my question is can i load only selected tab on pages? Like lazy load? For example; If i click to first tab, load that data. After click second tab, load data of second tab. Because the standard load of data system is too slow.
我的问题是，我是否可以只在页面上加载选定的选项卡?延迟加载吗?例如;如果我单击“第一”选项卡，加载该数据。点击第二个选项卡后，加载第二个选项卡的数据。因为数据系统的标准负载太慢。
Thanks!
谢谢!
ps: Im too newbie on umbraco. So i didnt create custom tabs...etc. Just i created from umbraco dashboard template settings.
ps:我太新手了。所以我没有创建自定义选项卡等等。我只是从umbraco仪表板模板设置中创建的。
1 个解决方案
#1
3
As far as I'm aware, there's no way to lazy-load tabs on an Umbraco node. At least that's not provided as functionality.
就我所知，没有办法在Umbraco节点上延迟加载制表符。至少这不是作为功能提供的。
We've often had a similar problem of a node/page having too much on it (a lot of rich text editors, with each of them loading TinyMCE), and the way around it for us was to pull this content out into child nodes.
我们经常遇到类似的问题:一个节点/页面上有太多的内容(很多富文本编辑器，每个编辑器都在加载TinyMCE)，对我们来说，绕过这个问题的方法是将这些内容拖放到子节点中。
By this, I mean that the main page content stays in the page node, but then you could create new document types that are created as children of the content node. You could then use XSLT/Razor to pull in the content stored in these child nodes to be published onto the main content page. By doing this, you'd still have all the content on the page, but it would be split up into multiple nodes, with each of them loading nice and quickly.
通过这种方式，我的意思是主页面内容保留在页面节点中，但是您可以创建作为内容节点的子节点创建的新文档类型。然后可以使用XSLT/Razor将存储在这些子节点中的内容发布到主内容页面。通过这样做，页面上仍然有所有的内容，但是它将被分割成多个节点，每个节点的加载速度都很快。
#1
3
As far as I'm aware, there's no way to lazy-load tabs on an Umbraco node. At least that's not provided as functionality.
就我所知，没有办法在Umbraco节点上延迟加载制表符。至少这不是作为功能提供的。
We've often had a similar problem of a node/page having too much on it (a lot of rich text editors, with each of them loading TinyMCE), and the way around it for us was to pull this content out into child nodes.
我们经常遇到类似的问题:一个节点/页面上有太多的内容(很多富文本编辑器，每个编辑器都在加载TinyMCE)，对我们来说，绕过这个问题的方法是将这些内容拖放到子节点中。
By this, I mean that the main page content stays in the page node, but then you could create new document types that are created as children of the content node. You could then use XSLT/Razor to pull in the content stored in these child nodes to be published onto the main content page. By doing this, you'd still have all the content on the page, but it would be split up into multiple nodes, with each of them loading nice and quickly.
通过这种方式，我的意思是主页面内容保留在页面节点中，但是您可以创建作为内容节点的子节点创建的新文档类型。然后可以使用XSLT/Razor将存储在这些子节点中的内容发布到主内容页面。通过这样做，页面上仍然有所有的内容，但是它将被分割成多个节点，每个节点的加载速度都很快。