WordPress.org

Ready to get started?Download WordPress

Forums

Don't know how to fix so I stop getting this message... (5 posts)

  1. dmpohlmeier
    Member
    Posted 4 years ago #

    I keep getting this message every time I try and save a file in WP. This only happens when I am in the editor mode making changes to the actual code of a theme.

    Warning: fopen(E:\sites\www.seminary.edu\wordpress/wp-content/themes/perforated/footer.php) [function.fopen]: failed to open stream: Permission denied in E:\sites\www.seminary.edu\wordpress\wp-admin\theme-editor.php on line 54

    Warning: Cannot modify header information - headers already sent by (output started at E:\sites\www.seminary.edu\wordpress\wp-admin\theme-editor.php:54) in E:\sites\www.seminary.edu\wordpress\wp-admin\theme-editor.php on line 69

  2. Samuel B
    moderator
    Posted 4 years ago #

    Warning: fopen

    this a security feature of your host
    ask them how you can work around it

    Warning: Cannot modify header information

    this is likely caused by a plugin conflict
    deactivate them and reactivate one by one until you find the offender

  3. Kailash
    Member
    Posted 4 years ago #

    From the first error, it seems you do not have enough permission to edit the file via wordpress editor. Regarding second error, sometimes it happen if there is a blank space before <?php tag or after ?>.

    Kailash

  4. dmpohlmeier
    Member
    Posted 4 years ago #

    samboll and Kailash1, thanks for the responses.

    I have tried changing my permissions with no success. What kind of security feature would you be referring to so I can let our I.T. guy know?

    As far as plugins go, I don't have any currently running on the blog.

    The lines in the code that the error refers to doesn't happen in the code where <?php tag or after ?> happens.

  5. Samuel B
    moderator
    Posted 4 years ago #

    What kind of security feature would you be referring to so I can let our I.T. guy know?

    wordpress uses fopen to retrieve http headers - if that doesn't work it falls back on cURL

    you could try chmod 666 on the one particular file to see if that helps but more likely something will need to be configured in php.ini or on server
    your IT guy will likely know about this error

Topic Closed

This topic has been closed to new replies.

About this Topic