Skip to main content

Public

Project privacy set to public. By default, its content is available to everyone (authenticated or not). Please note that more restrictive permissions might exist on some items.

    •  
      request #8880 "Comment" field on every page suddenly became locked and unusable
    Actions
    Infos
    #8880
    Nicolas (nico0las)
    2017-02-03 17:16
    2016-02-18 16:15
    8984
    Details
    "Comment" field on every page suddenly became locked and unusable

    Hello,

     

    Since we upgraded to Tuleap 8.11 then we can very hardly write comment on the pages we edit. Users have full rights. The "comment" field is locked, we can't write anything inside.

    After a certain number of refresh and logout/login then the "comment" field can appear as normal (after 3-12 attempts). Unfortunately this is very critic for us as we need to use a lot of comments every day and very often.

     

    Is it a known bug ?

    Do you reproduce it ? Does someone could help us ?

     

    Thank you a lot

    Nicolas

    Trackers
    Empty
    Empty
    • [ ] enhancement
    • [ ] internal improvement
    Empty
    Stage
    Empty
    Closed
    2017-02-03
    Attachments
    Artifact links
    Empty
    By Nicolas (nico0las)
    (53 kB)
    tuleap_comment_KO.png
    Etape 1 - KO
    By Nicolas (nico0las)
    (66 kB)
    tuleap_comment_OK.png
    Etape 2 - after X Refresh
    By Nicolas (nico0las)
    (22 kB)
    tuleap_comment_KO_2.png
    Etape 3 - other KO
    By Nicolas (nico0las)
    (81 kB)
    log.png
    Log - Error
    By Nicolas (nico0las)
    (76 kB)
    tuleap-prod.png
    By Nicolas (nico0las)
    (69 kB)
    tuleap-prod-2.png
    bug on tuleap.net
    By Nicolas (nico0las)
    (94 kB)
    tuleap-prod-3.png
    scenario - tuleap.net
    By Yannis ROSSETTO (rossettoy)
    (154 kB)
    select_contenteditable.png
    By Nicolas (nico0las)
    (200 kB)
    Comment_KO.png
    impossible to write a comment
    By Nicolas (nico0las)
    (161 kB)
    Comment_OK.png
    possible to write a comment
    References
    Referencing request #8880

    Artifact Tracker v5

    rel #8869 8.13

    Git commit

    tuleap/tuleap/stable

    Merge 'gerrit #5275' into stable/master 3575757e7a
    User avatar Thomas Gerbet (tgerbet) , 2016-03-17 11:35
    request #8880 "Comment" field on every page suddenly became locked and unusable 33c399715e
    User avatar Yannis ROSSETTO (rossettoy) , 2016-03-17 11:04
    Merge 'gerrit #5281' into stable/master 556b0cd62f
    User avatar Thomas Gerbet (tgerbet) , 2016-03-17 14:29
    request #8880 "Comment" field on every page suddenly became locked and unusable b574bcb313
    User avatar Yannis ROSSETTO (rossettoy) , 2016-03-17 13:46

    Release

    release #122
    Referenced by request #8880

    Other

    gerrit #5275
    gerrit #5181
    Display settings

    Follow-ups

    User avatar
    Yannis ROSSETTO (rossettoy)2017-02-03 17:16
    • Status changed from Verified to Closed
    • Reported in version cleared values: 8.11
    • Close date set to 2017-02-03
    User avatar
    Thomas Gerbet (tgerbet)2016-03-17 14:34

    Fallback to the default text format has also been ported in the modal (for the planning v2 and kanban) with gerrit #5181 and integrated into Tuleap 8.12.99.59.

    User avatar
    Thomas Gerbet (tgerbet)2016-03-17 11:40

    The fallback to the default text format has been integrated into Tuleap 8.12.99.58.

    • Status changed from New to Verified
    User avatar
    Yannis ROSSETTO (rossettoy)2016-03-17 11:07

    Hello,

    As the issue is on CKEDITOR and we have to check what we are able to do, I do a patch to switch back by default into Text format. Only users that have set HTML as default format will have tracker textares in HTML by default.

    The patch is here: gerrit #5275

    User avatar
    Nicolas (nico0las)2016-03-14 22:30

    Hi all,

    I would like to update Tuleap when this bug will be solved, do you have any idea when the fix will be included into the packages ?

    Thank you,

    User avatar
    Manuel Vacelet (vaceletm)2016-03-04 15:52

    For reference, on stuck pages, ckeditor code is:

    <iframe src="" frameborder="0" class="cke_wysiwyg_frame cke_reset" title="Rich Text Editor, tracker_followup_comment_new" aria-describedby="cke_58" tabindex="0" allowtransparency="true" style="width: 958px; height: 100%;">
