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

logging users out when publishing

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

    logging users out when publishing

    Hi all

    We are using version 12 to develop a web app.

    We have noticed that when we publish a change to anything, the logged in users are sent back to the log in screen.

    Has anyone else had this issue?

    Many thanks

    Miles

    #2
    Re: logging users out when publishing

    Generally speaking it is a bad idea to publish while a system is in production; you should avoid doing that.
    Frank

    Tell me and I'll forget; show me and I may remember; involve me and I'll understand

    Comment


      #3
      Re: logging users out when publishing

      In reality you cannot avoid publishing to live in-production systems, and generally there is no problem doing this. Miles, the only problem I have seen is if the user opens a particular component at the exact same time you are publishing; it can return an error and you have to re-publish that component. I tested publishing to a V12 system while logged in and did not get bumped out. Can you tell us what you are publishing?
      Steve Wood
      See my profile on IADN

      Comment


        #4
        Re: logging users out when publishing

        Hi Steve

        Thanks very much for looking at this for me.

        We have been using Alpha Web App development since Version 8, and never experienced problems publishing to Live enviroment.

        This is pretty much our first Project in Version 12, and have had this problem right from the start.

        Its when we pubish anything realy, Grids / Pages / UX......

        So if I am testing a UX say thats been published , and my colegue publishes a change to a different one.... when I submit my form it takes me back to the LOGIN page (like when you dont have permissions).

        It does not do this if NO publishing has taken place....

        Is is worth noting that we are publishing via a LAN (over VPN) to our server in a Data Centre?

        I cant think of any settings that we may have wrong, but if you can suggest some to check that would be great.

        Thanks for any help received.

        regards

        Miles

        Comment


          #5
          Re: logging users out when publishing

          You might try (as an experiment) setting the publishing to use External. That will push all of your files to a folder and you can then pick and choose which to publish. Or, an easier place to start might be to go to your Publishing Profile and set it to publish only "selected" file and not to publish any "support" files. That will publish a minimum of files.*

          *I got Alpha to add those options years ago as I insisted I only wanted to publish what I want to publish and accepted the potential risk.
          Steve Wood
          See my profile on IADN

          Comment


            #6
            Re: logging users out when publishing

            I think your problem has to do with the networked conditions of your environment issue, as You will see goofy behavior like that when you use two instances of chrome. Just for kicks, use a different browser than your colleague. So if he is using Chrome, you use IE.
            Test the same behavior, your probably not going to get kicked off like before...this is just a guess!
            Hope it helps.
            Finally test it from a laptop on a different network, I would bet you will not see that same behavior.
            NWCOPRO: Nuisance Wildlife Control Software My Application: http://www.nwcopro.com "Without forgetting, we would have no memory at all...now what was I saying?"

            Comment


              #7
              Re: logging users out when publishing

              When IIS will be around this whole thing will change anyway; IIS web deploy publishes everything you have no options but with IIS you can easily create a maintenance site or even a duplicate and there's probably ways to switch from one to another. IIS is very exciting; url rewriting, virtual hosting, extensionless pages, build selection etc. Sign up for the beta & see what a new world opens up!
              Frank

              Tell me and I'll forget; show me and I may remember; involve me and I'll understand

              Comment

              Working...
              X