[ Return to Bugs & Features | Post Text | Post File | Next ]

STR #1970

Application:	FLTK Web Site
Status:	5 - New
Priority:	4 - High, e.g. key functionality not working
Scope:	3 - Applies to all machines and operating systems
Subsystem:	Web Site
Summary:	Unable to add comment to FAQ article
Version:	Web Site
Created By:	engelsman
Assigned To:	Unassigned
Fix Version:	Unassigned
Update Notification:	Receive EMails Don't Receive EMails

Trouble Report Files:

No files

Trouble Report Dialog:

	Name/Time/Date	Text
	engelsman 00:58 May 27, 2008	I've successfully logged into the site as 'engelsman' and tried to add a comment to the out-of-date FAQ entry about the different versions at http://www.fltk.org/articles.php?L366+I10+TFAQ+M10+P1+Q Article #366: What are the Versions of FLTK? The comment text was: This FAQ entry is really out of date! <UL> <LI>1.0 was ancient history.</LI> <LI>1.1.x was the main development line. Last stable release: 1.1.9</LI> <LI>1.2 was a fork to incorporate utf8 but is no longer developed.</LI> <LI>1.3 is the new development line, and will be 1.1.9 plus utf8, etc.</LI> <LI>2.0 is an unstable, parallel development to 1.1.x with changed API, with various improvements, but missing many bug fixes found in 1.1.9.</LI> </UL> So as of 2008-05-27 you can choose 1.1.9 for stability, 2.0 for leading edge features but unstable, or help to develop 1.3... It previewed OK, but when I tried to submit I got a header saying "Error: Please fill in the fields marked as follows below and resubmit your comment." but no fields were marked so I couldn't see what was wrong :-(
	engelsman 01:00 May 27, 2008	And of course those &lt; and &gt; should be < and > but I thought they would be eaten...
	engelsman 05:39 Mar 24, 2012	This is probably also linked to STRs 2099, 2100 and 2213. I was able to add a comment to Article #366 but this was limited to a paragraph tag and the link to Article #825 which replaces it, so it may be that they type of tags influences behaviour. PS. This is the second attempt to post here - maybe I forgot to fill in one of the fields last time and didn't notice...