After installation of 5.2RC i get at some sites a :  Error - There was an error processing the last request. Please reload this page to continue. More Info -->  'Uri too long' -  - and cannot save  any changes. (My url is less than 20 letters)

In  stackoverflow i found to that  "Based on John's answer, I changed the GET request to a POST request. It works, without having to change the server configuration." To this theme also openjs and a demo

Can the error be caused by the exchange of ajax - put -get in the RC5.2 ?

My url is less than 20 letters

The problem is certainly an AJAX GET request. Can be checked via the web browser's Developer Tools -> Network tab.

I changed the GET request to a POST request

Which request did you change and in which editing context does the error occur?

The error comes, if i go into some of the sites - klick into the text and ckeditor opens. Then i add 2 letters without saving - thats sufficient for the error-popoup. (I added jquery-migrate -1.41. : no change --- newest ckeditor 4.14 - no change) . In the sourcecode is no special code (Example site) *In the network analysis are only 4 calls with GET for combinded css.

*In the console :  Das Skript von "https://www.typesettercms.com/index.php/Resources?cmd=er&mdu…lback=jQuery224059924982080022_1591716992714&_=1591716992715" wurde geladen, obwohl sein MIME-Typ ("text/html") kein für JavaScript gültiger MIME-Typ ist .  2. Das Cookie “cookie_cmd” wird in Zukunft bald abgelehnt werden, da es für das Attribut "sameSite" entweder "none" oder einen ungültigen Wert angibt, ohne das "secure"-Attribut zu verwenden. Weitere Informationen zum "sameSite"-Attribut finden Sie unter https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite

* Changed get request : I didnt change anything - You changed ajax before the RC52 in the git master - but that is not necessary the reason

* Perhaps it has something to do with autmatic saving. Is there a function, which checks the sourcecode before saving -  i thought that Ckeditor is sufficient , and codemirror shows no bad code either

P.S. The cms-cache shows no dates (minutes and seconds) of the files - is that wanted ? - if You do not want to change it - how can i do it ?

P.S. 2 :The " uri too long " comes from the over 1000 letters long debug-link to typesetter cms  http://www.typesettercms.com/index.php/Debug?data=eyJ0aHJvd25FcnJvciI........................ 414 Request-URI Too Large -- cloudflare) The files under /_pages have all 666. HTML Tidy is off. Maybe it is a problem of the filemanger, which saves the code.

I tried the same code at an installation of 5.1.1b2 of November 2109 - the same.... I validated the (corrected) code at https://validator.w3.org/nu - except deprecated 'center' - everything ok. If i make a new site and multiply the lorem ipsum 20 times - the saving is no problem - and also no problem with changes.  If the error comes from the above code, i am asked to refresh the site instead of saving.

It is not a provider-problem with content-filter as in China . The error is also at xampp 52rc. You  can klick at the top of  this example - site  - right mousekey - inspect : Treat html -->(frame) <div class="mui-panel">......and mark everything and copy - and paste this source into notepad++.

I had a similar problem years ago with gpeasy, when a very long site, in which i had collected bootstrap codesnippets, made the cms unstable. After i had distributed the code on 2 sides,  the problem disappeared.

I do not fully understand this bug - maybe a parser of the history function stops the saving  of changes , which may have problems with long linklists or long links - ..it just should not be ! I would save the history in a file of the directory of the actual site (evtl. only lines which are different and not codepieces)....

The " uri too long " comes from the over 1000 letters long debug-link to typesetter cms … 414 Request-URI Too Large -- cloudflare

Hmm, sounds reasonable. But that's just a symptom, not the cause. Another, earlier JS error must occur that triggers the debugging request.

The cms-cache shows no dates (minutes and seconds) of the files - is that wanted ?

Well, showing minutes and seconds can be confusing for people who are not aware that the webserver may be in a different time zone.
But I changed it anyway.

The 'uri too large comes' after over a minute in a new tab, after i had clicked at 'more info ' .

.

The new tab hangs for a long while  with an empty window, and then comes a very long  url to typesettercms with appendix of over 1000 letters and then comes the error  : 414 Request-URI Too Large -- cloudflare)

* Well - i can save similar code with tables and uls - no problem. In the code are very long urls to amazon like http://www.amazon.de/Die-Ayurveda-Pflanzenheilkunde-Der-Yoga-Heilkr%C3%A4uter/dp/3893856757/ref=pd_sim_14_3/280-9585099-0270653?ie=UTF8&amp;dpID=5164Jq9m87L&amp;dpSrc=sims&amp;preST=_AC_UL160_SR100%2C160_&amp;refRID=075HMM1J4D7RPHBQ6BT2" rel="nofollow" target="_blank">Die ...

