Viewing 9 posts - 1 through 9 (of 9 total)
  • Author
    Posts
  • #952762

    When trying to edit some Theme settings we are getting the following error message:

    Saving didnt work! The script returned the following error: Notice: Unknown: file created in the system’s temporary directory in Unknown on line 0. Warning: Cannot modify header information – headers already sent in Unknown on line 0 0

    We have a multisite installation. Only Plugin installed: BackWPup

    Please help!

    #953560

    Hey felix_frank,

    you would need to make your wp-content folder as CHMOD 775. Please try that and let us know if that would work for you.

    Best regards,
    Basilis

    #953956

    Thank you for your reply.
    I have changed the CHMOD of the wp-content folder to 775 but still getting the exact same error message…

    • This reply was modified 5 years, 11 months ago by felix_frank.
    #954817

    Hi,

    Can you please provide us details for login on WordPress & FTP?

    Best regards,
    Basilis

    #955318

    Hi, Your login credentials are below in the PC area.

    Regards
    Felix

    #955319

    You find the Site at: (see below…)

    #955884

    Hi,

    I have created the file and put the right settings can you please review?

    Best regards,
    Basilis

    #956333

    Hi,
    what kind of file have you created???
    I am still getting the same error message!
    I just tried to enter our Themeforrest username and API key to update the theme from our WordPress backend but it still didnt work.
    What is the problem?
    Regards,
    Felix

    • This reply was modified 5 years, 11 months ago by felix_frank.
    #957059

    Hi,

    We would like to modify files in your installation but the Appearance > Editor panel is not accessible. Please enable it or edit the js > framework > js > avia_option_pages.js file, look for this code around line 302.

    answer = 'Saving didnt work!
    The script returned the following error:
    
    '+response;
    

    Below, add this code.

    console.log(response);
    

    We’ll check the site again afterwards.

    Best regards,
    Ismael

Viewing 9 posts - 1 through 9 (of 9 total)
  • You must be logged in to reply to this topic.