Well, it turns out that no matter whether I use the original sidedeepcategory
and breadcrumbs screen within my own application or not, I always end up
with topLevelList = null.
I tracked it all down to the following: the sequence in which both screens
are loaded matter heavily, as right now the breadcrumbs.groovy script is
dependant on the sidedeepcategory.groovy list. Is this intentional?
I would argue that the breadcrumbs screen should be run independently, so
perhaps it is a smart idea to improve the original breadcrumbs script?
I compared both scripts and realized that both are pretty much identical
except that breadcrumbs.groovy misses the needed:
CategoryWorker.getRelatedCategories(request, "topLevelList",
CatalogWorker.getCatalogTopCategoryId(request,
CatalogWorker.getCurrentCatalogId(request)), true);
curCategoryId = parameters.category_id ?: parameters.CATEGORY_ID ?: "";
request.setAttribute("curCategoryId", curCategoryId);
CategoryWorker.setTrail(request, curCategoryId);
By adding the above or by simply loading sidedeepcategory.groovy within the
breadcrumbs screen, one can easily get both to work...
The question remains however, whether or not it is useful to have both
scripts in place when their purpose is identical and one of which can not be
run standalone...
--
View this message in context:
http://www.nabble.com/Breadcrumbs---misfunctioning-along-sidedeepcategory-tp21035525p21090678.html
Sent from the OFBiz - User mailing list archive at Nabble.com.
