1
RicoCali
templates_c
  • 2004/8/15 16:20

  • RicoCali

  • Not too shy to talk

  • Posts: 120

  • Since: 2002/7/29


Where is the code mechanism where it starts writing the cache information to templates_c directory.

2
tl
Re: templates_c
  • 2004/8/15 17:28

  • tl

  • Friend of XOOPS

  • Posts: 999

  • Since: 2002/6/23


I think footer.php deals with template files while header.php deals with module/block cache.

3
Dave_L
Re: templates_c
  • 2004/8/15 17:32

  • Dave_L

  • XOOPS is my life!

  • Posts: 2277

  • Since: 2003/11/7


I think that's triggered by calling one of the methods XoopsTpl::display or XoopsTpl::fetch. The class XoopsTpl is defined in class/template.php, and is derived from the class Smarty, which is defined in class/smarty/Smarty.class.php. Smarty generally keeps track of whether a template needs to be compiled (into templates_c/) and/or whether the cache needs to be generated (in cache/). The class XoopsTpl overrides some of Smarty's default behavior.

4
jlm69
Re: templates_c
  • 2004/8/15 17:43

  • jlm69

  • Module Developer

  • Posts: 719

  • Since: 2002/7/19


Also,

XOOPS_COMPILE_PATH

refers or equals to templates_c
as in class/template.php function XoopsTpl()

seems it might create the files from

class/template.php
function xoops_template_create

5
RicoCali
Re: templates_c
  • 2004/8/15 17:45

  • RicoCali

  • Not too shy to talk

  • Posts: 120

  • Since: 2002/7/29


Thanks guys! If XOOPS ever has a international conference I'll buy the first round

Login

Who's Online

66 user(s) are online (37 user(s) are browsing Support Forums)


Members: 0


Guests: 66


more...

Donat-O-Meter

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

Latest GitHub Commits