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

Announcement

Collapse

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

Ajax Callback Session Variable and Debugging

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Ajax Callback Session Variable and Debugging

    Two part question:

    1)How do i use a session variable in the ajax callback page? I have variable session.__protected__varname that i use on each page. i need to use this variable to add records to a table, however i cannot seem to access the variable from the callback page.

    2) What is the best way to debug an ".ajax.a5w" page? It seems as though the only way i know something is wrong with a page is if nothing happens when i run it. e.g. Hit button "Submit", on page.a5w, that calls page.ajax.a5w. I should see a return of A or B no matter what, however I only know there is a problem if i see nothing.

    #2
    Re: Ajax Callback Session Variable and Debugging

    I always have a couple rounds of debugging on making ajax callback pages. Any little error causes it to fail (appropriately).

    Here is what I do, and it always comes down to isolating the problem:

    I put save_to_file("got here", "c:\test.txt") at the top of the callback page just to see if it was called at all.

    Then I change it to save_to_file(id, "c:\test.txt") assuming I am trying to pass a variable named id. At this point it often fails because I have an error on the calling side with my button or link.

    Here is an example of a button with a callback. Notice I have a variable named "var". That's just a dummy so I can test that the value got over to my callback page.

    Buy_render = "<input name=\"setvar\" type=\"button\" value=\"Add to Cart\" onclick=\"alert('Your item ("+Data.title+") was added');a5_AJAX_Callback('addtocart.ajax.a5w','var=abc&id="+data.id+"');\"/>"

    You can also just execute your callback page directly by typing the full URL to your callback page. Often you will get a 500 error that explains what's wrong, whereas you get nothing if you call the page from your button.

    Once I get it to work I document everything in my homegrown Help document and work from that known-good code.

    Lastly, I often forget to put those three Javascript references in the Head area of the page with the callback button. I can test several dozen times before I realize I forgot that simple step.
    Steve Wood
    See my profile on IADN

    Comment


      #3
      Re: Ajax Callback Session Variable and Debugging

      1)How do i use a session variable in the ajax callback page? I have variable session.__protected__varname that i use on each page. i need to use this variable to add records to a table, however i cannot seem to access the variable from the callback page.
      I'm not 100% as to what your particular issue is.
      -
      In my case I would send the session.__protected__varname from the calling page to the AJAX page as a new variable
      eg something like this

      Code:
      var theSessionProt  = <%A5 ?session.__protected__varname %>;
      
      a5_AJAX_Callback('TheFile.AJAX.A5W','action=DoSumStuff&SendUp='+SendUp+'&theSessionProt='+theSessionProt);
      Something I have found little info on is the built in AJAX Session management.
      I have just started using my own home grown simple thread manager, and it's boosted the AJAX performance stacks, + saves notably on server performance.
      -
      What is the best way to debug an ".ajax.a5w" page?
      Better to use some form of structered programming currently. Since AJAX and on A5 is in it's infancy, I don't think anyone has worked out how to properly do any debugging.

      Comment


        #4
        Re: Ajax Callback Session Variable and Debugging

        There's no need to send the session variable to the callback page; if it exists at the time the callback is made, the session variable already exists and can be used on the callback page just like any other page. There is nothing special about a callback page; it is just an A5W page like any other.

        If you use Firefox's Firebug, there are some advanced ajax debugging tools there that work with Alpha. Check Alpha's release notes for some reference to "Firebug".
        Steve Wood
        See my profile on IADN

        Comment


          #5
          Re: Ajax Callback Session Variable and Debugging

          I was finally able to use my session variable in the afterFormValidate function. Any attemp to use the session variable during the onFormInitialize event failed, however.

          Thank you all, for your help.

          Comment


            #6
            Re: Ajax Callback Session Variable and Debugging

            This doesn't work for all bugs, but it has helped me tremendously:

            On the calling page, place a <span id=\"errorArea\"></span> at the top of the page. (Use span, rather than DIV because DIV causes an page break that will move your page down a line. SPAN will allow the area to remain unnoticed until needed.)

            In your AJAX page, place the following:

            at the very top:

            Code:
            <%a5
            on error goto error_handler
            ? "$('error_area').innerHTML = '';"
            at the very bottom:

            Code:
            end
            
            error_handler:
                err = error_code_get()
                error_line = error_line_number_get()
                error_print = error_text_get(err)
                msg = "Error " + ut(str(err)) + ": " + error_print + " (line " + error_line + ")"
                ? "$('error_area').innerHTML = '" + jsEscape(msg) + "';"
                if error_text_get(err) = "Got this far" then
                    resume next
                end if
            end
            %>
            The IF statement with the "got this far" string is used when I can't figure things out. I can place a line like this:

            Code:
            error_generate("got this far")
            in various locations throughout the code, and it will report the line numbers where they occurred. The "resume next" allows the code to continue running so you only see the last "error_generate" line and know that your error is after that line, but before the next "error_generate" line.

            This has been very handy! In fact, you can place one every once in a while, and then comment them out to be user as needed by simply un-commenting them.

            This has saved me a LOT of frustration. And it is important that it go at the top of your page, because you will often forget to look at the bottom to see if there was an error.
            Stephen Pilon
            Associate Librarian
            Christendom College

            Comment


              #7
              Re: Ajax Callback Session Variable and Debugging

              Stephen,
              I was just thinking Yesterday that there must be a way of doing this
              Thanks, I'm sure you have saved me a stack of work
              Regards
              Colin

              Comment

              Working...
              X