I didn't want to create unneccessary extra steps if an appropriate area already exists. I'm thinking I might need to step back and look at the problem again. Writing a text file isn't going to be a good solution in a multi-user system.Brf wrote:Why dont you just create a new folder?
What about the /store folder? It should be writable...microUgly wrote:I have an ACP module that needs to generate some text files. The url for the text files will then be loaded by flash object in the ACP. The files will be constantly overwritten.
Where is the best place to write these files to? I was thinking the cache, since it's the only folder I know of that will have write access, but web access is forbidden (the flash object needs a URL).
I could make the text files php files, but that would require having to duplicate a lot of code, implement security, etc ,etc. And I would still need to store it somewhere. If they are just plain text files I don't need to be concerned about people prodding them if they find them.
I'm aiming to make the mod easily distributable.
This is the kind of suggestion I was looking for But I don't quite get how it would work. When you say "text mode" you do mean a mode of a module (where a module can have several modes). How do you create a plain text mode--one that doesn't use the ACP template?eviL<3 wrote:I don't see why you are generating text files anyway. Why don't you just generate them in the ACP module? You just add a new "text" mode and have the swf call that. No need to write to any files at all.
Code: Select all
<?php header('Content-type: text/plain; charset=utf-8'); echo 'I am a text file.'; exit; ?>
Is there a trick to get around this? It doesn't really matter if I use a template or not, but I think it would be best to set the content type to plain text. Thanks.General Error
template->_tpl_load_file(): File ./style/.html does not exist or is empty