Announcement

Collapse
No announcement yet.

Endless query

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

  • Endless query

    Hi,

    Sometimes, I have this issue : when I save my form an endless message is displayed : "endless.jpg"

    Even if I kill it with MySql command it keeps running ...

    Would you have an idea ?

    Thank you
    CL

  • #2
    You have some ajax code in afterinsert events?.
    /Giuseppe

    Professional Scriptcase Services
    Some Customers opinions

    Comment


    • #3
      No, just native ScriptCase framework.

      However, I have just reproduced this case with 2 ways :
      - when I recompile the involved application with SC, and I go back to the running application to save
      - when I empty the cookies information of my browser, I go back to the running application to save

      EDIT

      My application is in security mode
      Last edited by xof; 06-21-2014, 03:04 PM.

      Comment


      • #4
        Anybody has an idea ?

        Comment


        • #5
          Don't understand. Can you share the failing application with an SQL file? And steps to reproduce the problem
          /Giuseppe

          Professional Scriptcase Services
          Some Customers opinions

          Comment


          • #6
            Unfortunately, No I can't. But I can detail the steps here.

            First scenario :
            1- Open SC
            2- Create a new form application with security module ("Activate Security" attribute set to Yes in SC)
            3- Generate the source code
            4- Execute this application thanks to SC and go to the new browser tab
            5- Update a field in the form and save ==> it works
            6- Go back in SC
            7- Generate the source code again
            8- Without execute the application, go back the to browser tab
            9- Update a field in the form and save ==> it doesn't work

            Second scenario :
            1- Open SC
            2- Create a new form application with security module ("Activate Security" attribute set to Yes in SC)
            3- Generate the source code
            4- Execute this application thanks to SC and go to the new browser tab
            5- Update a field in the form and save ==> it works
            6- (In Mozilla for example) Go in History Menu, and Click on Clear Recent History
            7- Update a field in the form and save ==> it doesn't work

            Comment


            • #7
              Has you tried to refresh page in last steps before update field? Can be a session problem. What you are trying is not normal behaviour of an user.
              /Giuseppe

              Professional Scriptcase Services
              Some Customers opinions

              Comment


              • #8
                You're right (session problem & abnormal behaviour) : when I refresh it is solved. I had seen it.

                But, what is not normal too, is that according to company policy the web browsers caches can be reset during the day (it's my case). And, when it happens while users are filling some forms, the data are lost because the screen is masked by this endless message and they are forced to refresh the page ...

                Anyway, even if it's not a normal behaviour, I think that ScriptCase should be able to detect that.

                Do you see what I'm trying to mean ?

                Comment


                • #9
                  Originally posted by xof View Post
                  You're right (session problem & abnormal behaviour) : when I refresh it is solved. I had seen it.

                  But, what is not normal too, is that according to company policy the web browsers caches can be reset during the day (it's my case). And, when it happens while users are filling some forms, the data are lost because the screen is masked by this endless message and they are forced to refresh the page ...
                  This is very very dangerous, on SC, Java and whatever other lang/enviroment. You can't expect to deploy a new version or modify client side of the application while users are working and all continues to working as expected, without the user has to "refresh". Think about it, you are modifying client side information while user work. It's like to expect to still logged on FB when you delete cookies.
                  There are a way IIRC to store session data on database on security module, but don't know if this will work in your situation.

                  Anyway, even if it's not a normal behaviour, I think that ScriptCase should be able to detect that.

                  Do you see what I'm trying to mean ?
                  I understant you, but I can't agree. I don't think SC framework is responsible to check if client data is modified or if session is manipulated, just because this is not normal. And if something weird happens, normal behaviour is to refresh. Web applications as is, web servers just answer petitions, and this petitions needs information about the context.

                  Conclusion: Problem is not in SC, but in your company or users.

                  /Giuseppe

                  Professional Scriptcase Services
                  Some Customers opinions

                  Comment


                  • #10
                    You're right, I understand for the risks !

                    And, althought, you just make me realize that without cookie SC does not work in Security Mode : I just set Firefox like that "Do not accept cookies" and my application always returns me "unauthorized user" ... it's good to know ...

                    Comment


                    • #11
                      Originally posted by xof View Post
                      And, althought, you just make me realize that without cookie SC does not work in Security Mode : I just set Firefox like that "Do not accept cookies" and my application always returns me "unauthorized user" ... it's good to know ...
                      As, maybe, every site thath needs a login. It's "the only" way for a browser to communicate to a server thath the user is logged.
                      /Giuseppe

                      Professional Scriptcase Services
                      Some Customers opinions

                      Comment


                      • #12
                        I'm not so sure about it, but avoid cookies force to work with hidden html input like that <input type="hidden" name="PHPSESSID" value="xxxxxxxxxxx"> for example.

                        And ... ScriptCase ... do that too.

                        Here is an example of one of my generated page with SC :
                        <form name="form_ajax_redir_1" method="post" style="display: none">
                        ...
                        <input type="hidden" name="script_case_session" value="sbb36nc7tdlfp3rj0d1em556i2">
                        </form>
                        ...
                        <form name="form_ajax_redir_2" method="post" style="display: none">
                        ...
                        <input type="hidden" name="script_case_session" value="sbb36nc7tdlfp3rj0d1em556i2">
                        </form>
                        And, those "script_case_session" values perfectly match the PHPSESSID cookie value and session_id() PHP clause.

                        Comment


                        • #13
                          If coockies cannot be used in a trustfully way then i think you should store the session variable in the database. You can change this in the project properties.
                          Albert Drent
                          aducom software netherlands
                          scriptcase partner, reseller, support and (turn-key) development
                          www.scriptcase.eu / www.scriptcase.nl

                          Comment


                          • #14
                            Where can I update that setting ?

                            Comment


                            • #15
                              Hello,

                              Not sure if this is a bug either.

                              Anyway, I will contact our bugs team regarding this issue.

                              regards,
                              Bernhard Bernsmann

                              Comment

                              Working...
                              X