These are chat archives for reactioncommerce/reaction

6th
Apr 2016
Aesop7
@Aesop7
Apr 06 2016 00:00
@zenweasel it's a bit late, but thank you for getting back to me about how to add the footer
And congratulations on the version upgrade w/ 1.3!
Just a quick followup question about getting the footer updated across all layouts -- what's the best way to add the footer entry for each entry under layout > structure ?
Lukas Sägesser
@ScyDev
Apr 06 2016 07:24
@aaronjudd Tnx. Yes I'm setting ROOT_URL in a docker env variable now, that works fine.
Maxim Pokrovskii
@m-pokrovskii
Apr 06 2016 13:41
Hi. I'm connected to the reaction by DDP. How i can get the cart? It requires user and session id, but reaction doesn't create those if there is DDP connection.
Brent Hoover
@zenweasel
Apr 06 2016 13:57
I believe you just need to subscribe to the cart
@Aesop7 You could do it by hand using the console or a program like Robomongo, or write a short script to loop over all the entries and write that out.
Maxim Pokrovskii
@m-pokrovskii
Apr 06 2016 14:02
@zenweasel I cannot subscribe cause it requres sessionId, userId.
I'll explain: when user comes to the site it creates anonymous user and session. Which is not happened when i use DDP.connect()
Brent Hoover
@zenweasel
Apr 06 2016 14:04
ah yes, true
I would need to look in the code to see what exactly trigger the creation of the session and user. Unfortunately I am not at my dev machine at the moment.
I am surpirsed you don’t get a session right away though
Maxim Pokrovskii
@m-pokrovskii
Apr 06 2016 14:21
@zenweasel Will be appreciated for the help. Session probably my be created, by i can't access to it by remoteServer.call("removeMethod")
Jeremy Shimko
@jshimko
Apr 06 2016 14:24
Technically, the client side of Reaction is just talking to the server over DDP, so literally anything that Reaction does can be done by another app over DDP. It’s just a matter of taking care of all of those bits that happen in the background (like the session and anon user). So it may end up being a little complicated, but it’s absolutely possible.
And @aaronjudd can probably make some good recommendations in that department since he wrote most of that.
Brent Hoover
@zenweasel
Apr 06 2016 14:30
I think you could just create a method to explicitly create those that would make it simpler, since these may be called by client-side JS that you are never running
Have to think about that a bit more, interesting question
Tilky Fox
@tilky
Apr 06 2016 18:08
hello folks, is there any live or demo store running on reaction ?
Aaron Judd
@aaronjudd
Apr 06 2016 18:19
@tilky there aren’t any demo shops, you can install / run locally, or sign up for the beta demo on reactioncommerce.com, but we’re still testing and won’t be are rolling out the invites slowly, still a couple weeks away from letting everyone launch shops there.
Spencer Norman
@spencern
Apr 06 2016 18:43

@aaronjudd tests are failing for me right now - are you guys seeing this issue as well?

=> Errors prevented startup:

   While processing files with cosmos:browserify (for target web.browser):
   packages/reactioncommerce:reaction-logger/client/bunyan.browserify.js: Cannot find module 'bunyan' from
   '/Users/spencer/tmp/reaction0-12/upstream/packages/reaction-logging/.npm/package'

   Missing module check:
   >  basedir exists     : MISSING
   >  node_modules exists: MISSING
   >  module exists      : MISSING

   Browserify options:
   >  {
   >  "basedir": "/Users/spencer/tmp/reaction0-12/upstream/packages/reaction-logging/.npm/package",
   >  "debug": true,
   >  "transforms": {}
   }

   Special options:
   >  {}

=> Your application has errors. Waiting for file change.

It then retries

