git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@43432 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@43431 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@43430 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@43429 20353a03-c40f-0410-a6d1-a30d3c3de9de

 - cleanup non used variables


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@43428 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@43427 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@43426 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@43425 20353a03-c40f-0410-a6d1-a30d3c3de9de

Use new property sheet. Change the constraint type to test registration and override of message because 
the old is not migrated yet


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@43424 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@43423 20353a03-c40f-0410-a6d1-a30d3c3de9de

The domain generator script uses short cache, so it is common to not the list immediated reloaded. Clear cache before check again.

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@43422 20353a03-c40f-0410-a6d1-a30d3c3de9de

Maybe this is enough to fix testCacheTool.test_06_CheckCacheExpiration

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@43421 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@43420 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@43419 20353a03-c40f-0410-a6d1-a30d3c3de9de

revert r42711 (erp5_jquery is used and can be used in other skins (not only "View"). Such a case is any ERP5 Web Site using jQuery). the biggest reason is that we don't use SkinTemplateItem but use PathTemplateItem in this business template, thus 'erp5_jquery' is not registered at any skin. now erp5_jquery business template's behaviour is exactly same as erp5_xhtml_style business template's behaviour where 'erp5_xhtml_style' is only registered in View skin.


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@43418 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@43417 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@43415 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@43414 20353a03-c40f-0410-a6d1-a30d3c3de9de

Note: It is acceptable to merge duplicates of same property, it was
working like this before.


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@43413 20353a03-c40f-0410-a6d1-a30d3c3de9de

in some cases like Web Page content /../ can be contained in image URL which will break restrictedTraverse calls, our best guess is to remove it.

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@43412 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@43411 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@43410 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@43409 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@43408 20353a03-c40f-0410-a6d1-a30d3c3de9de

   property ids


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@43407 20353a03-c40f-0410-a6d1-a30d3c3de9de

- create specific form to contain field used by budget reports
- use above field in reports

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@43406 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@43405 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@43404 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@43403 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@43402 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@43401 20353a03-c40f-0410-a6d1-a30d3c3de9de

The 2nd test failed because of a side effect of 1st test.
1st test failed because it (purposely) causes a failure when committing
transaction, and this is remembered inside the transaction itself, and it
then always refuses commit. Aborting is the normal execution path after an
error in commit, so do it.


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@43400 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@43399 20353a03-c40f-0410-a6d1-a30d3c3de9de

anymore as core property sheets will be stored in erp5_core bt5
directly and portal_property_sheets.xml is used for bootstrap



git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@43398 20353a03-c40f-0410-a6d1-a30d3c3de9de

"except: raise" is a no-pop.
"try:... except: self.fail()" just hides the actual exception.


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@43397 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@43396 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@43395 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@43394 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@43388 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@43382 20353a03-c40f-0410-a6d1-a30d3c3de9de