Edit error: Sorry, the form could not be submitted. Please try again.

els · 2015-02-21 00:52:35

That was Chrome. (Chromium actually)
Console in Firefox says

Use of getUserData() or setUserData() is deprecated.  Use WeakMap or element.dataset instead. cacheobj.js:829
Use of getPreventDefault() is deprecated.  Use defaultPrevented instead. jquery.js:3

Otherwise no differences as far as I can see.

Stef, it’s Friday night so I don’t expect quick answers!

els · 2015-02-21 00:55:12

Bloke wrote #288471:

EDIT: You could also check the inspector’s ‘Network’ pane, click the request that gets sent when you hit Save and see if anything looks amiss in either what is sent to the server, or its response.

Ah sorry, it’s getting late here… Clicking the request:

Fatal error: ob_clean() [<a href='ref.outcontrol'>ref.outcontrol</a>]: Cannot use output buffering in output buffering display handlers in /home/httpd/vhosts/arlettejeanine.com/httpdocs/textpattern/lib/txplib_misc.php on line 2822

Bloke · 2015-02-21 00:55:47

Els wrote #288472:

In the console I see this when I open an article in the write tab (but nothing happens when I hit Save) <snip>

That output on page load is expected.

In the Network pane, hitting Save gives me <snip>

OK, so it’s doing something. If you click that line, does it twist down to reveal more stuff? In both Firebug and Chrome’s inspector you should then see some tabs with Headers, Post, Response, Cache and so on. Clicking “Headers” shows what was sent to the server, clicking “Response” shows what was returned. That’s the main one we’re after. It usually starts something like this:

