silva external sources actually depends on SilvaDocument

[Andy Altepeter]

If SES and SilvaDocument are both uninstalled, and SES is installed via service_extensions, the following error is raised:

Traceback (innermost last):
  Module ZPublisher.Publish, line 119, in publish
  Module ZPublisher.mapply, line 88, in mapply
  Module ZPublisher.Publish, line 42, in call_object
  Module Products.Silva.ExtensionService, line 54, in install
  Module Products.Silva.ExtensionRegistry, line 119, in install
  Module Products.SilvaExternalSources.install, line 13, in install
  Module Products.Silva.ExtensionService, line 79, in refresh
  Module Products.Silva.ExtensionService, line 67, in uninstall
  Module Products.Silva.ExtensionRegistry, line 122, in uninstall
  Module Products.SilvaDocument.install, line 57, in uninstall
  Module Products.SilvaDocument.install, line 121, in unconfigureXMLWidgets
  Module OFS.ObjectManager, line 523, in manage_delObjects
BadRequest: service_editor does not exist

So, SES should be configured to depend on SilvaDocument, and not Silva.

[Kit Blake (kitblake)]

What does this mean for other textual content types, like Silva Article, or others 'out there'?

[Andy Altepeter (aaltepet)]

The textual content types I'm familiar with (document, and the news ones -- article and agenda item) either are in SilvaDocument, or depend on it. I think any textual content type probably already depends on SilvaDocument, so making SES depend on SD also most likely won't be a problem.

I can't really imagine using SES without SilvaDocument, anyways.

[Kit Blake (kitblake)]

Ok, configure SES to depend on SilvaDocument.

[Andy Altepeter (aaltepet)]

ok, this change has been made in SES 1.5.1 (unrelease / trunk)