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 |
|---|---|---|
| Ackis | Tue, 21 Apr 2009 15:03:29 | Changed component from None to Searching/Sorting |
| amirabiri2 | Thu, 25 Dec 2008 09:37:07 | Create |
- 2 comments
- 2 comments
Facts
- Last updated on
- 21 Apr 2009
- Reported on
- 25 Dec 2008
- Status
- New - Issue has not had initial review yet.
- Type
- Enhancement - A change which is intended to better the project in some way
- Priority
- Medium - Normal priority.
- Component
- Searching/Sorting
- #2
Phanx Sat, 10 Jan 2009 21:49:58I 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!
- #1
Drool Thu, 08 Jan 2009 02:22:15Personally, 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.