Okay
  Public Ticket #3516811
not working
Closed

Comments

  • Nikolay Kolev started the conversation

    Hello, when I change something in an existing and/or new project it doesn't let me save. That's the mistake. Everything in the system status is OK.

    Attached files:  Eror.jpg

  •  70
    John replied

    Hi Nikolay,

    Thank you for getting in touch with us. My name is John, and I'm happy to assist you today. I appreciate your patience while we've been working toward your ticket.

    Issues like this are usually caused by server configuration or database-related problems. In System Status, have you tried to press the "Update Database" button? 

    If that doesn't help, then this problem is almost always caused by a web server configuration issue. I'd recommend contacting your web server company to look into this. The error message on your screenshot would suggest that it might be an Apache/Nginx problem. Modules like mod_security and other content-filtering solutions might be in place and block requests based on some criteria, like the request body size. That essentially means that your web server automatically rejects requests without consideration because you send more data than what they are willing to accept.

    Best Regards,
    John | Kreatura Dev Team

  • Nikolay Kolev replied

    Hello,
    please give more detailed information. The problem is not in the firewall (we turned it off but it has no effect). The host says everything is fine. After all, we can't work. Everything else is thrown away. The site is a new WP and no other plugins are installed

  •  70
    John replied

    Please navigate to System Status and press the Update Database button if you haven't done it already. 

    If that doesn't help, it's almost certain that a server configuration issue causes the problem you're experiencing. Web hosts usually aren't too keen to help customers since they assume their problems are related to the plugins they use and external code. However, in the case of LayerSlider, saving issues are almost exclusively caused by the web server's (Apache, nginx, etc.) mod_security module. We have had several cases where the host insisted that everything is properly configured on their end, only to realize they do use mod_security, and the problem is caused by a limit on the request body size. 

    Only they have the necessary tools to make the necessary changes. They can access the log files to investigate this issue and identify the problem, so their cooperation is crucial, I'm afraid. As noted before, we usually blindly guess the actual issue based on past cases, but hosts sometimes simply refuse to look, so you might need to pressure them a bit.

    Best Regards,
    John | Kreatura Dev Team