Replies: 2 comments 4 replies
-
|
Okay, I looked into this a little more and came across a lot of discussions that are all related to version 2 of Timber. I'm running on 1.20 and got it working on if (have_posts()) {
while(have_posts()) {
the_post();
$post = new Timber\Post();
$context['post'] = $post;
Timber::render('single.twig', $context, 600);
}
}Is this a legit way of doing it? Are there other, better options or would you recommend to just migrate to version 2? |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for looking into this. Plugin compatibility sometimes is a pain. For premium plugins like Learndash it’s even a little harder, because they don’t seem to have a free version we could use and test. The issues you found could very well be what the underlying problem is. Could you check whether Learndash uses the For Timber 1.x, your solution looks like a good way of doing it. When you use In the long run, it’s probably better to migrate to Timber version 2. But for now, you should be fine. I think your way of doing it should even be fine for Timber v2. Or you could upgrade to the new |
Beta Was this translation helpful? Give feedback.
-
|
Hey @gchtr So this solution should work for A simplified version of my current $context = Timber::context();
$context['posts'] = Timber::get_posts();
Timber::render('archive.twig', $context, 600); |
Beta Was this translation helpful? Give feedback.
-
|
Hi @kilianso Provided that I have "timberized" the header and footer of my theme, which inside has Edit: of course the markup part depends on what you have in your theme :-) |
Beta Was this translation helpful? Give feedback.
-
|
Hey @langhenet $post = new Timber\Post();
$context['post'] = $post;One more thing to mention: I also tried your approach creating a |
Beta Was this translation helpful? Give feedback.
-
|
Hi @kilianso, yes also my theme has already the the get_footer/header calls, but I had to use this workaround to make it work :-) (so I'm extending a twig template which do not includes those calls. Also, the the_content() call was necessary to have it working. I was extending a parent theme with the need to only work with learndash though :-) |
Beta Was this translation helpful? Give feedback.
-
Hi all! I've seen some discussion on the topic of how to use Timber in plugin templates. But this is not my question. I use Learndash to sell courses. Learndash has a lot of templates and assets that are in the plugin directory in a theme called ld30. There are routes like
/courses/courseXYand/lessons/lessonXY.Now instead of picking the plugin templates, my Timber based theme just uses the default
archive.phpandsingle.phpfiles when I go to these routes. And of course, because of this, the entire user interface and functionality of the plugin doesn't work. What am I missing?Even if I could create pages like
archive-sfwd-courses.phpandsingle-sfwd-courses.phpetc and then place plugin shortcodes and functions on them, it would be a huge effort and most likely I would miss some of the functions and edge cases covered by the built-in templates. So I would prefer to use their templates rather than create my own ones from scratch. Even if I copy all the related files to my theme's root directory (as stated in this article), it doesn't work.If I switch to another Wordpress default theme that is not based on Timber, it works as expected. It's hard to determine if this is a compatibility issue between Learndash and Timber, or something general that I'm overlooking that occurs with any plugin that provides its own templates.
Here's the theme i'm building: https://github.com/kilianso/woodplane
Beta Was this translation helpful? Give feedback.
All reactions