994 - Search results project summary to ignore TOC

As it stands, curse generates the project summary that appears as popup text on mouse over by taking the first parts of the description and stripping markup.

However when using cursewiki, the first part of the description is the automatically generated TOC. The TOC with stripped markup in turn equals to gibberish.

I think the process should take the description before the TOC was generated and use that, so that the popup text is meaningful. Alternatively the "abstract" can be taken as a separate field or separate page.

User When Change
Torhal Jul 24, 2013 at 19:50 UTC Changed status from Accepted to Declined
Torhal Nov 09, 2011 at 17:27 UTC Changed status from New to Accepted
Torhal Jun 03, 2011 at 16:58 UTC Changed assigned to from Kaelten to prencher
Ackis Apr 21, 2009 at 15:03 UTC Changed component from None to Component #271
amirabiri2 Dec 25, 2008 at 09:37 UTC Create

You must login to post a comment. Don't have an account? Register to get one!

  • Avatar of Phanx Phanx Jan 10, 2009 at 21:49 UTC - 0 likes

    I also use the top of my description to post important messages for users in big bold text. I don't imagine it's helpful for anyone to see "Please scroll down and select the Beta file..." on a search results page or in the Curse Client. Short description field please!

  • Avatar of Drool Drool Jan 08, 2009 at 02:22 UTC - 0 likes

    Personally, I use the very top of my addon page to warn nubcakes not to post error logs and a list of their 100+ addons. I also have a TOC.

    Ideally we could use a small text field - limited to X amount of chars or whatever - for a short summary of the addon description. Solves the TOC problem and also caters better for Curse Client.



Last updated
Jul 24, 2013
Dec 25, 2008
Declined - We decided not to take action on this ticket.
Enhancement - A change which is intended to better the project in some way
Medium - Normal priority.

Reported by

Possible assignees