Closed (fixed)
Project:
Featured Content
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
3 Apr 2010 at 20:33 UTC
Updated:
5 Apr 2010 at 02:29 UTC
Jump to comment: Most recent file
Comments
Comment #1
kristen polCan you take a screenshot of your settings or let me know what they are? And, which version are you using?
Thanks,
Kristen
Comment #2
green monkey commentedThanks - there are 3 other factors, that may be involved here.
I'm using acquia_marina-6.x-3.0-alpha2
which also uses Skinr and Fusion
this is a pretty simple path match on first word
Comment #3
green monkey commentedooops - I downloaded dev version on 3/30
Comment #4
kristen polThanks. I looked through the screenshots and it looks like you are only doing:
unordered list for block
unordered list for more page
random
match on first part of path
I will try that with the dev version you are using and see what happens.
Kristen
Comment #5
kristen polI installed drupal from scratch and then the latest dev version (March 26th) and created a block with the same settings you have and couldn't reproduce the error.
Can you try changing it from random to something else? Also, try unchecking the path matching?
Thanks,
Kristen
Comment #6
kristen polp.s. When you wrote:
"sorry - nothing else shows up to send you just "Array" "
is that the error you get or do you just see "Array"?
Thanks,
Kristen
Comment #7
green monkey commentedyes - just Array
want a page source?
http://www.msgfree.org/aspartame
then click read more
Comment #8
kristen polNo, that's okay. Not sure what to tell you other than to play around with the settings to see if the mysterious "Array" goes away. I've never seen it do that. If you are just testing (not a public site), you could try changing themes as well though I don't know how that would make a difference.
Kristen
Comment #9
green monkey commentedok - will change out settings and see what happens
Comment #10
green monkey commentedI think I have this narrow down. As you probably figured, its a config/use issue.
config
- compare first word in path
/compare/no/no/no
- display only on following pages (notice no slash)
dogs* (the node sitting at dogs - is a view page) Read More does not work
dogs/term/nodetitle (regular node pages) Read More works
dogs/term/term/nodetitle (regualr node pages) Read More works
if display path is set to
dogs/* -- then everything good -- but I lose FC on the View page
which might not be in the plan
will config - per your advice
thanks
Comment #11
kristen polGood debugging! I imagine I can fix this... I'll take a look.
Kristen
Comment #12
kristen polI just checked in a fix that may work. Note though I could actually totally reproduce your bug. I was able to get it to say "No results found" though. The issue was that it was on a non-node page so I've added code to handle that. It'll be available once the cron runs.
Let me know if it works.
Thanks,
Kristen
Comment #13
kristen polComment #14
green monkey commentedthanks - I'll watch for new version
FC is running great - very solid module
Comment #15
green monkey commentedThanks - new dev version did the trick :)
Comment #16
green monkey commentedah oh
something else has changed in this version
I had a FC block on the front page
and now its gone, what can I check for?
filter = Use the content types selected below.
(edit)
found it
somehow
Featured Content Visibility Settings - became active and was matching Content Type Filter Options
Comment #17
kristen polCool!
Comment #18
kristen pol