[MGNLWCS-40] There is no tool/mechanism for assigning store id to the site Created: 31/Aug/14 Updated: 15/Sep/14 Resolved: 10/Sep/14 |
|
| Status: | Closed |
| Project: | Websphere Commerce Integration |
| Component/s: | None |
| Affects Version/s: | 1.0 |
| Fix Version/s: | 1.0 |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Jan Haderka | Assignee: | Jaroslav Simak |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Template: |
|
||||||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||||||||||
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
||||||||||||||||
| Date of First Response: | |||||||||||||||||
| Description |
|
or to the page tree. Current workaround is to assign storeId property to the home page directly via jcr browser. |
| Comments |
| Comment by Jaroslav Simak [ 09/Sep/14 ] |
|
storeId is still needed to be stored under root page of a shop because of navigation, product list, shopping cart (otherwise we would have to pass store id on every request via a request parameter for example). Maybe if we switch navigation and product into 'standard' components (not autogenerated) we could set storeId via dialog. But i am not sure if thats better than what we have now. Other than that, for components like carousels, stages, teasers, store id is now set via choose dialog. I also made websphere app 'store aware', which means that we can now switch between multiple stores. |
| Comment by Jan Haderka [ 10/Sep/14 ] |
return templatingFunctions.link(detailPage).replace(".html", "/" + org.apache.commons.lang3.StringUtils.replace(content.getProperty("productId").getString(), ":", "-") + "-" + WCSUtils.normalize(productName) + ".html"); Any need for including full package path? Also when stripping extensions, keep in mind that ppl might have configured different default extension than .html. The code above is present in multiple models ... any chance of placing it in common parent or outside in util class?
[#-- TODO: This is a hack, solution with imageLink return object must be implemented --]
/**
* This method should go away when MGNLWCS-57 is resolved.
*/
Please reconsider wording of above comments. |
| Comment by Jaroslav Simak [ 10/Sep/14 ] |
|
First todo removed - i actually have no idea what it really means (i copied that from internalTeaser.ftl from STK). And for removing .html extension - follow up ticket created and linked. |