Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
Re: Edit error: Sorry, the form could not be submitted. Please try again.
This is a plugin problem: you’ll need to identify the culprit(s) and hack them not to misbehave. You can narrow down your suspects by concentrating on ones that interact with the write tab.
I manually hacked bot_wtc and mck_article_image to make them behave themselves.
I found a solution that worked for me here Thanks Jukka
Identify the culprit plugins
- disable 1/2 your plugins and see if the error occurs:
- If YES, the culprit(s) is/are in the active batch
- If NO, the culprit(s) is/are in the disabled batch
- repeat the above on the batch with the culprits.
Hack the plugin(s)
- locate the callbacks for functions that look like this
register_callback('my_function_name', 'article'); - replace them with
register_callback('my_function_name, 'admin_side', 'head_end'); - locate the functions that start with:
function my_function_name (){... - insert inside the first “{” right after the code below:
global $event;
if($event !== 'article') {return;}
Alerts be gone.
Offline
Re: Edit error: Sorry, the form could not be submitted. Please try again.
etc wrote:
Weird that it happens only on article save.
Yes, and even weirder is that it happens only with edits, not with the initial article save.
Try to enable response body logging in Firefox web console
How and were do I do that? Do you mean Tools | Webdeveloper or Firebug?
Offline
Re: Edit error: Sorry, the form could not be submitted. Please try again.
mrdale wrote:
This is a plugin problem
Hi Dale,
But nothing changed before and after the popups started to appear. I will check them anyhow this weekend when sitetraffic is low(er).
Offline
Re: Edit error: Sorry, the form could not be submitted. Please try again.
etc wrote:
Try to enable response body logging in Firefox web console.
Looked around with Firebug Console | Warnings
This warning is displayed when the article is edited:
Use of attributes' specified attribute is deprecated. It always returns true.
[Break On This Error] ...ction(a,b){var c=b[0],e=b[1],g;f.isFunction(c)?i[a](function(){g=c.apply(this,ar... jquery.js (line 2)
Offline
Re: Edit error: Sorry, the form could not be submitted. Please try again.
what are your plugins?
Offline
Re: Edit error: Sorry, the form could not be submitted. Please try again.
mrdale wrote:
what are your plugins?
adi_menu
arc_youtube
ob1_pagination
pap_contact_cleaner
rah_comment_spam
rah_custom_feed
rss_admin_db_manager
rss_auto_excerpt
rvm_maintenance
smd_lately
smd_query
smd_where_used
tru_tags
wet_commentmagic
wet_haystack
wet_recent_comments
zem_contact_lang
zem_contact_reborn
Offline
Re: Edit error: Sorry, the form could not be submitted. Please try again.
kees-b wrote:
How and were do I do that? Do you mean Tools | Webdeveloper or Firebug?
Firefox own Web developer/web console, then right click inside the console and enable “Log request and response bodies”. Save an article, you should then see a POST request in the console. Click on it and check if the response body looks ok.
Online
Re: Edit error: Sorry, the form could not be submitted. Please try again.
etc wrote:
Firefox own Web developer/web console, then right click inside the console and enable “Log request and response bodies”. Save an article, you should then see a POST request in the console. Click on it and check if the response body looks ok.
Thanks! This is logged when the article is saved:
[21:59:33.678] Use of attributes’ specified attribute is deprecated. It always returns true. http://domain.nl/textpattern/jquery.js:2
[21:59:33.751] POST http://domain.nl/textpattern/index.php [HTTP/1.1 200 OK 82ms]
[21:59:33.752] GET http://domain.nl/textpattern/txp_img/spinner.gif [HTTP/1.1 304 Not Modified 31ms]
Same warning and nothing special. Should I look further?
Offline
Re: Edit error: Sorry, the form could not be submitted. Please try again.
Click on the POST link and look at the response body, you should see something like $(document).ready...
Online
Re: Edit error: Sorry, the form could not be submitted. Please try again.
etc wrote:
Click on the POST link and look at the response body, you should see something like
$(document).ready...
Indeed, it starts with:
$(document).ready(function() { $(“#messagepane”).html(“<span id=\“message\” class=\“success\”>Artikel geplaatst <a href=\”#close\” class=\“close\”>×</a></span>”); $(‘#message.success, #message.warning, #message.error’).fadeOut(‘fast’).fadeIn(‘fast’); });;
$(“[name=sLastMod]”).val(“1370635582”);
$(“[name=sPosted]”).val(“1370634184”);
$(“#keywords”).val(“”);
$(“#url-title”).val(“test”);
$(“#recent_group .recent”).replaceWith(“<ul class=\“recent plain-list\”>\n <li class=\“recent-article\”><a href=\”?event=article&step=edit&ID=558\”>test</a></li>\n
and continues with a lot of code…what should I look for?
Offline
Re: Edit error: Sorry, the form could not be submitted. Please try again.
That looks normal. Try to disable “Use admin-side plugins?” option in admin/preferences/advanced, and check if the popup is still there on save?
Online
Re: Edit error: Sorry, the form could not be submitted. Please try again.
etc wrote:
That looks normal. Try to disable “Use admin-side plugins?” option in admin/preferences/advanced, and check if the popup is still there on save?
It’s still there.
What actually wonders me most is that at the initial save no error appears but at a second (edit) save it does. This makes me think if there is a check by the textpattern.js script of the allready existing article content in the database. Weird but another hypothesis to check maybe?
-k
Last edited by kees-b (2013-06-08 06:49:58)
Offline