XOOPS 
Forum
Forum Index General Forums Community Support Modules Support Themes Support Development International Support Module Hack Reviews Theme Designer Talk

Subject:*
<
Name/Email:*
<
Message Icon:*
<
Select*
<
Message:*
<

 
 
 


Click the Preview to see the content in action.
Options:*
<
Confirmation Code*
< 		2 + 8 = ?  
Input the result from the expression
Maximum attempts you can try: 10
*
< 		     

Re: Please reconsider XOOPS 2.3.x Cache Directory Stucture
by phppp on 2008/9/16 8:49:58

Sorry for the confusing naming conversion rule.
perhaps it would be better to use the term of "temporary_data" for "caches" (automatically generated by system and can be removed) and "persistent_data" for "configs" (manually created data)
Re: Please reconsider XOOPS 2.3.x Cache Directory Stucture
by jdseymour on 2008/9/16 1:46:57

From the smarty website:
Quote:
Smarty is too complicated, how can it be that fast?

Smarty's core is pretty lean considering what it is capable of. Most of its functionality lies in plugins. The plugin architecture is designed so that only the required plugins are loaded on demand. With this framework, adding even hundreds of new plugins will not affect performance. This makes Smarty fast, scalable and flexible.

Smarty also has caching features that can dynamically refresh and keep portions of the page uncached at your liking. Caching stores the output of the compiled templates, saving the need to execute them on each invocation.


So smarty in some ways does cache so the code does not have to be compiled on each view.
Re: Please reconsider XOOPS 2.3.x Cache Directory Stucture
by yeppers on 2008/9/15 23:48:24

and skoda cars are generated by volkswagon.

ferrari are generated by scuderia

but you don't call them volkswagon or scuderia do you?

i agree the idea of allowing them to be moved is good. but don't confuse users by telling them that smarty_templates are cache files, because they are not cache. you are supposed to be making things more user friendly, a start on that regard would be to not confuse people and make people think that smarty compiled templates are cache files. maybe long time XOOPS users will know this, but what about the newbies that start looking through the code, like myself.
Re: Please reconsider XOOPS 2.3.x Cache Directory Stucture
by Mamba on 2008/9/15 23:36:59

Quote:
since when has templates_c been a cache folder?

No need to be so literal with the names!

Content of both directories is "generated" by XOOPS, and that's why they are placed together. Of course, if you don't like it to be called "cache", you can always change the name to something different. Actually, for security reasons, it is being encouraged.
Re: Please reconsider XOOPS 2.3.x Cache Directory Stucture
by Mamba on 2008/9/15 23:31:49

Quote:
However, what's the different having cache to be hidden in external directory to ensure the security but we have mainfile.php which contain very critical information, open to the world ?

Actually, we recommend to remove the critical information from the mainfile.php as well. See here...

Search

Advanced Search

Recent Posts

Who's Online

189 user(s) are online (145 user(s) are browsing Support Forums)

Members: 0

Guests: 189

more...

Donat-O-Meter

Stats
Goal: $15.00
Due Date: Jul 31
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $15.00
Make donations with PayPal!

Latest GitHub Commits