Page 1 of 1

New event description field character limit

Posted: Sun Dec 21, 2014 4:15 pm
by CruiseLite
Hey folks!

Trying to create my first event under SGV3 and I find that I cannot enter as much detail as I could in V2.
I guess 1000 characters is by design but that really limits what I can insert compared to V2.
Any plans to increase/remove this limit?

In addition, it would be nice if the description field would dynamically adjust size as it did in V2.

Re: New event description field character limit

Posted: Sun Dec 21, 2014 4:35 pm
by StatsGenie
We will look into this after the Holidays.

The 1000 char limit can certainly be increased.


Happy Holidays

Re: New event description field character limit

Posted: Sun Dec 21, 2014 4:59 pm
by CruiseLite
Awesome! And quick response!

I also just noticed after receiving the event invite that none of the formatting for the description field is maintained. All the text is crammed together and very hard to read.

Re: New event description field character limit

Posted: Thu Jan 22, 2015 10:44 am
by StatsGenie
Hi,

b3.13.15 implemented today should fix this.

Re: New event description field character limit

Posted: Sun Jan 25, 2015 2:56 pm
by CruiseLite
Great! Thank you.

Re: New event description field character limit

Posted: Wed Sep 14, 2016 5:56 pm
by jhhightower
I have searched the forum and this seems to be a common problem. The description field in the email that is sent to the invitees is just plain text all crammed together. I put line breaks in the description but they do not show up in the email and it makes it difficult to read at times. Is there a way to format the text in the description field on the invites to make it more readable?

Thanks for a great site, I have been using it to run my poker league for several years!

Jamie

Re: New event description field character limit

Posted: Fri Sep 23, 2016 12:59 pm
by JGuay
We will take a look at this issue. We'll also try to make it available it our next week update.

Edit:
I am now able to confirm that the issue will be corrected in our next version.