Hi all!
I'm trying to configure and use this module in a project. I define a Message type with 3 arguments, then I configure a rule that creates a new message entity and set values for my arguments.
Then I go to "message/example", that is the default message view example, and get an error "Recoverable fatal error: Object of class Message could not be converted to string en DatabaseStatementBase->execute()"
I go to the view and determined that the "Render message (Get text)" handler causes the problem, but I don't know what problem and how to slove this...
It seems that there are a lot of name-matching problems with some modules like Private message, and I'm thinking that it can be the same here...
Comment | File | Size | Author |
---|---|---|---|
#11 | messaging_1659228_fixing-conflict-with-message-module_11.patch | 592 bytes | kurtzhong |
#10 | messaging_1659228_fixing-conflict-with-message-module_5.patch | 631 bytes | milesw |
#5 | messaging_1659228_fixing-conflict-with-message-module_5.patch | 631 bytes | bendikrb |
Comments
Comment #1
milesw CreditAttribution: milesw commentedRan into the same error trying to render messages in Views. Disabling the Privatemsg module solved the problem for me as well. Thanks for the tip, eidoscom.
Most class names and function names are namespaced properly in both modules. This problem is this...
Privatemsg module:
Message module:
It seems Privatemsg is implementing hook_TYPE_load(), which doesn't appear to be a documented hook, but is invoked by the entity controller. So this is a Privatemsg issue. I'll file an issue over there.
Comment #2
milesw CreditAttribution: milesw commentedLooks like this is known issue, and there's already a patch. :)
#1353342: Private messages and messages not working well together
Comment #3
eidoscomHi here milesw, thanks a lot I will try to apply a patch and test if I can use the two modules together ;)
Comment #4
Michsk CreditAttribution: Michsk commentedApplied patch but did not fix it.
Comment #5
bendikrb CreditAttribution: bendikrb commentedMaybe you've got another module which has a 'message_load' suffix, like I had (messaging_simple.module from the Messaging Framework).
Patch is attached!
Comment #6
eidoscomPatch in #5 works for me thanks!!
This patch is commited to Messaging?
Comment #7
dimitriseng CreditAttribution: dimitriseng commentedI had the same issue when using Commerce and I can confirm that the patch in #5 fixes the issue, thank you!
This patch is for the messaging module and not the message module, should we move this issue to that module's queue? However, messaging does not seem to be very active (only up to alpha2 for D7 and last commit 24 weeks ago...) so not sure how fast that would go it. Is there anything that anybody can do to progress this?
I changed the status back to RTBC so that people can see it and hopefully move it to the messaging module, or maybe we could create a new issue there and close this one. I hope this is ok.
Comment #9
milesw CreditAttribution: milesw commentedThe conflict in Privatemsg has been resolved, so we can move this to the Messaging issue queue. I'm assuming the patch here is for 7.x. Changing status to run tests.
Comment #10
milesw CreditAttribution: milesw commentedRe-submitting patch #5 and changing status back (apparently "reviewed & tested" status also triggers tests).
Comment #11
kurtzhong CreditAttribution: kurtzhong commentedThanks very much, it saves my day. I am using the message and messaging module on the same site.
But i can't get this patch properly applied using drush make. I rerolled the patch from the messaging root directory rather than from within messaging_simple.
Comment #12
amitaibubtw, You can also checkout Message-Subscribe, which is part of the Message stack.
Comment #13
amitaibuAnd one final issue hijacking -- #1906334: Evalutae Message+ Message-notify + Message-subscribe Instead of Messaging
Comment #14
mpv CreditAttribution: mpv commentedPatch in #11 fixed this issue for me.
Comment #15
DamienMcKennaComment #17
Nafes CreditAttribution: Nafes as a volunteer commentedCommitted. Thank you, milesw and kurtzhong!