After upgrading to Drupal 6, I am getting some warning messages when viewing an e-journal issue (path ejournal/show/1/_/1):

warning: Invalid argument supplied for foreach() in /home/.muckl/mydomain/mysite.com/sites/all/modules/cck/content.module on line 1270.

Comments

bomarmonk’s picture

bomarmonk commented
Version: 6.x-1.0-alpha2 » 6.x-1.x-dev

Same problem in latest development snapshot.

nobios’s picture

nobios commented

I'm installing CCK so I can see if this is a ejournal or cck error...

Cause it didn't happen in my local installation that has only ejournal and token.

nobios’s picture

nobios commented
Status: Active » Postponed (maintainer needs more info)

Installed and didn't get the error, did you put some field in the ejournal content type? Any chance for more information about what was made to generate the problem?

Thanks

bomarmonk’s picture

bomarmonk commented

I am using the basic "story" content type with e-journal. The content itself was created in Drupal 5.x and has been upgraded to Drupal 6.x.. The only key difference that I could figure is that excerpts are handled differently in Drupal 6, so I made sure that I installed a 6.x dev version of the 3rd party excerpt module, hoping that would smooth things out. Any ideas as to what is going on? I still cannot get any of my content to show up because of this problem.

bomarmonk’s picture

bomarmonk commented

Ah, I should also emphasize that this only happens when I try to view an issue, not when selecting a category of articles from the drop down list. So the errors occur after clicking on the issue number listed on the archives page for e-journal (and the resulting page is totally broken).

bomarmonk’s picture

bomarmonk commented

This problem persists even after I have deleted all e-journal tables from my database, reinstalled the module, and recreated my e-journal issue. This would rule out any corruption of e-journal while upgrading, and I am also using the stock story content type for my ejournal articles. Any ideas as to why this happening?

bomarmonk’s picture

bomarmonk commented

I am anxiously awaiting an update for this; I also thought that this might be caused by the cover page/node for the journal, but alas, the problem persists without a cover page.

bomarmonk’s picture

bomarmonk commented
Status: Postponed (maintainer needs more info) » Active

Still getting the error with the latest development version (4/26/2009)

romca’s picture

romca commented

Looks like I was thinking Everson solved it. After o finish at work, I will try to solve it. Sorry for the delay, thanks for your reports.
Stay tuned...

bomarmonk’s picture

bomarmonk commented
Status: Active » Fixed

The 4/27/2009 development version seems to have fixed this problem for me.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.