ctools-buildscripts: Firefox does not display question/answer content in editor while in Edit Question mode. Mneme's TinyMCE upgrade.

Description

Editing either a new or existing question in Test Center (Mneme) will show blank text fields if you are using the Firefox browser. Sometimes the text of an existing question will show for a fraction of a second before disappearing. The TinyMCE editor is actually accepting text input but will not display it to the user. In my testing, I was able to blindly type in text for the question and the answer; my work did not show in FF during creation and after saving, but accessing the saved question in Edit Mode in Chrome and Safari showed the content that I'd typed and saved in FF.

Mneme users using Firefox can see the questions, answers, and take an assessment, so this issue does not generally appear to impair the creation, taking, or grading of assessments but instructors using Firefox will not be able to create or edit questions. Other browsers tested (Chrome and Safari) function as expected with Test Center.

To replicate:
1) Select the Question Pools link in Test Center
2) Select either an existing question pool or create a new pool
3) Select Add Question
4) Click in theTinyMCE text box (either question or answer text box) and type in some text; the typed characters will not display in the selected fields in the Firefox browser either while editing or after saving.

Although I am unsure whether this issue is related, in light of last week's extended issues with Firefox subsequent to the ACE software upgrade, this issue should be addressed ASAP to mitigate PR damage.

Environment

Firefox 11.0

Activity

Savitha Prakash July 5, 2012 at 7:42 AM

Tested on firefox..

Chris Kretler June 13, 2012 at 10:28 AM

I am unable to recreate this on Windows or Linux using FF12. Perhaps it was related to a particular browser version.

Adam York May 17, 2012 at 2:05 PM

please ignore erroneous submission for GradeServiceGradebook23Impl.java. Meant for UMICH-535.

Beth Kirschner March 26, 2012 at 7:56 PM

For those that didn't see the private conversation, the new war is on the sakai repo.

http://source.sakaiproject.org/maven2/tiny_mce/tiny_mce-war/3.5b2/

Thanks for verifying!

On Thu, Mar 22, 2012 at 1:26 PM, Robert E. Long <relong@svsu.edu> wrote:
Thanks for all the help. We've successfully upgraded and tested the newest version of TinyMCE 3.5b2. All is well, AFAICT.

--Bob


Robert E. Long, MA
Lead Java Developer / Analyst
Educational Technology Instructor
Saginaw Valley State University
M.A., Instructional Technology
relong@svsu.edu
O: 989.964.2245

On Mar 22, 2012, at 11:15 AM, Matthew Jones wrote:

Thanks for the tip Glenn. I can bundle and put this war up on the source.sakaiproject maven repo if you were able to test it out, Rob.

-Matthew

On Thu, Mar 22, 2012 at 11:02 AM, Glenn R. Golden <ggolden22@mac.com> wrote:
Robert -

Kenwrick Chan at Hawaii has run into this as well. You can update your tiny by building up a new Tiny war with this version, and then deploying it to your production servers. There's a project in svn for this:

https://source.sakaiproject.org/contrib/etudes/tinymce/trunk/

There's a file in there with instructions - basically, you download tiny, move files from the download into this source, remove the readme, and build it with maven (1).

  • Glenn

Glenn R. Golden
Chief Architect, Etudes, Inc.
ggolden@etudes.org

On Mar 22, 2012, at 10:19 AM, Robert E. Long wrote:

All,

We just came across this bug today in Test Center (Mneme).

It appears that TinyMCE (version 3.4.1) editor is broken in Firefox 11. This is due to have duplicate TinyMCE themes on the same page. Source: http://www.concrete5.org/community/forums/customizing_c5/firefox-11-tinymce-issue-workaround-and-fix/

Apparently the only fix is to upgrade to TinyMCE v.3.5.b2… Has anyone done this yet? Will the Etudes team release a new war file for 3.5.b2?

Any comments or help would be appreciated.

Thanks,
Bob

Fixed

Details

Assignee

Reporter

Fix versions

Priority

Created March 26, 2012 at 7:04 AM
Updated July 5, 2012 at 7:42 AM
Resolved June 13, 2012 at 11:13 AM

Flag notifications