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

Application Server Logs XBasic Warning regarding style.css in sharedStyles

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

    Application Server Logs XBasic Warning regarding style.css in sharedStyles

    When my login component opens the following entries are made to the logs.

    a5w_access log.
    172.58.233.62 - - [28/Jun/2018:03:36:52 -0400] "GET /usismobiletest/css/_sharedStyles/style.css?32 HTTP/1.1" 200 4


    A5XbasicErrorStackLog
    WARNING:A query parameter, form variable, or cookie name could not be used as an Xbasic variable and had to be renamed.
    Original name:32
    New name: _32
    Request Method: GET
    Request: /usismobiletest/css/_sharedStyles/style.css?32

    This was introduced when we upgraded to version 5028_5088.
    Can someone explain the meaning why the number 32? It seems related to sharedStyles which I did not see in older logs.

    I am also seeing Trace_SASS Errors_20180627_5 files in the log folder which I had not seen before.
    Any advise would be greatly appreciated. I am seeing thousands of entries every day which I believe is impacting my application.

    #2
    Re: Application Server Logs XBasic Warning regarding style.css in sharedStyles

    Originally posted by frankiez View Post
    I am also seeing Trace_SASS Errors_20180627_5 files in the log folder which I had not seen before.
    I get these too (Running 5151-5127 at the moment). A massive amount every day. I reported this to Alpha a little while back and I had a legitimate CSS error I needed to fix. But even after I fixed this I continued to get these. Alpha said they needed a sample but I never got around to sending one in. This is the error I get when you open the file...

    Code:
    [B][I]###-------------------------------------------------------------------------
    Error text: Error: Invalid CSS after "c": expected 1 selector or at-rule, was "color: #333333;"
            on line 1 of ../../Users/Administrator/AppData/Local/Temp/AlphaAnywhere/p_4376/a5_temp_1c77d2f3_bbee_4b39_bce5_46a34432c937.scss
    >> color: #333333;
       ^[/I][/B]

    I also get a similar xbasic stack log warning but Lenny (at Alpha) told be this was fixed starting with 5159-5132. I haven't updated to this just yet so I can't vouch for the fix.
    Mike Brown - Contact Me
    Programmatic Technologies, LLC
    Programmatic-Technologies.com
    Independent Developer & Consultant​​

    Comment


      #3
      Re: Application Server Logs XBasic Warning regarding style.css in sharedStyles

      I can confirm this is not fixed in build 5159-5132 Jun 22,2018.
      To duplicate this problem just create a new mobile login component, publish and open in browser. View the A5XbasicErrorStackLog.txt log file. Although the messages appear benign, the system still has to write several thousand log messages per day.


      Opening my login component, the app server created 6 warning messages.

      WARNING:A query parameter, form variable, or cookie name could not be used as an Xbasic variable and had to be renamed.
      Original name:35
      New name: _35
      Request Method: GET
      Request: /projectfolder/css/_sharedStyles/style.css?35
      Last edited by frankiez; June 28, 2018, 06:34 PM. Reason: Premature in my comment. It appeared fixed when publishing locally, but not to the server.

      Comment


        #4
        Re: Application Server Logs XBasic Warning regarding style.css in sharedStyles

        The strange thing is why is the application trying to parse the ?35 as anything for a css file. The css file should be a static file. I am guessing that AA is adding the "?35" for the sole purpose of trying to get the browser not to load it from cache when it is a new version of the app.

        But why does this seem to cause problem only for the "/css/_sharedStyles/style.css?35" and not for "/css/[StyleName]/style.css?35" ?
        I am assuming that on the application server side that although css should be static, the server is trying to handle it differently because there is something missing in the web.config (using the IIS version?) for the _sharedStyles path.

        Comment


          #5
          Re: Application Server Logs XBasic Warning regarding style.css in sharedStyles

          Anyone ever get a resolution for this? I am getting it too.

          Comment


            #6
            Re: Application Server Logs XBasic Warning regarding style.css in sharedStyles

            That reminds me of an error like the following that fills up my log, too:

            Code:
            WARNING: Thu Jun 20 04:58:58 2019
            A query parameter, form variable, header, or cookie name could not be used as an Xbasic variable and had to be renamed.
                   Source: FormVariables
            Original name: R-1
                 New name: R_1
            Request Method: POST
            Request: /MyGrid.a5wcmp?__virtualPage=__a5RunGrid.a5w&__pageName=MyGrid.a5wcmp&__gridFilename=MyGrid&__alias=XXXX&__unsaved=no&_isLookupGrid=false
            "R-1" does not appear anywhere in the source of MyGrid when searching the xbasic tab.

            Comment

            Working...
            X