Anyone else noticed this issue before?

PX-Z

legendary

Activity: 1554

Merit: 880

Wallet transaction notifier @txnNotifierBot

Quote from: jamyr on January 29, 2025, 02:28:51 PM

newbie suggestion(please go easy on me)
How about a warning when a session-code is about to expire that the user may be made aware so that he can maybe save things like a draft or other stuff.?

when the session-code becomes invalid, maybe apply mute in the "To" input field.

It's possible but not recommended using in this old forum software, and it requires a lot of resources if using like AJAX to inform every user their session expiry time every time.
Not unless if it uses like Websocket for the real-time notification which think it was never implemented here before.

hosseinimr93

legendary

Activity: 2380

Merit: 5213

Quote from: Perfectbaby on January 29, 2025, 11:41:08 AM

If sending messages to multiple users you should get the first user it says "to", you can add only one person, then below where it says "BCC" is the next place to add all the users you want to send out the pm to than putting all at the first place.

This is completely wrong.
You can add multiple users at both "To" and "Bcc" fields.

The differene between "To" and "Bcc":
The list of users you add at "To" field will be shown to all recipients.
The list of users you add at "Bcc" field will NOT be shown to other recipients.

jamyr

sr. member

Activity: 1848

Merit: 373

<------

Quote from: theymos on January 29, 2025, 12:26:57 PM

That can happen if you leave the PM-compose page open for a long time so that your session-code becomes invalid. Reloading the page should fix it.

(The JS autocompleter function should detect this and not dump the whole HTML error page, but it's a rare situation, and it's not immediately obvious to me how to fix it.)

newbie suggestion(please go easy on me)
How about a warning when a session-code is about to expire that the user may be made aware so that he can maybe save things like a draft or other stuff.?

when the session-code becomes invalid, maybe apply mute in the "To" input field.

Mia Chloe

hero member

Activity: 448

Merit: 560

Mia's Creative

Quote from: theymos on January 29, 2025, 12:26:57 PM

That can happen if you leave the PM-compose page open for a long time so that your session-code becomes invalid. Reloading the page should fix it.

(The JS autocompleter function should detect this and not dump the whole HTML error page, but it's a rare situation, and it's not immediately obvious to me how to fix it.)

I think this is what happened though I can't really remember vividly since I was on my mobile device while this issue occurred. Nevertheless thanks for noting it out . I'm not much of a JavaScript coder else probably I would have looked up a way to fix it.

Quote from: Pablo-wood on January 29, 2025, 12:19:28 PM

Alternatively he can still use the find Members button beside the "To" column. This will pop up a search bar where he can search for members by their username, if found he/she will simply tap on it and it will be added to the "To" column then when he/she has gotten the exact number of Members he/she wants to send the pm to then moving the names to the "BCC" column will be the next step that way the name accuracy will be 100% and it eliminate errors as well.

Yeah you do have a point, this too is feasible but I don't know if you've tried it before but if you have you would notice that sometimes even when you spell out the usernames correctly including being case sensitive, it still says user not found.

theymos

administrator

Activity: 5222

Merit: 13032

That can happen if you leave the PM-compose page open for a long time so that your session-code becomes invalid. Reloading the page should fix it.

(The JS autocompleter function should detect this and not dump the whole HTML error page, but it's a rare situation, and it's not immediately obvious to me how to fix it.)

un_rank

hero member

Activity: 644

Merit: 661

- Jay -

Quote from: Perfectbaby on January 29, 2025, 11:41:08 AM

,,, Using the Bcc, every single user must be separated by comma (,) and then add next person otherwise your pm wouldn't allow you to send out.

With this method can all the users who receive the message see others who got the message?

I think that is an issue that needs to be fixed as it sometimes results in a user who got the message replying to every other recipient and sensitive information can be leaked.

- Jay -

Pablo-wood

member

Activity: 73

Merit: 31

Quote from: Perfectbaby on January 29, 2025, 11:41:08 AM

...

Alternatively he can still use the find Members button beside the "To" column. This will pop up a search bar where he can search for members by their username, if found he/she will simply tap on it and it will be added to the "To" column then when he/she has gotten the exact number of Members he/she wants to send the pm to then moving the names to the "BCC" column will be the next step that way the name accuracy will be 100% and it eliminate errors as well.

Perfectbaby

full member

Activity: 162

Merit: 104

If sending messages to multiple users you should get the first user it says "to", you can add only one person, then below where it says "BCC" is the next place to add all the users you want to send out the pm to than putting all at the first place. Using the Bcc, every single user must be separated by comma (,) and then add next person otherwise your pm wouldn't allow you to send out.

Mia Chloe

hero member

Activity: 448

Merit: 560

Mia's Creative

So yesterday I had a PM to send over to a couple of members who won in the Naija board Christmas and New year contest themed THE NIGERIAN DISH. Nevertheless I encountered some issues when I tried to add up multiple recipients for the PM. So basically there were two issues, the first is in the image below;

I constantly got this DOCTYPE HTML syntax when I tried editing the recipients username basically clearing it was an issue that I had to use the select all button to highlight the total code and clear it.

Secondly I noticed that even with the correct username , the message still didn't get to some of them. Instead I got an error feedback saying; ('user does not exist')

Topic: Anyone else noticed this issue before? (Read 211 times)