@mo7sener if you’re willing to report any issue you’re getting with the Admin UI that’d be very helpful! We’ve been focused on the GraphQL API for our 3.0 release and the Admin UI hasn’t been updated fully to consume the GQL API instead of the Meteor API from before. Issues and PRs are welcome for any Admin related issue. @willopez and @mikemurray have been working on the Product UI a bit, but there’s more to do.
Hello everyone! Just like with our new devtools, we’ve updated our AWS S3 plugin to be used with Reaction 3.0. To make it consistent with the rest of out:grow’s open-source plugins, it’s now published on NPM with the org prefix
@outgrowio/. The setup instructions have changed too, so make sure to read them before doing the update. Hope that’ll help the community. https://github.com/outgrow/reaction-file-collections-sa-s3
The problem I get is as follows:
1) I
2) I create an account and open
3) When I click the "Create Product" button, I get the following error (https://cdn.discordapp.com/attachments/324535887788507138/674255378736873492/unknown.png) accompanied by a blank page
4) I, then, restart the "reactionadmin" container using
5) Clicking the "Create Product" button after that opens the product creation form. But whenever I try to interact with the form (even by clicking on the page), I get a
1) I
sudo make init then sudo make start2) I create an account and open
localhost:4080then the products tab3) When I click the "Create Product" button, I get the following error (https://cdn.discordapp.com/attachments/324535887788507138/674255378736873492/unknown.png) accompanied by a blank page
4) I, then, restart the "reactionadmin" container using
docker restart reactionadmin_reaction-admin_15) Clicking the "Create Product" button after that opens the product creation form. But whenever I try to interact with the form (even by clicking on the page), I get a
Match failed [400] and the following error in the console: (https://cdn.discordapp.com/attachments/324535887788507138/674256064706772992/unknown.png)
@mo7sener Pulled the latest
reaction-admin and running into the same bugs. Looks like the product editor is a WIP while @mikemurray is working on porting it to 100% GQL. The PR is right here, and it looks like it’ll be ready soon. reactioncommerce/reaction-admin#188 Hang tight!
That’s part of the whole beta-testing experience. :smile: But more seriously, if you absolutely need to use
reaction-admin right now, I would suggest to git checkout an earlier tag/commit. Going back one week would probably do the trick.
But I’m not sure he’s often on here. Maybe @aldeed can comment instead.
@bjanssen-pon Unfortunately, unlike on the example storefront, there isn’t any component context in
reaction-admin. So the solution would be to create a new component somewhere in your codebase, which would be a class extending ConfirmDialog, and then to replace any import of @reactioncommerce/catalyst/ConfirmDialog with your custom local component.
It would really be good to have a global component context for doing clean overrides in
reaction-admin. Definitely something we need, and not much work. I’ll try and work on that at some point.
Component context would work great if all components are actually in the context
but sometimes there are components that are hidden in the
reaction-component-library or double named in both components folder and reaction-component-library
I am planning on refactoring a lot of components
I just don't have enough time in a week :P
Working on RC every day for years, you kind of lose sense of this because you’re so used to the overall architecture… I agree with you, some things can be confusing and will contribute to the learning curve, so we should definitely tackle them. A good refactor to eliminate duplicates would be more than welcome. :clap:
So I can imagine the learning curve can be harder because of this
One new page for documentation would be awarded like 5 euro's.
The documentation for mendix got written in less than a week. Almost 200+ md files added by the community
1000 euro's for a complete documentation, seems fair to me
You can create a plugin where you will be listening to event "afterPublishProductToCatalog" and pushing product to ES
Then you just need to expose ES in your application - to get data in your storefront
Hi all, we have just released new
beta versions of all of our reaction-development-platform projects: https://github.com/reactioncommerce/reaction-development-platform/releases/tag/v3.0.0-beta.4
Please make sure to follow the instructions in any one of the 5 related PR's listed here to update your
env files to get all the docker networks synced up: reactioncommerce/reaction-development-platform#101
@daniel-rosiak Oh thanks. I somehow didn't think about using reaction's events. This will actually make it a bit of a trivial task.
If you want to create a fully automated bug bounty system with TDD you can set it up with k8s
You would have to apply for the alpha though
Hi!
@loan-laux belated thanks for answer :)
I've got one more question. Is there any way to catch worker event?
For example:
in src/core-services/files/jobs/saveTempImages.jsthere is context.backgroundJobs.addWorker,
which is triggered function async worker(job), then find jobs with suitable status in DB.
I need to catch successful completion of this process in my own plugin,
preferably without editing the code in project plugin files.
@adel1ne As far as I’m aware, there are no events yet for catching the completion of job workers. It’s definitely something that’s missing. I ran into the same issue when developing
reaction-dummy-data. But as a workaround, you could use a MongoDB change stream on the Jobs collection. Not ideal, but I’d say it’s an acceptable alternative while there’s no official API to monitor jobs. Would that work for you?