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

V12 Login component problem when published to server

  • Filter
  • Time
  • Show
Clear All
new posts

  • V12 Login component problem when published to server

    Hi there,

    It's working fine in my local. But there are error messages after published to server. What's problem?


    500 Internal Server Error

    Script Error
    Error:Script:" /login.a5w" line:47
    x_login = a5w_run_Component(tmpl_login) 'SYSTEM GENERATED COMMENT - PLEASE DO NO
    Property not found
    wf.page_fields[] subelement not found.

  • #2
    Re: V12 Login component problem when published to server

    The login component doesn't use that property. That suggests you are using a UX component for login, or previously created and published a UX or grid component with the same name. Try republishing the login component without selecting to "Publish new or modified files only" to force a fresh publish.


    • #3
      Re: V12 Login component problem when published to server

      Hi Jerry,

      I don't understand why in my local works fine but don't works on server. I selected "SecurityFramework-LoginComponentMobileApp" template to build Login. And followed step by step with VDO tutorial. I don't sure about config or set any properties on server.


      • #4
        Re: V12 Login component problem when published to server

        That is a UX component with security functionality added. The most likely problem is a mismatch in builds between the server and the development program. The server build must be the same as the development build.


        • #5
          Re: V12 Login component problem when published to server

          Hi Jerry,

          Do you meaning in Web project profile window? I had already checked right at "Web security data published". But still error!!


          • #6
            Re: V12 Login component problem when published to server

            Do you meaning in Web project profile window?
            no he means
            check the version number in your development machine
            and the version number of the application server that resides wherever you host your site.
            they should be same, both version and build.
            thanks for reading


            version 11 3381 - 4096
            mysql backend
            [email protected]
            Skype:[email protected]
            1 914 924 5171


            • #7
              Re: V12 Login component problem when published to server

              Thank for reply, Both are same version (V.12)


              • #8
                Re: V12 Login component problem when published to server

                stil more..
                take a look at the screen when you startup your development version, there are two numbers
                that should say something like version and build, they are 4 char long
                similar to the one appearing in my signature.
                those are the number to be checked.
                thanks for reading


                version 11 3381 - 4096
                mysql backend
                [email protected]
                Skype:[email protected]
                1 914 924 5171


                • #9
                  Re: V12 Login component problem when published to server

                  Hi, did you manage to resolve this issue? It is happening to me as well and I have checked that both are same build. I did have a login component previously and disable it to see if that was the problem but I keep getting the same error.