Warning Message in D6 alpha: invalid argument
bomarmonk - December 26, 2008 - 23:15
| Project: | E-Journal |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | critical |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Description
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.
#1
Same problem in latest development snapshot.
#2
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.
#3
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
#4
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.
#5
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).
#6
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?
#7
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.
#8
Still getting the error with the latest development version (4/26/2009)
#9
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...
#10
The 4/27/2009 development version seems to have fixed this problem for me.
#11
Automatically closed -- issue fixed for 2 weeks with no activity.