These are chat archives for reactioncommerce/reaction

15th
Feb 2016
Brent Hoover
@zenweasel
Feb 15 2016 00:51
if anybody else is looking for a relatively straight-ahead issue to take a crack at there’s this one: reactioncommerce/reaction#755
lijiming
@lijiming
Feb 15 2016 09:49
@zenweasel i have fixed it. I will submit a PR later.
Brent Hoover
@zenweasel
Feb 15 2016 10:54
@lijiming Nice!
Spencer Norman
@spencern
Feb 15 2016 18:16
Is v0.11.1 still on the roadmap or did that get shelved?
Mike Murray
@mikemurray
Feb 15 2016 18:55
@Aesop7 when the user is created you can set the permissions. Or set the defaults in the schema
Spencer Norman
@spencern
Feb 15 2016 19:22
What’s the process for starting up features-v0.12 @paulgrever and I are having trouble launching this branch on local
Current process:
  1. clone reaction into fresh directory
  2. Switch to features-v0.12 branch
  3. all payment packages fail to load
  4. exclude payment packages and launchdock package via .meteor/packages
  5. App loads, but fails to render
Spencer Norman
@spencern
Feb 15 2016 19:32
Update: we are actually only experiencing this on one machine
Spencer Norman
@spencern
Feb 15 2016 19:38
Update 2: it seems the issue was running --allow-incompatible-updates in between steps 3 and 4
Mike Murray
@mikemurray
Feb 15 2016 19:51
@spencern becuase the branched of all the other (external) reaction packges need to be on branch refactor-route-502
Spencer Norman
@spencern
Feb 15 2016 19:51
:+1: Are there working branches for all packages now?
I got v0.12 working with just internal packages, but received a Exception in template helper: TypeError: Cannot read property 'charAt' of undefined error when trying to log in to dashboard
Mike Murray
@mikemurray
Feb 15 2016 19:52
yea, mostly updated registery entries and routing in those packages
Aesop7
@Aesop7
Feb 15 2016 19:59
@mikemurray, I tried adding the package in a few spots (here, here, and here ) but the entry isn't appearing in mongo... is there another schema setting that I need to set somewhere?
Mike Murray
@mikemurray
Feb 15 2016 20:02
@Aesop7 on the third file, I think you need to set: shop.defaultRoles, instead of the array after the ||
shop.defaultRoles comes from the shop collection, which then should come from the shops.json fixture data
Spencer Norman
@spencern
Feb 15 2016 20:06
The charAt error went away after a server restart. Seems like the app failed to load the translations on the first go-around
Maged Eladawy
@meladawy
Feb 15 2016 20:10
Sorry guys i'm not sure if u discussed this before or not
Do you have any idea where to create shops
because i believe there should be a shops management page
but i didn't find any
and there is already a methods inside the core files such as "shop/createShop" which allow you to create a shop
Mike Murray
@mikemurray
Feb 15 2016 20:12
@meladawy There will be, but its not in yet. We're updating the routes now to be able to support multiple shops. Then comes the ability to create / manage / view multiple shops
Maged Eladawy
@meladawy
Feb 15 2016 20:14
Thank you @mikemurray , but i should have such function in my next project, so should i build this or did you take any step forward regarding this ?
rkhunter
@rkhunter
Feb 15 2016 20:27
@balsig99 +1
  • Dedicated Dashboard- Vendor have separate dashboard with analytic tools for day to day sales.
  • STORE LOCATOR- sellers to display their store addresses on google map.
  • TWO-Factor Authentication for Both admin and sellers using https://duo.com/
  • AJAX FILTER for Products
  • Color attributes for products That is ajax filterable.
@saad91 @aaronjudd can help you with it
Aesop7
@Aesop7
Feb 15 2016 20:36
@mikemurray, that fixes it so that at least I can see the permission for the user by default in mongo. However, the link doesn't appear in the UI. If I log in as admin and uncheck then re-check the package/permission for a particular user it shows, but by default after logging in, the custom link is not shown in the menu. Any ideas?
Mike Murray
@mikemurray
Feb 15 2016 20:51
@meladawy We'll be building it soon
Paul Grever
@paulgrever
Feb 15 2016 21:12
@mikemurray what is ‘coreAccountsWorkflow’ and what does it do? I can’t find it defined anywhere
Mike Murray
@mikemurray
Feb 15 2016 21:22
@Aesop7 might be a bug with permissions subscription?
@paulgrever used to pull in the layout with the key workflow: "coreAccountsWorkflow" from "layouts" in that same registry entry.
Aaron Judd
@aaronjudd
Feb 15 2016 21:28

@paulgrever that was stubbed for the new layouts in v0.12, where a layout is defined on the package.layout as

  layout: [{
    layout: "coreLayout",
    workflow: "coreAccountsWorkflow",
    collection: "Accounts",
    theme: "default",
    enabled: true,
    structure: {
      template: "accountsDashboard",
      layoutHeader: "layoutHeader",
      layoutFooter: "",
      notFound: "notFound",
      dashboardHeader: "dashboardHeader",
      dashboardControls: "accountsDashboardControls",
      dashboardHeaderControls: "",
      adminControlsFooter: "adminControlsFooter"
    }
  }]

and will be in the Shops collection as Layout when enabled for a shop

Aesop7
@Aesop7
Feb 15 2016 21:39
thanks @mikemurray , i'll look at that later this week
Spencer Norman
@spencern
Feb 15 2016 23:26
@aaronjudd are you guys planning to follow the FlowRouter method of template based auth or are you planning to do something with triggers in FlowRouter and use a more traditional ‘controller’ style auth method (e.g. https://medium.com/@satyavh/using-flow-router-for-authentication-ba7bb2644f42)
I definitely lean away from the template based auth myself, but curious where Reaction will land as it makes sense to have a similar style in the packages we are building