Bug 1086950 - Plugin installation blocked
Summary: Plugin installation blocked
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: wordpress
Version: 20
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Remi Collet
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-04-12 02:21 UTC by Fiable.biz
Modified: 2014-04-15 12:48 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-04-15 12:48:19 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Fiable.biz 2014-04-12 02:21:07 UTC
Description of problem:
/usr/share/wordpress/wp-config.php includes the 2 lines:
/* Disable all file change, as RPM base installation are read-only */
define('DISALLOW_FILE_MODS', true);

which disables all plugin and theme installation or update.

Version-Release number of selected component (if applicable):
wordpress-3.8.1-3.fc20

How reproducible:
Always

Steps to Reproduce:
1. Install "Packages" with "Software".
2. Thanks to Packages, install Wordpress and phpMyAdmin.
3. Create wordpress database and user with phpMyAdmin.
4. Configure the database connection in /usr/share/wordpress/wp-config.php .
5. With Firefox go to /localhost/wordpress/wp-admin/wp-install.php
6. Download, uncompress and copy a plugin into /usr/share/wordpress/wp-content/plugins .
7. With Firefox go to /localhost/wordpress/wp-admin ; in the menu, click on "Plugins".

Actual results:
There is no "Add new" button and no sub-menu in Plugins; there is no "Add new" button in Appearance→Themes; the site administrator is not warned for available updates and the copied plugin doesn't appear.

Expected results:
There should be a "Add new" button and a submenu in Plugins, and an "Add new" button in Themes; the administrator should be warned of available updates (For instance: "There is a new version of Akismet available. View version 2.6.0 details or update now."), and the plugin copied into /usr/share/wordpress/wp-content/plugins should appear.

Additional info:
Changing "define('DISALLOW_FILE_MODS', true);" to
"define('DISALLOW_FILE_MODS', false);"
solves the problems except that the plugin copied into /usr/share/wordpress/wp-content/plugins still doesn't appear.
Of course, when updating the package, the plugins and themes shouldn't be deleted... I don't know yet what will happen at the next package update.

Comment 1 Fiable.biz 2014-04-12 04:06:10 UTC
Related bug: #1070684

Comment 2 Remi Collet 2014-04-15 12:48:19 UTC
Auto-update feature is disable on purpose on RPM base installation, where /usr/share/wordpress is read-only.

Uppacking a theme or a plugin in the correct location work as expected.


Note You need to log in before you can comment on or make changes to this bug.