Where is mootools in joomla 1.5

There needs to be some way to determine if a particular request has been completed or not. To do this you can extend the MooTools Ajax class like this:. Having extended the Ajax class, you now need to set up a simple queue mechanism to hold the request information.

Each new request will be pushed into the queue and completed requests will be popped from the queue. The trick is to make sure that if a request completes before older requests have been completed it remains in the queue and does not get removed out of sequence. The window. Then you need to add some extra code to the onComplete function that will pop completed requests from the queue, but only in the correct order:. Note that the output is only placed in the document when the queue is finally empty, so the user never sees results from intermediate requests.

If you have multiple Ajax fields on a single page, then you will need to give each one its own queue, but the coding remains essentially the same. If you need to access a web service, using Ajax, that is running on a server that is not in your domain, then you will run up against the "same origin policy" [3] that will prevent you from retrieving data from outside your own domain for security reasons.

There needs to be some way to circumvent this restriction on those occasions where the web service is trusted. The most common method of circumventing the same origin policy in Ajax implementations is to access the remote web service via a proxy running in your domain. The proxy uses an HTTP client library such as [4] to access the remote server. This technique is usually simple enough, but can get tougher if the remote server requires authentication or uses cookies to track state between requests.

On the plus side, using a proxy generally makes it easier to cache Ajax responses; something that is normally quite difficult. To add a simple proxy to your Joomla component you simply need to add an extra task to the controller. The following code shows roughly what it might look like, given a static HTTP client class called httpClient with a method that will request a page from a remote server. This example also shows how to work around the situation where the remote server is also running Joomla, in which case it will require a URL containing option and task arguments that may not match those required by the proxy.

For example, suppose you want to make an Ajax request to a remote server using this URL:. You will need to adapt this code to meet your particular requirements, such as if you need to specify the controller in order to reach the proxy. Home What is Joomla? Download Launch. So when I create a basic content page using an article layout with no modules I am surprised to see these 3 lines.

This happens on both joomla 1. While this will remove it, I wanted to understand why this is added. This plugin is fairly simple. By the way, another advantage of using a system plugin is that it can be applied for specific components and not the whole website. In any case, you can always contact us and we will definitely help you!

Our rates are affordable, our work is swift and professional, and we really love to serve our clients! Read here for more information on how to do remove a JavaScript library from a Joomla page. Warning: that […]. I need faster backend loading because it takes about minutes to save a module or to change the template. Please I need help to solve this. I think you could disable moo tools for the back end? Sign up using Email and Password.

Post as a guest Name. Email Required, but never shown. The Overflow Blog. Does ES6 make JavaScript frameworks obsolete? Podcast Do polyglots have an edge when it comes to mastering programming Featured on Meta. Now live: A fully responsive profile. Related 0. Hot Network Questions. Question feed.