Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook



The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic

Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.

If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.

Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.

Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

Stripe and cURL

  • Filter
  • Time
  • Show
Clear All
new posts

  • Stripe and cURL

    I wanted to put this here as I see a lot of users who I know will probably show me exactly what I am missing (though it doesn't pertain to the DocuSign API but rather Stripe)..

    I have been very successful in implementing using stripe for subscriptions using Alphas cURL genie but today I saw 5 different people try to subscribe (I send myself an email when they click the button that on my site opens the a5w page that has the stripe checkout html on it so I know someone attempted to subscribe) but I never got an email saying their subscription was set up (which occurs when they submit the stripe checkout and the token is sent to another a5w page that contains all the cURL code and xBasic that updates my database). The issue I am running into is with the below xBasic generated by the genie:

    flag_1 = ce.Exec()
    if flag_1 then
            dim headers as c
    	dim contents as c
    	dim response as p
    	headers = cf_1.GetHeaders()
    	contents = cf_1.GetContent()
            response = json_parse(contents)
    	errors = ce.error()
    end if
    I expected that flag would be true if the call succeeded and the card was charged and false if it failed and there was an error from stripe (which would end up in ce.error()), however instead the flag_1 returns true no matter what if there was an error (i.e. card declined). I'm fine with this but the problem is the returned JSON (and resulting dot variable in response) from stripe doesn't always have an error property so I am trying to figure out how I can check if the error property exists so that if it does I can show an error to the user and if it doesn't I can tell the user their card was charged. If the error property returned as null when a successful charge occurred I would be fine but the issue I run into is when there is an error my error checking works but when there isn't an error my xBasic fails because it can't find the "response.error" property. I thought I might be able to use variable_exists() but this didn't work so any ideas on what I can do here?

  • #2
    Re: cURL Xbasic Object

    Josh... I would start a new thread on this. It's very different stuff.

    flag_1 returns true because the cURL call itself didn't fail. It was a good call. Put some garbage into some cURL property so that it fails and you'll catch the else section. Whether or not what was suppose to happen actually happened is another matter. You heed to examine contents for what happened on the Stripe end.

    Further... who is sending the email? You... or Stripe?

    Lastly, why use cURL? Stripe was already implemented on the Javascript and NodeJS side. It works and is lovely to use.


    • #3
      Re: cURL Xbasic Object

      I finally found some xBasic information on how to look at a dot variable and see if a property exists (specifically the prop_valid() function). With this I can check if the "error" property is inside my response dot variable so all is well now (wasn't easy finding that function though but sure glad it exists)!

      I'm using cURL because all my attempts at using node.js failed miserably and I wasn't sure the best way to debug the node.js (also I would have had to write the node.js files myself where the cURL genie created the code for me and I could just tweak it to work for my use case). Is there a reason to use node.js over cURL that I am missing?

      Also, the emails were coming from alpha (i.e. I was using them to alert me of what was going on) though this is moot now that I figured out how to check the dot variable. I do appreciate your quick response though!