Warning: array_keys() expects parameter 1 to be array, null given in featured_content_block_view() (line 209 of /var/www/sites/all/modules/featured_content/featured_content.module).
Warning: array_intersect(): Argument #2 is not an array in featured_content_block_view() (line 209 of /var/www/sites/all/modules/featured_content/featured_content.module).
When choosing content type - no problem, but when choosing a taxonomy term of a user vocabulary the I get this error
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | 2012-01-26_084808.jpg | 92.67 KB | msiemens |
| #2 | Modules _ Featured_content.pdf | 139.78 KB | msiemens |
Comments
Comment #1
kristen polCan you provide some more information because I'm not able to reproduce...
* Drupal version?
* other modules installed?
* screenshot of your FC settings? (can use screengrab or kwout or similar)
Thanks,
Kristen
Comment #2
msiemens commentedYes, of course:
* Latest 7 versions - all modules and core
* see attachment
To say: I am currently in the process of porting D6 to D7. So I have ported site - all seems to work so far, I have six vocabularies, lots of terms. All was ported by D7 update. Used featured content blocks in D6 but uninstalled the module BEFORE porting to 7. Installed and activated featured content in D7 after port was done. Then created a featured block. As long as not using one of my taxonomy terms for visibility, block works. But when activate even one tax term - I get error message.
Thanks
Martin
Comment #3
kristen polThanks for the details... I think I have figured it out and will try to get the code checked in tomorrow. I'll let you know when it's in dev and ready for testing.
Kristen
Comment #4
kristen polStill working on a glitch... stay tuned.
Kristen
Comment #5
msiemens commentedOK
Comment #6
kristen polIf you are just using one vocabulary, then the change I just checked in to *dev* should work. But, there seems to be a different issue if you are using more than one vocabulary with the visibility setting. I will fix that next.
Make sure to check the dev version timestamp to make sure it is dated after the timestamp on this comment.
Kristen
Comment #7
msiemens commentedSorry, but I have no idea how to access the lastest "dev" version...
Thanx, Martin.
Comment #8
kristen polIf you scroll all the way down on the main project page, there is a downloads section that has development versions that can be downloaded. Look for 7.x-1.x-dev and check the date next to it.
Thanks,
Kristen
Comment #9
msiemens commentedThanx - just tried - seems to work - as you mentioned - just with one vocabulary. I am excited what is coming next :-)
Cheers and thanks once again
Martin
Comment #10
kristen polOk, good! Thanks for the feedback. I'll try to get it working fully tomorrow if possible!
Kristen
Comment #11
msiemens commentedAny news on bug when choosing more than one tax terms?
Comment #12
kristen polYikes! Life caught up with me... writing a book and have been doing revisions. Hmm... okay, will take another look at this over the weekend.
Kristen
Comment #13
kristen polI have started to look at this again but need to configure "git" on my computer because I upgraded my OS... stay tuned.
Kristen
Comment #14
kristen polI think I fixed it... I pushed it out to the dev version (7.x-1.x-dev) so check the timestamp on that... when it's later than this comment then please try that version.
If you confirm, I'll roll a new release.
Thanks,
Kristen
Comment #15
kristen polComment #16
msiemens commentedLooks very promising! Have checked with various combinations - has worked - seems to be fixed.
Merci and many thanks!
Martin
Comment #17
kristen polExcellent, thanks for testing... I'll create a new release soon... maybe tonight.
Kristen