These are chat archives for reactioncommerce/reaction
I have this exported in my .profile
export REACTION_USER="display name" export REACTION_AUTH="some_password" export REACTION_EMAIL="email@example.com"
PACKAGES_DIR="" REACTION_USER="" REACTION_AUTH="" REACTION_EMAIL="” meteorand it worked..
reaction-core, maybe you need to pull that as well (although the most recently published packages work, hence my PACKAGES_DIR test)
bin/clone-packages.shif you want to really get all the most recent stuff to see if that fixes the issue. (beware: this is the heavy stick approach)
// create default admin user ReactionRegistry.createDefaultAdminUser();runs after the package entries are loaded in
developmentbranch, I’ve updated the fixtures load order to load the admin user earlier. This way there shouldn’t be any problems if a package load fails.
Provides: ‘’to an existing package, and that did cause the error.
/dashboardand editing integrated directly into frontend
Product.meta data: should have a title set to Example Productand
Router.Index.meta data: should have a title set to Index
waitForElementhelper about 1/2 through writing these… in many cases that solves the issues
I'm on the latest git pull so far.
Error is "Unable to send invitation email. " from dashboard/accounts. I don't see errors in the server console.
The emails from my test app (basically the app you get from meteor create, plus the mail code added in) is sending normally. Both apps have the same process.env.MAIL_URL, so I'm pretty sure there's no issues with ports getting blocked. (no port is specified in the SMTP string)
isDebug: debugis the more verbose version, I suspect you won’t get much more info there though