What are the Slack Archives?
It’s a history of our time together in the Slack Community! There’s a ton of knowledge in here, so feel free to search through the archives for a possible answer to your question.
Because this space is not active, you won’t be able to create a new post or comment here. If you have a question or want to start a discussion about something, head over to our categories and pick one to post in! You can always refer back to a post from Slack Archives if needed; just copy the link to use it as a reference..
Hi everyone ✌ hope you all had a nice transition into 2022 🙂 I have an issu
Hi everyone ✌
hope you all had a nice transition into 2022 🙂
I have an issue in regards to the most recent Spryker release "202108". While upgrading from an older version we now encounter some issues in relation to event triggering and publishing, especially for plugins which return no data and should be triggered without any ID.
Once the "event-behavior" module is updated to the latest version, modules like "category-storage" and "product-label-storage" loss parts of their functionality. In the most recent version of "event-behavior" triggering an event for no ID will not fallback to an empty trigger, if the TriggerPlugin does not return a collection of data. There are at least two types of publishing events that are not directly related to entities and return an empty collection, e.g. Category-Storage. Due to changes in the EventResourceQueryContainerManager (TE-3614) the PublisherPlugin will not be triggered anymore:
Comments
-
Hi @UP4C7GASJ
Thanks for reporting this, we will have a look into this issue and will provide you the answer/fix soon as soon as it registered in our support panel.0 -
we are also affected by this
0 -
@U01AC5J3LAW unfortunately every shop on the latest version will be affected. Did you resolve this already on project level?
0 -
Hey @UP4C7GASJ,
Could you please register this issue here support.spryker.com? then we have internal process to pick this automatically up and start the investigation for it. thank you!0 -
@UK9N7MP96 who is the client I should assign this to? Spryker in general? 😄
0 -
If you think it’s a general product issue, then yes
0 -
Will it be resolved as one then? Raising it here and also having others recognising the issue should bring some attention or not?
0 -
I just ask as other "issues" I so far reported took 3-6 months before being looked at 😉
0 -
@UP4C7GASJ i can assure you that it does not take 3-6 months until issues are getting "looked at" by my team. Bugs we can reproduce will need to get solved properly and that can take time. If an issue is severe and multiple customers are affected by it it can be prioritised appropriately. Please reference the customer project this issue relates to in your case
0 -
I think that for problems of this kind you shouldn't stand there asking to open a ticket or anything else. As @UP4C7GASJ says, it is a generic problem and Spryker should open a generic ticket for itself and inform customers promptly when the problem has been solved.
If @UP4C7GASJ intends to open a ticket for his internal control, that's fine, but to make the solution of the problem depend only on the fact that there is a ticket or not created by the customer is not a fast way to solve the problem.
0 -
@UL65CH0MC we ask our partners and customers to open tickets so we do not risk things getting missed in translation. Especially its meaning for a concrete project and the justification for the business impact that needs to be provided
0 -
It is perfectly fine to bring up issues and discuss them here, but we need to receive a proper ticket from you to be able to process it
0 -
Hi @tom.lehner, the past showed that just tickets which were ranked or related by certain customers had priority. I speak from experience when I say it takes 3-6 months to be looked at, as another issue I reported in September (associated to a client) was moved to "in review" (or whatever the first state after open is) after roughly 3 months.
0 -
If you do want to discuss individual cases and have issues with them, please PM me referencing them. I can see how many cases you opened and what their history is
0 -
My question here is simply: who should I reference as a client to this matter for fastest resolution? The business impact is highly critical as we need to resolve this manually. This is not a specific bug in general it can be reproduced on a clean B2X environment.
0 -
The customer which you are currently working for. If multiple, the one you are most closely involved with personally
0 -
If you need me to post the above message as a ticket, I can do it. I am not working with clients directly, i get this issue reported
0 -
customer reference is far less important than a sound business impact justification
0 -
"business impact justification" => it does not work anymore and used to work before, sound enough? 😄
0 -
Think of it this way: What would you want the person prioritising a lot of issues daily to know so that the urgency of your request is clear, even though that person might not work on your project and might not have any other context.
0 -
or, from a business user perspective: what does this bug prevent in terms of revenue, customer UX, etc.
0 -
Alright - I think I need to funnel this through other channels as reporting a bug now needs a partner login 🙌
0
Categories
- All Categories
- 42 Getting Started & Guidelines
- 7 Getting Started in the Community
- 8 Additional Resources
- 7 Community Ideas and Feedback
- 76 Spryker News
- 929 Developer Corner
- 787 Spryker Development
- 89 Spryker Dev Environment
- 362 Spryker Releases
- 3 Oryx frontend framework
- 35 Propel ORM
- 68 Community Projects
- 3 Community Ideation Board
- 30 Hackathon
- 3 PHP Bridge
- 6 Gacela Project
- 26 Job Opportunities
- 3.2K 📜 Slack Archives
- 116 Academy
- 5 Business Users
- 370 Docker
- 551 Slack General
- 2K Help
- 75 Knowledge Sharing
- 6 Random Stuff
- 4 Code Testing
- 32 Product & Business Questions
- 70 Spryker Safari Questions
- 50 Random