These are chat archives for reactioncommerce/reaction

24th
Apr 2019
Jerry Hammann
@hammannja
Apr 24 02:28
@elhil You can see the commits in the develop branch. They just haven't updated to a new release candidate in over a month.
progranime
@progranime
Apr 24 05:54
Hi everyone, why the @reactioncommerce dependency don't have reaction-components folder on it ? because in the example thats the way its imported. Thanks
Screen Shot 2019-04-24 at 1.51.35 PM.png
progranime
@progranime
Apr 24 06:01

This is the error message when I did that:
Unable to resolve some modules:
"@reactioncommerce/reaction-components" in /opt/reaction/src/imports/plugins/custom/beesknees/client/templates/layouts/core.js

But when I check the core plugins that is the way on how they imported the registerComponent like this accounts components

Screen Shot 2019-04-24 at 2.00.14 PM.png
Screen Shot 2019-04-24 at 2.00.34 PM.png
This is also the error when I check the console log
Screen Shot 2019-04-24 at 2.02.10 PM.png
Loan Laux
@loan-laux
Apr 24 07:33
@elhil Yeah I think everyone here runs the develop branch. That's where all the new stuff is. PRs merged almost every day.
@progranime The Bee's Knees plugin example is quite old (heck, I'd even forgotten that name) and I wouldn't recommend using it nor taking it as an example for anything.
First of all, it's all Meteor stuff which for the most part isn't relevant at all. And then, it's been most likely a year or two since the last update.
For storefront modifications, everything should happen on the Next.js starterkit nowadays. Everybody here will strongly advise you not to use the Meteor storefront anymore as it's been deprecated.
progranime
@progranime
Apr 24 07:42
@loan-laux it means its not advisable to follow it for creating plugin :( . I'm trying to follow the docs but its not working. Actually my colleague was using the 1.16.2 version thats why I'm looking to the 1.16.0 documentation in his part when he demo it to us it's working on him. I want to study it further but i'm stuck, can't find any resource on it.
Loan Laux
@loan-laux
Apr 24 07:43
Does that mean that you're using the Meteor storefront?
The first thing I would recommend doing is upgrading to 2.0 and relying on a storefront that uses the GraphQL API. Whether it's the Next.js starterkit or something you built from scratch, it's up to you.
progranime
@progranime
Apr 24 07:46
@loan-laux yeah it seems its the Meteor storefront the UI with the sidebar at the right side right?
Loan Laux
@loan-laux
Apr 24 07:46
Then, you'll have your customer-facing code and your backend/admin code nicely separated and everything will be much cleaner. You'll be able to follow the docs for the latest version and get help in an easier way.
progranime
@progranime
Apr 24 07:46
Screen Shot 2019-04-16 at 10.01.36 AM.png
Loan Laux
@loan-laux
Apr 24 07:46
@progranime Well, is your customer-facing UI on port 3000 or 4000?
progranime
@progranime
Apr 24 07:46
its on 3000
Loan Laux
@loan-laux
Apr 24 07:47
So you're using the Meteor storefront, which hasn't received any update since January.
As I said above, if the current status of your project allows it, just switch to the Next.js starterkit. It'll make your life way easier.
Do you have any plugins or specific modifications in place?
progranime
@progranime
Apr 24 07:48
yeah that's why it giving me a headache because he (vendor) is not using the latest version
but in his demo he created its own component and its working
Loan Laux
@loan-laux
Apr 24 07:49
Yes, but it's not supported anymore. You're free to use an outdated version of Reaction, but it'll be hard for you to get any kind of support on it.
progranime
@progranime
Apr 24 07:50
Actually I'm in the stage of learning the core of the reaction commerce but the vendor was using the outdated one which I don't have a choice but to follow because he is the expert on it.
Loan Laux
@loan-laux
Apr 24 07:50
What do you mean by "vendor"? Your client?
progranime
@progranime
Apr 24 07:51
outsource dev
outsource developer / expert that will guide us on how to develop it. but because he is using outdated version I can't find any solutions or support on it. :(
Loan Laux
@loan-laux
Apr 24 07:53
Is this a new project that you're starting from scratch? Or something that already has a lot of work done and/or is already in production?
progranime
@progranime
Apr 24 08:00
Actually what he show to us in his local machine only. Not yet in production
Loan Laux
@loan-laux
Apr 24 08:02
Well if that person is advising you to use a deprecated version of Reaction simply because that's what he's comfortable with, I highly doubt his expertise. This is a red flag to me.
amazedge
@amazedge
Apr 24 10:11
Iam using reaction-platform and able to install & run all the services.As well able to access landing page of reaction-next-starterkit. However iam not able to SIGN IN... I get below OAuth2 Error:
Error: invalid_request
Description: The request is missing a required parameter, includes an invalid parameter value, includes a parameter more than once, or is otherwise malformed
Could any one help here
Loan Laux
@loan-laux
Apr 24 10:12
@amazedge Can you try and update Hydra by doing a git pull inside its directory?
Afterwards, do a docker stop reaction-hydra_hydra_1, and make start again from your reaction-platform root directory.
We want to make sure the hydra-migrate container runs again, and it's only done on startup
Or maybe it's simply an expired token, but I believe this issue was fixed. Try and flush your local storage + cache and see if it solves it.
Paul Hoza
@PaulHoza
Apr 24 18:52
@loan-laux , et. al., I'm preparing to launch a new site imminently, and I'm trying to decide on going with Reaction vs other less exciting options using WordPress or Drupal. At the moment (especially after reading this recent thread in here), I'm wondering how reasonable it would be to do the likely-dangerous move of building out this stuff on Reaction 2.x RC? I'm sure "don't use in production" would be smartest here, but what is the likelihood of getting a production site going in the VERY near future based on v2.0? (if that's an answer anyone has)
For one thing, I was looking heavily at the Marketplace features, but I see that 2.0 will require more work to get that going.. I'm not sure if I can pull that off quickly based on my skills, but as long as it's possible, I still think Reaction is "where I want to be".. it seems so dang sweet. Thanks for any thoughts on this.
(for the record, I've been playing with v1.17 for several days, but I guess I should stop planning to launch a site on 1.x??.. it sounds like it. Thus, v2.0 or nothing, but 2.0 is not complete. Urgh!)
Janus Reith
@janus-reith
Apr 24 19:23
@PaulHoza maybe it helps asking yourself: Do I need a production-ready E-Commerce soltution asap, or do I want to build an ecommerce soltution specifically tailored to the needs of my client, using modern techniques (which thenselves are stable aswell) and use reaction as a boilerplate that covers the whole stack mostly and already has a lot of functionaility that you eould
*Would Otherwise implement yourself already built in
What are your requirements - Is 2.0 missing something you need? For those things that already work, you can assure yourself by using a palette of unit Test, maybe implement some yourself and do some e2e Testing
Aesop7
@Aesop7
Apr 24 20:37
Hi Everyone, i'm trying to get spun up on the new version and use the starterkit to build a marketplace (etsy-style) shop
I've got a couple of very different questions: 1) will marketplace functionality be supported via the platform/services without a lot of additional work, or will there be customization that will need to happen there? And 2) is there a way to style the <Link /> component so that it looks like a button?
Paul Hoza
@PaulHoza
Apr 24 20:48
@janus-reith Thanks much for your comments. Great points/questions. In my case, it's our own endeavor that we're launching, so the anser is "yes". haha.. really want something ASAP, but also want to not just end up with the same-old cruft as all the previous crufty crufts we've worked on. The plethora of exciting brainstorming that's sprouted from the mere /notion/ of having a system like Reaction has been enough to make me actually happy to build an ecommerce site! That's roughly shocking to me, tbh. So ++ for that notion. :)
Thank you for the simple comments about the general stability of the building blocks of Reaction, because honestly, I'm not used to such a decoupled system built on the shoulders of giants. I'll re-examine this from these points and others. Thank you for priming that process. Cheers, @Aesop7
oops, sorry to @ you, @Aesop7 ... I meant @janus-reith :/