I was hoping someone could give any advice on my situation. I am trying to build a website that will be used to sell magazine (one off issues and subscription), and to publish articles. The website also needs to be able to support authentication of users so visitors can sign up to the website to have access to member-only articles, and for people with subscription to be able to review their subscription information if possible. I have been looking at different integrations with Webflow to see what would be the best solution and so far here is what i’ve tried:
In terms of authentication, I have used Firebase (thanks to the tutorial by @jasondark - thank you for those), and it was working great apart from two key issues:
we are having issue to add custom fields to the sign up process (the information was submitted but would not be remembered in firebase, and trying to link it with firestore is proving a bit tricky)
we also found no easy way to create a rule to make sure that member-only article (flagged by a switch in the article cms) would only be seen by users that are logged in.
To counter those issues, we’ve started looking at Memberstack, and so far this is looking like a great option considering that we can add all the custom fields that we need, and that there are ways to hide member-only content in quite a straight forward way.
In regards to the shop, we are currently using foxy, which has been great and we’ve been able to set up products and subscription. However the main issue now is being able to link it to the authentication process (in Memberstack, or others if you have any other recommendations) to make sure that users with subscriptions can have a profile page with all their info, and the ability to change their payment details etc.
So my question really is do you have any recommendations for integrations or ways to be able to do this?
You may want to engage the Memberstack.io team and look at the Foxy.io API. They may have a recent project where this has come up before.
You have a rather complex use case for Webflow. You may discover that you will need to create a middleware app that bridges the chosen tools. Honestly, a Webflow hosted site would not have been my choice for this, since you really need server side application logic to create a seamless experience.
That depends on programming languages you or your developer(s) support. If you were well versed in PHP, I would suggest you look at processwire.com CMS/CMF. Everything you would need for this type of site is native to the core API in Processwire and Foxy integration is very common. You could skin your site with Webflow as well.
No we haven’t tried processwire, our development team is tied over at the moment so we’re trying to do as much without too much development.
At the moment we have the sign up on one site handled by Memberstack, and the shop handled by Foxy - but the two aren’t merging.
We know it is possible because of the way they both work (with custom attributes to be added to your content, and there is the possibility to link them together) However because it requires custom development to be able to change the foxy template to integrate the custom attributes to the field, and introduce the field needed to create a sign up form, we haven’t gotten to that point in the website yet.
We’re getting the shop and the sign up both to be working on their own first
No at the moment they are not linked however both have zapier integrations, so i’m waiting for Memberstack to add a new action of “add new member” to be able to link them together.
Hi all.
Our new customer portal / pay gate feature for Webflow is about to go into private beta. We have a more official announcement coming soon, but if you’d like to apply for private beta access, please fill out this short form: Foxy Beta Access
Hi Josh (@foxy) ,
is the private beta comment above still valid or has it moved past beta. We use alternatives for gated content projects but have had Foxy on the list to test for various projects (e-comm, subscription and gated content) for quite some time. Maybe now is that time?
Hi @Fathom.
Sorry for the late reply. It’s still in private beta, but we’ve got dozens of live stores using it, have released many improvements, multiple new features, and it just keeps getting better. We’d love to have you try Foxy. Please let us know if we can help with anything.
Hi Josh (@foxy) ,
No prob with delayed reply. Yes, we’d to try it in private beta as soon as possible. We have a gated content product in the mid to late stages of development with an alternative provider but I would like to try Foxy on a duplicated version as it seems likely to offer better reporting and flexibility. I’ve filled out the private beta form - is approval project-by-project or can we try any build once approved?
