These are chat archives for reactioncommerce/reaction

15th
Dec 2015
Aaron Judd
@aaronjudd
Dec 15 2015 03:09
@boboci9 I wasn’t able to replicate that startup issue
hrath2015
@hrath2015
Dec 15 2015 05:00
@rkhunter the issue what you are facing is resolved @aaronjudd as fix for #583
please read resolved by @aaronjudd
thanks @aaronjudd
Aaron Judd
@aaronjudd
Dec 15 2015 05:02
@hrath2015 thanks for timely GH issue.
Aaron Judd
@aaronjudd
Dec 15 2015 05:12
@pixelpunch just released 0.10.x which handles themes very differently, and should also resolve your .less issue. Recommend pulling that.
Bogi
@boboci9
Dec 15 2015 12:23

Hi, can anyone help me in explaining what is the meaning of coreOrderSummary order workflow step? It is only used in one place in the code and results in the new order not being counted as new anymore as it's passed in the coreOrderCreated status when the order is selected:

"click [data-event-action=selectOrder]": function (event) {
    event.preventDefault();

    if (this.workflow.status === "new") {
      this.workflow.status = "coreOrderCreated";
      Meteor.call("workflow/pushOrderWorkflow", "coreOrderWorkflow", "coreOrderSummary", this._id);
    }
....

I am going through the order steps and I wanted to understand the steps, so far this is the only one that is not making sense to me.
Thanks

Brent Hoover
@zenweasel
Dec 15 2015 13:21
@boboci9 I believe that “new” is supposed to mean “unseen”, so once the order is selected it is no longer “new"
Bogi
@boboci9
Dec 15 2015 13:22
I see thanks, and then is there any difference between "coreOrderCreated" and "coreOrderSummary"? As I see in the coreOrderSummary step the order gets in coreOrderCompleted status at once
Brent Hoover
@zenweasel
Dec 15 2015 13:30
Yes, that’s a good question. I’ve had the same confusion with the order statuses. I’ll have to defer to @aaronjudd who should be awake in a few hours.
I’ll follow up tomorrow my time. Since I am curious as well.
newsiberian
@newsiberian
Dec 15 2015 14:17
@mikemurray, Hi, please look at a typo: accounts/client/templates/addressBook/edit/edit.htmlline 4: data-i18n="addressBookEdit.addAddress" => data-i18n="addressBookEdit.editAddress"
Aaron Judd
@aaronjudd
Dec 15 2015 15:55
@boboci9 #570 mentions this, at least from the UI perspective, we’re going to refine those steps down. We just discussed yesterday what they should be updated to (and how some advanced/search filtering might look as well).
coreOrderCreated is a order that has been touched, but (so not new anymore), an order can be have split shipments (although the UI doesn’t accommodate this yet, we’re working on it), so you could have an order summary status where it’s partially completed. happens automatically now because the UI isn’t supporting the split orders yet.
Bogi
@boboci9
Dec 15 2015 16:28
ok I see, thank you, and when will an order be considered cancelled? I see you will take it out but I need that too so I can add the same logic in my app so it will be compatible when you add it back
Aaron Judd
@aaronjudd
Dec 15 2015 16:30
note that all items have a workflow status as well -> so that the order can be split,etc.. honestly I’m not certain how the cancelled status is working right now @mikemurray? I think we’d need to look at each item and see that they’re all cancelled before declaring the orders status cancelled.
Bogi
@boboci9
Dec 15 2015 16:42
I see so order items can be returned/cancelled just not with the current UI I see, and do you have a plan on how this will be implemented in the schema?
Mike Murray
@mikemurray
Dec 15 2015 17:41
@newsiberian Thanks!
munireusa
@munireusa
Dec 15 2015 21:45
Judd contact me when you can please. thanks
Aaron Judd
@aaronjudd
Dec 15 2015 21:46
@munireusa sent you a direct message.
the-modulus
@the-modulus
Dec 15 2015 22:11
How can you create an admin if you forgot yours?
Aaron Judd
@aaronjudd
Dec 15 2015 22:24
delete all your admin from users and restart (or if you don’t care about data, meteor reset will work)
the-modulus
@the-modulus
Dec 15 2015 22:32
thanks @aaronjudd what if I want to set a new user as admin?
the-modulus
@the-modulus
Dec 15 2015 23:03
I ended up just updated the default admin email: db.users.update( { 'emails.address': "defaultemail@localhost"}, { $set: { 'emails.0.address': 'brutus@example.com' } })