Plugin cannot upgrade without FTP

  • deanpence

    (@deanpence)


    15 years, 10 months ago

    I’ve been trying to upgrade a plugin on a new client’s site without resorting to FTP to no avail.

    WordPress is installed on CentOS Linux running Apache. Apache runs as apache:apache. The entire WordPress installation is owned by a plain user (call him bob, who, incidentally, has apache as a supplemental group) and the apache group. All files and directories are writable by both user and group, and all directories have the setgid bit set so all new files will be owned by the apache group (mainly so bob can manually upload/add files without messing up WordPress’s ability to write to itself).

    Example directory:

    # ls -ld wp-content/uploads
drwxrwsr-x 6 bob apache 4096 May  5 17:10 wp-content/uploads

    Example file:

    # ls -l wp-content/plugins/pretty-link/pretty-bar.php
-rw-rw-r-- 1 bob apache 6281 May 18 05:53 wp-content/plugins/pretty-link/pretty-bar.php

    The plugin is “Pretty Links Pro”, though I doubt it’s relevant.

    I’ve gone as far as making the apache user the owner of wp-content/plugins (and all its contents) and wp-content/upgrade (which is empty), but attempting to upgrade the plugin still prompts for an FTP login.

    Obviously I don’t want to run an FTP server here. Any ideas on why WordPress cannot upgrade on its own without an FTP login?

Viewing 1 replies (of 1 total)
  • Thread Starter deanpence

    (@deanpence)

    15 years, 10 months ago

    Just in case some details are throwing anyone, the pertinent facts are this:

    – Apache runs as the user apache and the group apache.
    – WordPress’s files and directories are owned by the user bob and the group apache, and they are all writable by user and group.

    Plugins won’t upgrade automatically and fall back to requesting an FTP login.

    Ideas?

Viewing 1 replies (of 1 total)

The topic ‘Plugin cannot upgrade without FTP’ is closed to new replies.