;
                $(document).ready(function ()
                {
                    $("#messagepane").html("<span class=\"messageflash success\" role=\"alert\"><span class=\"ui-icon ui-icon-check\"></span> Article posted. &#160;<a class=\"close\" role=\"button\" title=\"Close\" aria-label=\"Close\" href=\"#close\">&#215;</a></span>");
                    $(window).resize(function ()
                    {
                        $("#messagepane").css({

You might not see any of this until after you’ve acknowledged the Form cannot be submitted error, but perhaps mingled with that response output is an error we can sink our teeth into?

Bloke · 2015-02-21 00:57:52

Els wrote #288475:

Fatal error: ob_clean(). Cannot use output buffering in output buffering display handlers…

Aha! Our posts crossed. That’s the puppy, thanks. I’ve posted about that one before somewhere, probably on the MLP thread. If I come across it I’ll post the link, but you’ll probably beat me to it :-)

Last edited by Bloke (2015-02-21 00:59:42)

els · 2015-02-21 00:59:18

~~Yeah I missed that, sorry. See my previous post.~~

~~Ah thanks. I will search the MLP thread!~~

Edit: crossposting it is tonight ;)

Bloke · 2015-02-21 01:01:25

Els wrote #288478:

Ah thanks. I will search the MLP thread!

Found it, and yes, seems to be fixed in a later MLP version: the github one.

els · 2015-02-21 01:03:59

Haha, let’s stop crossposting :) Thanks very much, Stef! I haven’t read the entire post yet, but noticed you mentioning a cheap fix. Should I try that first?

Bloke · 2015-02-21 01:07:01

Els wrote #288480:

you mentioning a cheap fix. Should I try that first?

You can do so, but note the caveat in a much later post that the cheap fix breaks something else. That post outlines how to fix the fix… or you could just download the latest github MLP, backup everything and try that. The actual compiled plugins are linked from a fairly recent MLP post of mine.

els · 2015-02-21 01:09:19

OK, I’ll be good and upgrade both Txp and MLP :) Thanks again and sleep well!

kees-b · 2015-03-02 09:44:27

I just found that the txp_lib_misc.php fix interferes with the thru_tag plugin. On a site with a large number of tags we use the clickable list from the thru_tags plugin. With the fix applied, when saving an article with tags, all comma’s are removed between the chosen tags, thus creating one new enourmous multi-word tag! They can be re-inserted by hand though and then the comma’s will stick!

Bloke · 2015-03-02 09:59:41

kees-b wrote #288684:

With the fix applied, when saving an article with tags, all comma’s are removed

That’s crazy. Perhaps tru_tags internally uses newlines to delimit its list options, which are being stripped by the patch prior to article save, thus treating the keywords list as a single, humungous string. Someone would have to review the code to find out why.

gfdesign · 2016-01-15 18:08:01

Hi community.
I faced with this same problem (the original, not using MPL) in a TXP 4.5.2 site but I was able to fix it as you suggested writing the articles titles of the last five articles again.

However, upgrading to the last version to 4.5.7 didn’t fix the original issue in a cloned installation as I thought. I mean, not correcting the titles just relying the solution would be done by the upgrade.

I hope in a future this issue can be solved
I just wanted to say that. :)

Thanks

Leonick · 2016-04-12 14:35:38

I have the same problem on v4.6-dev
I’ve install the v4.6-dev because I think this version solve the recurrent problem on the v4.5.7
but no !

Perhaps this error came from this response “HTTP/1.1 401 Your session has expired” for the “POST /textpattern/index.php HTTP/1.1” ?
Finally, no : I’ve the same problem with HTTP 200 response

Last edited by Leonick (2016-04-12 14:41:03)

colak · 2023-02-17 07:56:32

Revisiting this old thread as I had the same error today, so I’m posting this for future reference. My FF console started returning a 418 error on saving any form or page. The error logs revealed that this was due to an “Execution error – PCRE limits exceeded (-8).” The easy fix was to add

pcre.backtrack_limit = 10000000
pcre.recursion_limit = 10000000

in the Dreamhost’s phprc.

colak · 2023-02-17 10:14:54

colak wrote #334651:

Revisiting this old thread as I had the same error today, so I’m posting this for future reference. My FF console started returning a 418 error on saving any form or page. The error logs revealed that this was due to an “Execution error – PCRE limits exceeded (-8).”

Thinking about it, why would the back-end return this error?

Active plugins:

act_if_mobile-0.1.2 (modified)
adi_matrix-2.1beta5
adi_notes-1.4
com_connect-4.7.0 (modified)
etc_query-1.5.1
ext_com_connect_verify-0.1 (modified)
ext_file_attach-1.0.5
fha_time_diff-0.23
ied_plugin_composer-1.2.1
mem_postmaster-1.0.20 (modified)
oui_cookie-1.0.0-BETA4
pap_comconnect-0.1.2 (modified)
pat_speeder-1.1
rah_external_output-1.0.4
rss_admin_db_manager-4.6.0
smd_where_used-0.4.0 (modified)
wet_opensearch-0.1

Textpattern CMS

Textpattern CMS support forum

#76 2015-02-21 00:52:35

Re: Edit error: Sorry, the form could not be submitted. Please try again.

#77 2015-02-21 00:55:12

Re: Edit error: Sorry, the form could not be submitted. Please try again.

Bloke wrote #288471:

#78 2015-02-21 00:55:47

Re: Edit error: Sorry, the form could not be submitted. Please try again.

Els wrote #288472:

#79 2015-02-21 00:57:52

Re: Edit error: Sorry, the form could not be submitted. Please try again.

Els wrote #288475:

#80 2015-02-21 00:59:18

Re: Edit error: Sorry, the form could not be submitted. Please try again.

#81 2015-02-21 01:01:25

Re: Edit error: Sorry, the form could not be submitted. Please try again.

Els wrote #288478:

#82 2015-02-21 01:03:59

Re: Edit error: Sorry, the form could not be submitted. Please try again.

#83 2015-02-21 01:07:01

Re: Edit error: Sorry, the form could not be submitted. Please try again.

Els wrote #288480:

#84 2015-02-21 01:09:19

Re: Edit error: Sorry, the form could not be submitted. Please try again.

#85 2015-03-02 09:44:27

Re: Edit error: Sorry, the form could not be submitted. Please try again.

#86 2015-03-02 09:59:41

Re: Edit error: Sorry, the form could not be submitted. Please try again.

kees-b wrote #288684:

#87 2016-01-15 18:08:01

Re: Edit error: Sorry, the form could not be submitted. Please try again.

#88 2016-04-12 14:35:38

Re: Edit error: Sorry, the form could not be submitted. Please try again.

#89 2023-02-17 07:56:32

Re: Edit error: Sorry, the form could not be submitted. Please try again.

#90 2023-02-17 10:14:54

Re: Edit error: Sorry, the form could not be submitted. Please try again.

colak wrote #334651:

Board footer