OpenCart Community

Normally the twig rendering engine compares the dates of the common/header.twig and its processed cache file to see whether it should update the cache with your changes.

	public function render($template, $cache = false) {
		// specify where to look for templates
		$loader = new \Twig_Loader_Filesystem(DIR_TEMPLATE);

		// initialize Twig environment
		$config = array('autoescape' => false, 'auto_reload'=>true);

		if ($cache) {
			$config['cache'] = DIR_CACHE;
		}

		$this->twig = new \Twig_Environment($loader, $config);
		
		try {
			// load template
			$template = $this->twig->loadTemplate($template . '.twig');
			
			return $template->render($this->data);
		} catch (Exception $e) {
			trigger_error('Error: Could not load template ' . $template . '!');
			exit();	
		}	
	}	

	public function index(&$route, &$args, &$template) {
		$this->log->write("ControllerEventTheme::index: route='$route' priority=1000");
		// If there is a template file we render
		if ($template) {
			// include and register Twig auto-loader
			include_once(DIR_SYSTEM . 'library/template/Twig/Autoloader.php');
			
			Twig_Autoloader::register();
					
			// specify where to look for templates
			$loader = new \Twig_Loader_Filesystem(DIR_TEMPLATE);		
			
			$config = array('autoescape' => false, 'auto_reload'=>true);
			
			if ($this->config->get('template_cache')) {
				$config['cache'] = DIR_CACHE;
			}
			
			// initialize Twig environment
			$twig = new \Twig_Environment($loader, $config);
				
			return $twig->createTemplate($template)->render($args);
		}
	}	

If true, whenever a template is rendered, Symfony checks first if its source code has changed since it was compiled. If it has changed, the template is compiled again automatically.

JNeuhoff wrote: ↑

Sun Jun 14, 2020 10:31 pm

There are no observable performance reductions when using 'auto_reload'. In fact, it's finally added in the latest OpenCart master branch.

Having said that, IMHO it was a bad idea to use Twig in the first place, PHP already is a template language anyway.

JNeuhoff wrote: ↑

Sun Jun 14, 2020 10:31 pm

There are no observable performance reductions when using 'auto_reload'. In fact, it's finally added in the latest OpenCart master branch.

Having said that, IMHO it was a bad idea to use Twig in the first place, PHP already is a template language anyway.

Melmoth wrote: ↑

Wed Jun 17, 2020 12:02 am

It's weird because no matter the piece of code I change in .twig files it doesn't affect the webpage, but if I delete the same twig files

xxvirusxx wrote: ↑

Wed Jun 17, 2020 12:57 am

Edited with what?

xxvirusxx wrote: ↑

Wed Jun 17, 2020 12:57 am

When you make changes don't forget first to : Refresh Ocmod modifcations and clear VQMOD cache if you use then clear Theme cache, SASS cache from Dashboard right top gear.

letxobnav wrote: ↑

Mon Jun 15, 2020 12:27 pm

I just change:

Code: Select all

            'auto_reload' => null,

to

Code: Select all

            'auto_reload' => true,

in system/library/template/twig/environment.php

check the same file next day from theme editor and the file goes back to the older one before I changed anything

to make this work I have to copy/paste the same code through Theme Editor

letxobnav wrote: ↑

Thu Jun 18, 2020 10:32 pm

scenario A

check the same file next day from theme editor and the file goes back to the older one before I changed anything

Since the theme editor stores the source in the database.
I would say that you or your host is restoring or losing database content at some interval.

Scenario B

to make this work I have to copy/paste the same code through Theme Editor

Since you have a version of the file stored in the database (theme table) which overides the core and any modification file, file changes there will have no effect.

So either use the theme editor (which you should never do as it is crap) or stick to using OCMOD for all changes.

And if I decided to stop using Theme Editor from now on, what I should do to make it work for an external editor/FTP approach (my scenario B)?

letxobnav wrote: ↑

Fri Jun 19, 2020 8:50 am

And if I decided to stop using Theme Editor from now on, what I should do to make it work for an external editor/FTP approach (my scenario B)?

remove the version from the theme editor.
If you need to keep those changes, save the source and put it in an ocmod or copy it over the core.
In the end, keep your theme table empty.

We don't copy over the core!

letxobnav wrote: ↑

Fri Jun 19, 2020 8:14 pm

We don't copy over the core!

There is no We.