[Testbot] Plone 5.0 - Python 2.7 - Build # 3070 - Regression! - 0 failure(s)
jenkins at plone.org
jenkins at plone.org
Fri Aug 22 23:43:23 UTC 2014
-------------------------------------------------------------------------------
Plone 5.0 - Python 2.7 - Build # 3070 - Failure!
-------------------------------------------------------------------------------
http://jenkins.plone.org/job/plone-5.0-python-2.7/3070/
-------------------------------------------------------------------------------
CHANGES
-------------------------------------------------------------------------------
Repository: plone.app.content
Branch: refs/heads/master
Date: 2014-08-23T00:06:09+02:00
Author: Gil Forcada (gforcada) <gforcada at gnome.org>
Commit: https://github.com/plone/plone.app.content/commit/69e1eae7f710239d9a21bdf20817bafa4fb92ef0
Whitespaces cleanup
Files changed:
M README.rst
M plone/app/content/basecontent.txt
M plone/app/content/browser/folderfactories.pt
M plone/app/content/browser/full_review_list.pt
M plone/app/content/browser/table.txt
M plone/app/content/browser/templates/content_status_history.pt
M plone/app/content/namechooser.txt
diff --git a/README.rst b/README.rst
index 83f3309..99d1675 100644
--- a/README.rst
+++ b/README.rst
@@ -1,7 +1,7 @@
Introduction
============
-plone.app.content contains various views for Plone, such as
+plone.app.content contains various views for Plone, such as
folder_contents, as well as general content infrastructure, such as
base classes and name choosers.
diff --git a/plone/app/content/basecontent.txt b/plone/app/content/basecontent.txt
index b47628b..03f618c 100644
--- a/plone/app/content/basecontent.txt
+++ b/plone/app/content/basecontent.txt
@@ -8,7 +8,7 @@ some simple examples of using them.
>>> from plone.app.content import container, item
Let us define two fictional types, a folderish one and a non-folderish one.
-We should define factories for these types as well. Factories can be
+We should define factories for these types as well. Factories can be
referenced from CMF FTI's, and also from <browser:addMenuItem /> directives.
With an appropriate add view (e.g. using formlib's AddForm) this will be
available from Plone's "add item" menu. Factories are registered as named
@@ -39,7 +39,7 @@ Then, an item:
>>> class IMyType(Interface):
... title = schema.TextLine(title=u"My title")
... description = schema.TextLine(title=u"My other title")
-
+
>>> class MyType(item.Item):
... implements(IMyType)
... portal_type = "My type"
@@ -54,21 +54,21 @@ We can now create the items.
>>> container.id
'my-container'
>>> container.title = "A sample container"
-
+
We need to add it to an object manager for acquisition to do its magic.
>>> newid = self.portal._setObject(container.id, container)
>>> container = getattr(self.portal, newid)
-
+
We will add the item directly to the container later.
-
+
>>> item = itemFactory("my-item")
>>> item.id
'my-item'
>>> item.title = "A non-folderish item"
-
+
Note that both the container type and the item type are contentish. This is
-important, because CMF provides event handlers that automatically index
+important, because CMF provides event handlers that automatically index
objects that are IContentish.
>>> from Products.CMFCore.interfaces import IContentish
@@ -76,9 +76,9 @@ objects that are IContentish.
True
>>> IContentish.providedBy(item)
True
-
+
Only the container is folderish, though:
-
+
>>> from Products.CMFCore.interfaces import IFolderish
>>> bool(container.isPrincipiaFolderish)
True
@@ -88,7 +88,7 @@ Only the container is folderish, though:
False
>>> IFolderish.providedBy(item)
False
-
+
We can use the more natural Zope3-style container API, or the traditional
ObjectManager one.
@@ -104,7 +104,7 @@ ObjectManager one.
'my-item'
>>> 'my-item' in container
True
-
+
Both pieces of content should have been cataloged.
>>> container = self.portal['my-container']
@@ -116,20 +116,20 @@ Both pieces of content should have been cataloged.
['A sample container']
>>> [b.Title for b in catalog(getId = 'my-item')]
['A non-folderish item']
-
+
If we modify an object and trigger a modified event, it should be updated.
>>> from zope.lifecycleevent import ObjectModifiedEvent
>>> from zope.event import notify
-
+
>>> container.title = "Updated title"
>>> item.title = "Also updated title"
-
+
>>> [b.Title for b in catalog(getId = 'my-container')]
['A sample container']
>>> [b.Title for b in catalog(getId = 'my-item')]
['A non-folderish item']
-
+
>>> notify(ObjectModifiedEvent(container))
>>> notify(ObjectModifiedEvent(item))
diff --git a/plone/app/content/browser/folderfactories.pt b/plone/app/content/browser/folderfactories.pt
index a5399db..f8e4c90 100644
--- a/plone/app/content/browser/folderfactories.pt
+++ b/plone/app/content/browser/folderfactories.pt
@@ -37,7 +37,7 @@
<metal:addlist define-macro="addlist">
- <form name="quickAdd" method="post"
+ <form name="quickAdd" method="post"
tal:attributes="action string:${context/absolute_url}/@@folder_factories">
<dl>
diff --git a/plone/app/content/browser/full_review_list.pt b/plone/app/content/browser/full_review_list.pt
index 9351b3e..25549e7 100644
--- a/plone/app/content/browser/full_review_list.pt
+++ b/plone/app/content/browser/full_review_list.pt
@@ -13,7 +13,7 @@
<metal:main fill-slot="main">
<h1 class="documentFirstHeading"
i18n:translate="heading_full_review_list">Full review list:</h1>
-
+
<div id="content-core">
<form name="worklistForm"
method="post"
@@ -25,7 +25,7 @@
<input tal:replace="structure context/@@authenticator/authenticator" />
</form>
</div>
-
+
</metal:main>
</body>
</html>
diff --git a/plone/app/content/browser/table.txt b/plone/app/content/browser/table.txt
index 0b9aa00..f333787 100644
--- a/plone/app/content/browser/table.txt
+++ b/plone/app/content/browser/table.txt
@@ -12,7 +12,7 @@ A table can be parameterized at creation time.
>>> view_url = 'http://plone/view'
>>> base_url = 'http://plone'
>>> table = Table(request={}, base_url=base_url, view_url=view_url,
- ... items=[], show_sort_column=False, buttons=[])
+ ... items=[], show_sort_column=False, buttons=[])
The most important argument is items. This must provide a list of dictionaries
because the table will add more information to them for rendering.
@@ -127,7 +127,7 @@ The same goes for selecting the screen and the whole batch.
>>> table.selectall_url
'http://plone/view?pagenumber=1&pagesize=20&select=all'
-
+
A template may want to display only one of these urls at the same time.
Therefore the table has a boolean property to query wheter or not to show the
select all option. The display of this depends on wheter the whole batch is
diff --git a/plone/app/content/browser/templates/content_status_history.pt b/plone/app/content/browser/templates/content_status_history.pt
index 3e9e3b6..89f9157 100644
--- a/plone/app/content/browser/templates/content_status_history.pt
+++ b/plone/app/content/browser/templates/content_status_history.pt
@@ -65,7 +65,7 @@
tal:attributes="action string:${context/@@plone_context_state/object_url}/${view/__name__}"
tal:condition="not:python:paths and not batch">
- <div class="field" tal:condition="batch"
+ <div class="field" tal:condition="batch"
tal:define="error errors/paths | nothing;"
tal:attributes="class python:error and 'field error' or 'field'">
<label i18n:translate="label_affected_content">Affected content</label>
@@ -266,7 +266,7 @@
</div>
</div>
</div>
- </div>
+ </div>
<div class="field">
<label for="comment"
diff --git a/plone/app/content/namechooser.txt b/plone/app/content/namechooser.txt
index 6b56c4f..43df6e0 100644
--- a/plone/app/content/namechooser.txt
+++ b/plone/app/content/namechooser.txt
@@ -3,7 +3,7 @@ Normalizing name chooser
========================
plone.app.content provides a namechooser for IFolderish objects that can
-pick a normalized name based on the object's id, title, portal type or class,
+pick a normalized name based on the object's id, title, portal type or class,
and can provide uniqueness.
Let's create some dummy content.
@@ -11,7 +11,7 @@ Let's create some dummy content.
>>> from plone.app.content import container, item
>>> from zope.interface import implements, Interface, alsoProvides
>>> from zope import schema
-
+
>>> class IMyContainer(Interface):
... title = schema.TextLine(title=u"My title")
... description = schema.TextLine(title=u"My other title")
@@ -25,7 +25,7 @@ Let's create some dummy content.
>>> class IMyType(Interface):
... title = schema.TextLine(title=u"My title")
... description = schema.TextLine(title=u"My other title")
-
+
>>> class MyType(item.Item):
... implements(IMyType)
... portal_type = "My portal type"
@@ -63,7 +63,7 @@ an object, if it has one.
>>> item = MyType("my-item")
>>> item.id
'my-item'
-
+
>>> name = chooser.chooseName(None, item)
>>> name
'my-item'
@@ -128,7 +128,7 @@ back on the class name.
>>> delattr(item, 'id')
>>> chooser.chooseName(None, item)
'my-portal-type'
-
+
>>> delattr(MyType, 'portal_type')
>>> chooser.chooseName(None, item)
'mytype'
@@ -140,7 +140,7 @@ An object can also gain a name based on its title. To do so, the object
must implement or be adaptable to INameFromTitle.
>>> from plone.app.content.interfaces import INameFromTitle
-
+
>>> class TitleAdapter(object):
... implements(INameFromTitle)
... adapts(IMyType)
@@ -150,7 +150,7 @@ must implement or be adaptable to INameFromTitle.
... def title(self):
... return self.context.title
>>> provideAdapter(TitleAdapter)
-
+
>>> item = MyType("some-id")
>>> item.title = u"My funky item"
-------------------------------------------------------------------------------
-------------- next part --------------
A non-text attachment was scrubbed...
Name: CHANGES.log
Type: application/octet-stream
Size: 9959 bytes
Desc: not available
URL: <http://lists.plone.org/pipermail/plone-testbot/attachments/20140822/3774004f/attachment-0002.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: build.log
Type: application/octet-stream
Size: 92685 bytes
Desc: not available
URL: <http://lists.plone.org/pipermail/plone-testbot/attachments/20140822/3774004f/attachment-0003.obj>
More information about the Testbot
mailing list