bguiz

bguiz supports this item

Supported

14 comments found.

I would like to purchase this product, would it be possible to connect this to a parser server?? https://github.com/ParsePlatform/parse-server

Hi,

Yes, indeed it will be possible to connect to a parse server.

The main thing to be aware of is that the parse server is written in expressjs, and this is written in koajs, therefore you will need to shim koajs routes to expressjs routes.

Hope this helps!

Brendan

would you advise me using your older version?

I wouldn’t, the code in the OKAccounts is much improved, and I’ve EZAccounts has been deprecated.

I’d have a go at shimming instead; as you can see they are quite similar:

function helloExpress(req, res, next) { res.send(‘Hello’); }

function *helloKoa() { this.body = ‘Hello’; }

Hope this helps!

Brendan

Hi bguiz, I downloaded the files but I am not seeing the mentioned installation instructions. Any way you can pass them on to me?

Hi,

In okaccounts.zip, you should find the complete set of instructions in the following files: info/index.md, info/install.md, and info/run.md

Alternatively, if you click on the main banner image for this item, you get taken to the documentation in PDF, generated from the above markdown files. For your convenience, here is the direct link: http://pdfsr.com/pdf/okaccounts

HTH, and let me know if you have any more questions!

Thanks, Brendan

W: http://bguiz.com

Would you happen to have an example for native app side that would auth/store session on a mobile side using the API in this application?

Hi again,

Went ahead and did a little more digging, and found that Stripe has changed the structure of its `customer` data type. See the `Example Response` from the create customer API: https://stripe.com/docs/api/node#create_customer

The card gets returned as `customer.sources.data[someIndex]`, whereas previously it was `customer.cards.data[someIndex]`. So something between our account settings on stripe.com, our installed dependencies versions, and our config values – My gut feel is that one of those differs, and that allows me to access the previous customer structure, whereas you get the new customer structure.

So, if you could, please try replacing `stripeAccount.cards` with `stripeAccount.sources` within `lib/account/payment-make.js` (4 occurrences). Let me know if this fixes things for you!

HTH, Brendan

W: http://bguiz.com

I dont have access to email you, i changed the 4 instances of stripeAccount.cards to stripeAccount.sources but still fails. However the first test that failed previously was failing with “AssertionError: expected 500 to equal 201” but now fails with “AssertionError: expected undefined to be an object” the second two failing tests still fail with the same reasons.

Hi,

OK, I’ll need to take a look at this. Use the form on this page: http://codecanyon.net/item/okaccounts-for-nodejs/14442764/support ... and we’ll take it from there.

Thanks, Brendan

W: http://bguiz.com

I am submitting this form the page you asked me to but it says it’s just going to post it as a comment… lets see :)

This item’s author support through comments.

Hmm, I have got to figure out which setting controls this. Currently the options I am given for support are just “Yes” and “No”.

In any case, I’m gonna DM you on twitter, looks like I have @medoix on my list.

We’re is the module, my zip just have instructions but not clear to install package and start to work with it.

Alright, I have followed this up with Envato, and in case you want to follow up with them yourself, the support ticket is #498225. For now, I’ll have to wait for them to respond.

Thx all working like a charm, great work and thx for the prompt response

Excellent! Happy coding!

Are subscriptions included in this abstraction? I have a basics online subscription web app that I would like to handle through this. Or do I have to write all that out via stripe?

Hi Samcus,

I assume you are referring to this: https://stripe.com/subscriptions

If so, unfortunately not, there is not any current support for recurring payments, only regular payments.

That being said, it should be fairly easy to add though, because the code is very thoroughly documented, and thoroughly tested; as prior customers can attest to – try asking @medoix !

Alternatively, if you add some integration tests to describe the functionality you are after – using the existing integration tests for regular payments as a reference – I’ll have a crack at implementing recurring payments.

HTH, Brendan

http://bguiz.com

Hi there,

I’m having trouble getting OKAccounts up and running, when I run the tests pass but whenever I run the server, with npm run start, on localhost with ports 3000 or 4000 (for ssl) I goto the browser and postman and I get a “Not found” and 404, I am on node v6.x and running mongo v3.x. I did switch to the recommended node v4.x and mongo 2.4 but same thing still.

Any help would be appreciated.

Hi Adam,

If the tests pass, the server should run. In order to diagnose this I’ll need a bit more info:

What is the exact URL you’re passing to the browser. For postman also let me know the HTTP verb, request body, and request headers. Just for HTTP for now will do (no need for HTTPS just yet)

Thanks,

Brendan

Awesome work, I like it!

demo not available

This comment is currently being reviewed.

x326

x326 Purchased

Hi, I have just bought OKAccounts. Do you have installation instructions for a Windows deployment?

The provided instructions for installation apply to both *NIX systems and Windows. Is there any particular section you are having trouble with?

Is the system still receiving support/updates? I noticed the last updated date was 16 May 16.. Please let me know asap.. Need to recommend this to someone..

Yes, this is indeed still supported.

deamoner

deamoner Purchased

I’m trying to get the server up and running on c9 for development. It won’t run seems to get an access issue from using default 0.0.0.0 and port 80 which I don’t think is how the containers work on c9. Any idea what I can do to fix this?

Hi daemoner,

I’m unfamiliar with c9, and a quick google yielded this: https://docs.c9.io/docs/deploying-via-cli

I can’t say for sure, but my first guess would be that your cloud provider does not allow you to bind to any port number, and instead requires you to bind only to the port number that they specify. Reads their documentation to see what they have to say regarding this. A common pattern is that they specify a PORT environment variable, and you simply use that.

If this is indeed the root cause, you will need a small change to make this work. Checked the included documentation for full instructions, I’ll just highlight the relevant part here:

Look in Install -> Configuration Settings -> and follow the instructions for setting up a config file. Next Change the value for config.server.http.port to the value that your hosting provider expects.

HTH!

Brendan

... Looks like I can do you one better:

I’m looking at the c9.io docs, and found this age: https://docs.c9.io/docs/run-an-application

Under “Run an Application” -> “Available ports on a hosted Cloud9 workspace”, it says:

Please note that 8080, 8081, and 8082 are the only available ports on a hosted Cloud9 workspace.

It looks like 8080 is bound to 80, and 8081 and 8082 are bound to the same numbers.

HTH!

Brendan

deamoner

deamoner Purchased

So is there no pre built simplisitic actual usage of the api for examples?

Hi again daemoner!

Indeed, the bundled code is a working server. It has built in APIs for authentication, authorisation, and payments; and the idea is that you simply have to add any other APIs that you need for your app/ business to build on top of that.

There is high level documentation bundled as a PDF file. There is also code usage documentation inline in the code, in JSDoc syntax: http://usejsdoc.org/about-getting-started.html

HTH!

Brendan

BTW, would you happen to be @Matt_JDavis on twitter?

by
by
by
by
by
by