Catalog, Business Template: Remove expression_instance property from CatalogFilter property sheets
Also, while exporting catalog methods, explicitly check for `expression_instance` property. Now we keep expression_instance property in a volatile attribute, so we should prefer using it.
Showing
-
Owner
How about making another "big commit" to re-export all business templates, similar to what we did in !496 (merged)
The diff we are trying to eliminate is:
--- a/bt5/erp5_accounting/CatalogMethodTemplateItem/portal_catalog/erp5_mysql_innodb/z0_uncatalog_accounting_transaction.xml +++ b/bt5/erp5_accounting/CatalogMethodTemplateItem/portal_catalog/erp5_mysql_innodb/z0_uncatalog_accounting_transaction.xml @@ -51,12 +51,6 @@ </value> </item> <item> - <key> <string>expression_instance</string> </key> - <value> - <persistent> <string encoding="base64">AAAAAAAAAAI=</string> </persistent> - </value> - </item> - <item> <key> <string>filtered</string> </key> <value> <int>1</int> </value> </item> @@ -89,17 +83,4 @@ </dictionary> </pickle> </record> - <record id="2" aka="AAAAAAAAAAI="> - <pickle> - <global name="Expression" module="Products.CMFCore.Expression"/> - </pickle> - <pickle> - <dictionary> - <item> - <key> <string>text</string> </key> - <value> <string>python: context.isAccountingTransactionType()</string> </value> - </item> - </dictionary> - </pickle> - </record> </ZopeData>
So we could look for
//item/key/string[text() = "expression_instance"]
, delete the grand parent<item>
and the corresponding<record>
byaka=
?
Please register or sign in to comment