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

CSS caching problem

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

    CSS caching problem

    I'm have a weird problem that I can only blame on the WAS. I've edited my css file in the css folder on my computer, uploaded the changes to the WAS, and viewed the changed web page on the server, but the page does not show the changes I've made to the page. I've checked the css file on the server and it is the correct file with the appropriate changes however the new css file is being marked as 304 Not Modified by the server (using firebug's net panel). I've cleared by cache and used two different browsers.

    any ideas?

    EDIT: i have rebooted the WAS as well

    #2
    Re: CSS caching problem

    Using the default server configuration, gzip and gzip caching are enabled. Gzip caching creates a cached gzipped copy of your static resources within your webroot. When you stop the server normally, it should clear these cached files. However, if the server is not properly shut down, the files may not be cleared. Or you may wish to update the cache without having to restart the server.

    In either of these situations, you can manually remove the cached gzip file. On the next request for that file, a new cache version will be created.

    The cache file will be created in the same folder as your normal file. It will be named the same, with the added extension .gzcache. So if you have updated MyStyle.css, simply delete MyStyle.css.gzcache.

    It is also possible to disable gzip caching in the Application Server settings. This can be found on the Performance tab.

    Lenny Forziati
    Vice President, Internet Products and Technical Services
    Alpha Software Corporation

    Comment


      #3
      Re: CSS caching problem

      I disabled the gzip settings on my V10 localhost server long ago. I also set IE and Firefox to NOT cache anything while I am working locally.

      When I went to confirm, I see we have a new Advanced Tab with a bunch of nifty options that invite exploration, including the new IP binding setting.
      Steve Wood
      See my profile on IADN

      Comment


        #4
        Re: CSS caching problem

        I just recently had a problem with gzcache files being generated for every xml file. My solution was to include in the code for generating the xml files a routine to check if xml.gzcache existed and if they do, delete the files automatically.
        Last edited by mmaisterrena; 10-26-2009, 05:50 PM.
        Cheers
        Mauricio

        Comment


          #5
          Re: CSS caching problem

          I've disabled gzip and gzip caching and the problem is fixed. Shouldn't the server have a check to see if the file has changed since it was last gziped?

          Comment


            #6
            Re: CSS caching problem

            I think it should, because if not gzip is rather obtrusive.
            Cheers
            Mauricio

            Comment


              #7
              Re: CSS caching problem

              New in the next patch is a more intelligent cache that monitors for file changes and automatically removes the stale .gzcache files for you. This will eliminate the current need for you to manually delete the .gzcache files.

              Lenny Forziati
              Vice President, Internet Products and Technical Services
              Alpha Software Corporation

              Comment


                #8
                Re: CSS caching problem

                Originally posted by Lenny Forziati View Post
                New in the next patch is a more intelligent cache that monitors for file changes and automatically removes the stale .gzcache files for you. This will eliminate the current need for you to manually delete the .gzcache files.
                Great :)

                Comment

                Working...
                X