Forum Replies Created

Viewing 15 replies - 46 through 60 (of 195 total)
  • Thread Starter Kir 2012

    (@kir-2012)

    Hi there, ok great thank you for letting me know I’ll look through it asap.

    Meanwhile a couple of errors I spotted, I noticed that no matter how many times I activate ‘comments’ on posts activity in the front end settings in buddypress, the ‘on’ switch doesn’t save and it reverts to the off position after saving has processed.

    Also when I choose a custom colour for the bell icon, it saves the info in the colour settings but isn’t reflected in the icon, either in admin or front end.

    Thread Starter Kir 2012

    (@kir-2012)

    Hi there, did you release it last Friday? I thought I had better just check that I’m looking out in the right place! Thanks ??

    Thread Starter Kir 2012

    (@kir-2012)

    Apologies I overlooked by accident to respond to your question here:

    You said: “At present, if you switch off schedule option and switch off in background option (for activities/comments/post) then it will unschedule the corresponding tasks in scheduler.

    Are you getting scheduled notifications for activity/comments/posts even if you switch off scheduling option for activity/comments/posts? If scheduling options are off then it will automatically unschedule related tasks in scheduler.”

    Answer: Yes the notifications don’t continue then, but the unscheduling above is not permanent and when you switch it on again the same old notifications come through, for example we received three old post notifications sent during testing in one go. Of course we need to be able to ensure we can remove these permanently or new users once we finish trials will still be seeing TEST messages.

    Hope that helps ??

    Thread Starter Kir 2012

    (@kir-2012)

    Hi, ok great, I’ll wait to hear, thanks again :).

    One other thing, apologies if I have just overlooked this, however I couldn’t see where to edit the messages presented to the user in the bell icon.

    It says MANAGE PUSH NOTIFICATIONS in the bell.
    For the unsubscribed it says PUSH NOTIFICATION NOT SUBSCRIBED.
    For subscribed it says YOU ARE SUBSCRIBED TO PUSH NOTIFICATION.

    I have updated all options via ‘customise buttons’ tab to our required terminology, and the customiser for the bell icon in the push settings tab also. However none of these have affected the above messages.

    Can those be made available in admin settings so that the desired language can be used, in keeping with the other customised buttons?

    Thanks ??

    Thread Starter Kir 2012

    (@kir-2012)

    Hi thanks so much for this information, that all sounds great and the extra info is really useful when thinking about how to incorporate the plugin into a site – I will wait to hear about the scheduling issues.

    An option to cancel scheduled tasks directly in plugin admin settings tab sounds really useful.

    I will wait to hear about the app install shortcode, it sounds like your idea could fix the issue.

    Could it be handy to add some of this to the plugin page, the bit about how to cancel scheduling? Also about the events where scheduling isn’t an option like friending etc, really useful to know :).

    Additional:

    • Will the plugin accommodate for activity privacy? Many buddypress communities employ this so could be useful and we noticed that it doesn’t at the moment because we tested a post that was visible to ‘mentioned only’, and the notification came through for a member login not involved in the exchange.
    • Desktop screens are prompted for the pwa app – but for most desktop devices probably this wouldn’t be applicable, perhaps an option to limit app install prompt to tablet / mobile screen size or ‘smaller than X’ in admin?
    • I’m told we added a bit of css earlier via the customizer in wp and received a browser notification about it (I wasn’t here for that but just adding mention of it on the fly here, just for your info) – is there a way to double check CPTs on an installation that notifications are limited to?

      Thanks ??
    Thread Starter Kir 2012

    (@kir-2012)

    Additional regarding expiry / duplication, in your previous post where you say:

    “i will update the logic in next release(in 7 days). I will change the design for scheduling logic to avoid repeated notification for deleted activity.”

    Just to ensure I understand properly, will your upcoming re-design ensure that there are not repeated notifications at all, (as well as not for when the activity has been deleted)?.

    A ask because I can’t think of any use cases where community front-end users would like to receive the same notification more than once – surely there should not be any repetition of notifications? Or have I misunderstood?

    I have about 4 or 5 duplications of the same notifications on my tablet here since I started tests again today, that would definitely upset my users.

    Thanks ??

    Thread Starter Kir 2012

    (@kir-2012)

    Hi, Additional –
    Regarding the logic for post scheduling, (please disregard this if it’s not relevant now after your updates etc)

    For the front-end user experience, (certainly in our use case, and I’m guessing in most others) – if one of our site users has agreed to receive push notifications, it would not seem appropriate to them that they might receive a notification about something that happened a couple of days ago for the first time, so much later than it happened, and having received other notifications about things that happened between, prior to receiving it.

    This arose during testing, a notification was received for the first time today about a comment that was made a couple of days ago.

    I received this notification a couple of seconds after I updated the admin settings. Then I received it again twice since, each time the increment rolled around.

    How can we stop this from happening without deleting that comment, because obviously once live, it won’t be feasible to delete our user’s content if duplicate notifications arise – or will your new update deal with this?

    Thanks ??

    Thread Starter Kir 2012

    (@kir-2012)

    Additional: This isn’t a pressing thing obviously, just an added idea really for best convenience, but I’m about to edit the name of the PUSH NOTIFICATION SUBSCRIPTION tab (that is added by your plugin in the front end profile settings), and it occurred to me to add here that it would be great to include a way to do that in the plugin admin, maybe one for later ??

    Thread Starter Kir 2012

    (@kir-2012)

    • Hi, Thank you for helping me to understand a bit more regarding the logic for scheduling push notification / repeated notification for deleted activity. And ok, I will follow this – so will reworking this mean that if an issue arises, to delete the activity itself will be enough to resolve it? That would certainly be much better from an admin point of view.

      To stop the existing issue we have with these repeated notifications from happening any more (including the one we’re getting repeated notifications about now), I have to wait and download your update that prevents deleted activities being sent, is that correct?
    • Regarding scheduling, I hope I read your question correctly, – was it to ask whether my aim is that either –

      A: The user should receive an individual notification for each and every single activity that has happened at their login since the last instance of timeframe (eg 300 seconds) or –

      B: To send only the most recent activity that occurred before the instance of the timeframe?

      Did I understand what you’re asking correctly?

      I think I understand your considerations as you’re describing them regarding sending of just one title, content etc. From a front-end user point of view, if you agree to receive notifications at a community website with friend requests, follows and mentions etc, then it seems natural that you would expect to hear -every- time you receive a friendship request, and -every- time you are mentioned. So, if you were to receive only info about the most recent notification, and that particular event was unrelated to a friend request, (eg a comment), but, you had also received a friend request and you did not receive any news in a notification about that, that would seem strange, and probably insufficient, from a website front-end user point of view.

      On the other hand, on a busy site a notification for every action could seem a lot. Could an idea be that just for certain (key) activity types there is an individual notification per action? Like each time a friend request is accepted or received, or each time someone mentions you and each time someone follows you? (I read back through all of the support history before my original comment, and saw you already added support for Buddypress Follow which is great!).

      Then for other less important types, perhaps when the time increment (the 300 seconds) rolls around, you hear about just the latest one, and we could append a message to that via message field in admin for your plugin, so for the front end user who received notification about only the latest of these kinds of updates, it would say

      “TITLE: Just now on XXXXX
      – MSG: (The latest activity content) –
      APPENDED: (Or just included in the existing msg field?)
      “Login now for new activity….”.

      What do you think?

      Otherwise, if one notification for every one of the key events is not possible, and it is only feasible to send the most recent event that happened before the timeframe rolled around again to users, then I think it’ important that’s clear enough for the front end user, or at least that there’s no grey area left for them. They may otherwise find it ‘messy’ and wonder “why do I only hear about some friend requests and not others?” – or follows, mentions etc. If the first idea is not feasible, then in this case we would want the notification to say something like

      “TITLE: – You have new activity at your XX login”
      – MSG “A friend request, comment or mention? Login to find out now…..”
      – which I think we can do with the existing fields in the admin for your plugin as they are, am I correct?

      Keen to hear your thoughts ??
    • Regarding shortcode, ok great thank you I will download it now.
    • Yes I understood from your last message about the shortcodes working only with Firebase – I am using Firebase and we will continue to use it ongoing. The subscription shortcode works for us, although it was taking a while for the button to appear. Once the button appears, the action when you click it seems fine, the subscription box pops up just fine and the user can select and save their preferences, that all seems to work well. But it’s the PWA / App Install shortcode that doesn’t seem to work in Firebase for us, it doesn’t appear at all.

      Thanks ??
    Thread Starter Kir 2012

    (@kir-2012)

    Good morning,
    Thank you for your reply and for that information, it’s much appreciated, this is a great plugin idea and we’re looking forward to getting it going .

    I don’t think I understand what you said, this bit “If we have to queue all scheduled activities then it requires customisation that will create lot of push notifications for every activity.” How /why does it create a lot of push notifications for every activity?

    I am keen to ensure I properly understand how to choose the settings correctly, I chose the 300 seconds schedule option on the assumption that all of the activity posts due to send to users about what has happened at their login would do so every 300 seconds. Of course during testing we are looking for the shortest interval, so we can see what happens – but also this site will be active with a lot of stuff going on so, it will likely be set to every 300 seconds when we activate it. (If I’m understanding correctly about how to use it?)

    The duplicate message that arose in testing was one of these messages – it wasn’t a one-off message, it was just a standard buddypress activity post, as that’s what we are focused on, notifying users automatically when things happen at their page. (Although the one-off message tool is great and we will certainly find it useful).

    The repeating notification we are receiving is one about a simple message, something like “Hi what about this @mention-name?”. Written by one profile for another during testing of this plugin to see the resultant browser notification. The only thing unique about that activity post, is that we have received endless repeat browser notifications for it and we continue to. I have deleted that activity post, and then removed One Signal and activated Firebase – but continue to receive that browser notification about an activity that no longer exists.

    Obviously it will annoy our users if this happens to them once active, to be told about the same post at our website every five minutes, so I am keen to try to get to the bottom of why it’s happening, so we can avoid it again in future. I can’t see that I did anything wrong in settings, they all made good sense to me. But I may have misunderstood something, because something about my configuration has caused that one message to be sent again and again, what could it be?

    I also need to know if possible, where I can find info about any outgoing notifications, and ensure that if we need to, (like we do on this occasion), we can disable any duplicate message notices without removing the service for all users, where would I do that when this plugin is activated, in my database, in Firebase?

    Shortcode – ah ok that makes sense then, thanks and I will wait to hear. One thing, after I changed to Firebase in an attempt to stop the problem with the repeating browser notification, the app install shortcode doesn’t appear for me at all, that’s in Firebase, what could I have done wrong? The other one does appear now, although there is a long delay before the button renders (why is that, style sheet taking a while to render?)

    Thanks again ??

    Thread Starter Kir 2012

    (@kir-2012)

    Ok update: I deactivated and reactivated the plugin, and now the save button says ‘processing’ and that the settings have been saved ?? For now I will try to change the settings to only have notifications once a day and wait for your reply. Many thanks

    Thread Starter Kir 2012

    (@kir-2012)

    Hi there, thanks for your input to help me I really appreciate it.

    I solved this now for anyone else who could benefit, I put the code below in the single layout from my theme (in child theme of course) to show the link when the custom field is present :

    	<center><?php
      if ( get_post_meta( $post->ID, "my_custom_field_name_with_url_values", true ) ){
        echo '<div class="pros"><p><strong><h2>More Event Info:</h2>  </strong><a href="' .
        get_post_meta( $post->ID, "my_custom_field_name_with_url_values", true ) .
        '" target="_blank">' .
        get_post_meta( $post->ID, "my_custom_field_name_with_url_values", true ) .
        '</a></p></div>';
      }
    ?></center>
    Thread Starter Kir 2012

    (@kir-2012)

    Hi there, thanks for your reply, but there is nothing in the attributes section of the settings tab, I haven’t used that. The ‘attributes’ option is on, (nothing appears as a field in the event registration form otherwise), but the other fields like ‘website’ and ‘price’, these are only added in the format tab for single event, using similar code to your example above, but conditional as in the code paste. I tried your code as described also, but the field still remains on the add event form, is there anything else I could try? Perhaps amending the code in attributes public template in my child theme to make an exception in the code for that custom field name, where it adds detected attributes to the form? Is there a good way to do that?
    Thanks

    Thread Starter Kir 2012

    (@kir-2012)

    In your link above it says:

    “Now we need to define our attributes by giving them names and possible values. Attributes are defined by either adding them to your attributes box in the same settings page where you activated attributes above, or entering them directly into your formats on the settings page. Events Manager will detect that there is a new attribute and generate the right form fields on the event or location registration page.” Can I do something to prevent that from happening for this particular item? Prevent that function from running for just that one custom field name?

    Either that or if you could help me understand what I should be entering into the single event format window on the formats tab, to bring in this custom field without it adding to the form that would be brilliant ??

    • This reply was modified 1 year, 3 months ago by Kir 2012.
    Thread Starter Kir 2012

    (@kir-2012)

    Hi, thanks but I can’t do that as I have other unrelated attributes that need displaying. So I’ve got both custom fields and attributes on at the mo. Is there code I should be using other than this to display the custom field value from the plugin in the single event section of formats tab, with that in mind?

    {has_att_the_custom_field1}
    <strong>More Event Info:</strong>
    <br><a href="#_ATT{the_custom_field1}" target="_blank">#_ATT{the_custom_field1}</a>
    <br><br>{/has_att_the_custom_field1}

    Or if entering that code in format for single event isn’t causing it to appear on add event form, might you know what is causing the field to be added, so that I can address it?

    To clarify further, whereas I have added the attributes I wish to appear on the form, and then display on an event post, this one custom field comes when I import an event from elsewhere, I don’t add it in admin. It’s there already. I wish to display it on the event page, which I have done, using the above code. But if I add this code into the single event in the format tab, it immediately adds it to the form. When I remove it from the the single event format, it removes it from the form.
    Thanks ??

    • This reply was modified 1 year, 3 months ago by Kir 2012.
    • This reply was modified 1 year, 3 months ago by Kir 2012.
Viewing 15 replies - 46 through 60 (of 195 total)