How to call a variable from within the Threadbit template?

[Tamtams]

I am using the default VBulletin 4, without any template changes.
I tried putting the word "hello" in the template, with no results - that's what caused me to start this thread in the first place...

Have you been able to successfully create and use a template in threadbit, or just via preprocess?

[consolegaming]

I'd suggest trying a different hook like the parse_templates hook and see if that makes any difference. I had problems when I was trying to pre-register a custom template in the global hook. Changed it to the parse_templates hook after reading a comment and it fixed my problem. Can't hurt trying it anyway lol.

[Tamtams]

I thought the problem with using hook parse_templates is the template will be loaded for every page load, even though it is only required for threadbit?

Either way, the problem has been narrowed down to registering the variables within the template - obviously creating the template is working, as it is appearing in the debug information, but registering it is not. Will try to move the register to another hook, and report back on what happens

--------------- Added [DATE]1262373019[/DATE] at [TIME]1262373019[/TIME] ---------------

Ok, I can't move the template to parse_templates, as it needs access to a function which isn't loaded by that hook.

[Lynne]

Can we see the exact code you are currently using for the plugin (which location?) and the templates.

[Tamtams]

Originally Posted by Lynne

I would guess something is wrong with your template then. Try just putting "hello" in the template and see if you get that to print out.

I tried this, no go. Very strange that the template can't render, even though VBulletin is recognizing that it was created!

[consolegaming]

Originally Posted by Tamtams

Ok, I can't move the template to parse_templates, as it needs access to a function which isn't loaded by that hook.

Hmm. I just did a quick test and it worked fine for me. I created a blank template called custom_template and I put "Testing123" into it. I then created a plugin with the code that Lynne originally suggested and finally added {vb:raw custom_template} to the threadbit Template. That worked fine for me and I ended up with loads of Testing123's appearing above the list of threads (because of the floated divs I presume).

[Tamtams]

Here's the exact code i'm using - hook location is threadbit_display

PHP Code:

        $test_value = "It Works!";
    $templater = vB_Template::create('threadworks'); 
    $templater->register('custom_template', $test_value); 
        $custom_template = $templater->render();
        vB_Template::preRegister('threadbit', array('threadworks' => $custom_template)); 


(I'm trying to port the Threadworks mod to VB4 )

[Lynne]

What does your template threadworks look like?

[consolegaming]

That is still working for me Tamtams. I copied that code directly into a new plugin that I created especially to test this. I then created a custom template called threadworks and then added {vb:raw threadworks} to the threadbit template.

Are you definitely adding the above variable (vb:raw thing) into the correct template i.e. threadbit. If you're trying to use it in one of the other templates then that'll be why. You need to pre-register it exactly for the template you're trying to use it in.

Granted my threadworks template that I created just has Testing123 in there but its working as I'd expect. Remember this will be showing in the thread listing (inside a forum) and not inside the thread itself (I doubt you're making that mistake but just mentioning the obvious lol).

As far as I can see either you're doing something different to the above or something is seriously going crazy on your forums lol. Especially if you're trying just a test message in your template. If the test message works then that'll obviously point to the template itself causing the issue but if not then I don't know what else to suggest.

EDIT: You haven't been trying to use {vb:raw custom_template} with the above plugin code have you?

If so then that'd be wrong lol. The pugin code above registers the $custom_template variable for use inside the threadworks template and the threadworks variable for use inside the threadbit template. So {vb:raw custom_template} with your plugin code will only show it's contents at the moment inside the threadworks template of yours.

[Tamtams]

Originally Posted by consolegaming

That is still working for me Tamtams. I copied that code directly into a new plugin that I created especially to test this. I then created a custom template called threadworks and then added {vb:raw threadworks} to the threadbit template.

Are you definitely adding the above variable (vb:raw thing) into the correct template i.e. threadbit. If you're trying to use it in one of the other templates then that'll be why. You need to pre-register it exactly for the template you're trying to use it in.

Granted my threadworks template that I created just has Testing123 in there but its working as I'd expect. Remember this will be showing in the thread listing (inside a forum) and not inside the thread itself (I doubt you're making that mistake but just mentioning the obvious lol).

As far as I can see either you're doing something different to the above or something is seriously going crazy on your forums lol. Especially if you're trying just a test message in your template. If the test message works then that'll obviously point to the template itself causing the issue but if not then I don't know what else to suggest.

EDIT: You haven't been trying to use {vb:raw custom_template} with the above plugin code have you?

If so then that'd be wrong lol. The pugin code above registers the $custom_template variable for use inside the threadworks template and the threadworks variable for use inside the threadbit template. So {vb:raw custom_template} with your plugin code will only show it's contents at the moment inside the threadworks template of yours.

Hah nope, I wasn't using {vb:raw custom_template }, I am using {vb:raw threadworks) . This issue has ben racking my head though! Consolegaming - could you just copy and paste the exact code your using so I can ensure I have replicated it properly on my local install! That would likely help me quickly identify why it is not working...
Thanks!