After installing the advanced_forum module and making the changes noted in the readme.txt, my breadcrumb divider appears to be missing/broken and replaced with a "?" (question mark).
I am using the default Garland theme, and replaced the "template.php" with the contents of "template-garland.php" as well as placing the "fortheme" files as indicated.
I have not experimented with using another theme to see if it is specific to the Garland or not.

File attachments seem to be disabled here, so I have placed a reference image at: http://www.SpiraStudios.com/files/misc/advanced-forum-breadcrumb-trails.jpg

Once again, thank you for the great work.

Comments

michelle’s picture

Status: Active » Closed (duplicate)

See:

http://drupal.org/node/198711
http://drupal.org/node/197400

I'm not doing anything with the breadcrumb code. The template-garland.php file is the template.php out of Garland from Drupal 5.5 with _phptemplate_variables fixed to call advforum and phptemplate_comment_wrapper commented out because it doesn't work properly. That's it. Everything else is exactly the same. I have no idea why this is happening to some people but it's not happening on the test site, which uses Garland.

Unless someone can point me to something in advforum that's doing this, I can't do anything about it. But using template-garland.php is just a convenience. You can always merge the function in manually instead.

Michelle

michelle’s picture

Ok, I could have sworn I saw an update to this issue come through my email. Unfortunately, I deleted it as I just use the email to alert me that there's something new on an issue. Did you maybe send me an email privately and I mistook it for an issue response? If so, could you resend please. I barely glanced at it because I intended to read and respond to it here.

Thanks,

Michelle

Matthew Kivett’s picture

Just getting back into things after the holiday break...

I think it was a personal message, and it was just me apologizing for submitting a duplicate issue. I'm just now starting to post issues and try to interact with the community, and it was my oversight for not seeing the earlier post about this issue. If I understand correctly, it was a problem in Garland, and not your module, and should be fixed already.

Thanks again for your work on the module.

michelle’s picture

Ah, that's ok. I actually ended up implementing the change in the original issue after all. It was less of a headache to make the change to Garland's code than to explain to people how to add my code to Garland's template.php. I can't wait until 6 so I don't have to deal with this anymore! Preprocess sounds yummy.

Michelle