notification in conversation

    • # 1 year ago

      Hi,

      i have a quick question,

      when using conversation and notification add on, every time an answer is written, everybody gets an email, even the user that wrote the answer.

      is it possible with a code snippet to change the behavior, and only the receiver in the conversation get an email when an answer is created ?

       

      thanks

    • Thomas
      Keymaster
      # 1 year ago

      Hi,

      every time an answer is written, everybody gets an email

      What do you mean by “everybody”? Actually, with WP Customer Area, a content can be assigned to multiple users, or even to groups. If you create a private content, all users from the assigned group should be notified of a file creation for instance.

      Do you mean that you just want administrators to not be notified?

      Regards.

    • # 1 year ago

      Hi Thomas,

      let me give more details! 🙂

      I’m using severals add ons, conversation, notification and managed group.

      let say I have a conversation between a manager and a user in the managed group :

      when any of the 2 is writting an answer, both will receive a notification …

      could we only have the recipient of the answer get a notification?

      Thanks,

      Francois

    • Thomas
      Keymaster
      # 1 year ago

      Hi,

      Yes, but, you can set many recipients.

      Do you mean instead, that you want the person posting a reply to not receive a notitification?

      Regards.

    • # 1 year ago

      Hi thomas, that’s true we can set many recipient.

      Do you mean instead, that you want the person posting a reply to not receive a notitification? 🙂 yes that’s exactly what is needed!

       

      Thanks,

       

      Francois

       

       

       

       

    • # 1 year ago

      Hi,

      That should already be the case : the currently logged-in user is excluded from the recipients of any notification.

      let say I have a conversation between a manager and two users A and B in the managed group

      So in that case, potential recipients are the manager and the users A and B.

      • When the manager is replying, a notification should go out to A and B (not himself)
      • When A is replying, a notification should go out to the manager and B (not himself)

      Could you have a look at the plugin logs (in the admin interface, you have a log menu) and check out which notification goes to whom when pushing the button? Both when logged in as the manager and when logged in as the user.

    • # 1 year ago

      Hi,

       

      thanks for the info,

      here is what we get when a reply is sent (in picture)

      a notification from the sender and a notification to the recipient.

      I agree, only the recipient should receive the notification 🙂 that would be best.

       

      thanks,

    • # 1 year ago

      Avez-vous des filtres dans un plugin personnalisé sur les notifications ?

    • # 1 year ago

      Merci de la question, j’ai effectivement 2 plugins personnalisĂ© pour WP customer, mais pas de customisation sur la partie des notifications… du moins, je vois pas de filtre au premier regard qui pourrais changer le fonctionnement de cela…

      voulez vous que je dépose les 2 plugins en Zip sur le support ?

    • # 1 year ago
      This reply has been marked as private.
    • # 12 months ago
      This reply has been marked as private.
    • # 12 months ago

      Essayez d’ ajouter le bout de code suivant dans votre plugin custom :

       

      function cuar_disallow_notification_to_self($is_allowed, $recipient_id, $notification_id, $post_id, $notif_settings, $extra)
      {
          // You can customize this to allow for type of notifications and not for some other types.
          return false;
      }
      add_filter('cuar/notifications/allow-notification-to-self', 'cuar_disallow_notification_to_self', 10, 5);
      
      
    • # 12 months ago
      This reply has been marked as private.
    • # 12 months ago

      C’est assez bizarre. Avez-vous possibilitĂ© de dĂ©bogguer ça ? Y-a-t-il des logs PHP en erreur dans les fichiers de log serveur ?

    • # 12 months ago

      je vous joins la capture d’Ă©cran de ce qui se passe ….

      je vais voir si je vois quelque chose dans les logs…

    • # 12 months ago

      non, il ne dĂ©tecte pas d’erreur d’après le log sur cpanel ..

      et je viens de confirmer avec un autre utilisateur du site le mĂŞme freeze en cliquant sur terminĂ© …

       

    • # 12 months ago

      est ce que je ne devrais pas plutĂ´t ajouter le snippet dans function.php ? est ce que cela serait mieux ?

       

    • # 12 months ago

      Vous avez des logs dans la console Javascript du navigateur ?

    • # 12 months ago
      This reply has been marked as private.
    • # 12 months ago
      This reply has been marked as private.
    • # 12 months ago

      Il faut chercher dans les logs PHP la raison de cette erreur 500.

    • # 12 months ago

      Re-

      J’ai cherchĂ© malheuresement,  je ne vois rien de mon cĂ´tĂ© qui me permet de rĂ©parer l’erreur 500.

      si je dĂ©sactive le snippet, je n’ai plus l’erreur, tout refonctionne normalement…sauf que l’expĂ©diteur du message reçoit lui aussi la notification…

       

    • # 12 months ago

      Une erreur 500 c’est un problème de syntaxe dans un fichier PHP par exemple. Il y a dans vos logs une trace de la cause de cette erreur, c’est certain. Il n’est pas normal que vos logs ne fassent pas ressortir cette erreur.

    • # 12 months ago

      merci, mais je ne trouve pas…

      est il possible de vous demander un devis pour m’aider sur ce point ?

      Merci,

      Francois

       

    • Thomas
      Keymaster
      # 12 months ago

      Bonjour,

      Si vous ne trouvez pas votre fichier log, vous pouvez passer WP_DEBUG Ă  true et on pourra voir l’erreur s’afficher en frontend dans Chrome -> RĂ©seau -> admin-ajax.php > RĂ©ponse.

      Aussi, veuillez svp mettre Ă  jour WP Customer Area et ses extensions. Les extensions que vous avez actuellement ne sont pas compatibles avec votre version de WP Customer Area.

      Nom Version actuelle Version recommandée
      WP Customer Area – Additional Owner Types 6.0.1 6.0.0
      WP Customer Area – Authentication Forms 6.0.1 6.0.0
      WP Customer Area – Conversations 5.0.1 5.0.0
      WP Customer Area – Design Extras 2.0.1 2.0.0
      WP Customer Area – Front-office publishing 5.0.1 5.0.0
      WP Customer Area – Managed Groups 5.0.1 5.0.0
      WP Customer Area – Notifications 7.0.1 7.0.0
      WP Customer Area – Owner Restriction 5.0.1 5.0.0
      WP Customer Area – Unread documents 2.0.1 2.0.0

      Cdlt.

    • # 12 months ago
      This reply has been marked as private.
    • Thomas
      Keymaster
      # 11 months, 4 weeks ago
      This reply has been marked as private.
    • Thomas
      Keymaster
      # 11 months, 4 weeks ago

      Merci pour l’info concernant les extensions. je vais checker les mises a jour, la dernière fois que j’ai tenté la mise a jour… tout était cassé …

      Avez-vous suivi la procédure de mise à jour ? (Cf section documentation)

      Cdlt.

    • # 11 months, 4 weeks ago
      This reply has been marked as private.
    • Thomas
      Keymaster
      # 11 months, 4 weeks ago

      Bonjour,

      Pouvez-vous svp remplacer la fonction donnĂ©e par Vincent par celle-ci svp ? Cela rĂ©soudra ce soucis (il y’avait une mini erreur dans le code pas facile Ă  repĂ©rer Ă  l’Ĺ“il nu en relecture).

      function cuar_disallow_notification_to_self($is_allowed, $recipient_id, $notification_id, $post_id, $notif_settings, $extra)
      {
          return false;
      }
      add_filter('cuar/notifications/allow-notification-to-self', 'cuar_disallow_notification_to_self', 10, 6);

      Cdlt.

    • # 11 months, 4 weeks ago

      Bonjour,

       

      Merci beaucoup, ça a l’air de fonctionner 🙂

       

    • Thomas
      Keymaster
      # 11 months, 4 weeks ago
      This reply has been marked as private.
Viewing 31 reply threads

The topic ‘notification in conversation’ is closed to new replies.