Hello

I am using Drupal 5.7, and have just uploaded and enabled Autotagger. When trying to get to the settings page, I get the following errors:

  • warning: Missing argument 1 for blog_form() in /home/XYZ/public_html/d5/modules/blog/blog.module on line 186.
  • warning: Missing argument 1 for book_form() in /home/XYZ/public_html/d5/modules/book/book.module on line 205.
  • warning: Missing argument 1 for forum_form() in /home/XYZ/public_html/d5/modules/forum/forum.module on line 386.
  • warning: Missing argument 1 for minutes_form() in /home/XYZ/public_html/d5/sites/all/modules/minutes/minutes.module on line 258.
  • warning: Missing argument 2 for minutes_form() in /home/XYZ/public_html/d5/sites/all/modules/minutes/minutes.module on line 258.
  • You must associate minutes with an event using the calendar.

I know I need to upgrade to Drupal 5.10 for security reasons, so I'm not sure whether that would solve these problems. But the documentation says Autotagger is good for Drupal 5.x. (Note it also says that one must instal jQUIB or JQueryUI + JQuery Update, and as those links are dead, the general info on the Modules page seems to need tidying which makes we wonder whether in fact Drupal 5.x is not in fact supported but only certain specific subversions of 5?)

Thanks

R

Comments

sdrycroft’s picture

They're warnings, I'll fix the module at some point, but they're nothing to worry about.

As for the front page, it's now updated.

Rasputin Paracelsus’s picture

Thanks for the really quick response!

However, there's more (and I'm not sure whether this should be a new thread... I didn't say more before because the warnings led me to believe that the module wasn't working--and in fact, as far as I can see, it isn't).

When I try to configure autotagger at admin/settings/autotag, not only do I get all these warnings, but I end up on my post content page. I don't ever get to any autotagger configuration page.

Was there something else I had to do to make it functional? I don't see anything under Access Control...

Thanks again,

R

sdrycroft’s picture

Status: Active » Closed (won't fix)

Apologies, but I'm marking this as "won't fix". We're currently pushing all our modules up to D6, and won't be fixing any D5 bugs (unless major). D5 is no longer a supported release.

Rasputin Paracelsus’s picture

Bummer. I guess I'm not going to have much choice but to upgrade. Which is unfortunate, because a number of things quit working when I migrated to Drupal 5, and without having them addressed, I'm concerned there will be cascade effect by upgrading yet again.

But thanks for letting me know. (Though as I can't even configure the module, it begs the question as to what constitutes 'major'... :) Thanks again.

R