Public Ticket #1083609
Imported Slider will not Save


  •  2
    cjkeeme started the conversation

    I am receiving the following error when trying to edit an imported slide: 

    It seems there is a server issue that prevented LayerSlider from saving your work. Please check LayerSlider -> System Status for potential errors, try to temporarily disable themes/plugins to rule out incompatibility issues or contact your hosting provider to resolve server configuration problems. Your HTTP server thrown the following error: 

    Not Found

    This plug came with my theme (X Theme), but I purchased a separate license so I may import slides.  It was working fine before.  What is wrong?

    EDIT: The first slider I imported is working just fine.  Any other I import does not work. Also, when I import 'FREE' sliders it is also working properly.  It is only with the 'PREMIUM' sliders beyond the first one I imported that the problem continues. 

  • [deleted] replied

    Hey cjkeeme,

    As the notification suggests, the problem is most likely related to a server issue or misconfiguration (some kind of limitation probably). Please check the LayerSlider System Status located on the WordPress sidebar for any related error messages.

  •  2
    cjkeeme replied

    All green check marks.  I have also opened up a ticket with my host, but they don't see any issues.  

    I am able to edit some of the ones that I import.  Out of the 12 I have loaded only 2 will allow edits to happen.  What else can I check?

  • [deleted] replied

    The problem is almost certainly caused by a server configuration issue or server limitation. As the error message suggests, the webserver cannot save and fails with a '404 Not Found' error, which is definitely related to the server.

    Unfortunately we cannot provide additional feedback on this as we do not have access to your server settings. Your hosting company will have to look into this. They should be able to see the problem from the log files as well.

    Our best guess would be that there's a filter enabled that is causing this issue. For example query strings or content length.

    You could also check the custom .htaccess files to see if there are any custom rules that might be interfering.