Problem/Motivation

When I try to add a comment to a task I often get redirected to comment/reply/# and the comment isn't saved. I've stepped through several validation functions, but I can't seem to find anything causing it. Nothing in watchdog or php log.

Steps to reproduce

  1. Click on a task in the issue tracker.
  2. Add some text to the body.
  3. Save the comment.
  4. Page redirects to comment/reply/# and nothing is saved.
CommentFileSizeAuthor
comment_redirect.mp43.57 MBTim Bozeman
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Tim Bozeman created an issue. See original summary.

Tim Bozeman’s picture

Issue summary: View changes
Tim Bozeman’s picture

.

Tim Bozeman’s picture

Issue summary: View changes

Updated issue summary. I don't think it's wysiwyg any more. Creating a task also gets redirected to the node/add page with no save.

Clicking the browser back button and resaving eventually works, but usually messes up the images.

dpoletto’s picture

On a OA 2.43 stock site (I'm using for testing) I'm not able to reproduce although, with respect to your steps, I did:

  1. Add (Hovering "+" and selecting the only one action available "Create Task") a new Task on a Task Section.
  2. Fill the newly created Task with relevant information (Task Title, Body and Information) and Publish it.
  3. Task is correctly created.
  4. Update the newly created Task by updating its information and/or by adding a new comment to it and Save -> Task information is correctly updated and/or a comment is added (this action could be done by owner/creator or by another user, it doesn't matter).

If, while updating the Task, I also add - as you did - an image file through the WYSIWYG toolbar's "Add media" mini button, Submit and Save it all looks good -> the comment shows up with the image file uploaded with the size/style chosen. Adding an image file through the WYSIWYG toolbar during task's first creation doesn't change the final expected result: Task is correctly created.

So...could it be something specific to (your) OA 2.44? Was it updated from a pre-2.40 or was it a new fresh install of OA 2.44?

Tim Bozeman’s picture

Component: Code » Miscellaneous
Assigned: Unassigned » Tim Bozeman
Category: Bug report » Support request
Priority: Normal » Minor
Status: Active » Closed (cannot reproduce)

Thank you very much for your time trying to reproduce this @dpoletto! I'm sorry. This was a case of operator error. I think my varnish configuration was the culprit.