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:
Twice from the original working application on my testing remote server.
From the latest version of Evolution on ModX's website
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!
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.
Related
After trying out all typical solutions for wordpress wsods, I am out of ideas.
I migrated my website from wordpress.com to a self-hosted solution using all-in-one-wp-migration, which looked to work fine, until a coworker wanted to use the backend and got wsod.
After going through all the suggestions for fixing wsods and a few of my own, namely:
checking every single plugin used
checking memory (980m should be enough?)
deleting and reinstating all saved accounts
scrubbing the database off of old wordpress.com entries or deprecated urls
running debug mode and not getting any logs from the wsod
I of course landed on my self made theme as the issue. I went over the functions.php file to remove and clean up all custom additions that are not necessary for functionality. I used a theme check plugin to help me weed out most of the issues that come from being a beginner at this, but nothing looks to be related at all to backend.
Especially irritating is the part where it works fine for me while using my pc, but any other device, like smartphone, tablet or other pcs can't seem to get into the wp-admin version of the site while my theme is activated.
P.S.: while the theme is active, backend functionalities like searching for new plugins or changing settings seem to not work right or lead to wsod even for me.
For anyone running into a simillar issue, the solution given by online guides always mentions making sure the END of the functions.php file does not have any empty space there, but they neglect to mention that there can't be any empty line anywhere in the whole file, even within the code.
I am working on project on localhost (not live yet) which is built in php using codeigniter framework, recently it start showing warning message which might due to malicious code injected in website, I tried all solution like checked my index.php, .htaccess and other plugins but nothing worked for me, I have followed some blogs also how to remove malware from site but that also didn't work, so my question is how to figure out in which file, in which line malicious code is injected and how to remove using any plugin or offline tool.
some links which I followed:
https://www.globalsign.com/en-in/blog/how-to-find-malware
https://dzone.com/articles/what-is-deceptive-site-ahead-warning-in-chrome-and
I was having the same issue couple of weeks before.
I noticed that wp has been installed automatically in my CI. Then i try to find from where it's calling. Then i found something in my libraries that i installed.
Firstly i remove all that calls and then remove one by one wp files
Note: Don't forget to check your htaccess files.
That was my case you might have same. Else you can search.
Ok so long and short of this is, I built a custom plugin for a Wordpress site and was working on a small update. Think perhaps I have a small typo error in the code but after saving the update my site is now showing a 500 error.
I have already attempted the following usual methods without success:
1: renamed the plugin and plugins directories to attempt to both disable individual/all plugins.
2: disabled all plugins via db.
Now the change itself was made via the wp back end, which updated the file. However I cannot see this change via FTP. This baffles me. I would assume somehow the database updated the file somewhere within itself which is perhaps overriding the original file? I haven't seen Wordpress do this before.
I'm not sure but would like to be able to figure out why this happened and if it's fixable.
For now I am just going to do a rollback. Any thoughts on this would be most welcome.
I suggest you try:
restoring the database. If you can’t see which file changed probably means that the database was changed and not a specific file. A popular plug-in for back up and restoration is updraft plus which enables you to select files, the database, or themes. Assuming you don’t have a restore plugin installed you could contact your hosting provider who may be able to restore the database to an earlier version. This functionality may also be available through the control panel on the Domain and Hosting. If this works then at least you know where the trouble lies with your dog and development.
HELP PLEASE! When upgrading my Joomla 2.5.24 to 3.3, the process hung. Now I get the WSOD and get into the administrator (front end does not work either) with error:
ADMINISTRATOR:
Fatal error: Call to undefined method JAdministrator::setHeader() in /home/.... /libraries/cms/html/behavior.php on line 712
FRONTEND:
Fatal error: Call to undefined method JHtml::getJSObject() in /home/..... /libraries/cms/html/behavior.php on line 271
I did a backup up all databases and the files prior to update, but the problem is not resolved when restoring either. I have spent all day trying to figure this out, and I don't know how to debug the setheader(). Can anyone please help me?
First of all, get you site back up.
Since you have a backup, that's going to be "easy".
a. Download a copy of Joomla 3.3, extract the files, and run
find
to get the list of files in Joomla 3.3.
b. Now delete all of those files from your current installation, and restore the backup on top.
There are files that Joomla 3.3 adds that will break Joomla 2.5.
c. Restore the database, and your old site will be working again.
Now the tough part. Figure out what's wrong.
Make an off-line copy of your website.
Are you in the "I'm feeling lucky" mood? Run the update and follow the instructions below.
Do you want to minimize the headaches or you're not comfortable with typing shell commands? First update all your third party extensions to their latest version, and make sure they support Joomla 3.3.
You must have some third party extension that's breaking the site. Here's my quick and dirty procedure to identifying the culprit (but don't share it, it's a secret):
Is it a module, a plugin or a component?
If the WSOD is on both the frontend and backend, it should be a plugin.
Is it a plugin? Rename the plugins folder "plugins2". If the site loads, rename it back to plugins, cd to it, and rename in turn system, content etc. until you find where it is. Keep digging down to the last level and isolate the plugin.
Is it a module? Rename the modules folder and see if the site loads. If it does, go back and rename the folders of the modules you are using in turn. In case you don't know which ones you're using, move them away a few at a time using wildcards to be quicker
Is it a component? Then it's the homepage component and the other pages should load fine.
Once you have identified the culprit, download an update, and apply it manually (open the zip and copy the files where they belong).
You might have to do this multiple times for each broken extension. Remember Murphy's law.
I got a call from a customer who's Wordpress site is not working and I started taking a look at but I cannot understand what's going on there.
On the same server (only another directory) there are other wordpress setups running and they are working perfectly fine. So that's the first part that is kind of ... interesting.
When I logg in to the WP-Admin and access the page again it loads without any problems. Everything is displayed correctly. Same if I add a PHP GET-Parameter like ?anythinginteresting.
In the apache error logs I only find "PHP Notices" - nothing I would worry about.
Any hints? I'm going out of ideas right now...
Seems to be a caching issue as mentioned by #michealrmcneill it comes from the WP-Super-Cache Plugin. This plugin is not "knocked out" when disabled in WP-Admin it needs to be deleted in /wp-content/plugins/wp-super-cache/* to be removed. Addionally there are two files: wp-content/advanced-cache.php and /wp-content/plugins/wp-cache-config.php that are related to the plugin.