ns_fact has a dependency on ns_article so if you want to use a fact box on another content type you must enable ns_article as well, that kind a suck! I'm going to write a patch to remove the dependency so that you are free to use ns_fact on what ever you want.

Comments

whitefluffy’s picture

whitefluffy commented

The problem here was that the node reference field in the article needed to be in ns_fact since ns_article would depend on ns_fact if the field was in that feature. This is why there is a separate fact box for pages.

But now that there are no fields in features anymore, I guess this can be done. Do you plan on adding the node reference field for all content types that should be able to have fact boxes referred to them in ns_fact, and them remove the fields you dont want to use through the .info file?

logaritmisk’s picture

logaritmisk commented

I think we should remove the reference from ns_* to ns_fact in ns_core and let products add this on a higher level. ns core should only provide us with a great starting point and if we want to use ns_fact we will have to create the reference for us self.

fabsor’s picture

fabsor commented

There has been quite a lot of discussion on this subject, and it might be that we need another solution than features entirely for this. In the meantime I guess we should go ahead and make ns_fact a "content provider" without worrying about that part for now.

pontus_nilsson’s picture

pontus_nilsson
Location Stockholm
commented

What is the status on this now that fields are not installed through features?

fabsor’s picture

fabsor commented

It's still relevant, we need to have a real content provider, so that we can use the same fact box feature in conjunction with other different content providers.

whitefluffy’s picture

whitefluffy commented

Isn't it sane to do as logaritmisk described, and not include the fact box node reference field at all? Then whenever you want to refer to a fact box, you just add a node reference field yourself and put it in one of your own features.

gumdrop’s picture

gumdrop commented

BTW, it might be a silly question but how do we enable the fact box so anonymous viewers can see it? I do have "View Published Content" checked in permissions but you have to be logged in to see the fact box.

whitefluffy’s picture

whitefluffy commented

gumdrop - If you are using the web channel you might want to check out one of the views displaying fact boxes. The access permissions on the views has been set to "View revisions", which is silly (as oppose to your question) and should be fixed shortly.

There is an issue about it: http://drupal.org/node/1422320

gumdrop’s picture

gumdrop commented

@ heyintern I kind of figured that out after a bit of traversing through views and panels. Which makes me wonky to say the least. Thanks.

fabsor’s picture

fabsor commented
Status: Active » Fixed

This should be fixed now, due to #1404898: Turn all "extension" features into content providers

gumdrop’s picture

gumdrop commented
Status: Fixed » Needs review

Seems fact doesn't show as being enabled as an attachment to an article, or neither does a form.

fabsor’s picture

fabsor commented

If you enable facts before articles, you will have to to into "Extensions" under structure and select that you want facts on your articles. Do facts seem to be enabled under extensions?

gumdrop’s picture

gumdrop commented

They appeared to be checked "Enabled" but I had to save Extensions before they showed up.