These are chat archives for reactioncommerce/reaction

23rd
Apr 2017
Janus Reith
@janus-reith
Apr 23 2017 08:57
@aviadbd totally agree, it was confusing for me aswell. I ran docker build -t customname in the reaction folder, then I replace reactioncommerce:latest in the docker-compose file with customname, and run docker-compose up -d .
Dmitry
@dshitik
Apr 23 2017 10:03
Hi, do you plan in the near future to implement the support of PayPal Payflow getway on API SOAP?
So that you can be allowed to pay by card. Not all countries support restfull API.
Janus Reith
@janus-reith
Apr 23 2017 10:36

Reaching out for help on this again, since nobody answered it so far:
I created a plugin with custom layout, including a custom footer.

It is displayed fine everywhere, except for the Product Detail Page.
When i insepct it in chrome, it also just shows:
<!-- begin layoutFooter -->
<!-- end layoutFooter -->

Is there something else I have to out in my register.js?
Or what else would I need to overwrite?

I also tried a custom pdp template based on product-detail-simple, but appareantly it just defines the main part, not header, footer, etc...
Im a bit lost

Altough this is not the was I want to implement it,
I even tried to edit the register.js of the included product-variant plugin and set the layoutFooter to my custom template there - no effect.
I also tried several reaction resets between the steps
*way
Janus Reith
@janus-reith
Apr 23 2017 13:07

Hmm, guess I wont get feedback on this...

Another question:
If I want to add custom fields to the product edit view on the right, what would be best practice?
As far as I understand, it is defined in the product-admin.

How can I alter this in a plugin, or even better, define a different customized version of that that is only used for one pdp template I created?

Janus Reith
@janus-reith
Apr 23 2017 15:58
Okay, created a copy of product-admin, it works and I can alter it, but it is automatically replacing the product edit view for all products, no mater which pdp template..
Spencer Norman
@spencern
Apr 23 2017 17:55

@janus-reith regarding the footer, it may not be displaying on the PDP because the register.js specifies an empty footer.

https://github.com/reactioncommerce/reaction/blob/master/imports/plugins/included/product-detail-simple/register.js#L23

