[Testbot] Plone 5.0 - Python 2.7 - Build # 3071 - Still failing! - 0 failure(s)

jenkins at plone.org jenkins at plone.org
Fri Aug 22 23:49:18 UTC 2014


-------------------------------------------------------------------------------
Plone 5.0 - Python 2.7 - Build # 3071 - Still Failing!
-------------------------------------------------------------------------------

http://jenkins.plone.org/job/plone-5.0-python-2.7/3071/


-------------------------------------------------------------------------------
CHANGES
-------------------------------------------------------------------------------

Repository: plone.app.contentrules
Branch: refs/heads/master
Date: 2014-08-23T00:07:39+02:00
Author: Gil Forcada (gforcada) <gforcada at gnome.org>
Commit: https://github.com/plone/plone.app.contentrules/commit/bfd53ed149c239250b6766ca3625ec34d0c0469e

Whitespaces cleanup

Files changed:
M buildout.cfg
M plone/app/contentrules/browser/templates/manage-elements.pt
M plone/app/contentrules/tests/assignment.txt

diff --git a/buildout.cfg b/buildout.cfg
index 56c4146..4178c9e 100644
--- a/buildout.cfg
+++ b/buildout.cfg
@@ -4,4 +4,4 @@ package-name = plone.app.contentrules
 package-extras = [test]
 
 [versions]
-plone.app.contentrules = 
+plone.app.contentrules =
diff --git a/plone/app/contentrules/browser/templates/manage-elements.pt b/plone/app/contentrules/browser/templates/manage-elements.pt
index 4bd5250..e40b755 100644
--- a/plone/app/contentrules/browser/templates/manage-elements.pt
+++ b/plone/app/contentrules/browser/templates/manage-elements.pt
@@ -265,7 +265,7 @@
           <tal:noassignments condition="not:assignments">
             <div class="portalMessage warning" i18n:translate="">
               <strong>This rule is not assigned to any location</strong>
-            
+
             <tal:enabled condition="view/rule_enabled">
               <span i18n:translate="">
                 The rule is enabled but will perform nothing since it is not assigned anywhere.
@@ -273,7 +273,7 @@
                 Go to the folder where you want the rule to apply, or at the site root,
                 click on 'rule' tab, and then locally setup the rules.
               </span>
-              
+
               <form  tal:attributes="action view/view_url" method="post">
                 <span tal:replace="structure context/@@authenticator/authenticator"/>
                 <label i18n:translate="contentrules_assignments_shortcuts">Shortcuts:</label>
@@ -290,13 +290,13 @@
             <div class="portalMessage info" i18n:translate="description_contentrules_rule_assignments">
               <strong>Info</strong>
               <span>This rule is assigned to the following locations:
-      
-      
+
+
                 <tal:items repeat="assignment assignments">
-  
+
                         <a tal:attributes="href string:${assignment/url}/@@manage-content-rules"
                            tal:content="assignment/title" />
-        
+
                 </tal:items>
               </span>
             </div>
diff --git a/plone/app/contentrules/tests/assignment.txt b/plone/app/contentrules/tests/assignment.txt
index 95db1d2..859b795 100644
--- a/plone/app/contentrules/tests/assignment.txt
+++ b/plone/app/contentrules/tests/assignment.txt
@@ -16,7 +16,7 @@ Setup
 
 
 Let's visit the control panel and add two content rules. They will be assigned
-at the root of the site. 
+at the root of the site.
 
 First, we add a rule with a triggering event of `Workflow state changed`:
 
@@ -74,7 +74,7 @@ A second rule will be added to notify users when a content is added.
   >>> browser.getControl('Add', index=3).click()
   >>> ctrl = browser.getControl(name='form.message')
   >>> ctrl.value = 'Content added'
-  >>> browser.getControl('Save').click()  
+  >>> browser.getControl('Save').click()
 
 
 We're done with setting up content rules.  We need to now apply them




-------------------------------------------------------------------------------
-------------- next part --------------
A non-text attachment was scrubbed...
Name: CHANGES.log
Type: application/octet-stream
Size: 3300 bytes
Desc: not available
URL: <http://lists.plone.org/pipermail/plone-testbot/attachments/20140822/d173c5c3/attachment-0002.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: build.log
Type: application/octet-stream
Size: 93137 bytes
Desc: not available
URL: <http://lists.plone.org/pipermail/plone-testbot/attachments/20140822/d173c5c3/attachment-0003.obj>


More information about the Testbot mailing list