Modifying the email notification template?

[nebulous]

I'm just starting to set up my first forum on boards.net. I'm tinkering with the capabilities and playing around with the discussions just to see how it all works.

The email notification that tells you when a response is made to a discussion is big and bold and colorful with the text surrounded by graphics.

I would prefer a simple non-graphical or minimally graphical text notification, preferably with the full text of the post. 

Is this possible? I'm not seeing where to modify the design of the email notifier.

Thanks,

~N

[Tumbleweed]

May 11, 2016 18:42:18 GMT -8 nebulous said:

I'm just starting to set up my first forum on boards.net. I'm tinkering with the capabilities and playing around with the discussions just to see how it all works.

The email notification that tells you when a response is made to a discussion is big and bold and colorful with the text surrounded by graphics.

I would prefer a simple non-graphical or minimally graphical text notification, preferably with the full text of the post. 

Is this possible? I'm not seeing where to modify the design of the email notifier.

Thanks,

~N

I'm a bit confused by what you are asking. Are you talking about the email you receive in your email? Like the screen cap below?  


Sorry, there is no way to change the layout but I have found  you can somewhat tone down the colors by setting your login register colors. Admin Home> Settings> Forum Settings> Login & Registration>


Here is a screen shot of me changing the login/register colors I posted above and here is the email notification I got this time.




Or are you talking about something else?

[nebulous]

Tumbleweed - Thanks for this reply. Yes, that is what I was referring to. I appreciate the tip on changing colors.

I do wish there were a way to change that email template altogether. My board will be a bit more serious - studious, even - and a big, bright, boxy, modern notification doesn't fit my theme as much as a regular text-based email would. It's not a huge deal, but it would be nice to have that flexibility.

Thanks again!

[bkohne]

Is there any update to this request by nebulous? I am experiencing the same dilemma. The notification email is too colorful and actually obscures the message of the update in my opinion.

Is there any way to edit this today?

[Kami]

May 24, 2020 9:48:03 GMT -8 bkohne said:

Is there any update to this request by nebulous ? I am experiencing the same dilemma. The notification email is too colorful and actually obscures the message of the update in my opinion.

Is there any way to edit this today?

It would have been better to create your own thread as per the forum rules than bump up a thread that is four years old.

In any case, this has not changed. There have been several requests for this for the next version (v6) of the software, so we will have to wait and see if it's been included as a feature. There is unfortunately no current ETA on release.

[nebulous]

May 24, 2020 9:52:51 GMT -8 Kami said:

May 24, 2020 9:48:03 GMT -8 bkohne said:

Is there any update to this request by nebulous ? I am experiencing the same dilemma. The notification email is too colorful and actually obscures the message of the update in my opinion.

Is there any way to edit this today?

It would have been better to create your own thread as per the forum rules than bump up a thread that is four years old.

In any case, this has not changed. There have been several requests for this for the next version (v6) of the software, so we will have to wait and see if it's been included as a feature. There is unfortunately no current ETA on release.

Kami, I disagree that another request should have been started on the same topic. I am the originator of the request and I would still like to see this change made available even 4 years later.

What benefit is there to starting a new thread on an identical request? Doing so clutters up the request board and makes search for an identical issue more challenging. It also would have prevented me from knowing that others want the same thing and, if there had been a resolution, would have prevented either bkohne or me from knowing about it.

Most support boards I know of encourage people to find other requests on their topic if they exist and replying to those.

[Kami]

May 24, 2020 15:15:42 GMT -8 nebulous said:

May 24, 2020 9:52:51 GMT -8 Kami said:

It would have been better to create your own thread as per the forum rules than bump up a thread that is four years old.

In any case, this has not changed. There have been several requests for this for the next version (v6) of the software, so we will have to wait and see if it's been included as a feature. There is unfortunately no current ETA on release.

Kami, I disagree that another request should have been started on the same topic. I am the originator of the request and I would still like to see this change made available even 4 years later.

What benefit is there to starting a new thread on an identical request? Doing so clutters up the request board and makes search for an identical issue more challenging. It also would have prevented me from knowing that others want the same thing and, if there had been a resolution, would have prevented either bkohne or me from knowing about it.

Most support boards I know of encourage people to find other requests on their topic if they exist and replying to those.

Regardless of your opinion, that's how this forum operates. Cool reasoning, still not following the rules.

It's generally recommended that if someone wants to reference an old thread as the basis of their question, to simply link to it in their opening post for context. You also may want to check out the Development Blog board on the main page if you actually want updates. This thread won't get 'em.

For added measure, a quick tag to Scott to get his 0.02, though he might not get to this til Tuesday, due to the local holiday.

[bkohne]

I'm with Nebulous. If my problem has four issues, for example, and his thread answered three of the four - and my only interest is in solving the fourth - a new thread buries the solutions for the (new) user.

Rules are rules though.

[Kami]

May 25, 2020 9:36:27 GMT -8 bkohne said:

I'm with Nebulous. If my problem has four issues, for example, and his thread answered three of the four - and my only interest is in solving the fourth - a new thread buries the solutions for the (new) user.

Rules are rules though.

Again, it doesn't matter if y'all disagree. If it's really bugging you, I recommend taking it up with a staff member and not me. In the mean time, don't necropost & create your own topic for your own issue, as per forum rules.

[Scott]

nebulous , whether or not we will allow for customization of the notification emails in the future I can't say, although we are always listening to our users and anything is possible.

In regards to including the full text of the post in a notification email, this is not something we will ever implement. It discourages users from visiting the forum. It would only encourage users to come to the forum when they wish to reply.

-----------------------------------------

All feature requests regarding ProBoards software should be made on the Support Board. That is the only place that management and the developers will look. 

Any new features or implemented software changes will be announced on the Development Blog board, as Kami stated above.

------------------------------------------

Most of the boards on this forum have a written no necroposting rule. Some boards, like this one, it is implied and do not have it spelled out as it hasn't been necessary - especially since it's generally accepted on any bulletin board/forum site that necroposting is frowned upon. Suppose now I'll need to update our rules. 


Ideally, Tumbleweed should have invited you to make a  feature request on the Support Board, if you so desired; and bkohne should have posted on the Support Board with a link to this thread (or your request on Support, if made) as a reference when inquiring if there were any updates to your initial request.