Descriptions appearing as "n/a" for anonymous and registered user

Anyone here?

Yes, I am around. Take a look at my profile and see how many modules I support. If you want to pay me, then I will change my priorities, otherwise you'll have to wait until I get back to this one, which should be soon.

Are the terms being translated? Do you use any modules that restrict access to terms? I don't see this problem, so I'll need your help in trying to track it down.

Hi NancyDru,

thanks for your answer. I sincerely appreciate your work here at drupal ;). More people like you are needed here!

My site is translated, yes. As an admin I can view correctly the glossary page, each item with it´s description, but no as an anonymous or registered user.

I use taxonomy access control module, but all the permissions seems to be correct.

Cheers, Simon.

I doubt TAC is doing it. It might be i18ntaxonomy - but Stella just figured out how to fix that in FAQ, so I will be borrowing that code.

I don´t use that module (i18ntaxonomy), it was moved into core NancyDru? Thanks again for your time.

According the the project page it is still part of the i18n package. I have not heard of plans to move it into core yet.

I have dissable TAC, enabled all the input formats glossary filter (just to test), without success. Just to inform.

Cheers, Simon.

Hi, just to add I am also experiencing a loss of glossary terms when not logged in as admin. I get the acronym tag over a term, but clicking takes me to an empty glossary page. Logging in as admin, reveals the definition.

I am using built-in translation.

I am using latest Drupal 6.6 with all modules updated. I do not use TAC but do use ACL for Forum and Content.

I found one way to recreate this problem: Please check your default Input format and make sure it is not "PHP code."

There is also a "Default input format" setting at the bottom of the "General settings" tab. Please make sure it is not set to "PHP code."

Hi Nancy,

I don´t have it enabled. I have a custom input format with line break and html filters (<a> <em> <b> <ul> <ol> <li>) enabled.

Hope that helps ;).

Hi,
Yes your modul is awesome and i like it very much, but it would be excellent if you build option to restrict certain users and roles. And of course error message can be like: Please login or register to see glossary...

There is an "access glossary" permission. If you want more than that, pleas open a new feature request. This has nothing to do with this issue.

Just to inform. The stable version of the module works right with my configuration. I will use that for now.

Thanks for all, Simon.

We had a similar issue these days. Just for the record.
We use glossary together with better formats and paging. Since some roles (editors) are allowed to use markup input formats (including paging), anonymous users are not allowed to do so. Also the default input formats are different between these roles. We had to enable the markup input filter for anonymous as well. That makes a difference. Does glossary use the standard input filter to render its page?
It should be possible to view content with an input filter even if the user is not allowed to create content with it. Or am i wrong?
I have to dive into the filter settings since we use a quite complex configuration. It seems to be the <!--paging_filter--> tag which makes the difference, but that's just a guess so far. Paging sets this tag at the beginning of every node (have a look at the source of http://www.lullabot.com/about for example). So it does at the glossary page for every term description. This results in a return of "n/a" while the terms itself (hover) are accessable, so it's not a permission issue.

cheers, Ronald