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

Alarm can be recognised as replaceable in catalog in two cases:

 * if alarm_date from catalog is empty (existing case)
 * if alarm is not existing in catalog yet (case added by changing indentation)

Second case happens during first indexation.


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

Note: test_21_AlarmCatalogPresence proves that there is a bug in Alarm reindexation.
When new alarm enabled and configured alarm is added to site using one transaction
and one reindexation it will be not properly cataloged.

This affects alarm installation from Business Templates.

This problem was hidden until fix for multiple-reindexation in Business Templates
was applied.


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

* Add alarm to check Conversion Tool availability (oood)
reviewed by romain

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

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

 - getPropretyDictFromContent does not try to find anything from empty content
 - convertTotBaseFormat does not try to convert



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

* Add a category exporting feature

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

* Update ERP5Site_reindexAll and index some tools correctly.

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

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

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

This was responsible for the recent failure of the test.
Remove the two XXX and use instead a assertMatchesPossibleSortList to match all
possible combinations


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

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

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

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

Update the bt to use the new structure of the base amount category :

- update local part of the base amount category

- update odt reports to use the new category structure

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

There were three surprising things in the previous version:
 * the XXX mention: leafs can indeed be detected at construction time
 * the need to track both children and parents of a node: usually only one
    or the other is enough to work efficiently on a graph
 * the idiom:
      if n in list: list.remove(n)
      list.append(n)

Replace it by a generic sort on node depth. A dictionary is used for lookups to
avoid linear list lookups, and only the successor relation is kept (parent_dict)

Also explicit in comments the graph we are building/the order expected for code
clarity (ie avoid confusion wrt what is the parent/child of the graph node)


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

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

* revert commit r31528, bug was fix by commit r31549 by removing duplicates of uri and class_name in DocumentationHelper_viewDocumentationHelper and BusinessTemplateDocumentationHelper_view

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

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

* moving fields your_uri and your_class_name from hidden to bottom in DocumentationHelper_viewDocumentationHelper

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

* adding action for documentation helper report

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

* Correcting display left and right order

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

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

flag utf-8 support in the request, required for proper functioning of the zpt unicode conflict resolver in Zope 2.12

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

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

This image is used in case there is no image defined for header_background_image on web site layout. So in this case, the image was not found and error was raised.

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

* Make listbox unlimited in report mode

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

getConversion return a list of two values, so previous code ("return
len(self.getConversion(**kw))") always return 2.
Now the len of the data is returned.
In case of images, data is an OFSImage object. But OFSImage objects support
len, so it works also in case of images.

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

This height attribute was useless and make strange displaying in firefox (text entered in search field was not vertical centered, now it is).

I test the displaying in FF 3.016, Konqueror 4.2.4 and Opera 9.64 and it was good on the 3.

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

the return made in try and in except was the same. Take it of from both and put
it after.

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

It was reported that in some web_site (like km), some people think that this field was used to login. Writing "Search" inside make not possible to think this now. (And when the field get the focus, the field make him empty to be able to receive the search text).

I try this without javascript support, and the search is usable, the only thing is that the user have to remove the default text manualy (it's the behaviour of most of the popular websites).

reviewed and approved by jm

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

change a bit the behaviour to keep text entered by the user (if the focus is lost and gain, the text entered by the user is kept, this permit to complete a search after changing the focus).

Put back the version number commited in r31536 by mistake.

reviewed and approved by jm

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

It was reported that in some web_site (like km), some people think that this field was used to login. Writing "Search" inside make not possible to think this now. (And when the field get the focus, the field make him empty to be able to receive the search text).

I try this without javascript support, and the search is usable, the only thing is that the user have to remove the default text manualy (it's the behaviour of most of the popular websites).

reviewed and approved by jm

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

When I reverted [31533], I thought the 3rd replacement was useless:
I didn't notice [27255] was only for non-existing objects.

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

Revert [31533] partially.

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

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

Image were not stored in the same way in every methods :
in case of index_html, the image was stored, in case of convert, the image.data
was stored.
This lead to conflicts because in both cases, the cache_id was the same, so if
inded_html was first call, and after that, convert was call on the same image,
convert will return an Image object instead of image.data String.

Now in all cases, the image is stored by setConversion, and in case of convert,
only image.data is returned.

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

getSizeFromImageDisplay method was returning (heigh, width), but all other
 methods were returning (widht height). In addition to this, there was
 mistakes :
from Document/Image.py +295 :
                        'width': self.getSizeFromImageDisplay(id)[0],
                        'height': self.getSizeFromImageDisplay(id)[1],
and also l 450:
      (width, height) = self.getSizeFromImageDisplay(display)

the use of width and height was mixed up.
Currently, all default preferences display size define squares (width = heigh),
 so this mistake was never detected.

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

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

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