One thing that is kind of annoying is you can't manage multiple subscriptions from one user account.
Why not? Make subscription a many to one and code it up. Easy as pie.
https://github.com/laravel/spark
Getting quite a few Vue errors so far, but I'm sure those will get sorted.
Very exciting.
Getting quite a few Vue errors so far, but I'm sure those will get sorted.
@vkronlein It is an alpha, and may even change in the next 24 hours and that was the “official” release date Taylor tweeted.
I have a lot of problems as well, but most if can be fixed really quickly so I just wait till the full release!
As usual, I failed to follow the directions. I didn't uncomment the plans, as soon as I did that, all went perfectly.
It does concern me that making the payment and registration takes quite a long time to complete, but I imagine that will get better. A little bit too much javascript for me though to be honest. I'm gonna keep my current build on the project I'm working on, I don't have time to recreate all the work I've done so far in javascript to make it work in this.
Maybe next time.
The resources/js/spark/components.js file contains the statements to load some common Spark Vue components. Vue is the JavaScript framework used by the Spark registration and settings screens.
You are free to change any of these require statements to load your own Vue component for a given screen. Most likely, you will want to copy the original component as a starting point for your customization.
Ok, are we stuck with VueJS or can we use a framework of choice? (or even go back to JQuery) I understand that this is opinionated, but it should allow the user to change JavaScript frameworks / implementations. It's a bad idea if you have to stick with VueJS, because learning yet another JavaScript Framework might be a nightmare for people.
Why should you go for jQuery if VueJS is way better? Its the same if you say give the user the option to choose between php or ruby for spark ..
And VueJS is really simple and easy to learn. There is no mountain learning curve like AngularJS or something like this.
but ... of course you could write your own jQuery without VueJS. Its up to you.
I am talking in general, not saying that VueJS is bad or anything, I can learn it but what about other people who are not ready yet to get into frameworks?
And Spark is part of Laravel so no point to offer it in other languages.
More and more curious to see if this will be useful or not.
Ok, are we stuck with VueJS or can we use a framework of choice? (or even go back to JQuery) I understand that this is opinionated, but it should allow the user to change JavaScript frameworks / implementations. It's a bad idea if you have to stick with VueJS, because learning yet another JavaScript Framework might be a nightmare for people.
@Ruffles It is an opinionated package. It’s opinionated in that Taylor choose to use VueJS for the front-end just like he choose to use Laravel for the back-end. It’s like a CakePHP developer wading in and being upset they’re stuck with having to use Laravel if they want to use Spark.
As the documentation says, you are free to copy the resources (views, assets) into your application and do what you wish with them. If that includes ripping out the VueJS stuff, then that’s your prerogative.
is anyone else getting Method [callCustomValidator] does not exist. while registration? or am i doing something wrong?
@hardsshah no issues here with registering and invites, but make sure you're using the master version (change composer.json version requirement to dev-master for spark). There were some changes by me and a few other people that fix some issues with registrations and invites. Also, should you still have issues after doing that, it's advisable to post a new question for that.
PayPal Advanced implements recurring billing, subscription billing. I am actually working on an extension for that. Hopefully to have it an alpha release for Laravel by next month.
PayPal Advanced implements recurring billing, subscription billing. I am actually working on an extension for that. Hopefully to have it an alpha release for Laravel by next month.
Before you put too much work into that, look at the Paypal REST API.
Payments Advanced is one of Paypal's "classic" APIs. They are replacing all of these with the REST API.
Payments Advanced also is not available outside the US and Canada and costs $5 a month, whereas the REST API is free and available everywhere.
The downside to the REST API is that they are still developing implementations (e.g. for PHP), but they seem to be in a decent state now.
It would be great to have implementation of BrainTree (has also awesome API) as Stripe mainly works in the US. This "small" change would make a huge difference. Also they don't change anything for the first $50.000 and this is awesome for startups.
I see a lot of what looks to me like complaining in this thread. This seems analogous to me with having Grant Elliot prepare a world-class free lunch for you then, while gorging yourself on it, making improvement suggestions that you may not have the experience or skills to implement.
If you have a desire, need or preference to use something like an alternate payment gateway or javascript framework, I suggest forking the laravel/spark repo and providing alternate implementations to the community would be the super-coolest way to go about getting it. If that's too much work maybe you should consider learning the package more deeply or learning to implement all this stuff yourself; which is hard damn work, but great experience. I'm not pointing any fingers at individuals, I'm just offering a different way to look at it. A grateful way. I started hacking on it yesterday and I think it is a fantastic piece of scaffolding that is going to save me dozens if not a hundred or more hours in the next year. It feels like Alton Brown made me Thanksgiving Dinner, and I am not going to complain about doing the dishes.
Does anyone know if Spark will allow a one off payment followed by a recurring monthly subscription of a different value.
E.g - when a customer registers for an account they will pay an initial cost of $199, and then $49 each month after that.
Thanks in advance.
@Mike With Spark using Stripe under the hood, I guess that would depend on whether Stripe supports subscriptions like that.
@martinbean thanks for the reply. I will take a look at the stripe documentation to see if the functionality exists.
I guess my question was aimed more towards spark to check if anyone has set up subscriptions in this way. I understand the spark API allows you to configure your subscriptions and these are automatically handled in the registration page.
I will dig a little deeper into the code to check if it is available.
Thanks again
@Mike I remember seeing a video where Taylor showed a first month discount being applied (I think!) - possibly the laracon.eu talk.
yeah it was the Laracon.eu talk where taylor showed spark. But it was also recoreded from the laracon.us -> https://www.youtube.com/watch?v=uOU_N8PNOD8
Spark looks very promosing even now being in alpha. Does anyone have some transparency on the release schedule and when it might make sense to start using it for a production project?
@KaiH No - no one.
The Vue component 'spark-simple-registration-screen' is throwing an error when I try and go to the 'register' screen. I get a blank page. The javascript error is : Uncaught ReferenceError: URI is not defined
Anyone know how to get past this? I'm not familiar enough with Vue yet to figure out the issue/solution.
Thanks
@freedomfflow Do bear in mind Spark is still officially in alpha.
@jananderson a point well made. I'm enjoying hacking away at Spark. It's been a great intro into VueJS (Jeff's videos are good but looking for intermediate stuff) and great to see how Taylor's mind works when he builds apps.
There were some annoyances on my part that I couldn't just "mould" Spark around my idea. But so what? There's a good 70% that I can use or learn from or fork from to complete my app.
bump. Spark! Spark! Spark! For Christmas!
Is spark active? Usable in production I should say.. It has been in "This is an alpha, experimental release" phase for quite some time. Personally have been waiting for it to be committed to the laravel docs before even playing with it.
Nevermind, saw other threads quoting Otwel, that it isnt ready. :/
Please or to participate in this conversation.