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

template


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

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

Make ti possible that 2+ gadgets having same preference fields form work in ERP5 like one HTML form name space without conflicting each other (i.e. if two fields for 'field_my_title' exists they are transmitted as a list of two values, now no longer). Trick is to use unique form field prefixes for every gadget preference form.

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

different paths


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

using two different names, and not catching exceptions because of different module
paths


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

add an 'editable' parameter to render, to allow overriding a field's
editable property from the listbox renderer


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

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

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

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

* partially apply guidelines for field library

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

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

  * remove blank spaces
  * use urlencode to encode url parameters
  * password_request_dict is now private (renamed into _password_request_dict)
  * various optimisations
  * update test according code refactoring 


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

* login_form redirect on new form PasswordTool_viewEmailPassword

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

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

if removed workflow is still used somewhere else, make the default choice 'unchecked' and displays 'Removed but used'.


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

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

* remove all field not compatible with the guideline in Base_viewFieldLibrary
* use eavily the proxy rename dialog in order to make proxy fields using the
correct proxy in the field libray

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

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

# After the previous command finish (--start or --stop), call start.py flush, this prevents leave openoffice and xvfb running after stop.


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

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

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

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

Fulltext operator (MatchComparisonOperator) is special because it generates
ORDER BY expression, which is to be used only if caller tells catalog to sort
on the fulltext column. This code tests just that.


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

As the generated order-by expressions now (rightly) differ based on data, the
exception generated when detecting the difference must be postponed to when
expression is actualy used, as it might not be used.
Also, test that postponing effectively works, and demonstrate another way to
express the same condition, but which allows sorting.


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

* partially apply guidelines for field library

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

rename 'installed_bt' argument in preinstall() to 'installed_item' because it is not a business template object.


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

When full-text expression uses both boolean and natural mode, the expressions
should be merged, otherwise there would be 2 different definitions for the same
(fulltext) column alias in the SELECT or ORDER BY expressions. If any of the
full-text expressions contain boolean operators, the whole expression will be
executed in boolean mode.

Reviewed by Vincent.


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

ProxyField


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

by exporting delegated_list property.
* fix indentation issue which duplicates 'tales' node in formToXML
brought by r27696


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

This was always broken, and went unnoticed because of another breakage: these
expressions were never rendered in final SQL. That will be fixed in a separate
commit.


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

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

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

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

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

in this case _checkConsistency should not examine those children objects.
It might be better to filter portal types directly in contentValues.


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

* add more fields for dialog with last rules of the guideline

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

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

Assume that the test starts in English.

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

It is acceptable to have newest - only recipes and other helpers would be
updated if not pinned by versions.


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