Error message when resaving a current collection

Bug #1392140 reported by Jinelle Foley-Barnes
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mahara
Invalid
Undecided
Unassigned

Bug Description

Hi,

I am getting an error when resaving a current collection.

To replicate use:

Master
Firefox 33.0
PostgreSQL 9.3.5
PHP 5.5.9

The method:
Portfolio -> Collections -> Edit the current collection (img icon) -> Save.

Then if it replicated you will see a page full of error reports.

Thanks,

Jinelle

Tags: collections
description: updated
tags: added: collections
Revision history for this message
Kristina Hoeppner (kris-hoeppner) wrote :

Hi Jinelle,

Can you please be more specific about your steps and also post the error message? I have not been able to replicate the problem. My steps were:

1. Create a new collection and add some pages.
2. Go back into the "Edit" screen for the collection and re-save.
3. Go back into the "Page management" screen for the collection and re-save.
4. Copy the collection and save it.
5. Go back into the "Edit" screen for the collection and re-save.
6. Go back into the "Page management" screen for the collection and re-save.

There are no error messages anywhere that I can see.

Thanks
Kristina

Changed in mahara:
status: New → Incomplete
Revision history for this message
Jinelle Foley-Barnes (jinelleb) wrote :

Hi,

Yeah sure thing.

This bug report can be cancelled. It was present in commit 6c3e1cc70a401721efe6c8b6be3538138a5a97c5 but it's been fixed as of commit 6c3e1cc70a401721efe6c8b6be3538138a5a97c5

One of the commits inbetween must have fixed it inadvertently. I'm not sure which one.

Thank you,

Jinelle

Changed in mahara:
status: Incomplete → Fix Committed
Aaron Wells (u-aaronw)
Changed in mahara:
status: Fix Committed → Invalid
Revision history for this message
Aaron Wells (u-aaronw) wrote :

I ran a git bisect on this to see which commit fixed the problem, and it turns out this is a dupe of bug 1381811. The fix for that was pushed back on Oct 16. I think Jinelle saw this problem last week, because the testers are still using an older branch with the behat tests on it.

We need to see about getting those Behat tests merged into Gerrit so that they can use the latest code more easily!

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.