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

How to bypass my login component for mobile?

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

    How to bypass my login component for mobile?

    Ok, I've got a normal login component set into an A5W page. In that page I'm using a script to detect mobile devices. If a moblile device is detected, I have it set to redirect to a UX component that has login/logout functionality and is set to "always allowed" in security.

    Unfortunately, when it redirects it just goes into a loop in between the two components. My app always wants users to go to the login component no matter what. Do I have something set wrong or is this a bug?

    P.S. This happens even if tell the browser to go directly to the mobile component.

    #2
    Re: How to bypass my login component for mobile?

    Jinx,

    I would do it differently. Have your index page be xbasic only. From the index direct to your web site or your mobile site for their respective logins. Not sure what happens when you log out of mobile in that case? Will it take you back to index, because it really shouldn't, although if it does, it should immediately redirect back to the mobile login screen. If it works that way it shouldn't be a problem I would think.
    Peter
    AlphaBase Solutions, LLC

    [email protected]
    https://www.alphabasesolutions.com


    Comment


      #3
      Re: How to bypass my login component for mobile?

      What two components? Web login and mobile login? Where do you have it pointed after the login button is clicked? Example:
      Client_Side Events
      afterlogin
      {dialog.object}.panelSetActive('PANEL_APPLICATION'); //This is my mobile menu.

      Comment


        #4
        Re: How to bypass my login component for mobile?

        how does this interact with Alpha s redirect security settings? Maybe its getting hung up there?

        Comment


          #5
          Re: How to bypass my login component for mobile?

          Thanks guys,
          Sorry it took me a while to respond but I've been busy.

          I have a normal login component that is wrapped with an A5W page. In that page I have the following code:
          Code:
          <script type="text/javascript">
          
          var isMobile = {
              Android: function() {
                  return navigator.userAgent.match(/Android/i);
              },
              BlackBerry: function() {
                  return navigator.userAgent.match(/BlackBerry/i);
              },
              iOS: function() {
                  return navigator.userAgent.match(/iPhone|iPad|iPod/i);
              },
              Opera: function() {
                  return navigator.userAgent.match(/Opera Mini/i);
              },
              Windows: function() {
                  return navigator.userAgent.match(/IEMobile/i);
              },
              any: function() {
                  return (isMobile.Android() || isMobile.BlackBerry() || isMobile.iOS() || isMobile.Opera() || isMobile.Windows());
              }
          };
          
          //if( isMobile.any() ) window.location = "address to my mobile navigator";
          
          </script>
          When I run this, it get's stuck in a loop in between my login page and my mobile navigator/login page. If I'm already logged in and navigate away from my mobile page for some reason, it will redirect me and work fine. For some reason though, even though I have my mobile navigator page set to "allways allowed" it get's stuck in the loop when I'm not logged in.

          I don't have an index page, unless alpha automatically creates one.

          Maybe I'm missing something obvious here?

          Comment


            #6
            Re: How to bypass my login component for mobile?

            It appears that Alpha is not recognizing that I have my mobile navigation/login page set to "always allowed".

            Comment


              #7
              Re: How to bypass my login component for mobile?

              Ugh, I just figured it out. It seems that when you put a login component on a UX, Alpha automatically creates an A5W page with the same name. The security for my UX component was set to always allowed but the security for the stupid A5W page wasn't. It's working properly now.

              Thanks guys.

              Comment


                #8
                Re: How to bypass my login component for mobile?

                Thanks for posting back, useful info

                Comment

                Working...
                X