Modified -- restarting.
reactioncommerce:reaction-logger: updating npm dependencies -- bunyan, bunyan-format, bunyan-loggly...
$> 
$>  .meteor/packages/meteor-tool/.1.1.10.1metfpd++os.osx.x86_64+web.browser+web.cordova/mt-os.osx.x86_64/dev_bundle/server-lib/node_modules/fibers/future.js:245
$>                          throw(ex);
$>                                ^
$>  Error: HTTP.methods not implemented on client-side
$>      at Object.HTTP.methods (/private/var/folders/v9/txwznh8d5fg8bgz0fw0f9s080000gn/T/meteor-test-runwsg69e/.meteor/local/build/programs/server/packages/cfs_http-methods.js:688:9)
$>      at Package (/private/var/folders/v9/txwznh8d5fg8bgz0fw0f9s080000gn/T/meteor-test-runwsg69e/.meteor/local/build/programs/server/packages/cfs_access-point.js:861:6)
$>      at Package (/private/var/folders/v9/txwznh8d5fg8bgz0fw0f9s080000gn/T/meteor-test-runwsg69e/.meteor/local/build/programs/server/packages/cfs_access-point.js:881:4)
$>      at /private/var/folders/v9/txwznh8d5fg8bgz0fw0f9s080000gn/T/meteor-test-runwsg69e/.meteor/local/build/programs/server/packages/cfs_access-point.js:885:4
$>      at /private/var/folders/v9/txwznh8d5fg8bgz0fw0f9s080000gn/T/meteor-test-runwsg69e/.meteor/local/build/programs/server/packages/cfs_access-point.js:892:3
$>      at /private/var/folders/v9/txwznh8d5fg8bgz0fw0f9s080000gn/T/meteor-test-runwsg69e/.meteor/local/build/programs/server/boot.js:242:10
$>      at Array.forEach (native)
$>      at Function._.each._.forEach (.meteor/packages/meteor-tool/.1.1.10.1metfpd++os.osx.x86_64+web.browser+web.cordova/mt-os.osx.x86_64/dev_bundle/server-lib/node_modules/underscore/underscore.js:79:11)
$>      at /private/var/folders/v9/txwznh8d5fg8bgz0fw0f9s080000gn/T/meteor-test-runwsg69e/.meteor/local/build/programs/server/boot.js:137:5
=> Exited with code: 8
This is with the latest dev
running the app works fine
Was working fine yesterday afternoon for me and worked this morning until i restarted
Boris Shifrin
@ramusus
Apr 06 2016 19:09
HI guys, I'v got question - I need to show icon in the bottom of right sidebar of 2 pages - index and tag. I register it in my register.js with container: "tag" attribute and now I see it on all tag pages. What container should I use for index page?
Boris Shifrin
@ramusus
Apr 06 2016 19:16
I'v got one obvious solution - another registry item with container: "index". But the problem is - I see double icons in dashboard card of package. How could I avoid this? actually I don't need to have any icons there at all, only in right sidebar. Current attributes are { provides: "settings", template: "filtrationFilters", label: "Filters", icon: "fa fa-filter", container: "index" } Notation container: ["index", "tag"] doesn't work
Spencer Norman
@spencern
Apr 06 2016 19:20
But still not sure what’s causing it and why it changed recently
Aaron Judd
@aaronjudd
Apr 06 2016 20:08
@spencern we've seen that, but it usually goes away on re-run.. if it doesn't install those the npm packages the first time, it retries and should add them the second
Spencer Norman
@spencern
Apr 06 2016 20:09
hmm, for some reason it’s being stubborn for me and not installing them at all right now.
Aaron Judd
@aaronjudd
Apr 06 2016 20:09
have not seen the HTTP errors though, that's new.. and seems wrong
Spencer Norman
@spencern
Apr 06 2016 20:10
oh, or they aren’t related
for some reason, I connected the two errors in my mind, but if they aren’t connected, then my npm stuff is probably working as well
the HTTP errors are only happening on test for me
Aaron Judd
@aaronjudd
Apr 06 2016 20:11
you could just add the http package into .meteor/packages (or if onTest, use an api.use("http") and force the inclusion)
Spencer Norman
@spencern
Apr 06 2016 20:12
are you seeing these errors when you run tests locally?
I’m currently able to reproduce with a fresh clone of dev
but could be my machine if you’re not seeing them
Aaron Judd
@aaronjudd
Apr 06 2016 20:13
let me check with a fresh clone, I'm currently in 1.3 hell branch ;-)
Spencer Norman
@spencern
Apr 06 2016 20:14
yikes :fire:
Mike Murray
@mikemurray
Apr 06 2016 20:21
@ramusus I think thats a bug / oversight and should be fixed.
Aaron Judd
@aaronjudd
Apr 06 2016 20:21
@spencern I'm able to replicate your issue in test
Spencer Norman
@spencern
Apr 06 2016 20:23
good to know, thanks for checking
Aaron Judd
@aaronjudd
Apr 06 2016 20:25
did you have another project that updated to 1.3.x by any chance?
Spencer Norman
@spencern
Apr 06 2016 20:26
i haven’t
interestingly I was just able to fix it by cloning git@github.com:CollectionFS/Meteor-http-methods.git into my packages directory
Aaron Judd
@aaronjudd
Apr 06 2016 20:28
that is interesting, I was wondering if we're starting to get some dependency hell from new packages being published for 1.3.x
Spencer Norman
@spencern
Apr 06 2016 20:29
I was wondering the same thing, but it looks like what I cloned was released in September 2015, so I’m not really sure why that would have changed anything
unless atmosphere has a different version
well, would you look at that
v0.0.31 - added today
so much for semantic versioning
Aaron Judd
@aaronjudd
Apr 06 2016 20:34
and doesn't seem to be in repo, so published from a local, non published version
Spencer Norman
@spencern
Apr 06 2016 20:35
yep
Aaron Judd
@aaronjudd
Apr 06 2016 20:35
you making an issue, or i? (and I bet we're going to see a lot of this)
Spencer Norman
@spencern
Apr 06 2016 20:35
I checked that package first when I discovered the bug, but neglected to check Atmosphere because github didn’t show updates
I’m making one
Aaron Judd
@aaronjudd
Apr 06 2016 20:35
:thumbsup:
Spencer Norman
@spencern
Apr 06 2016 20:35
want me to tag you in it?
Aaron Judd
@aaronjudd
Apr 06 2016 20:35
yes please...
Spencer Norman
@spencern
Apr 06 2016 20:35
ok
Aaron Judd
@aaronjudd
Apr 06 2016 20:38
I’m testing pinning the version in packages like cfs:http-methods@0.0.30 (waiting on recompile now)
Spencer Norman
@spencern
Apr 06 2016 20:38
:+1:
It’s annoying that you have to pin a patch version :unamused:
CollectionFS/Meteor-http-methods#52
Aaron Judd
@aaronjudd
Apr 06 2016 20:45
does seem to be specific to onTest though, runs fine in app mode
. pinning in packages doesn’t help, which backs that theory up
Spencer Norman
@spencern
Apr 06 2016 20:45
yeah
xiaoc li
@brianxcli
Apr 06 2016 23:44
Hi, just noticed that "./reaction pull" is to get packages from Atmosphere, what's the idea of that? I can still run reaction without pulling anything. But if I need to, why not pushing them to reaction.git instead?
Brent Hoover
@zenweasel
Apr 06 2016 23:44
actually reaction pull clones packages locally
it’s just a wrapper about the clone-packages.sh
It’s just an easy way to keep your local packages up-to-date
was more critical when we had a lot more packages external to the main repo
Now really only payment packages are external
xiaoc li
@brianxcli
Apr 06 2016 23:59
launchdock-connect
reaction-auth-net
reaction-braintree
reaction-paymentmethod!reaction-paypal