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

Gocom · 2013-06-08 19:52:44

Is your site in testing or debugging mode?

kees-b · 2013-06-08 20:09:16

It is live but I checked it also in debug mode. No errors visible. Should I show response headers and diagnostics in debug mode?

Edit: checked that, no difference.

Is it thinkable that something in my hosting provider’s server settings is changed, although they said it is not, that could trigger the error?
This is the php info of the server in question.

Last edited by kees-b (2013-06-09 07:34:42)

kees-b · 2013-06-13 09:41:32

The problem I described above continued this whole week, but as out of the blue as it came it disappeared yesterday!

In the meantime I had mirrored the site to a new textpattern install to a subdomain debug.domain.nl on the same server. This new clean textpattern install did not show the error popup en everything worked as it should! But when I imported the database from the main site the error reappeared. I also checked this debug installation with an older database. This old database did not show the problem, and editing was normal, but without the green bar at the bottom at a successful edit. Maybe a related problem.

On the debug mirror with the most recent version of the site I retested all options, disabling all scripts, plugins etc. but the errors continued to pop up. In the meantime the site owner and magazine editor continued to add content to the main site and yesterday reported the problem was gone. (Thinking it was me who had solved it…).

So far so good, and everybody happy again!

But what I would like to find out now is what could have caused this problem. Does anybody have an idea what I could test at the debug subdomain (that still shows the edit error popup)?

Kees

CeBe · 2013-06-13 15:27:56

Did you install or update a plugin recently ?

I just ran into this error and it is clearly related to a plugin, but I still don’t know how. Investigations begin.

Edit: Ok for me, the error was mentioned in my error.log. I was due to a call to an undefined function.

Last edited by CeBe (2013-06-13 15:54:51)

Winstontaneous · 2014-03-12 05:07:53

Hello, I’m getting this error as well, using Textpattern 4.5.5 on my MAMP localhost on OSX 10.8.5. I cleared browser cache, logged out of TXP, signed off computer and back on.

This is a fresh install for local testing, no plugins. What’s extra weird:

most articles will show the error but save the additions when reloaded, when I check in Firefox Dev Tools there’s POST Request/Response, etc, but -
there’s one article that won’t let me save any additions, I just see the Request and a Sent Cookie (yum!), but nothing more.

I don’t see anything strange on Diagnostic tab, but this gets added to apache_error.log with each attempted save:

[Tue Mar 11 22:05:17 2014] [notice] child pid 6895 exit signal Segmentation fault (11)

Thanks for any help!

Last edited by Winstontaneous (2014-03-12 05:12:11)

Bloke · 2014-03-12 08:54:18

Winstontaneous wrote #279682:

Segmentation fault (11)

Very strange. Thanks for the detailed breakdown of what you’ve tried so far. A few more things you can look into:

Does the problem still show up if you change the Production Status? If the problem goes away in Live mode, or only shows up in Debugging mode then that might give us some clues.
What version of PHP are you using? Some versions (like 5.2.3) don’t like arrays to be passed as arguments directly into functions like implode(), and Textpattern still uses this construct in some places. More details of a similar segfault outcome, if not the same symptom as yours.
Anything in the various server error logs that might give any more info, such as a line number of where the problem is triggered? Do you get an error.log file produced in your textpattern folders at all that might help track this down?

I’m sure we can nail this, just need to think it through a bit and do some further sleuthing first so we know what we’re up against.

Winstontaneous · 2014-03-13 01:34:37

Hi Bloke, thanks for your response.

Happens in Live, Debug & Testing
I’m using PHP 5.5.3
No, my Bash shell “find” search didn’t reveal a file with that name in my TXP installation (which makes me realize I have to fix my vhosts.conf as I thought it was set to make logs per site). Also no record in php_error.log, or apache_error.log (aside from seg fault info I originally pasted). Mac system log has httpd error reports matching times this happens, but nothing I see has line numbers or references TXP files/folders.

Last edited by Winstontaneous (2014-03-13 01:36:53)

Bloke · 2014-03-13 09:08:09

Winstontaneous wrote #279706:

no record in php_error.log, or apache_error.log (aside from seg fault info I originally pasted). Mac system log has httpd error reports matching times this happens, but nothing I see has line numbers or references TXP files/folders.

Rats. Was hoping there might be some kind of trail we could latch onto. Is it just articles this happens on? Can you upload, edit and save images ok?

