array(4) { ["type"]=> int(1) ["message"]=> string(55) "Call to a member function user_access() on a non-object" ["file"]=> string(84) ".../public_html/sites/all/modules/flag/includes/flag_handler_field_ops.inc" ["line"]=> int(105) } n/a

My site is a fresh installation and no content yet added.

I do not understand the above error.

CommentFileSizeAuthor
#1 Capture.JPG56.43 KBbakr

Comments

bakr’s picture

bakr commented
StatusFileSize
new Capture.JPG56.43 KB

I have used:

http://..url.../nodeselect_search

After disabling the Flag, module, now i can access the nodeselect_search screen...

see attachment.

quicksketch’s picture

quicksketch
he/him
commented

It looks like this error is coming from the Views integration (which it looks like you're using). Did you configure the view yourself? I think it may be because the Node Select Search module includes a default view that is not API compatible with the 2.x version of Flag.

bakr’s picture

bakr commented
Title: error after clicking "search content" » Error after clicking "search content"

The case above is occurring on the fresh installation + 270 carefully hand-picked all-purpose Modules blend.

Defaullt installtion of View + Simple views.

Everything is kept at default.

It could be like you said, an old api call.

Off-the-record: I came from a programming background in Lasso Middleware (lassosoft.com), though not good in php, as for drupal, working with this big number of module, aiming to stress test the tolerance of different modules.

Under the hood, I have finely tuned cache + php + mysql + apache for optimum response.

quicksketch’s picture

quicksketch
he/him
commented
Category: bug » support

Hrm, you have 270 modules installed??? Note that the 2.x version of Flag is supported by very few modules. I'd suggest installing the 1.x version if you're testing for compatibility. As noted on the project page, unless a module specifically says it supports the 2.x version, it probably doesn't. As it is, you'll need to find which module is not compatible currently and then move this issue to that modules queue, requesting an updated version that works with 2.x.

bakr’s picture

bakr commented

I am considering your advice, In principle, I have uninstalled "nodeselect", as I think I do not need it.

I have one more apparently trivial/fundamental question:


What is the significance of using flag module, over a derived usage of taxonomies for the same kind of purpose.(flagging vs tagging)?

I am trying to get the ration into my head, i think that am missing the full concept of the flag module.

Could be if we have a "functional comparison sheet" to be published on module's front page, that which will cover the answer to the question above.

Really, thanks to you in advance.

quicksketch’s picture

quicksketch
he/him
commented

Flags are boolean, and every user gets a say. Just because one user says that something is "cool" (through Taxonomy) doesn't mean that other users will, yet Taxonomy has no concept of per-user tagging. In Flag, an administrator can set up a flag for "cool", then each user that visits the node gets to decide if that item is cool or not.

Basically Flag is a "each individual users gets to express a relationship towards a thing" module. Perhaps that "relationship" is an opinion (such as "is this cool", or "is this offensive") or sometimes it is for personal use, such as a "bookmark" flag. Of course Flag *can* be used for "global" purposes, in which all users toggle the same value (such as a "Promote" flag), but the main purpose of Flag is for establishing user-to-thing relationships.

bakr’s picture

bakr commented

Wow, there you go.

I really admire that mental differentiation.

Thanks alot.

bakr’s picture

bakr commented
Title: Error after clicking "search content" » Flaggig vs Tagging
Status: Active » Fixed

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.