eZ Community » Forums » General » Editing ini.append files, restart?

Editing ini.append files, restart?

Editing ini.append files, restart?

Thursday 24 July 2014 9:59:44 pm - 3 replies

I have a settings/override/*.ini.append.php file to edit and when I do the change does not take effect. It's a filter dropdown entry name. There's another ini.append.php file for it in the extension folder. Neither takes effect immediately. Is there something to restart or cache to clear? site.ini.append.php takes effect immediately. Thank you.

Friday 25 July 2014 10:43:43 am

The theory goes as follows:

a: the values in file in override/* folder take precedence over the ones in settings/siteaccess/* or extension/settings/*

b: all changes in ini files take effect immediately (unlike, say, template changes, where you need to clear the template cache). UNLESS you activated a dedicated option in file config.php

What I suspect is happening here is that you might be using the value from your ini file in a template.

If you do so, you need to take into consideration that the caches get layered/stacked because of the execution flow:

ini cache => template cache => view cache (this last one only if the template is used as part of a node view and not as part of page layout).

So, in the worst case scenario, you need to clear 3 caches before the effect of the ini are evident on the site (or just clear "all caches" once).

There is a workaround, to avoid having to clear tpl cache every time your ini changes (in case you are using ezini() in your templates): the "dynamic" flag. See https://doc.ez.no/eZ-Publish/Tech...ata-and-information-extraction/ezini

Modified on Friday 25 July 2014 10:43:57 am by Gaetano Giunta

Friday 25 July 2014 3:50:35 pm

This is helpful, thank you. I edited the override ini file and cleared all caches at once. The change still did not take effect. I am going to hunt down the template file.

Modified on Friday 25 July 2014 3:51:10 pm by Thaler Thaler

Saturday 26 July 2014 2:38:31 am

You might want to turn on the debug display, and use {$value|attribute('show')} to see the value as it is in the template.

Modified on Saturday 26 July 2014 2:39:21 am by Betsy Gamrat


You must be logged in to post messages in this topic!

36 542 Users on board!

Forums menu

Proudly Developed with from