If the routine, which sans for differences, has problems with ?, ; or & - it will stop - is it written in Javascript ?  But You can put the source code into any site at xampp with the same result.  May be just an utf8 somewhere in the routine helps. (The routine scans first after the first saving for differences ...- and i can copy the code into an empty site and save, but then make no more changes)

There are 2 diifferent parts of the issue

1. You get an 'Error - There was an error processing the last request.' That's because something causes a JS error when you try to edit content.
2. Cloudflare - which hosts typesettercms.com - doesn't allow GET requests with URLs longer than 1000 characters. 1000 is quite restrictive (the default value  is 8190)
   I don't know if this setting is new or how long it has been in effect. Unfortunately I have no control over it.

In any case, you should first find out what is causing the initial error. The HTTP 414 URI too long error is not the cause.

* The 'uri too large ' is of course not the reason - but comes from cloudflare - but why the uri is so long, is not clear.

* I finally found the reason : The code of the page is rather old, and it contains at one part

<a class="nodisplay" data-arg="text_inline_edit" data-cmd="inline_edit_generic" data-gp-area-id="1"
href="http://tm-meditation.net/Ayurveda?section=0" id="ExtraEditLink1" title="Editierbarer Text">Bearbeiten</a></span>
<a href="https://www.ncbi.nlm.nih.gov/pmc/articles/PMC3562518/" rel="nofollow" target="_blank">Prakriti</a>

Atfer return to normal HTML in the first 2 lines  it functions now... but still : If i have  a 'nonsensic' code , why do i get an error as above - if the site functions and htmlvalidators see nothing .

First https://www.online-toolz.com/tools/html-validator.php  gave me  a hint. ( the functioning site is http://www.tm-meditation.net/test2 - i will continue tomorrow)

but why the uri is so long, is not clear.

It contains all the data required to display the debugging info shown on typesettercms.com when you click 'More Info". It can easily exceed 1000 characters, depending on the error thrown.

The code … contains at one part <a class="nodisplay" data-arg="text_inline_edit" …

That's not part of the page content. It's an editing overlay that only shows up when hovering a section. It will not get posted/saved.

If i have  a 'nonsensic' code , why do i get an error as above

The HTML shouldn't be the issue, even if it's weird or malformed. What you get is a JavaScript error.
Check the web browsers developer tools -> Console (or press Control+Shift+J). You should see the error (in red) that triggers the whole thing.

Sorry - but the code is the source which i had in codemirror.  Obviously the history-backup-routine gets mixed up with such code (which comes from gpeasy times - i use now only html and no gparea) - i just hope that it doesnt get mixed up with other data-types appendices or makes changes like ckeditor does. There is no Javascript - error : I removed for test the prev-next at the bottom - no change.

The only message i get repeatedly already BEFORE the saving and the popup is

[Exception... "Favicon at "https://www.typesettercms.com/favicon.ico" failed to load: Not Found."  nsresult: "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: resource:///modules/FaviconLoader.jsm :: onStopRequest :: line 227"  data: no]

The saving and then popup causes no javacript activity.

The error comes from the code with "data-arg="text_inline_edit" data-cmd="inline_edit_generic" data-gp-area-id="1"......" , which is in there out of whatever reason. The site functions now. Interesting would therefore also be a change, which shows the error already in the 1st popup.

the code is the source which i had in codemirror.  Obviously the history-backup-routine gets mixed up with such code (which comes from gpeasy times - i use now only html and no gparea) - i just hope that it doesnt get mixed up with other data-types appendices or makes changes like ckeditor does.

However you managed to get editor code in the content, such will definitely cause problems.

But don't just blame Typesetter for it. I have never encountered such a problem myself, nor have I heard of it. I also can't imagine how it could ever happen. It is neither the save nor the revision history or the export function.

It rather sounds to me as if you just copy-pasted some source code from a different site into CKEditor, which contained the editor overlay code.

There is no Javascript - error / The saving and then popup causes no javacript activity.

You might need to enable log display in your console. But it doesn't matter anymore since we already know the source of the issue
FYI: This is where AJAX debugging happens in main.js

Interesting would therefore also be a change, which shows the error already in the 1st popup.

I believe Josh decided to send the errors to typesettercms.com's remote debugging service, to get a stripped-down and more clear analysis of what happened. Unfortunately It sometimes doesn't work so well. Since the error is also logged into the web browser console, I prefer to use that source for debugging. It's less clear but more complete info.