Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
erp5
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Kristopher Ruzic
erp5
Commits
5134943e
Commit
5134943e
authored
Jan 14, 2014
by
Aurel
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
implement RFC-5861 in CachingPolicyManager
parent
b5735cfc
Changes
3
Expand all
Hide whitespace changes
Inline
Side-by-side
Showing
3 changed files
with
716 additions
and
0 deletions
+716
-0
product/ERP5Type/ZopePatch.py
product/ERP5Type/ZopePatch.py
+1
-0
product/ERP5Type/dtml/cachingPolicies.dtml
product/ERP5Type/dtml/cachingPolicies.dtml
+396
-0
product/ERP5Type/patches/CachingPolicyManager.py
product/ERP5Type/patches/CachingPolicyManager.py
+319
-0
No files found.
product/ERP5Type/ZopePatch.py
View file @
5134943e
...
...
@@ -76,6 +76,7 @@ from Products.ERP5Type.patches import _transaction
from
Products.ERP5Type.patches
import
default_zpublisher_encoding
from
Products.ERP5Type.patches
import
DCWorkflowGraph
from
Products.ERP5Type.patches
import
AceEditorZMI
from
Products.ERP5Type.patches
import
CachingPolicyManager
# These symbols are required for backward compatibility
from
Products.ERP5Type.patches.PropertyManager
import
ERP5PropertyManager
...
...
product/ERP5Type/dtml/cachingPolicies.dtml
0 → 100644
View file @
5134943e
This diff is collapsed.
Click to expand it.
product/ERP5Type/patches/CachingPolicyManager.py
0 → 100644
View file @
5134943e
This diff is collapsed.
Click to expand it.
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment