• Resolved jfranzone

    (@jfranzone)


    I just created a full WordPress theme using Timber and I love it. However, when I deployed it to my website I realized that other plugins were not working. The main one I’m concerned with is the Crayon Syntax Highlighter. I tracked it down to the fact that using Timber, I do not make calls such as “the_excerpt” and “the_content” within the WordPress loop. I just call Timber::get_posts(). They’re plugin uses hooks into those method calls in order to do the syntax highlighting magic.

    My question is, is there any way to trigger those hooks and still be able to use Timber? Thanks for the help!

    Theme is deployed to http://www.franzone.com. You can see on the main index page that there is some code that is not highlighted.

    http://wordpress.org/plugins/timber-library/

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author jarednova

    (@jarednova)

    Hey! Sorry, just getting back from holiday break.

    If you use {{post.content}} in your twig theme file, it will fire all the normal filters attached to the_content (which _should_ include the one from Crayon Syntax Highlighter). This differs from {{post.post_content}} which will output directly from what’s stored in the DB.

    Give that a shot and let me know if it works…. If this plugin is doing something funny there are ways to manually trigger a function

    Thread Starter jfranzone

    (@jfranzone)

    No, it’s still not working. If you go to my website (http://www.franzone.com) you’ll see the second post down has a block of code that should be highlighted. That’s using {{post.content}}. If you click the title you’ll get the single page, which I changed to use {{function(‘the_content’)}}. That does perform the highlighting. I tried using the function call on the index page, but that just listed out the first post multiple times.

    Hi there. I’m having a similar problem. It seems like the normal hooks aren’t firing, and when I try to call fn(‘the_content’) I get no output from it. This has caused two side effects: Shortcodes aren’t being evaluated within the post content, and when I’m editing a post, if I click on the “preview” button, it doesn’t load my changes–only what’s already been saved.

    page.php

    <?php
    
    global $paged;
    if (!isset($paged) || !$paged) {
    	$paged = 1;
    }
    
    query_posts("post_type=post&posts_per_page=3&paged={$paged}");
    
    $context               = Timber::get_context();
    $context['page']       = new TimberPost();
    $context['posts']      = Timber::get_posts();
    $context['pagination'] = Timber::get_pagination();
    
    Timber::render(["page-{$context['page']->post_name}.twig", 'page.twig'], $context);
    
    ?>

    From there it loads up page-writing.twig, which is my loop for displaying recent posts. There’s a little more to it than this, but this is the relevant part. Might be worth noting that the fn(‘post_class’, …) does work as expected, even though fn(‘the_content’) yields no output.

    The following code successfully gives me output using {{p.content}}, but doesn’t evaluate shortcodes etc.

    {% for p in posts %}
    
       {# Post article begins. #}
       <article {{fn('post_class', 'blog-listing')}}>
    
          {# Post metadata eg. datetime and comment info. #}
          <header class="post-meta">
             <h3 class="post-title"><a href="{{p.permalink}}">{{p.title}}</a></h3>
    
             <span class="post-meta">
                Posted on {{p.post_date|date}} ·
                <a href="{{p.permalink}}#comments">
                   {% if p.comment_count == 0 %}
                      No comments
                   {% elseif p.comment_count == 1 %}
                      1 comment
                   {% else %}
                      {{p.comment_count}} comments
                   {% endif %}
                </a>
             </span>
    
          </header>
    
          {{p.content}}
    
          ...more...
    
       </article>
    {% endfor %}

    Any ideas?

    WP 3.9.2, PHP 5.5.9, installed Timber through plugin settings in WP dashboard.

    I finally figured out my problem.

    I had my blog on a subpage (site.localhost/writing), but I hadn’t actually configured WP to use a static front page with the blog on another. Once I did that it started working.

    Edit: Maybe not. Only the latest post is processed correctly–anything after is not, and viewing single posts are not correctly processed either. Back to the drawing board, I guess…

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Getting Hooks Back in Conjunction With Timber’ is closed to new replies.