Since it might be AJAX related, is there anything given away in the browser’s inspector/Firebug if you reload the Write panel with the article being edited and hit Save? You should get a network call to the admin side with a bunch of parameters and a splurge of HTML thrown back to the console, but no errors. Anything untoward there might give us a clue.

By way of eliminating or implicating AJAX, you could also try adding this to the end of your config.php file:

define('AJAXALLY_CHALLENGED', true);

That switches off the AJAX interaction and reverts the admin side to old skool saves. If that improves things, at least we have a place to start hunting.

Winstontaneous · 2014-03-14 05:17:10

Let’s see:

Just articles (but not all). It happens on one all the time and only intermittently on others.
I can upload, edit, and save images (and post them in articles)
With Firefox dev tools open, successful saves return the like:
22:00:58.956 POST http://txptest/textpattern/index.php [HTTP/1.1 200 OK 29ms]
…and clicking on the link gives an “Inspect Network Request” box showing Request Headers, Cookies Sent, and Response Headers
Unsuccessful save attempt shows Request and Cookies sent but no Response
Adding AJAX bit to config.php didn’t do anything, still getting same edit error

Thanks again!

fiddle · 2014-03-19 01:55:52

Getting the same thing on a live site.. nothing has changed in about a month, then all of the sudden, editing a specific brings up this error..
If i delete something, goes through fine, only when I try to add text to the post does it happen..
Im confused..

kees-b · 2014-03-19 08:31:56

fiddle wrote #279819:

Getting the same thing on a live site.. nothing has changed in about a month, then all of the sudden, editing a specific brings up this error..

In my case it disappeared as sudden as it came! Never found any reason why it came and went… Though I have the impression that is had something to do with asynchronus ‘timing’ between javascript(s) and server. Making it in essence some sort of a fast time-out error. But correct me if I’m wrong.

fiddle · 2014-03-19 11:53:48

kees-b wrote #279823:

In my case it disappeared as sudden as it came! Never found any reason why it came and went… Though I have the impression that is had something to do with asynchronus ‘timing’ between javascript(s) and server. Making it in essence some sort of a fast time-out error. But correct me if I’m wrong.

I hope mine does too….
Its weird, its only on a specific post… So I thought, ok, let me delete it, rewrite it… Same thing, although I write edit different posts no problem, my textpattern has something against that specific content… lol

Gocom · 2014-03-19 12:22:10

fiddle wrote #279826:

I hope mine does too….
Its weird, its only on a specific post… So I thought, ok, let me delete it, rewrite it… Same thing, although I write edit different posts no problem, my textpattern has something against that specific content… lol

That sounds like your host’s, or server’s, HTTP packet filtering is blocking the submission. Its getting flagged due to that specific content.

fiddle · 2014-03-19 15:09:05

I dont know, dont think so..
It was something that has existed for awhile, was changing a file id on on a custom field.. Deleted the old one, was able to create an identical post, added content, saved, added a little more, saved, at some point stopped letting me.. But dosent happen anywhere else.. A little weird..
Noticed that when I the save button, I get a
File not found [/home/site/public_html/500.shtml]
Have a ticket open with my host, but Ive made the mistake to get a host that works off a ticket system, no telephone support… not happy… :(

Winstontaneous · 2014-03-27 05:01:02

Strangely this error (which I’ve only seen on my MAMP localhost) has gone away for me on the one persnickety post.

I had upgraded MAMP to latest version (with PHP 5.5.9) after I first experienced it, but that didn’t solve it directly. Didn’t play with TXP for a few days, now everything seems to be peachy. I did reboot (as opposed to just “sleeping”) the computer for probably the first time since the MAMP upgrade, maybe that did it.

Textpattern CMS

Textpattern CMS support forum

#31 2013-06-08 19:52:44

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

#32 2013-06-08 20:09:16

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

#33 2013-06-13 09:41:32

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

#34 2013-06-13 15:27:56

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

#35 2014-03-12 05:07:53

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

#36 2014-03-12 08:54:18

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

Winstontaneous wrote #279682:

#37 2014-03-13 01:34:37

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

#38 2014-03-13 09:08:09

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

Winstontaneous wrote #279706:

#39 2014-03-14 05:17:10

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

#40 2014-03-19 01:55:52

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

#41 2014-03-19 08:31:56

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

fiddle wrote #279819:

#42 2014-03-19 11:53:48

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

kees-b wrote #279823:

#43 2014-03-19 12:22:10

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

fiddle wrote #279826:

#44 2014-03-19 15:09:05

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

#45 2014-03-27 05:01:02

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

Board footer