Ticket #2203 (new feature)

Opened 9 years ago

Last modified 9 years ago

Persistent themes containers

Reported by: gracinet Owned by: gracinet
Priority: P2 Milestone: CPS 3.5.7
Component: CPSDesignerThemes Version: 3.5.0
Severity: normal Keywords: persistent theme

Description (last modified by gracinet) (diff)

This has been on the CPSDesignerThemes roadmap from the beginning. Currently themes are read from the file system only. This is simple and fast, but not so appropriate in some cases:

  1. Big ZEO clusters: the themes must then be carefully duplicated
  2. Publication farm: local managers should be able to edit their themes. This depends on #2202, of course.

In the persistent form, a theme should be a simple hierarchy of folders, image and file objects.

There should be a nice UI to upload a theme as a zip file, or fetch it from an online bank (Dotclear has such features, for instance). It could also be a case of restoring FTP support (most web designers are used to that)

Another implication is that a caching system for theme pages would be needed (lxml is so fast that this isn't currently needed). Actually, it should cache PageEngine objects with the URI rewriting already done (meaning that base_url must be in the cache keys) ; negociators would return a big deepcopy.

Finally, this cache should be tied to the themes container object.

Change History

comment:1 Changed 9 years ago by gracinet

  • Keywords persistent theme added
  • Description modified (diff)

Add note about cache.

Note: See TracTickets for help on using tickets.