Last modified: 2013-07-02 12:36:28 UTC
Just getting a "Form submission error." that I can reproduce every time on a new installation of MW with this article. Is this an installation error / are there any diagnostics?
Hi Adam, unfortunately this report is not very useful because it does not describe the problem well. If you have time and can still reproduce the problem, please check https://www.mediawiki.org/wiki/How_to_report_a_bug , and http://www.mediawiki.org/wiki/Manual:How_to_debug for debugging. MW version information plus what "this article" means is also welcome. Thanks!
Apologies, We're running MW 1.20.0 on a Unix/Apache server with MySQL 5. After placing the include to the main file in our LocalSettings.php and running the update.php, the form is displaywed well on all forms. However on *every* article (typo in my origional post) I get the error aforementioned when clicking Post. I've tried changing the exception handling in ApiArticleFeedbackv5.php to $this->dieUsage( $e->getMessage(), 'inserterror' ); instead of $this->dieUsage( $this->msg( 'articlefeedbackv5-error-submit' ), 'inserterror' ); however am still getting the same message. The following settings prevent the display of the rating box completely when turned on, and I am unable to debug using these (hence my need to change the exception handling). error_reporting( -1 ); ini_set( 'display_errors', 1 );
Which git branch / version of ArticleFeedbackv5 is this about? Also see Special:Version
This was a get from the master branch. Version 5.1.0 (2e57588)
Some more information. The Ajax query to call the API returns a 500 Internal Server Error. From what I can see, the $.articleFeedbackv5.apiUrl variable is just set to "/api.php" - is this correct?
Upgrade to MW 1.21.1 Fixes this
master might not be compatible with 1.20. In general I'd recommend to run MW 1.20 with corresponding REL_1_20 branches of extensions, or run MW 1.21 with REL_1_21. Using master (=unstable) for extensions but a stable version of MediaWiki might create issues the more the codebases evolve... Anyway, glad that you found a way to fix the problem.
