Timeline for How to create missing rules event when user flags a statuses updates?
Current License: CC BY-SA 3.0
20 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 10, 2016 at 3:17 | comment | added | Niall Murphy | Have you made any progress since posting? What view ae you trying to add the contextual filter to and what is the purpose of the view? | |
| Dec 9, 2016 at 15:53 | comment | added | Umair | @NiallMurphy I am waiting for your reply. I cannot use your module until and unless these problems are solved | |
| Dec 8, 2016 at 19:12 | history | bounty ended | Umair | ||
| Dec 8, 2016 at 19:11 | vote | accept | Umair | ||
| Dec 9, 2016 at 15:51 | |||||
| Dec 8, 2016 at 19:07 | comment | added | Umair |
When I try to add the contextual filter "Statuses: Content from flagged users or the argument user" I get this error SQLSTATE[42S02]: Base table or view not found: 1146 Table 'drupal_7_52.flag_content' doesn't exist This is the same error which I got previously when I tried to use official statuses module with flag 3. If I have these problems, I cannot use your module
|
|
| Dec 8, 2016 at 7:42 | comment | added | Umair | The data selector in "condition" ([Not]Status was posted to own profile) is showing "flagged-status:". Even tried without colon. When I save, it says "The data type of the configured argument does not match the parameter's status requirement" | |
| Dec 8, 2016 at 7:33 | comment | added | Umair | I did it. Thanks to @Pierre.Vriens I applied what he taught me earlier, but I am not able to add a condition so that when a user flags his own status, the message is not logged. | |
| Dec 7, 2016 at 18:11 | comment | added | Umair | I did a clean install and selected the event in rules. Now the problem is that when try to create a "condition" ([Not]Status was posted to own profile) and the "action" (Create new entity), I do not get the appropriate data selectors. In (Create new entity) "action", you have to select a data selector for "user for which to log message". Obviously "message" will be logged for the status owner. What is the problem? | |
| Dec 7, 2016 at 1:49 | comment | added | Niall Murphy | Also try on a clean install with flag 3, rules and the module I posted. | |
| Dec 7, 2016 at 1:21 | comment | added | Niall Murphy | You don't enable the like flag, you create a new one for "status". And in rules, the event will be under Flags and called something like "A status had been flagged under "Like". Try that and report back. | |
| Dec 6, 2016 at 17:28 | comment | added | Umair | Moreover the required event "status flagged" is also showing in the list under flags | |
| Dec 6, 2016 at 17:26 | comment | added | Umair | These events are showing in rules screenshot | |
| Dec 6, 2016 at 17:05 | comment | added | Umair | I am having the same problem I had before when I tried to use statuses with flag 3. What I did? Uninstalled statuses and its submodules and flag 2 as well. Installed your module and flag 3. What I am doing wrong? Should I install flag 2? Secondly, I was not able to enable the like flag, so I changed the entity type from "statuses" to "status" in fbss_flag.module file under function fbss_flag_flag_default_flags() | |
| Dec 5, 2016 at 15:20 | comment | added | Niall Murphy | Should do. Nothing else changed for me. | |
| Dec 5, 2016 at 15:06 | comment | added | Umair | So everything else will work as it does? for example the "follow" flag. | |
| Dec 5, 2016 at 13:36 | comment | added | Niall Murphy | Ha Pierre, it was to perfect for the question to not share the patched module. I had the exact same problem as Umair around six months ago and it felt hopeless trying to get it to work! | |
| Dec 5, 2016 at 13:07 | comment | added | Niall Murphy | Yep. It's just a slightly changed Statuses module. Just enable it and any of its sub-modules that look like they'd be needed and clear the cache. Then, create a new flag for "status" and the default setting will add the flag to /statuses/all. I'm sure you can add it elsewhere no problem. Then create your rule to create the message. Hopefully, it will work as it did for me. The third paragraph was just about re-creating the module as it is now by going through the patches but it's not necessary. | |
| Dec 5, 2016 at 11:46 | comment | added | Umair | If pierre trusts you then I trust you. In short, I simply have to install your module and it will solve my problem. right? Of course as you have mentioned above that it will not work on comments. Its ok. I did not understand the 3rd paragraph of your answer. | |
| Dec 5, 2016 at 6:01 | comment | added | Pierre.Vriens | Wow, sharing an entire module, that is really nice Niall! I have not looked at it in detail, but as per your various answers I've seen in the past, I would definitely give it a try as you described here. BTW, no need for any Mentions (or similar). And of course +1 | |
| Dec 5, 2016 at 4:04 | history | answered | Niall Murphy | CC BY-SA 3.0 |
