Hooks

[Lynne]

It is being called, however I believe the template gets evaled before it is called, so doing the preregister of the variable may not be working. (You'd have to do a str_replace in the evaled template instead.)

[kh99]

I think the problem might be that the template name used by PMs is "postbit" and not "postbit_legacy", or at least that's what it shows in the html comments. Try changing the preRegister call to 'postbit', or just do preRegister twice, once each to 'postbit' and 'postbit_legacy', and see if that works.

BTW, if that is all the plugin code you don't need the ob_ calls, you could just replace the "echo"s with "$php_include = " and remove all the ob_ lines. Also, if you replace only the style= part instead of the entire <div> tag, it won't mess up the html even if the variable is blank.

Edit: or it might be what Lynne said - I was typing while she posted.

[Revelence]

Originally Posted by Lynne

It is being called, however I believe the template gets evaled before it is called, so doing the preregister of the variable may not be working. (You'd have to do a str_replace in the evaled template instead.)

Originally Posted by kh99

I think the problem might be that the template name used by PMs is "postbit" and not "postbit_legacy", or at least that's what it shows in the html comments. Try changing the preRegister call to 'postbit', or just do preRegister twice, once each to 'postbit' and 'postbit_legacy', and see if that works.

BTW, if that is all the plugin code you don't need the ob_ calls, you could just replace the "echo"s with "$php_include = " and remove all the ob_ lines. Also, if you replace only the style= part instead of the entire <div> tag, it won't mess up the html even if the variable is blank.

Edit: or it might be what Lynne said - I was typing while she posted.

See if it were that problem, then there wouldn't be a problem with the PM's in the first place because it wouldn't read the postbit_legacy which I made edits to.

I'll try with the just replacing the style, as that would be a lot easier and did not think of that, not quite sure how I didn't lol

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

Okay I did what you said, Kh99. Just make it edit the style, and add a background. Which works, it doesn't mass up any PM templates, and adds a background correctly.

I appreciate your help with this. Thanks.

[kh99]

Originally Posted by Revelence

See if it were that problem, then there wouldn't be a problem with the PM's in the first place because it wouldn't read the postbit_legacy which I made edits to.

Well it's obviously displaying postbit_legacy just from looking at it. But the way the postbit/legacy switching works is weird, and like I said, when you turn on template names in html comments it says "postbit_legacy" when viewing the forum, but "postbit" when viewing a pm, so I was guessing that the preregistering was also getting confused. It could also be what Lynne said except that I'm pretty sure postbit_display_start is called before the template is rendered.

In any case I guess it doesn't matter now.

[Revelence]

Originally Posted by kh99

Well it's obviously displaying postbit_legacy just from looking at it. But the way the postbit/legacy switching works is weird, and like I said, when you turn on template names in html comments it says "postbit_legacy" when viewing the forum, but "postbit" when viewing a pm, so I was guessing that the preregistering was also getting confused. It could also be what Lynne said except that I'm pretty sure postbit_display_start is called before the template is rendered.

In any case I guess it doesn't matter now.

Yeah that does seem pretty weird how it works I guess, but it's fixed now and I appreciate your help. Thanks again.