[ php-blog-Feature Requests-1771722 ] add templates_local and plugins_local directories
"SourceForge.net" <[email protected]>
| Newsgroups | gmane.comp.serendipity.trackers |
|---|---|
| Message-ID | <[email protected]> |
Feature Requests item #1771722, was opened at 2007-08-10 16:54
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=542825&aid=1771722&group_id=75065
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Priority: 5
Private: No
Submitted By: Christian Boltz (christian_boltz)
Assigned to: Nobody/Anonymous (nobody)
Summary: add templates_local and plugins_local directories
Initial Comment:
When doing a shared installation, symlinking the templates and the plugins is too difficult because the same directory can contain subdirs shipped with s9y and subdirs later installed by the user.
The current way is:
cd plugins && ln -s ../s9y-shared/plugins/*
which results in lots of symlinks.
The better way would be to have
a) a symlink to the shared plugins directory (like the htmlarea symlink)
b) another directory ("plugins-local") for plugins installed by the user
Advantages:
- less symlinks needed
- no manual work required in case s9y ships with more templates or plugins one day (with the current way, you have to create a symlink for the new plugin)
- read-only and writeable directories (from user's and webserver's POV) are better separated
- users can install newer versions of plugins in their plugins-local directory
All this is also valid for templates.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=542825&aid=1771722&group_id=75065
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/