Hi and thanks for the detailed analysis and description! It will be valuable in fixing this problem for our next release.
Cheers Stefano Rago On 04/gen/2013, at 00:31, Elaborate Ruse <[email protected]> wrote: > Hi Stefano, > Thanks for your response. We have mostly resolved this problem. What we > saw is that the problem actually had to do with Trac's new auto preview > functionality. I don't think line numbers will line up perfectly in this > case, so I will attempt to describe the location where we found the issue. > > Looking at a http://<tracserver>/<contextRoot>/ticket/#### document, we > found that the callback function from the line > $("#propertyform").autoSubmit(...) was not processing the data returned from > the autoSubmit function properly. The callback function is apparently > intended to update various elements of the current page with elements scraped > from the returned preview page. However, the preview page returned by Agilo > (the parameter reply' in the callback function) is not formatted exactly the > same as the Trac JS function is expecting and the callback fails to find the > view_time hidden input field. > > When running the callback function, the line (~line 115 of mine, the line > under the comment "Update view time") does not find any results with the > filter "input[name='view_time']" because the actual input is several levels > down in the "items" hierarchy. It does not appear that the JQuery filter > function is recursive, thus the value for view_time is not populated and the > hidden input field for view_time is removed from the document (since it is > being replaced with nothing). > > If you look at Trac's ticket.html template, you see that the hidden input > for view_time is at the top level of the document (not including <html>). > Agilo uses a different template it seems (agilo_ticket_view.html among > others), and the way the document tree comes out, the view_time hidden input > is not inserted at the top level of the document (where it is expected by the > Trac JS function). Our somewhat hacky quick & dirty fix was to simply copy > the hidden input field from Trac's ticket.html template and insert it into > Agilo's agilo_ticket_view.html, etc. Of course, I recognize that the fix is > not perfect and we may come back with a cleaner fix, but hopefully the next > version of Agilo will have a better fix than ours in it! > > Thanks again. > > On Thursday, December 20, 2012 2:23:24 AM UTC-6, Stefano Rago wrote: > Hi, > On Dec 13, 2012, at 10:36 PM, Elaborate Ruse <[email protected]> wrote: > > > Hello all, > > We had Agilo 1.3.4 with Trac 0.11.4, and recently upgraded to Agilo > > 1.3.9 with Trac 1.0. Since the upgrade, the first few updates made to > > tickets for the day experience the error seen in the attached screenshot: > > "The ticket has been modified by someone else since you started." There > > are no new modifications, however. More specifically, users come in in the > > morning, open their browsers, and go to a ticket. They make an update, > > such as adding a comment, and attempt to save when they experience the > > error. They press save again and the error may occur one or two more > > times, but eventually the save goes through. This has happened for about > > the last four days. After seeing the issue in the morning, they do not see > > it again for the rest of the day. > > > > We have a number of different non-Agilo projects in this Trac > > environment, none of which are experiencing this issue. I did find this > > article regarding the XML-RPC plugin that saw a similar issue due to a > > change in Trac: http://trac-hacks.org/ticket/9921 . I have disabled all > > plugins in this environment except AdvancedTicketWorkflow, AccountManager, > > and Agilo. Does anyone have any idea how to fix this? Thank you! > > > > Thanks for reporting this problem. Can you please try and disable also the > AdvancedTicketWorkflow plugin and see if the problem is still there? > > Cheers > > > Stefano Rago > > > -- > Follow Agilo on Twitter: http://twitter.com/agilofortrac > Please support us by reviewing and voting on: > http://userstories.com/products/8-agilo-for-scrum > http://ohloh.net/p/agilo-trac > http://freshmeat.net/projects/agiloforscrum > > You have received this message because you are subscribed to > the "Agilo for Trac" Google Group. This group is focused on > supporting Agilo for Trac users and is moderated by > Agilo Software GmbH <http://www.agilosoftware.com>. > > To post to this group, send email to [email protected] > To unsubscribe from this group, send an email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/agilo -- Follow Agilo on Twitter: http://twitter.com/agilofortrac Please support us by reviewing and voting on: http://userstories.com/products/8-agilo-for-scrum http://ohloh.net/p/agilo-trac http://freshmeat.net/projects/agiloforscrum You have received this message because you are subscribed to the "Agilo for Trac" Google Group. This group is focused on supporting Agilo for Trac users and is moderated by Agilo Software GmbH <http://www.agilosoftware.com>. To post to this group, send email to [email protected] To unsubscribe from this group, send an email to [email protected] For more options, visit this group at http://groups.google.com/group/agilo
