adgreen
Posts: 27
|
| Posted: 11/15/2006, 3:18 AM |
|
It would be useful to be able to specify the location of common files that are generated by CCS.
Just as we can put templates into a folder, being able to group common files into a folder rather than in the site root makes sense because:
1. It's just neater that way - less clutter.
2. "Namespace" issues cannot occur - files are unlikely to be executed (or overwritten/deleted) accidently by external code.
3. Critical common files can be protected (using permissions or whatever) more easily in folders.
And, if you're like me and you get lost easily, anything helps.
DonB wished this kind of thing some time ago. I wish it again.
|
 |
 |
WKempees
|
| Posted: 11/15/2006, 4:05 AM |
|
Second that.
Also to be able to define :
temp and upload path for both design time and publish,
all ServerProfile dependant.
Walter
"adgreen" <adgreen@forum.codecharge> schreef in bericht
news:22455af7816571c@news.codecharge.com...
> It would be useful to be able to specify the location of common files that
> are
> generated by CCS.
>
> Just as we can put templates into a folder, being able to group common
> files
> into a folder rather than in the site root makes sense because:
> 1. It's just neater that way - less clutter.
> 2. "Namespace" issues cannot occur - files are unlikely to be executed (or
> overwritten/deleted) accidently by external code.
> 3. Critical common files can be protected (using permissions or whatever)
> more
> easily in folders.
>
> And, if you're like me and you get lost easily, anything helps.
>
> DonB wished this kind of thing some time ago. I wish it again.
>
>
> ---------------------------------------
> Sent from YesSoftware forum
> http://forums.codecharge.com/
>
|
|
|
|
dhempy
Posts: 40
|
| Posted: 11/15/2006, 6:34 AM |
|
Just to piggyback on this wish, how about allowing a custom location for style sheets, images, and javascript files? Our Apache server does not allow these files to be served from below the cgi-bin directory, so we get none of those features right out of the box.
We get around it for the styles by copying them out under the document root and editing the <link> tag for the .css file, and could do it for the javascript and images, I suppose.
This would be a MAJOR convenience to Apache users..
Thanks,
-dave
_________________
David Hempy
Director of Broadcast and Education Technology
Kentucky Educational Television
800-333-9764 |
|
|
|
Joe Blocher
|
| Posted: 11/17/2006, 2:45 PM |
|
Hello,
I agree to all that wishes above..
I'm evaluating CCS and tried to integrated some CCS-reports, grids ... into
some of my existing large php-projects.
For these projects I use the concept of the Fusebox
(http://www.fusebox.org/) in an extented way.
That means, the php-files are situated in a private folder and cannot be
called directly from the URL .
For example: http://mydomain/main.php?fuseaction=eventslist.show calls a
script ../private/events/lists/dsp_show.php.
Besides:
I have to edit Navigator.php and Sorter.php to comment out
//$this->FileName = $FileName;
because the calling script (dsp_show.php) is not visible for the browser.
Then the grids/reports work well.
So - for me:
- the Style-folder should be located in the public-folder with direct access
- the common files I would like to place into private/lib
- the locale-files (en.txt, de.txt ...) I want to locate in a folder
(private/lang ..) where the customer has permission to edit and translate
- the db-configuration should be seperated (for example config.db.inc.php)
so that I can store it with my other config-files
in a folder private/config ...
I know, these are my private wishes. But as I can see above, a
path-configuration for all that parts (like the template-path)
can be usefull for many others.
Best regards
Joe
|
|
|
|
|
