Hi @codewisenicolas,
Thanks for your message and for reporting these issues.
You’re right in that the [user_ip_address] shortcode is missing – I have no idea where this has gone but remember testing it. I suspect it was removed accidentally during a branch merge. I’ll try and find it and reinstate it.
Wrt the [post_update_author] issue, can you provide reproducable steps so that I can test this and see if I can find the issue?
Thanks for responding so quickly.
Problem 1 has been very hard to track down and reproduce as its seemingly random. A user will edit a page but the notification will instead show a different user as the person who made the edit.
I have looked thru the plugin code and the only situation I could figure is that somehow the post edit lock (_edit_lock) meta must not be getting updated and when the plugin tries to grab the editor it uses the meta value and thus it shows the wrong user in the notification email; however this is an assumption/best guess not an actual diagnosis.
We also tried the [user_***] shortcodes as listed here https://betternotificationsforwp.com/documentation/notifications/shortcodes/?notification=update-post because it says “These multi-purpose shortcodes relate to the person triggering the notification” however we found those shortcodes are not related to who triggered the notification for post/page updates; I checked the code and confirmed this – its actually the post author.
Would it be possible to request a new shortcode that is directly connected to the wp_get_current_user() function ?
I think this would quickly resolve our issue with actions on posts/pages.
Again thanks for responding and looking into it.
Hi @codewisenicolas,
You could always try to use [email_user] shortcodes instead, in case they better reflect the user triggering the notification in this instance.
You can create your own shortcodes to use with BNFW. Some information on this can be found here: https://betternotificationsforwp.com/documentation/adding-custom-shortcodes/
Let me know if this helps.
Closing due to inactivity. If you need further help with this, please feel free to re-open this thread.
