Go to the Aptana Studio download page, click the tab for your Operating System, and fill out and submit the form to receive the License key for your Pro Trial:

Aptana Studio Download page

If you are using the current version of Studio, you do not need to download the application again. You can can click the Cancel button when the download starts, and your Pro license trial key should still be emailed to you.

If you are not using the current version of the Community Edition of Studio, we recommend completing the download, then backing up your workspace and preferences and then uninstalling your old version of Studio and installing the new version.

For ubuntu users expereiencing this erro, download the following file and unzip and place in the jaxer/components folder of your jaxer install.

libjxMySQL50.zip

Jaxer provides a mechanism to identify an application by it's URL structure, this is controlled by the 'configRoutes.js' configuration script.

The Jaxer global routing object (Jaxer.Config.routes) holds an array of javascript functions that return either a NULL, if the url doesn't match the rule, or, a 2 value array, if the url matches the rule, the first value is the identifier for the application and the second value is the identifier for the page. These identifiers are used to manage script access to the Jaxer application and page containers.

Jaxer.Config.routes = // add the following to the top (beginning) of routes: [ function(url) { if ((url.pathParts.length > 0) && (url.pathParts[0] == 'myApps') && (url.pathParts[1] == 'toys')) { return ['ToyStore', url.hostAndPort + url.pathAndFile]; } else { return null; } }, function(url) { if ((url.pathParts.length > 0) && (url.pathParts[0] == 'myApps') && (url.pathParts[1] == 'books')) { return ['BookStore', url.hostAndPort + url.pathAndFile]; } else { return null; } }, ].concat(Jaxer.Config.routes); })()

The example above would create two applications predicated on the folder structure, the first,the ToyStore application, would be active for any pages server from the myApps/toys folder, the second from the myApps/books folder. These would have an application identifer (Jaxer.application.key) of 'ToyStore' and 'Bookstore' respectively, with each page being identified by it's full URL.

In the event that a URL doesn't match any of the provided rules, the default Jaxer rules would apply which provides an application name based on the fullpath to the folder, and a page context based on the full path to the document being served.

We've seen this issue periodically with Windows users. If you experience this issue, try the following workaround:

1. Navigate to the folder where you have Aptana Studio installed (usually under C:\ Program Files), and find the jre folder.
2. Re-name the jre folder to jre.old.
3. If you have another instance of the latest JRE installed on your machine, skip to the last step.
4. Download and install a new instance of the JRE from the java web page:

   http://www.java.com/en/download/index.jsp.

5. Start Aptana Studio.

If the above workaround does not fix the problem, please file a support ticket in ASAP.

For some users, an update to Aptana will appears to stop network connections and throws an error about being unable to download a particular .jar file. This is caused by an interaction between Aptana and certain network cards, in particular cards using the the Marvell network chipset. If you experience this issue, there are a number of remedies.

Patching Aptana Studio

The simplest way is to solve the issue is to download a special file and place it in your Aptana folder. This technique requires Aptana Studio 1.1.5 or later. If you have an earlier version, you can manually update to 1.1.5, or uninstall and reinstall.

1. Download the attached file and place in your plugins folder under Aptana Studio/plugins.
2. Restart Aptana Studio.
3. Once Aptana Studio has restarted, open up Preferences > Aptana > Updates
4. Set the values under Network Troubleshooting to "1" and "1000" respectively

Manual Update

You may choose to do a manual update of the existing plugin. Instructions are posted here.

Advanced Option

If you are on Windows XP with a Marvell-based network adapter, you may be able to tweak your network adapter settings:

1. Get to your adapter properties (device manager -> network adaptors -> marvell... > right-click > properties)
2. Go to Advanced & increase Number of Receive & Number of Transmit Buffers (for example from 50 to 200)

To change the Aptana Studio UI to another language:

1. Download and install the i18n plug-in from the Aptana plug-ins page:http://aptana.com/plugins
2. Follow the instructions in the Help topic to change the Aptana Studio interface to another language:http://www.aptana.com/docs/index.php/Changing_the_Aptana_Studio_interface_to_a_different_language

Yes, but we do not include CVS support with the standalone Aptana Studio. You can download and install the CVS plug-in from our plug-ins page to enable CVS support:

http://aptana.com/plugins

While we no longer officially support the old SFTP plug-in that was included in beta versions of Aptana Studio, you can still download and install this plug-in from our plug-ins page:

http://aptana.com/plugins

Jaxer has configuration settings that allow logging levels be adjusted. Here are some of the settings that you can turn on/off when trouble shooting a problem (Assuming windows platform here).

mod_jaxer (applicable only if apache is configured talking to Jaxer):
This is the module that apache uses talking to Jaxer. The loggings generated by this module are in your apache log (“Aptana Jaxer\logs\apache_error.log” if using the shipped apache server).
To generate extensive loggings, go to your httpd.conf (“Aptana Jaxer\Apache22\conf\httpd.conf” if using the shipped apache server.), change the LogLevel to debug, and restart apache.
LogLevel debug

JaxerManager:
JaxerManager manages the individual Jaxers. It is the bridge between the webserver connector (eg mod_jaxer) and jaxer. JaxerManager writes logs in the same file as Jaxer does. The log file is jaxer.log under “Aptana Jaxer\logs” if you are using the standalone Jaxer install.
You can turn on trace either from the JaxerManager command line (--trace=on) when you start JaxerManager or issue a (set trace on) command through its command port. You can use the utility program tellJaxerManager to do it.
From command line:
JaxerManager –trace=on
After JaxerManager has started:
tellJaxerManager “set trace on”
To turn off the trace,
From command line:
JaxerManager –trace=off
After JaxerManager has started:
tellJaxerManager “set trace off”

Jaxer:
Jaxer is the main process that does the work. It has a few settings that control various logging levels. All Jaxer logs go to the same log file as JaxerManager.

Turn on protocol dumping:
When it is turned on, Jaxer logs all network traffic between it and the webserver connector. The setting is in defaults\pref\Jaxer_prefs.js under the jaxer folder (Aptana Jaxer\jaxer\defaults\pref\Jaxer_prefs.js if using the shipped apache server.).
pref("Jaxer.dev.DumpProtocol", true);
The change requires restarting jaxer. To turn it off,
pref("Jaxer.dev.DumpProtocol", false);

Other Jaxer settings:
In the same Jaxer_prefs.js file, the following settings can be turned on (true) or off (false). Note that these settings control individual levels. Thus to get the maximum loggings, you should setting all of them to true.
pref("Jaxer.CoreTrace.EnableWarning", true);
pref("Jaxer.CoreTrace.EnableInfo", true);
pref("Jaxer.CoreTrace.EnableDebug", true);
pref("Jaxer.CoreTrace.EnableTrace", true);
The configLog.js (under “Aptana Jaxer\local_jaxer\conf” if you are using the standalone Jaxer install) contains additional settings mainly controlling the loggings for server-side javascript execution. You can edit the function() body to adjust the logging levels. Your settings here override the settings in jaxer\framework\configLog.js.