Hi,

I've just installed the 7.1 dev version of FAQ. I've used pathauto and assigned an alias for the FAQ nodes.

I've also set up an FAQ Taxonomy, and then created a term reference field in the FAQ node.

Added a node without a problem.

When I go to the views provided with the module, there's a broken/missing handler for all the views.

Is there a dependency I might be missing, or something I may have missed in terms of setup that would be causing the views issue?

I've attached a screenshot in case it may be helpful.

I appreciate any guidance you might be able to provide.

Thanks!

CommentFileSizeAuthor
faqview.jpg415.88 KBplay4quarters

Comments

brad.bulger’s picture

Title: Problem with Views » built-in views are broken
Component: Miscellaneous » Code
Category: Support request » Bug report
Issue summary: View changes

Two years later, this is still true. If you edit the built-in view, this error is displayed:

This view has been automatically updated to fix missing relationships. While this View should continue to work, you should verify that the automatic updates are correct and save this view.

The "Page - Categories Inline ... details" page display, for instance, has no apparent connection to categories at all. Looking at the view code, there is an explicit reference to a "field_category". But users have to add their own custom term reference field to add category support, so the odds that this will be the field name seem slim at best.

If these views are not meant to work, they should be moved to an optional module or something.

jjozsi’s picture

Version: 7.x-1.x-dev » 7.x-2.0-alpha2
Component: Code » Miscellaneous

I've got the same using the 7.x 2.0 alpha2 version. Broken handles in every view display. The content type filter was also broken but it was an easy fix, I added the faqs content type created by the module. How to fix the broken handler?

cjwest’s picture

Subscribe

Imaaxa-Cory’s picture

Delete / Remove the Filter Criteria: Broken/missing handler (= Array) For All displays, then save
or
Turn on the Locale module