Bug 4012 – Allow 'public' files directory to be manipulated by the Files Browser

Bug 4012 - Allow 'public' files directory to be manipulated by the Files Browser

Summary:

Allow 'public' files directory to be manipulated by the Files Browser

Status:	RESOLVED WONTFIX

Product:	PKP-LIB
Classification:	Unclassified
Component:	General
Version:	2.0
Platform:	PC Mac OS X 10.0

Importance:	P1 minor
Assigned To:	PKP Support

URL:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2009-01-16 17:15 PST by James MacGregor
Modified:	2009-01-16 17:27 PST (History)
CC List:	0 users

See Also:
Version Reported In:
Also Affects:

Attachments
Add an attachment (proposed patch, testcase, etc.)

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

Description James MacGregor 2009-01-16 17:15:10 PST

Currently, the Files Browser is only connected to the Administrator-specified 'files' directory. If a Manager wants to modify a public galley, batch upload supplementary images, upload extra content, etc., they have to do so via FTP or similar. Adding read/write functionality for the 'public' directory via the Files Browser would considerably simplify matters, esp. for non-technical JMs. 

Workarounds exist: see http://pkp.sfu.ca/support/forum/viewtopic.php?f=8&p=15395#p15395. However, these workarounds do require a certain level of technical know-how, not to mention command-line access.

Comment 1 Alec Smecher 2009-01-16 17:27:11 PST

Actually, we'll probably go with the solution suggested for bug #1452 instead -- this means getting rid of the public files directly in favour of PHP-mediated access to the files that are currently public. This will be more secure but will require some thought about how to permit users to add their own means of access into this directory (e.g. if they post images etc. for public use).