jarednova

This is now resolved in Timber 1.20.0 — thanks @rakesh1247 !

@jbchristy hi there! You can return the output via Timber::compile instead like so …

$output = Timber::compile( $layout_template, $context );
// do other stuff
$output .= Timber::compile( $layout_template, $context );
// etc.

echo $output;

@gutterboy333 it’s a whole different workflow outside of the WordPress plugin repo. You manage/update through Composer — not the WP plugin dashboard.

With Composer/Packagist it becomes a theme dependency that lives inside your project’s /vendor directory. Here’s a setup guide from Timber:

https://timber.github.io/docs/getting-started/setup/

@gutterboy333 we distribute the WP.org version to work with PHP 5.6. Unfortunately that means we have to use Twig 1.x.

HOWEVER, you can use Twig 2.x by installing through Composer!
https://packagist.org/packages/timber/timber

@zsoltbarat everything should work with 5.3! The readme just needed to be updated. We’re working now to integrate of some of the new methods that are now available into the codebase so future versions take full advantage of WordPress’s new functionality.

@henrywright this is just a catch-all advisement about upgrading Timber. Since it’s just handling template processing, there’s no real benefit to upgrading if everything is stable. It’s not like an old site will suddenly become better because it went from version 1.8 to 1.12, but there will become a big risk that old functionality has been tweaked over those versions in a way that (unintentionally) breaks something on the site.

Thus, we advise to only upgrade if you’re in the midst of active development and will receive the benefit of new features and patches

Thank you @bartbury! I removed the duplicate directory — really appreciate the heads-up!

Glad to hear @dparvanova! Yes, Timber requires PHP 5.3

Two ways…

{{ post.parent.title }}

{{ Post(post.post_parent).title }}

@timlogemann I’d recommend using the Routes plugin:

https://github.com/upstatement/routes

… we’ve deprecated the routing features of Timber for now (they’ll still be there for a while, but no new features/improvements). Routes is probably the best way forward for you plugin!

Yes, display_date was removed. But {{ post.date }} or {{ post.post_date|date }} will do the trick.

@ageibert —?I was about to tell you to avoid using dashes in fields. I didn’t realize Twig supported array notation. Good find!

… and it’s now deployed as 1.0.3!

thanks @christianjameswagnergmailc I’m working on a hot fix right now that will resolve that!

@carlosreynolds @oxyplay: The new version of Timber (1.0.2) restores the old comment_form function and adds a new {{ post.comment_form }} method