• I have problems after the automatic update to 4.1.1.

    The Appearance Editor gives me this line in place of Update button –
    “You need to make this file writable before you can save your changes. See the Codex for more information.”

    The files are 0664. Made it 755. Still didn’t work. Worked only after 777. But I am sure that is not the right permission to set. Right?

    A related problem is Media Library – files uploaded AFTER the 4.1.1 update are bad links even though I see them on the server via cPanel and ftp in my media folder.

    Using a custom theme.

Viewing 5 replies - 1 through 5 (of 5 total)
  • Hi, jainy25, & welcome. The usual recommendation when we see this kind of thing is to ask the user to reupload WordPress, as some sort of file corruption has generally occurred. Please let us know if that does or does not resolve your prolem, won’t you?

    All the very best.

    I am the owner of the site with this problem. I just reinstalled 4.1.1 with “No Change to the problem”. I also have an interaction problem between wordpress templates and external scripts that started exactly when 4.1.1 autoupdate occurred last month. I had no problems with 4.1.

    suggestions?

    Hi, the508seal. It does sound as though there’s some incompatibility between a theme, a plugin, or both & the latest version of WordPress.

    Could you please provide us w/a link to your site? Doing so often proves really helpful.

    Here are the usual steps to take when this type of situation arises.
    1) Revert to a default theme (that’s 2015 now) & see if that resolves the issue.
    2) If it does not, then rename the plugins folder under wp-content to something like plugins1.
    3) If that resolves the problem, then what we do is:
    a) Rename the plugins1 folder back to plugins.
    b) Rename all the plugins in that folder, i.e., akismet1, etc., except 1. Generally, the plugins that ship w/WordPress, such as Akismet, are renamed to their correct names first, as these are the least likely to cause compatibility issues.
    4) Test after each rename to see if it breaks the site. Disable any caching, & don’t forget to clear your browser cache prior to each retest. By so doing, it’s generally pretty easy to determine what’s breaking the site’s compatibility.

    Please don’t hesitate to request additional clarification if you need it, though judging by your previous posts, (your employee’s/contractor’s? previous post), you’ve likely got it well in hand.

    Please also let us know your findings, as they’re always instructive.

    arasan.com

    changing the theme or renaming plugin directory has no impact on
    you need to make this file writable before you can save your changes. See the Codex for more information.

    I have a cloned test site on the server running 4.0.1 – and it has the same problem.
    Could an issue with a software update?
    Apache Version 2.2.29
    PHP Version 5.3.29
    MySQL Version 5.5.42-cll

    the508seal, sorry, but I have a few more questions:
    First, could you please provide a copy of your .htaccess file?
    2nd, who are you hosting with? There have been some issues like this w/some hosts, so it’s best to see if yours is 1 that falls into that category. Although this seems coincidental to the 4.1.1 update, since you’re having a problem w/a clone test server, it rather suggest to me that the host may have altered some configuration files & caused this, as opposed to the update itself. You might wish to check w/them & see whether this is the case.

    What type of hosting do you have, i.e., shared, virtual, dedicated?

    Here is an article regarding permissions that you might wish to consult:
    http://codex.wordpress.org/Changing_File_Permissions
    but from the sound of it, you’ve set them according to this article. Still, since server configurations vary, the article may well be worth a look. I really am wondering if your host altered its configuration files, though.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Appearance and Media Library not working’ is closed to new replies.