升级 magento 后自定义模块链接不会出现。它可以在本地机器上运行，但不能在现场运行？
由于我的错误或 magento 的结构，我有一个大问题不知道。我已将 magento 更新到 1.4.1.1，并且在我的本地计算机上一切正常，但是当我将其移动到实时状态时，管理自定义模块的链接不会出现。
我也尝试过清除缓存并重新登录，但它不起作用..任何人都可以帮忙吗？
I have one big issues don't know due to my mistake or magento's structure. i have update the magento to 1.4.1.1 and all work fine on my local machine but when i have moved it to live then in admin custom module's link are not appeared .
i have also tried for clearing the cache and re login but it wont work.. can any one help??
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
实时代码库和本地代码库是否完全相同
您确定实时代码库实际上正在被 apache 使用吗
如果您的模块已加载到系统中吗？
您的用户是否拥有正确的 ACL 权限来查看导航项？
您是否清除了用户会话（与缓存分开）以确保为用户刷新 ACL 权限
最后，at 类
是负责渲染导航的类。从 到 进行调查/调试，找出为什么它会跳过和/或看不到您的自定义导航项。
Are the Live code bases and local code bases exactly the same
Are you sure the live codebase is actually being used by apache
If your module loaded into the system?
Does your user have the right ACL permissions to view the navigation items?
Have you cleared your user sessions (separate from cache) to ensure that ACL permissions are flushed for the user
Finally, the class at
is the one responsible for rendering the navigation. Investigate/debug from to to figure out why it's skipping and/or not seeing your custom navigation items.
我发现这通常是由区分大小写的文件和模块名称引起的。您是否在与您的产品不同的平台上进行开发（Windows 与 *nix）？检查您的模块名称是否采用
Module_Lowercasenamesonlyworkhere的形式。------编辑------
尝试从他的网站安装 Alanstorm 的 ConfigViewer 模块或 CommerceBug 扩展，这将向您显示所有管理模块的“已遵守”配置。然后您可以查看是否包含您的
adminhtml节点。据我所知，这是确认 Magento 正在读取您的配置的唯一方法，这听起来像是问题所在。I have found that this is often caused by caseSensitive file and module names. Are you developing on different platforms to your production (Windows vs *nix)? Check that your module names are in the form of
Module_Lowercasenamesonlyworkhere.------EDIT------
Try installing Alanstorm's ConfigViewer module or CommerceBug extension from his website, that will show you the "complied" config for all the admin modules. You can then see if your
adminhtmlnodes are being included. That's the only way that I'm aware of that will confirm that your config is being read by Magento, which sounds like the issue.