mahara-contributors team mailing list archive
-
mahara-contributors team
-
Mailing list archive
-
Message #16390
[Bug 1261610] A change has been merged
Reviewed: https://reviews.mahara.org/2928
Committed: http://gitorious.org/mahara/mahara/commit/8986b3313319c126a67e4f951cbe5b5a92e97c0d
Submitter: Aaron Wells (aaronw@xxxxxxxxxxxxxxx)
Branch: master
commit 8986b3313319c126a67e4f951cbe5b5a92e97c0d
Author: Aaron Wells <aaronw@xxxxxxxxxxxxxxx>
Date: Wed Jan 15 12:31:22 2014 +1300
Don't run the JSDetector for CLI scripts.
Bug 1261610
Change-Id: I9f28525571da10ccf62b75f0c2134db28bf51073
--
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara Contributors -- please ask on #mahara-dev or mahara.org forum before editing or unsubscribing it!
https://bugs.launchpad.net/bugs/1261610
Title:
JSDetector adds output to command-line scripts
Status in Mahara ePortfolio:
Fix Committed
Bug description:
In Mahara 1.9dev, every time I run the command-line installer, I see
this at the start of the output:
<form name="jsdetector_form" id="jsdetector_form" method="post">
<input name="javascriptenabled" type="hidden" value="true" />
<script type="text/javascript">
document.jsdetector_form.submit();
</script>
</form>[INF] d4 (admin/cli/install.php:68) Installing Mahara
I suspect this is from the JSDetector class that we added. We should
disable that, because it's not needed when you're running at the
command-line.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1261610/+subscriptions
References