Silva shouldn't allow broken ghosts to be published

Bug #101601 reported by Martijn Faassen on 2006-01-20
Affects Status Importance Assigned to Milestone
Sylvain Viollon

Bug Description

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

Martijn Faassen (faassen) wrote :

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

Changed in silva:
assignee: faassen → aaltepet
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
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
Changed in silva:
assignee: Andy Altepeter (aaltepet) → Sylvain Viollon (thefunny)
importance: Medium → Low
milestone: none → 3.0.2
Kit Blake (kitblake) on 2013-03-27
Changed in silva:
milestone: 3.0.2 → 3.1.0
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers