View Issue Details

IDProjectCategoryView StatusLast Update
0000581Composr[All Projects] General / Uncategorisedpublic2012-06-11 16:19
ReporterChris GrahamAssigned ToChris Graham 
SeverityMinor-bug 
Status resolvedResolutionfixed 
Product Version 
Fixed in Version 
Summary0000581: Possible error when going to 'full editor' in Conversr
DescriptionIf you're on a non-threaded topic, Conversr tries to show the post being quoted when typing your reply, so you can cut up the quotation into pieces if you like. It also tries to remove that quotation if unchanged, so that a cleaner direct-parent-post-reference may be used instead.

When moving to the full editor it loses the reference to the prepopulated quote, so it passes one via a 'stub' parameter.

However this is done as a 'GET' parameter, which has a length limit on Apache. Doing it for a very long quoted post will produce a server-side error.

Move to using a 'POST' request. This will require making the quick reply form a bit more sophisticated.
TagsNo tags attached.
Time estimation (hours)
Sponsorship open

Activities

Chris Graham

2012-06-11 16:04

administrator   ~0000625

Fixed in git commit 4c67ed0 (https://github.com/chrisgraham/Composr/commit/4c67ed0 - link will become active once code pushed)

A hotfix (a TAR of files to upload) have been uploaded to this issue. These files are made to the latest intra-version state (i.e. may roll in earlier fixes too if made to the same files) - so only upload files newer than what you have already. Always take backups of files you are replacing or keep a copy of the manual installer for your version, and only apply fixes you need. These hotfixes are not necessarily reliable or well supported. Not sure how to extract TAR files to your Windows computer? Try 7-zip (http://www.7-zip.org/).

Chris Graham

2012-06-11 16:04

administrator  

hotfix-581, 2012-06-11 4pm.tar (245,760 bytes)

Chris Graham

2012-06-11 16:19

administrator   ~0000627

Forgot to mention, this solves a JS syntax error for Windows users also. On some browsers anyway. This is because JS injects a "\r" into its runtime data and this breaks the JS parser when embedded back into a string, unless stripped.

Issue History

Date Modified Username Field Change
2023-02-26 18:29 Chris Graham Category General => General / Uncategorised