Umbraco - 回发缓存问题
我在 umbraco 中开发的页面遇到问题。我对此还很陌生，所以非常感谢一些指导。
该问题似乎与 umbraco 缓存页面的方式有关。
我拥有的是库存定位地图（我的例子是澳大利亚地图）。
在此页面中，用户可以选择一个区域来查看该区域内的库存商。
我有一个很大的搜索按钮和一些复选框，供用户选择他们想要搜索的区域。
当我选中“悉尼”并点击我的搜索按钮时，一切都很好。它返回我期望的结果。
但是...如果我立即（再次）单击搜索按钮 - 那么搜索结果就会消失。
这几乎就像 umbraco 正在做一些奇怪的缓存事情。我尝试摆弄开发人员区域内的缓存设置（即“缓存周期”），但没有发现任何一致的模式来阐明问题。
哦，另一件事 - 它不执行页面加载和 pageInit 事件（从缓存检索时）。
I'm having a problem with a page I'm developing in umbraco. I'm fairly new to it so would really appreciate some guidance.
the problem seems to be connected to the way umbraco caches pages.
what i have is a stockist locator map (a map of Australia in my case).
from this page, the user can select a region to see stockists within that area.
i have a big fat search button along with some checkboxes for the user to choose what region they want to search in.
when i check say 'Sydney' and hit my search button, all is well. it returns the results i would expect.
but... if i go and click the search button straight away (again) - then the search results disappear.
its almost like umbraco is doing some weird caching thing. I've tried fiddling with the caching settings within the developer area (i.e. 'Cache Period'), but haven't spotted any consistent patterns which shed light on the problem.
oh, another thing - its not executing the page load and pageInit events (when retrieving from the cache).
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
因此，当您提交控件而不选择任何内容时，您会得到空结果。难道这就是一个控件本身的逻辑？正如我所看到的，它只是为空搜索查询提供空结果。
So when you submit you control without selecting anything, you get empty result. Can this be, that is the logic of a control itself? As I see, it just gives empty result for empty search query.
您能提供一些示例代码来演示您的实现吗？
我做过很多 Umbraco 站点，但很少发现 Umbraco 会中断正常的 ASP .Net 页面生命周期，因此我更倾向于猜测您的代码中存在错误。
您是否尝试过完全禁用自定义缓存以确保问题与您的代码无关？
您的缓存是否有正在清除的参数依赖性或其他什么？
Can you provide some sample code to demonstrate your implementation?
I've done plenty of Umbraco sites and have rarely found that Umbraco interrupts the normal ASP .Net page lifecycle so I'd be more inclined to guess you have a fault in your code.
Have you tried disabling your custom caching completely to ensure that the issue does not relate to your code?
Does your cache have a param dependency that is being cleared or anything?