what happens when the collection field doesn't match the collection directory that the accomplishment is in?

Bug #1024080 reported by Matt Fischer
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu Accomplishments Daemon
Invalid
Low
Unassigned

Bug Description

It is possible to have an accomplishment in, for example, the collection "foo" who has the field collection set to "bar".

For example:

/usr/share/accomplishments/accomplishments/foo/test.accomplishment looks like this

title = "Bar Accomp"
collection = bar

What should we do in this scenario?

Revision history for this message
Jono Bacon (jonobacon) wrote :

If this occurs I think the daemon should ignore the accomplishment.

Changed in ubuntu-accomplishments-daemon:
milestone: none → 0.3
status: New → Confirmed
importance: Undecided → Low
Revision history for this message
Rafał Cieślak (rafalcieslak256) wrote :

Currently, this field is ignored. When loading such accomplishment to accomplishments database, the 'collection' field will be overwritten with "foo", e.g. the real collection this accomplishment file belongs to.

Revision history for this message
Jono Bacon (jonobacon) wrote :

Thanks, Rafal. Because of this I am marking this bug as Invalid. Re-open if you feel it needs more focus. :-)

Changed in ubuntu-accomplishments-daemon:
status: Confirmed → Invalid
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.