Hybrid external source/asset that contains HTML content
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Silva |
Fix Released
|
Low
|
Guido Goldstein | ||
Bug Description
Unfortunately we see the a common situation where people are misusing code sources
to quickly put HTML content online. We can counter this by improving editors
(Epoz) and HTML importing tools (would be nice to have some Silva extension to
do that..), but this probably still leaves open the use case of the code source
misuse.
Two ways to solve this:
* allow escaped (or even namespaced..) HTML in the Silva Document schema in
a new element. Ugh, no.
* Make a new type of external source to allow this.
I think the external source way is the best way to go about this. This is an
external source where it makes sense to expose this in the SMI, though possibly
only to editors and up, not to authors (they can't change them or create them).
This source would contain HTML content that people can copy & paste into it
or upload into it. It can then be included into the page using the
external data reference. It doesn't allow any parameters.
We should make clear to the users that what they're doing is an Evil Hack and
that they lose a huge range of Silva benefits, such as part of content/layout
separation, loss of control by site manager, not possible to use Epoz, DocMa,
other tools doing stuff with Silva XML, for this stuff, etc.
| Marc Petitmermet (petitmermet) wrote | #1 |
| Martijn Faassen (faassen) wrote | #2 |
| Kit Blake (kitblake) wrote | #3 |
| Flynt (flyntle) wrote | #4 |
| Martijn Faassen (faassen) wrote | #5 |
| Kit Blake (kitblake) wrote | #6 |
| Changed in silva: | |
| status: | Confirmed → Fix Released |
We have a special use case for this: Professors like to export their old PowerPoint files as web page and
upload it into silva. I guess that this should be almost possible out of the box when using the ExtFile by
Stefan. But the flexibility of the configuration should be enhanced, e.g. a rewrite rule which supports deep
virtual hosting, files should be stored 1:1 in the file system as they are in silva, the EXTFILE_STATIC_PATH
environmental variable should be deep virtual host aware and be tight with silva files services and only be
valid in specified folders and not throughout the whole zope instance. I don't understand all configuration
options yet, maybe this is already possible. If yes:
Just an idea: a new type of silva static folder. When added it creates
1. a silva folder (without index;-) with the id "static" (this cannot be changed)
2. a silva files service within this folder with automatically created filesystem path (which is deep virtual
host aware)