#document
<html>
<head></head>
<body></body>
</html>
</iframe>
    User avatar
    Patricia Carrasco (pcar)2016-02-29 16:32

    Hi Marc, yes thanks the workaround described below is working and we have advised our users.

    User avatar
    Marc TERRIER (mterrier)2016-02-29 16:27

    Hello Patricia,

    Did you try the workaround suggested by Yannis (text by default in your account, and switch manually to HTML)? Does it work for you?

    Best regards,

     

    User avatar
    Nicolas (nico0las)2016-02-25 16:23
    Thank you for the workaround this tip help for sure ! Please let me know when this bug will be fixed and we will quickly update our Tuleap version. Let me know also if I can do anything to help. Have a good day :-)
    User avatar
    Yannis ROSSETTO (rossettoy)2016-02-23 11:32

    As a workaround while we are debuging the issue, you can set text by default (in your account settings) for textarea in trackers and switch by hand to HTML (as done before Tuleap 8.10).

    User avatar
    Nicolas (nico0las)2016-02-23 10:30

    @rossettoy : which "div class : xxx" should I search for ? I see a lot of "div class" in the editor.

    Thank you
     

    User avatar
    Yannis ROSSETTO (rossettoy)2016-02-22 23:22

    Thanks for the output.

    On my side, I've tested on windows and linux on multiple tuleap instances, but I'm still not able to reproduce this.

    It seems that the body tag inside the editor is not loaded. Is it possible to open the div when the .cke_editable is not here and provide us its content ?

    In addition, can you provide us the content of the JS section of your "Network" tab in the console when you are note able to click on the editor ? I want to check if there is something wrong on javascript loading.

    User avatar
    Nicolas (nico0las)2016-02-22 20:06

    @rossettoy : it appears that :

    1) If we can edit the commentary field : we find the "cke_editable" term in the inspector of the page

    2) For the same page, if the commentary field is locked :  we can't find the "cke_editable" term in the inspector of the page

    Please see the attachements : Comment_KO.png & Comment_OK.png

    User avatar
    Nicolas (nico0las)2016-02-22 17:35

    @Yannis : I'm not sure to understand, do you mean that i need to use a tool called CKEDITOR (http://ckeditor.com/) ? What should i do after opening the console (F12) ?

    User avatar
    Yannis ROSSETTO (rossettoy)2016-02-22 17:09

    @nico0las when you encounter the bug, what is the value of the contenteditable class ?

    To check this, open your browser console (F12), select the CKEDITOR and check the value please.

     

    User avatar
    Nicolas (nico0las)2016-02-22 16:43

    Ok thank you. Just for information : is it possible to revert our last software version (8.11) to the previous working one (8.8) with keeping the actual database ? This is only "good to know" if we have some problem with solving this bug. Thanks.

    User avatar
    Manuel Vacelet (vaceletm)2016-02-22 15:58

    Well, for the time being it's not really reproduced, some of us just "hit" this bug but we don't have a reliable way to reproduce/understand (hence fix).

    I don't know when it will be fixed.

    User avatar
    Nicolas (nico0las)2016-02-22 15:55

    That's great we are glad that your team reproduced this bug, we are not alone anymore :-) what will be the next step ? do you have any idea of the estimated date of resolution ?

    User avatar
    Nicolas (nico0las)2016-02-22 13:05
    last edited by: Nicolas (nico0las) 2016-02-22 14:03

    Tuleap server : we cleaned caches as asked, as root

    Client (Windows 10 / Firefox 44 - Chrome 48 - Edge 20) : we cleaned caches of every client too

    Client (Windows 10 / Firefox 44 - Chrome 48 - Edge 20) : we still can't write text in the "comment" field (not always but very often)

     

    This prolem with commentaries never happened in our previous version of Tuleap (8.8) but appear since the last update to 8.11

    User avatar
    Nicolas (nico0las)2016-02-22 12:24

    I did a new test where I lost the use of "comment" field on this page (works same with our tuleap platform)

    see : tuleap-prod-3.png

    I am online now on internet only with IE 9 (i am away) so I will stop to test tuleap.net if this browser is not supported. Our Tuleap platform is accessed by computer with Windows 10 and last versions of Firefox / Chrome / IE (Edge).

    User avatar
    Manuel Vacelet (vaceletm)2016-02-22 12:19

    IE9 is no longer supported so your tests should focus on firefox.

    What is the OS version ?

    User avatar
    Nicolas (nico0las)2016-02-22 12:00
    last edited by: Nicolas (nico0las) 2016-02-22 12:04

    I am now on IE 9 (I know it's old :-)) but the same problem appeared with Firefox 44

    In 40-50% of the cases when I am on this page I can't write something in the "commentary" field. Icons are active, but I can't click in the field to write something. If I refresh the page, it may works

    User avatar
    Nicolas (nico0las)2016-02-22 11:20

    I did it. Server returned in green lines :

    info Invalidate Restler cache

    info Invalidate language cache

    info Invalidate JS combined cache

    info Invalidate WSDL

    info Invalidate Plugin hooks

     

    Then I came to this page to write you a comment, i logged in and i found the same problem (see attached file : tuleap-prod.png).

    I pressed F5 then it worked on the next loading.

    User avatar
    Manuel Vacelet (vaceletm)2016-02-22 10:17

    As root on the platform, could you run:

    • tuleap --clear-caches

    Then go on page and, in your browser Ctrl + shit + F5

    User avatar
    Manuel Vacelet (vaceletm)2016-02-19 09:45

    That's stange, it works perfectly here and on our other platforms, with 8.11.99.38.

    I suspect a JS issue, it here any Javascript error in console (F12) ?

    Could you try to flush your browser cache (Ctrl+shift+F5) ?

    What OS/browser are you using ?

    User avatar
    Manuel Vacelet (vaceletm)2016-02-18 17:29

    What is the exact version you are using?

    After a certain number of refresh and logout/login then the "comment" field can appear as normal (after 3-12 attempts).

    Can you provide print screen of "when it works" and "when it doesnt work" ?

    User avatar
    Nicolas (nico0las)2016-02-18 16:17
    • Original Submission
      Something went wrong, the follow up content couldn't be loaded
      Only formatting have been changed, you should switch to markup to see the changes