Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 7696817
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 31, 20262026-05-31T21:52:05+00:00 2026-05-31T21:52:05+00:00

I have the same problem described here on the e-office blog , but in

  • 0

I have the same problem described here on the e-office blog , but in my case it also happens in IE9. When I manually do a refresh of the page, everything is working again. It looks like the JS aggregator tries to do something with the javascript files.

Does anyone found a solution for this?

This is the way I load my client javascript files. The ‘xast.locationJS’ variable is the location on the server where I the javascript files can be found.

   <xp:this.resources>
    <xp:script clientSide="true">
        <xp:this.src><![CDATA[${javascript:return  applicationScope.get("xast.serverUrl") +"/" +applicationScope.get("xast.locationJS") + "/jquery-1.5.1.min.js"}]]></xp:this.src>
    </xp:script>
    <xp:script clientSide="true">
        <xp:this.src><![CDATA[${javascript:return applicationScope.get("xast.serverUrl") + "/" + applicationScope.get("xast.locationJS") + "/jquery.hoverIntent.minified.js"}]]></xp:this.src>
    </xp:script>
    <xp:script clientSide="true">
        <xp:this.src><![CDATA[${javascript:return  applicationScope.get("xast.serverUrl") + "/" + applicationScope.get("xast.locationJS") + "/jquery.tools.min.js"}]]></xp:this.src>
    </xp:script>
    <xp:script clientSide="true">
        <xp:this.src><![CDATA[${javascript:return  applicationScope.get("xast.serverUrl") + "/" + applicationScope.get("xast.locationJS") + "/jquery-ui-1.8.14.custom.min.js"}]]></xp:this.src>
    </xp:script>
    <xp:script clientSide="true">
        <xp:this.src><![CDATA[#{javascript:return  applicationScope.get("xast.serverUrl") + "/" + applicationScope.get("xast.locationJS") + "/C2C_dojo.tools.js"}]]></xp:this.src>
    </xp:script>
    <xp:script clientSide="true">
        <xp:this.src><![CDATA[#{javascript:return  applicationScope.get("xast.serverUrl") + "/" + applicationScope.get("xast.locationJS") + "/CommonXmlFunctions.js"}]]></xp:this.src>      
    </xp:script>
    <xp:script clientSide="true">
        <xp:this.src><![CDATA[#{javascript:return  applicationScope.get("xast.serverUrl") + "/" + applicationScope.get("xast.locationJS") + "/C2C_WebCaseSuggest.js"}]]></xp:this.src>
    </xp:script>
    <xp:script clientSide="true">
        <xp:this.src><![CDATA[${javascript:return  applicationScope.get("xast.serverUrl") + "/" + applicationScope.get("xast.locationJS") + "/uncompressed/xpUtils.js"}]]></xp:this.src>
    </xp:script>
</xp:this.resources>
  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-31T21:52:06+00:00Added an answer on May 31, 2026 at 9:52 pm

    It looks like the ‘compute on page load’ property was the problem. I think libraries that are computed on page load wil be automatically picked up by the JS aggregator, or something like that.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have the same question problem as described here How to purge a cached
I have essentially the same problem discussed here: http://khason.net/blog/dependency-property-getters-and-setters-in-multithreaded-environment/ public static readonly DependencyProperty MyPropertyProperty
I have the same problem as described here: UIWebView doesn't scroll to the bottom
I have exactly the same problem as described here: http://bugs.jqueryui.com/ticket/7930 . The problem is
I have the same problem as described here : I am using two orchestrations.
I have the same problem as described in the posts listed below. That is,
I have the same problem as described in ( Last record of Join table
I actually have two questions regarding the same problem but I think it is
I am facing more or less the same problem described here , (i.e. I
I have the same problem outlined here . That is, nested view models in

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.