I had to do clearing of Templates Cache and was going to system/cache
folder to execute the "clean.sh" script while 2 things crossed my
1. Why do we keep "clean.sh" within system/cache folder while it's a
clearly a Utility and should be located under tools/ folder where it
I see the following benefits with moving it there:
a. all utility scripts should be moved to 1 location (ie. fix_perm.sh
and so on)
b. don't have to have anything within system/cache folder that can NOT
c. shorter path to reach the script in ssh when typing.
2. Why not to give a better name once it's in tools/ folder - I don't
think "clean.sh" is self explanatory by any means
I propose - "clear_cache.sh".
Let me know what you think.
1. I would MOVE tools/.htaccess to ROOT of installation.
a. most of people installing In-Portal NEVER know where to
look .HTACCESS so when it's in the right place from the step one - we
have one thing less to explain about considering there is NO harm to
the system even if ModRewrite is Off.
b. we need kind of need to protect tools/ folder with it's
own .htaccess so NO other then PHP files can be executed (minor)
To unsubscribe, reply using "remove me" as the subject.
About .htaccess, of course I agree too, as this is the first action I
perform when I install In-Portal.
2010/4/5 Dmitry Andrejev <dand...@gmail.com>:
685: Moving .Htaccess and Cache.sh files to more suable location
> 2010/4/6 Dmitry Andrejev <dandre...@gmail.com>
> > Hi Phil,
> > It a bit too early to work on French Documentation for Developers since we
> > don't have English fully completed yet. Besides it a lot of work and not as
> > easy as you think. I think community would love to see more themes first and
> > then French version of Technical document since in most cases English
> > is sufficient.
> > What Alex meant is that we'll be documenting it in English first.
> > DA.
> > On Tue, Apr 6, 2010 at 7:50 AM, Phil -- wbtc.fr -- <p...@wbtc.fr> wrote:
> >> I was replying to your message where you said "create proper user
> >> documentation"
> >> Should I post questions in groups, or can we start working on
> >> documentation directly?