Silva

Silva shouldn't allow broken ghosts to be published

Bug #101601 reported by Martijn Faassen
4
Affects Status Importance Assigned to Milestone
Silva
Confirmed
Low
Sylvain Viollon
Silva 3.1.0

Bug Description

Need some more information about this issue. Is this new in 1.5?

Revision history for this message
Martijn Faassen (faassen) wrote :

Doesn't appear to be a new issue, not tackling for Silva-1.5

Andy Altepeter (aaltepet)
Changed in silva:
assignee: faassen → aaltepet
Revision history for this message
Andy Altepeter (aaltepet) wrote :

I think fixing this would involve changing the IPublishable, 'is_ok_to_publish()' or something. If the versionedcontent object isn't OK to publish (e.g. a broken ghost), then this is false, otherwise it's true.

The publishing machinery would need to be updated to take this new api call into account.

Changed in silva:
assignee: aaltepet → kitblake
Revision history for this message
Kit Blake (kitblake) wrote :

If we fix this the solution must allow batch publishing actions to complete. If someone selects 20 vcontent objects and clicks "publish", and one of them is a broken ghost, the 19 others must get published. The feedback message should contain a note, as it does now for objects that couldn't be published, notifying the user of the problems. Hopefully we can actually say why, e.g. "...object14 is a broken ghost..."

Changed in silva:
assignee: kitblake → aaltepet
Sylvain Viollon (thefunny)
Changed in silva:
assignee: Andy Altepeter (aaltepet) → Sylvain Viollon (thefunny)
importance: Medium → Low
milestone: none → 3.0.2
Kit Blake (kitblake)
Changed in silva:
milestone: 3.0.2 → 3.1.0
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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