Installing Reflio affiliate manager
I am trying to install Reflio to handle my affiliate deals. In their walkthrough, in step 6 they ask to install the following JS when a user signs up:
I am a bit lost in where to place this, since the sign up is a bit abstracted with the Google OAuth.
24 Replies
Hi @Ricardo Batista. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
I'm sorry, but as an AI assistant for Wasp, a Rails-like framework for React, Node.js, and Prisma, I can only provide information related to Wasp. I don't have the necessary information to guide you on installing Reflio affiliate manager. I recommend reaching out to Reflio's support or checking their documentation for more detailed instructions.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @Ricardo Batista, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?
Auth hooks are still in progress (which will enabled executing backend code before/after the signup).
One thing I could suggest here is going with a client based solution.
For example, on the Homepage or on the page where the user is redirected to after the login - do the following:
- make sure you have some sort of a field on the user
didSignUpForReflio
- check if it's true or false by using a query that checks for the current user in the DB
- if it's false, call the code to signup await Reflio.signup('[email protected]')
- use an action to set the value of didSignUpForReflio to trueHooks are coming in a couple of weeks probably though, and they will make this much easier!
Ok, will wait for the hooks!
What is the best way to stay updated?
Just hang around here 🙂 we publish updates in #💬general
@Ricardo Batista what you could try to do to stay updated is also watching for new releases at https://github.com/wasp-lang/wasp/releases . Github says here https://github.blog/changelog/2018-11-27-watch-releases/ you can subscribe to get notifications from the repo exclusively for new releases. I haven't set that up myself, but that is probably the most efficient way. We usually produce a new release for Wasp every couple of months, so that is probably a perfect amount of "noise" to stay updated with new versions of Wasp.
GitHub
Releases · wasp-lang/wasp
The fastest way to develop full-stack web apps with React & Node.js. - wasp-lang/wasp
admin
The GitHub Blog
Watch releases
You can now limit repository notifications exclusively to releases. Receive notifications when new releases are published in a repository without receiving notifications about other updates and conversations. Learn more about release notifications
Thanks!
Wohooo @Ricardo Batista, you just became a Waspeteer level 5!
@miho any news on this one?
@Ricardo Batista is that regarding the hooks?
So they are super close to being merged, you can see the PR here: https://github.com/wasp-lang/wasp/pull/1993 .
But, then we also need to cut the release: we added quite some stuff to Wasp so we will have to do some thorough QA + we want to make sure some bigger featuers also make the cut. So realistically, the new release, 0.14, with hooks included, will be out most likely in 4 weeks.
Gotcha, thanks for the update!
@kapa.ai do I also need the upcoming PR to send a welcome email on signup?
Let me check the knowledge base for you. One moment! :books:
----------------------
Based on the information provided in the knowledge sources, it seems that the Wasp framework does not currently have built-in support for sending welcome emails upon user signup. However, there is a discussion about adding email functionality in the future (source (https://github.com/wasp-lang/wasp/issues/691)).
In the meantime, you can create a custom sign-up action to send a welcome email. This would involve using an external service to send the email. You can find an example of how to create a custom sign-up action in the Wasp documentation (https://wasp-lang.dev/docs/auth/email#creating-a-custom-sign-up-action).
Please note that this information is based on the current state of Wasp and may change in the future. Always refer to the latest Wasp documentation for the most accurate information.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @Ricardo Batista, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?
Auth hooks have been merged, but hey are going to be released next month 🙂 we are doing some other stuff as well that we want to include in the release
@miho on a separate note, but in the same topic: I need to implement a Google refresh token taking advantage of this auth flow. This will only be possible when the Auth hooks are released, correct? Right now I can't seem to access the return of the OAuth process 😦
Yep, you'll be able to get the access token that we received on signup, but we'll upgrade it in
0.14.1 to include the access and refresh tokens on login as well 😄Hum, just to be clear: right now I cannot access the refresh token, correct? But when you guys release, I will be able to do so, correct?
You'll be able to access the access token on signup on release of 0.14.0, but we'll quickly release a new minor release (0.14.1) which would contain code related to the refresh token.
So, you'll wait for a us until July, but then you'll wait a few days more 😄 Hopefully you're able to wait that long 🙈
Doing things this way enables to focus on finishing up major things for 0.14.0 related to Prisma
man, don't worry with that - I fully understand!
This situation blocks one feature that I want to release, but I can buy time and release some others 💪
@miho thanks for the 0.14.0 😄
When are you planning to launch 0.14.1 (with the refresh token)?
It's hard to say right now, we are going to plan out the upcoming sprint next and then see what we want to include in
0.14.1 and when we will release it 🙂 I'll be prioritising the hooks work for sure. And since it's a minor release, it should be faster to go out.
Have you tried using the access token so far?Yes, so far so good with the
access token 👏Noice! I'm glad it works for you 🙂
hey @miho any plans for this? I have a few users already churning because I can't deploy a fix that depends on the
refresh token 😦Hey @Ricardo Batista sorry to hear that. We are working on the refresh token impl right now and it's in review: https://github.com/wasp-lang/wasp/pull/2212
I can't really tell you when it will be released, but we'll try to make it happen soon!
GitHub
Refresh token impl by infomiho · Pull Request #2212 · wasp-lang/wasp
Closes #2124
What was done
Moved init of OAuth clients (google, github, discord and keycloak) to the SDK so users can also import them and use them
These clients are needed to refresh auth tokens...
Thanks for the quick reply!