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

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

Just forget about it, and retry later.


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

It means that we cant access the Legacy module anymore,
so for now we hardcode this default_large_image_height value


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

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

- add search box
- refactor code to save and load notes of events in description field. This change is to use SearchableText search in event module

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

Will be dropped as soon as cloudooo will support this conversion.


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

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

issue as _getDefaultAcquiredProperty() already takes care of such case
as per r42852 (consistent with its default value in parameters) and
getContentPortalType() would fail anyway if no portal type is given


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

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

* improve css

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

- move button to create new event to your_calendar_box
- remove not used field

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

With MyISAM full text catalog bt5 we need to use deferred connection only for catalog / uncatalog methods.

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

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

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

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

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

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

extend code to make possible add fields on edit dialog. This patch was send to wdcalendar developers

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

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

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

I need some way to distinguish what happens when, later, an automatic migration
happens, or when a Tool is not found: if this happens in a "normal" context,
then logging should be very loud and verbose, as this is likely to crash your
site.
On the other hand, during bootstrap/setup, this is perfectly normal to miss
some tools/modules, and we should not worry/log about it, or the NECESSARY
logs will be quickly removed by developers tired of seeing "useless" logs...

Better ideas that can work in a fresh site without workflows, portal types,
or any advanced mechanism? I'm all ears.


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

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

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

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

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

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

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

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

Clarify the situation: raise useful errors.


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

Just a smaller function that exposes generation of related category accessors.
For now it's used in both Utils and dynamic/, but soon enough the Utils caller
will be gone and we will be able to simplify all this.


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

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

(I'm implementing my own TODOs; I know, nice, right?)


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

* Changes to dynamic_class_generation_interaction_workflow:
* use resetDynamicDocumentsOnceAtTransactionBoundary so that several changes to portal types during the same transaction are cheaper.
* change trigger to happen after action since it's always queued at end of transaction anyway
* add ERP5TypeInformation._setBaseCategoryList to triggers as well so that accessors are regenerated when base categories are changed.



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

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

replace _aq_reset calls/resetDynamicDocuments calls with resetDynamicDocumentsOnceAtTransactionBoundary calls


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

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

interactions/interactors calls to resetDynamicDocuments and only
ever do once a reset.
If used wisely, with clever enough tests (aka do not commit
like crazies after each setter call), this should allow tests
to run much faster.


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

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

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