Closed (fixed)
Project:
Journal
Version:
5.x-1.0
Component:
User interface
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
10 Dec 2007 at 17:31 UTC
Updated:
19 Jan 2008 at 16:23 UTC
Just installed the journal module. I went into site configuration, and received the following error. Note that I am working off a "almost" brand new installation of Drupal 5.5.
warning: call_user_func_array() [function.call-user-func-array]: First argument is expected to be a valid callback, 'journal_settings_form' was given in /home/mysite/public_html/includes/form.inc on line 218.
Comments
Comment #1
ycim69 commentedA further comment on this bug noted....after going into the configuration, the journal is now mandatory for all pages (whereas before it was simply there and could be left blank)
Comment #2
rick.archibald commentedJust created a new Drupal site. Installed the package journal-5.x-1.0.tar.gz downloaded on 12/11/2007. I filled out the journal form when changing system settings, but when I looked at the journal log, there were no entries, and I received the following warning:
"warning: array_shift() [function.array-shift]: The argument should be an array in /var/www/html/sites/all/modules/journal/journal.module on line 208."
Comment #3
jimlove commentedJust installed the Journal. For some reason, the journal fields are open at the top of each page. Using the new 5.5 and a couple of different themes. I will test it out further, since this is such a useful idea, but I'd like to integrate it without it destroying the cosmetics of the theme.
Comment #4
sun@KKit: Journal does not have any settings yet. The menu item is gone in CVS/HEAD and there will be a new release shortly.
@rick.archibald: That shouldn't happen. Please file this issue as a new bug report including any possible information you can give.
@jimlove: That shouldn't happen either. Perhaps you have a block containing a form enabled in your theme and the journal entry field is attached to it, too. Anyway, please file a new support request if you still encounter this.
Marking as fixed, since original issue has been resolved.
Comment #5
(not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.