Error when enabling Tags module [#2001934]

I receive a ton of errors when I enable the tag/mention submodule. Any thoughts? Cleared Cache, tried the Beta and the Dev version too.

Comment	File	Size	Author
	Screen Shot 2013-05-23 at 1.35.28 PM.png	87.25 KB	TravisJohnston

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

IceCreamYou CreditAttribution: IceCreamYou commented 27 May 2013 at 10:55

Status:

Active

» Postponed (maintainer needs more info)

Not sure. I can't reproduce it in a clean installation, and I can't see how that could happen from the code. The error is about a helper function being called with an array parameter instead of a string, but there isn't any code in the Statuses project that calls it with anything other than a string, and also that function only gets called when a status is being rendered and it shouldn't be rendering anything when you're enabling the module.

Can you do a stack trace on the code to find out where the bad parameter came from?

Comment #2

TravisJohnston CreditAttribution: TravisJohnston commented 27 May 2013 at 13:13

Love to help, not sure how to run the trace though.

Also, I am using this with Drupal Commons if that helps.

Comment #3

IceCreamYou CreditAttribution: IceCreamYou commented 30 May 2013 at 04:43

In the statuses module folder go to submodules/statuses_tags/statuses_tags.module and edit _statuses_tags_filter() and put this line after the function declaration:

print_r(debug_backtrace());

Then when you enable the module and you see the errors in question, look at the page source and you should see something that looks like this (but much longer). Copy and paste that into a text file and attach it in a comment here.

Thanks

Comment #4

TravisJohnston CreditAttribution: TravisJohnston commented 30 May 2013 at 18:56

K I think this is it..

Array
(
    [0] => Array
        (
            [file] => /Users/tjohnston/Sites/commons/includes/bootstrap.inc
            [line] => 1101
            [function] => include_once
        )

    [1] => Array
        (
            [file] => /Users/tjohnston/Sites/commons/includes/module.inc
            [line] => 24
            [function] => drupal_load
            [args] => Array
                (
                    [0] => module
                    [1] => statuses_tags
                )

        )

    [2] => Array
        (
            [file] => /Users/tjohnston/Sites/commons/includes/common.inc
            [line] => 5095
            [function] => module_load_all
            [args] => Array
                (
                )

        )

    [3] => Array
        (
            [file] => /Users/tjohnston/Sites/commons/includes/bootstrap.inc
            [line] => 2198
            [function] => _drupal_bootstrap_full
            [args] => Array
                (
                )

        )

    [4] => Array
        (
            [file] => /Users/tjohnston/Sites/commons/index.php
            [line] => 20
            [function] => drupal_bootstrap
            [args] => Array
                (
                    [0] => 7
                )

        )

)

Even though it was in the right spot, im not seeing anything in the array about the tags...

Comment #5

IceCreamYou CreditAttribution: IceCreamYou commented 6 June 2013 at 03:43

Category:

bug

» support

Hmm. Yeah. There should be a lot more to that. Maybe try calling drupal_set_message(print_r($subject, TRUE)); at the same place to see what value the bad parameter has?

I'm sorry, I don't really know what else to tell you. Without a stack trace that actually goes to the function in question, I can't tell what would have been calling it erroneously. And the fact that this is a private function that never gets called from Statuses in a way that would cause this error, on top of the fact that I can't reproduce this in a clean installation, means that this is probably a weird one-off situation.

Comment #6

TravisJohnston CreditAttribution: TravisJohnston commented 7 June 2013 at 13:53

Yeah I tried that too, no difference. I will keep playing around to see if I can find the issue. When you did a clean install, did you do it with Drupal Commons installed as well?

Comment #7

IceCreamYou CreditAttribution: IceCreamYou commented 16 June 2013 at 06:51

No, I didn't try it with Commons.

One thing you might try is grepping your code base for the function name, e.g. grep -rn "_statuses_tags_filter" . -- and then working backwards to see if you can figure out where it's being called incorrectly.