document.mutate.save 未定义

发布于 2024-12-10 16:18:24 字数 671 浏览 0 评论 0原文

我正在使用 ModX CMS。

如果我要保存一个块,这个错误 document.mutate.save is undefined 会不断出现。

假设这是一个错误的安装,我删除了该应用程序,并重新安装了四次。其中包括:

  1. 来自我的测试远程服务器上原始工作应用程序的两次。
  2. 来自 ModX 网站上最新版本的 Evolution
  3. 来自另一个工作网站,我维护它也是在 ModX 中创建的。

假设这是一个 javascript 冲突,我进入我的 QM,从后端删除了 jQuery,然后最终一起删除了 jQuery,不确定它是否仍然放在那里。我无法查看后端的源代码,因为它完全由 iFrame 组成。

document.mutate.save 文件来自位于以下位置的文件夹: /manager/actions/

此文件夹设置为 777 以及所有周围的 golders 和父 code>manager 文件夹也是如此。

任何人都知道为什么会调用此错误以及如何修复它?

我是一个 Rails 人员,但这似乎是一个在控制器问题中未定义的简单方法。不幸的是,我不太了解 PHP 的 MVC 架构,否则我会手动修复这个问题。

谢谢!

I'm using the ModX CMS.

And this error, document.mutate.save is undefined keeps coming up if I were to save a chunk.

Assuming it was a faulty install, I deleted the application, and reinstalled it four times. Those included:

  1. Twice from the original working application on my testing remote server.
  2. From the latest version of Evolution on ModX's website
  3. From another working site I maintain that was also created in ModX.

Assuming it was a javascript conflict, I went into my QM, and removed jQuery from the backend, and then eventually removed jQuery all together unsure if it was still being placed in there. I can not view the source of the backend because it is entirely composed out of iFrames.

The document.mutate.save files come from a folder located in: /manager/actions/

This folder is set to 777 as well as all the surrounding golders and the parent manager folder as well.

Anyone have any idea as to why this error is being called, and how to fix it?

I'm a rails guy, but this seems like a simple method not being defined in the controller problem. Unfortunately, I'm not too conscious of PHP's MVC architecture otherwise, I would fix this manually.

Thanks!

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

听风吹 2024-12-17 16:18:24

老线程,我知道......但我有一个可能对我有用的解决方案。
经过一番折腾,我终于发现我在配置中激活了编辑器,但卸载了TinyMCE Plugin。停用编辑器后,错误消失了。

Old thread, I know... but I have a possible solution which worked for me.
After a lot of fiddling around, I finally found that I had activated the editor in the configurations, but had uninstalled the TinyMCE Plugin. After deactivating the editor, the error disappeared.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文