| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | |
| |
| |
| | |
PHPBB3-10392
|
| |\ \
| |/
|/|
| |
| |
| | |
* cs278/ticket/10384:
[ticket/10384] Language variable replacements should not check for var prefix.
[ticket/10384] Update unit tests to test for failing variable.
|
| | |
| |
| |
| | |
PHPBB3-10384
|
| | |
| |
| |
| |
| |
| | |
Only set the file if an mtime check or recompile are required.
PHPBB3-10375
|
| | |
| |
| |
| |
| |
| |
| |
| | |
- Removed duplicate variables
- Set $source_file earlier for cache checks
- Fixed useless mtime check
PHPBB3-10375
|
| |/
|
|
| |
PHPBB3-10375
|
| |
|
|
| |
PHPBB3-10374
|
| |
|
|
|
|
|
|
|
| |
Most template variables can now have their PHP variable name resolved instead
of only compiling directly. This allows for the use of block vars in INCLUDE
statements. This does not work for language variables since they require
multiple checks. Added tests for the new types of allowed INCLUDEs.
PHPBB3-10322
|
| |
|
|
|
|
|
| |
Dynamic template includes from variables was not implemented in the new
templating system.
PHPBB3-10322
|
| |
|
|
|
|
| |
Fixing bug in class phpbb_template_renderer_eval
PHPBB3-10350
|
| |
|
|
|
|
| |
It is no longer needed as locator is injected into template.
PHPBB3-9726
|
| |
|
|
| |
PHPBB3-9726
|
| |
|
|
| |
PHPBB3-9726
|
| |
|
|
|
|
|
| |
set_custom_template performs these calls, repeating them in
set_template is not needed.
PHPBB3-9726
|
| |
|
|
| |
PHPBB3-9726
|
| |
|
|
| |
PHPBB3-9726
|
| |
|
|
| |
PHPBB3-9726
|
| |
|
|
| |
PHPBB3-9726
|
| |
|
|
| |
PHPBB3-9726
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The origins of orig_tpl_* are not pretty. Please see the following commits
and associated tickets: r9823, r9839, r9847, r10150, r10460.
In short, multiple hacks were required due to template engine reading
inheritance/storedb flags from $user (global) even when the template that
was being looked up or rendered was not the "active style of the
current user".
We no longer store templates in the database, removing half of the problem.
This commit fixes the second half of the problem by deleting
set_template_path function from template locator, and moving that logic
back into the template class' set_template. set_template now calls
set_custom_template, the latter only taking the template path and the
fallback paths as parameters. With this change template locator no longer
uses $user and does not use phpbb root path either.
All logic involving setting the user's "active" template is now
encapsulated in a single template class's function, set_template.
Setting other templates is done via set_custom_template and the caller
is responsible for determining and passing in fallback/inheritance path,
if any.
PHPBB3-9726
|
| |
|
|
|
|
|
|
|
| |
set_custom_template.
This parameter was unused, it was only used by template's set_custom_template
to determine cache file prefix.
PHPBB3-9726
|
| |
|
|
| |
PHPBB3-9726
|
| |
|
|
|
|
|
|
|
|
|
| |
Template locator is responsible for maintaining mapping from template
handles to filenames and paths, and provides resolution services
using these mappings.
Template locator is aware of template inheritance and is capable of
checking template file existence on the filesystem.
PHPBB3-9726
|
| |
|
|
|
|
|
|
| |
This seems to have been used for db storage of templates.
We no longer offer db storage of templates, and thus currenty
$files_template is only written to but not read anywhere.
PHPBB3-9726
|
| |
|
|
| |
PHPBB3-9726
|
| |
|
|
|
|
| |
Add docblocks for phpbb_template_filter, remove the useless constructor.
PHPBB3-9726
|
| |
|
|
| |
PHPBB3-9726
|
| |
|
|
| |
PHPBB3-9726
|
| |
|
|
| |
PHPBB3-9726
|
| |
|
|
|
|
|
|
|
|
| |
The template stream filter no longer depends on the $config global.
Instead it uses a 'allow_php' param that is passed via
stream_bucket_append's last argument.
Tests also adjusted.
PHPBB3-9726
|
| |
|
|
| |
PHPBB3-9726
|
| |
|
|
|
|
| |
This allows making use of autoloading.
PHPBB3-9726
|
| |
|
|
|
|
| |
This is not used since the switch to git.
PHPBB3-9726
|
| |
|
|
| |
PHPBB3-9726
|
| |
|
|
|
|
| |
Access specification in php 5 is done directly on functions/properties.
PHPBB3-9726
|
| |
|
|
| |
PHPBB3-9726
|
| |
|
|
| |
PHPBB3-9726
|
| |
|
|
|
|
|
| |
Hopefully this is right, I have not checked it against the manual
(assuming the manual even covers these things).
PHPBB3-9726
|
| |
|
|
| |
PHPBB3-9726
|
| |
|
|
| |
PHPBB3-9726
|
|
|
PHPBB3-9726
|