| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
| |
PHPBB3-11598
|
| |
|
|
| |
PHPBB3-11598
|
| |
|
|
|
|
|
|
| |
Was originally moved because I thought that a new test file might mean a new
instance and the memory would be cleared, fixing the original problem, but
that isn't true and it was fixed another way.
PHPBB3-11598
|
| |
|
|
| |
PHPBB3-11598
|
| |
|
|
| |
PHPBB3-11598
|
| |
|
|
| |
PHPBB3-11598
|
| |
|
|
| |
PHPBB3-11598
|
| |
|
|
|
|
|
|
|
|
| |
Must create a template file in the cache to load as this causes errors
otherwise. The problem was that Twig builds template files into classes,
which are always stored in PHP memory after being loaded. Because of this,
Twig would never recompile a template that was already compiled on the same
page load (so switching enable PHP on/off in two tests would not work).
PHPBB3-11598
|
| |
|
|
| |
PHPBB3-11598
|
| |
|
|
|
|
|
| |
Automatically parsing inline variables the same way it is done for
INCLUDE, INCLUDEPHP
PHPBB3-11598
|
| |
|
|
|
|
|
| |
This had to be done because cached template files are available in memory,
so Twig doesn't ever reparse a template on the same page load
PHPBB3-11598
|
| |
|
|
|
|
|
| |
Various tests were broken completely, and some things such as whitespace
changed with Twig
PHPBB3-11598
|
| |
|
|
|
|
| |
My method was not working correctly, will work on it more later.
PHPBB3-11598
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
According to the test, template event behavior was never correct.
Only ONE template event file is supposed to be included from EACH
extension. As it was before, EVERY matching template event file from
each extension was included (this was how it was designed).
E.g.
Event call in prosilver "foo"
Extension has template "foo" in prosilver AND all
foo from all would be included, then foo from prosilver would be included
This was clearly not designed correctly as only the most specific event
file from each extension should be loaded, otherwise events could only
ever be put in a single style tree (either only all, or only prosilver
and subsilver2 and any style that inherits from neither of those).
Otherwise the events would be duplicated on output (which is clearly not
desirable).
The Twig behavior already was correct as I designed it, so only the one
most specific template event file found would be included from each
extension. The tests had to be updated for the correct expected output.
PHPBB3-11598
|
| |
|
|
| |
PHPBB3-11598
|
| |
|
|
| |
PHPBB3-11598
|
| |
|
|
|
|
| |
No longer needed
PHPBB3-11598
|
| |
|
|
|
|
| |
No longer needed
PHPBB3-11598
|
| |
|
|
| |
PHPBB3-11598
|
| |
|
|
| |
PHPBB3-11598
|
| |
|
|
|
|
| |
No longer necessary
PHPBB3-11598
|
| |
|
|
|
|
| |
No longer necessary
PHPBB3-11598
|
| |
|
|
|
|
|
|
| |
Invalid tags is no longer a valid test (invalid tags are ignored)
Twig contains tests for loading files, so we should not need to test this
PHPBB3-11598
|
| |
|
|
| |
PHPBB3-11598
|
| |
|
|
|
|
| |
Replace all new phpbb_template( with new phpbb_template_twig(
PHPBB3-11598
|
| |
|
|
| |
PHPBB3-11435
|
| |\
| |
| |
| |
| |
| |
| |
| |
| | |
# By Vjacheslav Trushkin
# Via Vjacheslav Trushkin
* remotes/cyberalien/ticket/11482:
[ticket/11482] Use double quotes for code
[ticket/11482] Unit tests for advanced DEFINE
[ticket/11482] Implementation of advanced DEFINE tag
|
| | |
| |
| |
| |
| |
| | |
Unit tests for advanced DEFINE and ENDDEFINE
PHPBB3-11482
|
| | |
| |
| |
| |
| |
| |
| | |
As requested by Oleg
https://github.com/phpbb/phpbb3/pull/1340#issuecomment-17306967
PHPBB3-11519
|
| | |
| |
| |
| |
| |
| |
| |
| | |
This test fails until 11435 is fixed
Add newlines at EOF
PHPBB3-11435
|
| | |
| |
| |
| | |
PHPBB3-11435
|
| |/
|
|
| |
PHPBB3-11435
|
| |
|
|
| |
PHPBB3-11323
|
| |\
| |
| |
| |
| | |
* develop-olympus:
[ticket/11323] Add tests for inclusion of defined variables
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
This adds 2 tests for the template engine. The test using
include_define_variable.html will test if a defined variable, which was
defined with another template variable, can be used to include a file.
The second test will do the same inside a loop using a loop variable.
PHPBB3-11323
|
| | |
| |
| |
| | |
PHPBB3-11159
|
| | |
| |
| |
| | |
PHPBB3-9550
|
| | |
| |
| |
| | |
PHPBB3-9550
|
| | |
| |
| |
| | |
PHPBB3-9550
|
| | |
| |
| |
| | |
PHPBB3-9550
|
| | |
| |
| |
| | |
PHPBB3-9550
|
| | |
| |
| |
| |
| |
| |
| | |
This allows template code to know the entire style hierarchy for
templates being rendered.
PHPBB3-9550
|
| | |
| |
| |
| | |
PHPBB3-9550
|
| | |
| |
| |
| | |
PHPBB3-9550
|
| | |
| |
| |
| |
| |
| | |
Having all files in one directory is too much of a mess.
PHPBB3-9550
|
| | |
| |
| |
| | |
PHPBB3-9550
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
Also drop the irrelevant includejs code and add a simple
template event test. The simple test is not working yet however
due to the template engine not correctly tracking which template
it is rendering.
PHPBB3-9550
|
| | |
| |
| |
| | |
PHPBB3-9550
|
| | |
| |
| |
| |
| |
| | |
Adding template events test
PHPBB3-9550
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* p/ticket/10933:
[ticket/10933] Prose for get_first_file_location.
[ticket/10933] Remaining documentation for added functions in resource locator
[ticket/10933] Update template locator test to use style resource locator.
[ticket/10933] Dispose of locate function in template class.
[ticket/10933] Add mutators for template_path to style resource locator.
[ticket/10933] Delete template_path assignment.
[ticket/10933] Delete template_path from template class.
[ticket/10933] Add get_first_template_location.
|