blue-carpenter-85560
06/08/2023, 2:03 PM...
<table>
{% for shipmentGroup in mail.shipmentGroups %}
<tr><td> shipment details... </td></tr>
{% for item in shipmentGroup.items %}
<tr><td> item details... </td></td>
{% endfor %}
{% endfor %}
</table>
when viewed in the b2b-demoshop cms block editor, it has changed into
{% for shipmentGroup in mail.shipmentGroups %}{% for item in shipmentGroup.items %}{% endfor %}{% endfor %}
...
<table>
<tr><td> shipment details... </td></tr>
<tr><td> item details... </td></td>
</table>
At the moment, I'm importing the csv with my edits to get around this. Should it be possible to edit the blocks with twig code in the backoffice editor?adorable-wolf-29357
06/08/2023, 4:47 PMicy-furniture-80558
06/09/2023, 5:40 AMicy-furniture-80558
06/09/2023, 10:29 AMclean-sundown-47111
06/12/2023, 7:54 AMelegant-agent-58713
06/13/2023, 7:50 AMrough-rainbow-3431
06/13/2023, 9:11 AMrough-rainbow-3431
06/13/2023, 9:22 AM/**
* Register global event listeners
*/
$('body')
.on('click', '.add-another-image-set', addAnotherImageSet)
.on('click', '.add-another-image-collection', addAnotherImageCollection)
.on('click', '.remove-image-set', deleteImageSet)
.on('click', '.remove-image-collection', deleteImageCollection);
/**
* @param event
*/
function addAnotherImageCollection(event) {
event.preventDefault();
var prototypeTemplate = $(event.target).closest('[data-image-collection-prototype]');
var imageSet = $(event.target).closest('.image-set');
var imageSetIndex = imageSet.data('imageSetIndex');
var imageCollectionIndex = imageSet.find('.image-collection').length;
var newOptionFormHTML = prototypeTemplate
.data('imageCollectionPrototype')
.replace(/__image_set_name__/g, imageSetIndex)
.replace(/__name__/g, imageCollectionIndex);
newOptionFormHTML = setSortOrderFieldValue(newOptionFormHTML);
imageSet.find('.image-collection-container').append($(newOptionFormHTML));
}
rough-rainbow-3431
06/13/2023, 10:10 AM/**
* Register global event listeners
*/
$('body').on('click', '.add-another-image-collection', addAnotherImageCollection).on('click', '.remove-image-collection', deleteImageCollection);
/**
* @param event
*/
$('.add-another-image-set').click();
brave-rocket-76034
06/13/2023, 1:52 PMbrave-rocket-76034
06/13/2023, 1:52 PMastonishing-raincoat-78292
06/13/2023, 2:29 PMbroad-queen-33863
06/13/2023, 10:00 PMgetGiftCardOnlyShipmentMethods
and so far it doesn't seem to be any issues anywhere, but i'm looking over the code for 'NoShipment' mentions, and there seems to be a bunch of sanitization and processing based on config value of NoShipment, some places even directly refer to string 'NoShipment', that said they're using GiftCardConfig shipment method instead of ShipmentConfig, the former being deprecated. Are there any places i should pay attention to or should the return function being changed handle it alone ?fancy-garage-20650
06/14/2023, 8:53 AMbright-architect-19696
06/14/2023, 9:43 AMbrave-rocket-76034
06/14/2023, 12:08 PMclean-sundown-47111
06/14/2023, 12:34 PMtall-spring-12746
06/15/2023, 5:52 AMcalm-toddler-60539
06/15/2023, 11:00 AMrough-rainbow-3431
06/15/2023, 2:30 PMclean-sundown-47111
06/19/2023, 6:35 AMclean-sundown-47111
06/19/2023, 7:47 AMbrave-rocket-76034
06/19/2023, 9:15 AMsome-toddler-5937
06/19/2023, 9:30 AMgit clone <https://github.com/spryker-shop/b2c-demo-shop.git> -b 202212.0-p2 --single-branch ./b2c-demo-shop && \
cd b2c-demo-shop && \
git clone <https://github.com/spryker/docker-sdk.git> --single-branch docker && \
docker/sdk bootstrap deploy.dev.yml
but I can't open this project in browser. The browser showing me unable to connect error.wonderful-microphone-68413
06/19/2023, 11:24 AMfast-monkey-21184
06/19/2023, 3:43 PMgreen-salesmen-82630
06/19/2023, 4:42 PMclean-sundown-47111
06/20/2023, 5:18 AMwooden-king-30682
06/20/2023, 6:07 AMspryker/queue: ^1.10.0
which does not exist yet (https://github.com/spryker/queue/tags).
When I first looked into the documentation some months ago I though, it's pretty new, maybe the next days the release will follow.
But ~6 months later there is still no release of the feature or do I miss something?
As we pretty much run into memory issues on a daily base with a huge Jenkins instance this feature seem to solve our problem and therefore I would really like to test it instead of implementing it on project level. @plain-city-95899 do you know if this feature release got missing internally or is it abandoned?