Just upgraded to latest glossary.module but on the settings page getting the error:

Warning: call_user_func_array(): First argumented is expected to be a valid callback, 'glossary_admin' was given in /home/vrealms/public_html/beta/includes/menu.inc on line 351

In addition, prior to this "upgrade" I've never been able to get glossary to work. Previously there were no errors but glossary terms within content were not highlighted in any way as expected.

I'm using Drupal CVS.

Comments

inteja’s picture

inteja commented

After disabling then re-enabling the glossary, there is now no settings page at all listed under administer -> input formats.

inteja’s picture

inteja commented

Actually, I should note that I've applied the taxonomy.patch that comes with the taxonomy_access.module. This would undoubtedly affect glossary.module also.

I assume this is probably the issue but can someone else confirm?

Frodo Looijaard’s picture

Frodo Looijaard commented

Couple of things here.

If by 'latest Glossary version' you mean the CVS version, then yes, there is no global settings page anymore under administer » input formats. All settings are now done for each individual input format. So go to administer » input formats, select configure for the input format you want to configure, make sure you have Glossary selected, choose the configure filters tab and fill in your settings.

As this is still a CVS version, you would be wise to go to your Drupal database and execute a DELETE FROM cache to make sure there are no cache issues (this caused the menu to still be cached and display the glossary settings page). This has probably also have caused the strange error you saw.

At this moment Glossary HEAD CVS is being developed against Drupal 4.5.0, so if your are using Drupal HEAD, you may see errors that I can not reproduce.

Please let me know if everything works given the above instructions, and do not hesistate to open new issues if you find problems.

Have fun,
  Frodo

inteja’s picture

inteja commented

Thanks for the help.

It all works fine now. Had to flush cache for setting changes to take effect.