lukasbash
@lukasbash
Apr 23 2017 18:39
Hey guys, quick question. Is it possible to customize the name of the running application? The one that is present on the layoutHeader bar. I did not find any information about this kind of customizing in your documentation.
Spencer Norman
@spencern
Apr 23 2017 18:41
@lukasbash - you can customize that from the admin dashboard in the “Shop” section. Just change the name.
lukasbash
@lukasbash
Apr 23 2017 18:49
Thanks for the fast reply, I am just following the tutorial, how can I get to the admin dashboard?
Spencer Norman
@spencern
Apr 23 2017 18:49
Once you’ve started the app, login as the admin
lukasbash
@lukasbash
Apr 23 2017 18:50
LOL, too obvious, thanks a lot !
Spencer Norman
@spencern
Apr 23 2017 18:50
:+1:
Priyabrata Chatterjee
@priyochatterjee08
Apr 23 2017 18:51
I did not save my username password . How to find it
Spencer Norman
@spencern
Apr 23 2017 18:52
If it was randomly generated, you can’t really “find” it - you can generate a new one by running reaction reset - that will nuke your database and reset everything
Priyabrata Chatterjee
@priyochatterjee08
Apr 23 2017 18:53
I have run reaction reset
It says to get out of meteor development mode
Spencer Norman
@spencern
Apr 23 2017 18:54
When you start the app the first time, the admin username and password will be generated and displayed in the console
The better option is to edit the settings/dev.settings.json file
you can specify your username and password in that file and the Reaction will use that whenever starting an app in development
Priyabrata Chatterjee
@priyochatterjee08
Apr 23 2017 18:58
@spencern thanks
Chandler Freeman
@Stat1c14
Apr 23 2017 19:14
Quick customization question for you guys. If I wanted to change the header bar to display my logo instead, what file would I override in my plugin to change that?
Spencer Norman
@spencern
Apr 23 2017 19:14
Do you mean the favicon? Or the app logo?
Chandler Freeman
@Stat1c14
Apr 23 2017 19:21
Both, actually haha. The default is for the text to display Reaction in the upper left-hand corner, I need that to be my logo instead
xuanvinhvu
@xuanvinhvu
Apr 23 2017 19:53
is there an eash way to export products from shopify into reaction?
I converted the shopify csv export into json and now I’m modifying the key value pairs. It’s pretty tedious, just hoping there is an easier way :)
Spencer Norman
@spencern
Apr 23 2017 19:59
@Stat1c14 I think you’d just need to use your own logo and replace this template here from a plugin:
https://github.com/reactioncommerce/reaction/blob/master/imports/plugins/core/layout/client/templates/layout/header/brand.html
That being said, we’re in the midst of converting everything to React, so this may change shortly
Spencer Norman
@spencern
Apr 23 2017 20:07
@xuanvinhvu - we’ve got a Shopify importer on our roadmap, but no ETA right now. If you build anything let us know! I know it’s tedius right now
xuanvinhvu
@xuanvinhvu
Apr 23 2017 20:07
thats good to know!
Janus Reith
@janus-reith
Apr 23 2017 20:10
@spencern I creadted a custom pdp template plugin based on product-detail-simple and put the footer into register.js
So that is probably not the reason. The same footer works on other pages
I'll give it a try and directly modify register.js of product-detatail-simple to my custom tempalte
*template
Spencer Norman
@spencern
Apr 23 2017 20:14
Check in the db for where the layouts get registered (in Shops) (db.Shops.findOne().layout) from meteor mongo
and see if your template has the footer there too
Janus Reith
@janus-reith
Apr 23 2017 20:28
Tried to directly put in my footer in the product-detail-simple and did a db reset - no luck
Janus Reith
@janus-reith
Apr 23 2017 20:33
Checked the db, which entry do I have to look for?
The one that with "template" : "productDetailSimple" has the footer set there, but one with "template" : "productDetail" doesnt have an footer entry there. Both use coreProductWorkflow.
This is the whole output:
{
"layout" : "coreLayoutCustom",
"workflow" : "coreAccountsWorkflow",
"collection" : "Accounts",
"theme" : "default",
"enabled" : true,
"structure" : {
"template" : "accountsDashboard",
"layoutHeader" : "layoutHeader",
"notFound" : "notFound",
"dashboardHeader" : "dashboardHeader",
"adminControlsFooter" : "adminControlsFooter"
},
"priority" : 999,
"position" : 1
},
{
"layout" : "coreLayoutCustom",
"workflow" : "coreCartWorkflow",
"collection" : "Cart",
"theme" : "default",
"enabled" : true,
"structure" : {
"template" : "cartCheckout",
"layoutHeader" : "checkoutHeader",
"notFound" : "notFound",
"dashboardControls" : "dashboardControls",
"adminControlsFooter" : "adminControlsFooter"
},
"priority" : 999,
"position" : 1
},
{
"layout" : "coreLayoutCustom",
"workflow" : "coreDashboardWorkflow",
"theme" : "default",
"enabled" : true,
"structure" : {
"template" : "dashboardPackages",
"layoutHeader" : "layoutHeader",
"notFound" : "notFound",
"dashboardHeader" : "dashboardHeader",
"dashboardControls" : "dashboardControls",
"dashboardHeaderControls" : "dashboardHeaderControls",
"adminControlsFooter" : "adminControlsFooter"
},
"priority" : 999,
"position" : 1
},
{
"layout" : "coreLayoutCustom",
"workflow" : "coreEmailWorkflow",
"theme" : "default",
"enabled" : true,
"structure" : {
"template" : "email",
"layoutHeader" : "layoutHeader",
"notFound" : "notFound",
"dashboardHeader" : "dashboardHeader",
"dashboardControls" : "dashboardControls",
"adminControlsFooter" : "adminControlsFooter"
},
"priority" : 999,
"position" : 1
},
{
"layout" : "coreLayoutCustom",
"workflow" : "coreOrderWorkflow",
"collection" : "Orders",
"theme" : "default",
"enabled" : true,
"structure" : {
"template" : "orders",
"layoutHeader" : "layoutHeader",
"layoutFooter" : "layoutFooter",
"notFound" : "notFound",
"dashboardHeader" : "dashboardHeader",
"dashboardHeaderControls" : "orderListFilters",
"dashboardControls" : "dashboardControls",
"adminControlsFooter" : "adminControlsFooter"
},
"priority" : 999,
"position" : 1
},
{
"layout" : "coreLayoutCustom",
"workflow" : "coreOrderPrintWorkflow",
"collection" : "Orders",
"enabled" : true,
"structure" : {
"template" : "completedPDFLayout",
"layoutHeader" : "layoutHeader",
"layoutFooter" : "layoutFooter"
},
"priority" : 999,
"position" : 1
},
{
"layout" : "coreLayoutCustom",
"workflow" : "coreOrderShipmentWorkflow",
"collection" : "Orders",
"theme" : "default",
"enabled" : true,
"priority" : 999,
"position" : 1
},
{
"layout" : "coreLayoutCustom",
"workflow" : "coreUIWorkflow",
"collection" : "Themes",
"theme" : "default",
"enabled" : true,
"structure" : {
"template" : "uiDashboard",
"layoutHeader" : "layoutHeader",
"notFound" : "notFound",
"dashboardHeader" : "dashboardHeader",
"adminControlsFooter" : "adminControlsFooter"
},
"priority" : 999,
"position" : 1
},
{
"layout" : "coreLayoutCustom",
"workflow" : "coreInventoryWorkflow",
"collection" : "Inventory",
"theme" : "default",
"enabled" : true,
"priority" : 999,
"position" : 1
},
{
"layout" : "coreLayoutCustom",
"workflow" : "coreProductWorkflow",
"collection" : "Products",
"theme" : "default",
"enabled" : true,
"structure" : {
"template" : "productDetailSimple",
"layoutHeader" : "layoutHeader",
"layoutFooter" : "layoutFooterCustom",
"notFound" : "productNotFound",
"dashboardHeader" : "productDetailSimpleToolbar",
"dashboardControls" : "productDetailDashboardControls",
"adminControlsFooter" : "adminControlsFooter"
},
"priority" : 999,
"position" : 1
},
{
"layout" : "coreLayoutCustom",
"workflow" : "coreProductWorkflow",
"collection" : "Products",
"theme" : "default",
"enabled" : true,
"structure" : {
"template" : "productDetail",
"layoutHeader" : "layoutHeader",
"notFound" : "productNotFound",
"dashboardHeader" : "productDetai
Janus Reith
@janus-reith
Apr 23 2017 20:41
In a running instance, I replaced all entrys in the Shops Collection to have "layoutFooter" : "layoutFooterCustom" - Both those that had just layoutFooter set and those that didn't have that var at all - Still no change
Chandler Freeman
@Stat1c14
Apr 23 2017 20:49
@spencern Thanks for the help. How would I go about overriding that template from the plugin? The documentation contains information on how to add templates, but not on how to override existing ones
xuanvinhvu
@xuanvinhvu
Apr 23 2017 20:51
where can I find reaction log file?
Janus Reith
@janus-reith
Apr 23 2017 20:53
@Stat1c14 In order to achieve that, you would't even need to change the template:
In the dashboard on the right, go to shops, there you can upload a custom image that will be displayed in the navbar
Janus Reith
@janus-reith
Apr 23 2017 21:04
@xuanvinhvu As far as I know, the default is only console output. Should be easy to change, see here: https://docs.reactioncommerce.com/reaction-docs/development/logging
Chandler Freeman
@Stat1c14
Apr 23 2017 21:12
@janus-reith Wow, can't believe I missed that. But the text still shows next to the logo. I would also like to know how to modify the default templates via a plugin, for future reference
The lack of documentation on simple modifications like this is perplexing. It seems as though there is a lot of customizability possible with Reaction, but the documentation does a poor job of explaining how to actually perform tasks a developer might want to perform, such as adding menu items, overriding default templates, or adding assets
Chandler Freeman
@Stat1c14
Apr 23 2017 21:17
I would love to contribute to the docs once I figure out the process for these things (I am already pseudo-documenting everything I'm learning)
Janus Reith
@janus-reith
Apr 23 2017 21:19

@Stat1c14 I agree, e.g. I think the customization tutorial is not that self explantory at all.

You could take a look at https://github.com/hydrotik/reaction-hydrotik-plugin/blob/master/client/components/navbar/navbar.html and pick out the necessary parts to customize the navbar

That plugin + the customization tut helped me a bit
Janus Reith
@janus-reith
Apr 23 2017 21:25
But mostly I am still searching the /imports/Plugns
*/import/plugins folder for keywords, and try to find out how everything is connected
Chandler Freeman
@Stat1c14
Apr 23 2017 21:30
@janus-reith That's exactly what I've been doing haha. Good to know I'm not the only one who feels lost trying to navigate through this
Janus Reith
@janus-reith
Apr 23 2017 21:31
a kind of track plan could be helpful, that shows how each integrated plugins are connected to each other, and what makes up which part of what you will be presented with in your webbrowser
Chandler Freeman
@Stat1c14
Apr 23 2017 21:36
Thanks for the project link, by the way. That's a real lifesaver. I started an apparel company not to long ago, and we plan on launching our online store on the 30th. Coming from a NodeJS development background, I figured Reaction would be an easy pick-up-and-run solution. Turns out it's probably the most complex open-source e-commerce solution ever built lol, between Meteor and the Reaction components. Hopefully that repo can get me where I need to be soon
aviadbd
@aviadbd
Apr 23 2017 21:40
@janus-reith Thanks! How did you get your plugins etc into it?
aviadbd
@aviadbd
Apr 23 2017 23:24
@janus-reith Also, I'm getting this at docker build:
[-] Building Meteor application...


Even with METEOR_ALLOW_SUPERUSER or --allow-superuser, permissions in your app
directory will be incorrect if you ever attempt to perform any Meteor tasks as
a normal user. If you need to fix your permissions, run the following command
from the root of your project:

  sudo chown -Rh <username> .meteor/local

/opt/build_scripts/build-meteor.sh: line 30:   116 Killed                  meteor build --directory $APP_BUNDLE_DIR
Brent Hoover
@zenweasel
Apr 23 2017 23:30
@aviadbd Are you running Reaction as root or with sudo?