Viewing 18 posts - 1 through 18 (of 18 total)
  • Author
    Posts
  • #1439346

    saving doesn’t work. I tried looking for news in the support forum and saw that it is a very common problem but I didn’t have access to the answers for the solution.

    thanks for any help

    Luca

    #1439354

    Hey danieleflacco,
    The message “saving didn’t work” can be giving for many different actions, please explain what you were tring to do when you saw the message.
    I tried to login but I was given a this message:

    Potentially malicious access detected. Access to the page has been blocked due to possible malicious activity

    please disable any security plugins or server settings that might be blocking our access.
    I think that you are tring to import the parallax demo, if so please ensure that the “frontpage” is set as the Frontpage Settings and the blog page is not set, like this:
    Enfold_Support_5306.jpeg

    Best regards,
    Mike

    #1439359

    I don’t know what to say, I checked, I don’t have active protections, perhaps the message reached you because I was also connected from Italy… in any case I receive the message “saving didn’t work” on any page for any customization I do. I also noticed that the builder doesn’t even load the page to customize it… maybe it could be the fault of WP 6.5? I saw that the theme is for WP 6.4?

    #1439362

    Hi,
    The theme works for WP 6.5, when I check the frontend the demo loads:
    Enfold_Support_5318.jpeg
    when I try to login the block message also says: “Servizi Internet” is that your webhost?
    Perhaps they are using mod_security in the server, try asking them. If they are blocking us from loging in they might also be cause a 403 (Forbidden) error in the backend on /wp-admin/admin-ajax.php and causing the “saving didn’t work” message.
    Try asking your webhost if they see any errors in the error log for the server, perhaps they can help solve.

    Best regards,
    Mike

    #1439426

    Hi Mike, thank you for the support
    I disabled ModSecurity. in the meantime I created another account so I can give you another login attempt.
    Unfortunately, the provider does not give me the opportunity to read the logs that interest me to try to understand the problem. Unfortunately, at this moment the problems remain. Save does not work and the main page does not allow the correct use of page builder

    #1439427

    Hi,
    Sorry I’m not able to access, please see the screenshot in the Private Content area.
    If the webhost doesn’t give you access to the error logs, and can’t assist you will server errors, perhaps try a different webhost.

    Best regards,
    Mike

    #1439514

    Hi, I’m checking with the provider. If I don’t find a solution I will change the theme and not the webhost. Forgive me but requesting compensation will be the shortest route. Unfortunately I don’t see any other solutions. I’ll keep you updated. in the meantime I thank you

    #1439519

    Mike I have logs
    In the meantime, take a look when you can, I’m also trying to resolve your access to admin

    #1439538

    Hi,

    I see a lot of errors for server-generated directory index forbidden by Options directive this sounds like you have some server setting making some of your directories forbidden.
    I’m not a server expert so you should have your webhost try to solve this.

    Best regards,
    Mike

    #1439588

    Hi Mike, can you tell me your IP address? I need to let the provider know to understand why you cannot access the dashboard.
    Now I’m trying to do a fresh install of WordPress

    #1439589

    Are the 755 folder permissions OK?

    #1439591

    It is clear that the problem is the ajax call on admin.php?avia_welcome=true&page=avia

    now it’s a clean install with Wp 6.4 without cache and with mod_sec disabled. as soon as the theme was loaded I went to the general setup page and did “save”. the message I got was still unable to save settings and the logged error is attached below

    #1439592

    https://github.com/resource-watch/resource-watch-blog/blob/master/www/wp-content/themes/enfold/framework/php/function-set-avia-ajax.php

    maybe you can try accessing with a proxy… although from the logs I see that there have been accesses from IPs outside Italy

    thnk Mike

    #1439763

    Hi,
    I tried a proxy and was able to get to the login page but the login that you posted above doesn’t seem to be correct, please check:
    Enfold_Support_5384.jpeg

    Best regards,
    Mike

    #1439766

    hi Mike try now, as there was no confirmation access the user was disabled. it should work now

    #1439885

    Hi,
    Thanks when I try to save a setting in the theme panel I see a 500 server error on the core WordPress file admin-ajax.php:
    Failed to load resource: the server responded with a status of 500 () ▸ /wp-admin/admin-ajax.php
    I’m not sure that would cause this as I’m not a server expert, but I see an error user_get_body(tmpstackbuf, 16384): read from client failed, and when I search online it seems to point to the server reaching a limit in mod_lsapi setting, so you cound ask to have this increased.
    I also note that your PHP max input variables is at a low setting, you should ask to change it to 10000, perhaps these are related, but I don’t know.
    It this doesn’t help then try changing your PHP version down to 8.0, I don’t think this is the issue but it is worth trying.

    Best regards,
    Mike

    #1439902

    Unfortunately we haven’t solved anything. I’ll have to change Theme, we’ve already spent a lot of time. I used avada and a couple other themes used by other clients to try and had no problems. Enfold code must be mad at me :-D

    #1439904

    Hi,
    Sorry to hear this, but we don’t have a way to fix server errors. You can login to your Theme Forest account and request a refund We will go ahead and close this thread, Thank you for your patience and understanding and for using Enfold.

    Best regards,
    Mike

Viewing 18 posts - 1 through 18 (of 18 total)
  • The topic ‘Saving didnt work’ is closed to new replies.