Answer the question
In order to leave comments, you need to log in
Problem with writing data on the server. Error: Blocked a frame with origin. Server problem?
Error code:
Uncaught DOMException: Blocked a frame with origin " http://domain.ru " from accessing a cross-origin frame.
at contents ( http://domain.ru/wp-admin/load-scripts.php?c=0&load...
at Function.map ( http://domain.ru/wp-admin/load-scripts.php? c=0&load...
at a.fn.init.n.fn.(anonymous function) [as contents] ( http://domain.ru/wp-admin/load-scripts.php?c=0&load...
at http://domain.ru/wp-content/themes/spring/admin/js/...
I didn't work
on the server and the site, there were problems with saving any changes on the site.During
the check, I found out that the problem is on the entire server There are only wordpress sites on it.I read that the engines have nothing to do with it.
There was also a problem with FTP, I can upload, I can’t upload, a transfer error. Tried different users.
I checked the file attributes, everything is fine.
The server administrator assures that everything is fine with them, there are no errors.
Manipulation with X-Frame-Options: SAMEORIGIN didn't work.
I don't understand the cause and can't fix it. All description of the error is related to the operation of the frame, multi-domains, and loading in different domains... The admin panel does not work for me. Did a reset, reset the engine. The result is the same.
Answer the question
In order to leave comments, you need to log in
Hello!
As I understand it, you have a VPS -
- check the user rights on the public_html directories and the lower ones for the VP.
To change permissions use:
- check chmod for files and folders. Folders - 755, files 644
CMS WP will work even if it does not have enough read and write permissions. Only you will not be able to update plugins and themes, update the core of the WP, as well as update htaccess & robots files from the admin panel and upload images, but it will work. If the admin panel does not work for you (white screen), look for a conflict with plugins. Enable wp-config.php debug and see what's wrong. Try to also remove the content of htaccess and create a new one.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question