Download the PHP package rmp-up/wp-twig without Composer
On this page you can find all versions of the php package rmp-up/wp-twig. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package wp-twig
WP Twig
WordPress with Twig on budget.
- Make WordPress use ".php" and ".html.twig" theme templates
- Split model from view by using filters or
$wp_query - Inherit from multiple themes instead of just one parent
| Before | After |
|---|---|
|
|
Installation / Usage
Require via composer:
And add to your "functions.php" or elsewhere:
This function exists when composer's autoload.php is used. From now on WordPress uses ".php" and ".html.twig" templates.
Templating / How Twig works
See given files in this repo like the "index.html.twig" file:
So by default this page shows "Hello world". In other templates we can use the surrounding HTML but replace blocks:
Note: The path to the theme itself is also needed. This way it is possible to access files of other themes.
Using (WordPress-)Functions
Twig is extended in a way that any function can be used as a filter.
This means functions like date_i18n('l, d.m.Y') or wp_list_pluck are available as filter and function:
But for the sake of segregation
and performance, don't do get_posts('post_type=foo') within a template.
Data, lists and other expensive things should be injected as follows.
Data- / Model-Layer
Injecting data via WP_Query
Since WordPress 1.5 you can inject data in templates using $wp_query->query_vars.
The load_template function (and locate_template in some cases)
extracts the data as variables
and so does wp-twig:
This is how you may have injected data in templates until now and it is still available in Twig:
Injecting variables in the Twig-Context
It gives you four filter for injecting data:
wp_twig_template_{type}_block_{name}(e.g. "wp_twig_template_404_block_foo")wp_twig_block_{name}(e.g. "wp_twig_block_foo")wp_twig_template_{type}(e.g. "wp_twig_template_index" or "wp_twig_template_search")wp_twig_context
Those are executed in the given order so you can basically add data to templates:
The order is important to bypass already added data on the more generic levels:
Bypassing the generation of data spares some time which results in a better performance of the theme. We suggest that you encapsulate data in a Generator of other lazy contructs to enhance this even more.
