All / Any

Company Name & Contact Information Change

Question: 

What is the company name, contact information and information needed for purchase orders and payments.

Answer: 

“ActiveState Tool Corp.” has changed its name. Our new legal name is now
“ActiveState Software Inc.”

Please also note the changes to our contact and mailing information.

To ensure that we receive all orders and your payments in a timely manner, we ask that you update your files with the following information:

New Legal Name: ActiveState Software Inc.
New Address: #1700 – 409 Granville Street
Vancouver, BC
Canada V6C 1T2

New Main Telephone#: (778) 786-1100
New Fax#: (778) 786-1133
Email: Sales@ActiveState.com

ActivePerl for HP-UX

Question: 

Where can I find ActivePerl for HP-UX?

Answer: 

Current versions of ActivePerl for HP-UX are available with a Business Edition License.

http://www.activestate.com/business_edition/

Finding @INC

Question: 

How can I find out which directories are in @INC?

Answer: 

@INC is a special variable which contains the directories perl looks through for files included through use, require or do statements. To see which directories are in @INC, run the following at the command-line:

    perl -e "foreach (@INC){print $_.\"\n\"}"

ActivePerl and Apache CGI config

Question: 

How do I configure Apache to use ActivePerl for CGI?

Answer: 

To configure appache to use ActivePerl for CGI:

  1. Edit your httpd.conf file. You can open this file by selecting
    Start | Programs | Apache HTTP Server | Configure Apache Server
    | Edit the Apache httpd.conf Configuration File
    which will open
    httpd.conf file in the notepad editor.
  2. Search for "DocumentRoot". You should see a section that looks like this:

    # DocumentRoot: The directory out of which you will serve your
    # documents. By default, all requests are taken from this directory, but
    # symbolic links and aliases may be used to point to other locations.
    #
    DocumentRoot "C:/apacheroot"

  3. Change the value of DocumentRoot to the actual local path to your web site.
    Make sure you use '/' forward slashes in the path. Apache doesn't understand
    '\' backward slashes in paths.
  4. Just below the DocumentRoot section you will see the main directory section:
    Options FollowSymLinks
    AllowOverride None
    

    on the Option line, add "ExecCGI":

    Options FollowSymLinks ExecCGI
    
  5. Search for the line:
    #AddHandler cgi-script .cgi
    

    Remove the '#' at the beginning to uncomment this line.

    AddHandler cgi-script .cgi
    

    If you want to use the .pl extension for your CGI scripts, change the extension
    so that the line looks like this:

    AddHandler cgi-script .pl
    
  6. Save and close httpd.conf.

  7. Restart the Apache service using the Apache Service
    Monitor
    .
  8. Test your configuration by placing the following test script in your
    DocumentRoot directory as 'test.pl' (or test.cgi). Open the
    local URL http://localhost/test.pl in your browser.

    The test script:

    #!c:\perl\bin\perl.exe
    # ^^^ this must be the first line of the script! ^^^
    # start code

    use strict;
    use CGI;
    my $q = new CGI;

    # print header and start the markup output

    print $q->header( "text/html" ),$q->start_html( "hello from perl cgi!" );
    print $q->h2("Hello World!");
    print $q->end_html;
    # end code

Start-up problem on Komodo Pro after evaluating Personal Edition

Question: 

Komodo Pro won't start after evaluating Komodo Personal. How can I fix
this?

Answer: 

If you evaluated Komodo Personal edition prior to purchasing Komodo
Professional edition, you may encounter problems when you try to start
Komodo. This is a known issue when moving from Komodo Personal to
Professional. To get around this, you will need to delete your Komodo
preferences directory, located here:

Windows:

  C:\Documents and Settings\username\Application Data\ActiveState\Komodo\3.5\

Linux and Solaris:

  /home/username/.komodo/3.5

Mac OS X:

  /Users/username/Library/Application Data/Komodo/3.5

If you have already customized Komodo or added to the toolbox, you
will need to back up some files first in the above directory. Copy out
the toolbox.kpf file to preserve your toolbox, and the
schemes sub-folder to preserve any key-binding or font coloring
schemes.

Remove Mozilla Profile Lock File

Question: 

I get the error "Could not remove running lock file". How do I fix this?

Answer: 

Sometimes Komodo will leave an orphaned lock file if it hangs or
quite unexpectedly. If you get an error that says:

  komodo: error: Could not remove running lock file,

Try manually removing the following file:

  .komodo/2.5/Mozilla/default/jhgkjhg.slt/lock

Komodo Debugging with PHP / Apache

Question: 

How do I configure Apache for PHP debugging in Komodo?

Answer: 
  1. Edit the php.ini file that Apache is using and add these values:

        zend_extension_ts=c:\path\to\php_xdebug.dll
        xdebug.remote_enable=1
        xdebug.remote_handler=dbgp
        xdebug.remote_mode=req
        xdebug.remote_host=127.0.0.1
        xdebug.remote_port=9000
        xdebug.idekey=1
    

    To verify that this is configured properly, create a script called 'info.php' containing the code:

        <?php phpinfo(); ?>
    

    You should see the xdebug extension settings section near the bottom of the output.

  2. Open Komodo and go to Edit / Preferences / Debugger. Change the debugger
    listener port to 9000. Also, go into the 'Debug' menu and make sure the
    debugger listener is enabled.
  3. Open up a browser window and point it at a PHP script on your local Apache,
    but first append the XDEBUG_SESSION_START variable to the url:

        http://localhost/index.php?XDEBUG_SESSION_START=1
    

    A dialog-box should appear in Komodo announcing that a remote debug session has been
    requested.

UTF-8 Encoding

Question: 

My non-English language files do not appear correctly. What can I do to correct this?

Answer: 

Customers running with non-English language localizations need to adjust
their Komodo localization settings to UTF-8 unicode:

  1. Click to Edit | Preferences | Internationalization
  2. De-select 'Use Encoding Defined in Environment'
  3. Select 'UTF-8' from the Encoding list.

To change a specific file's encoding scheme:

  1. Open the file in Komodo
  2. Right-click and select 'Properties and Settings'
  3. Select UTF-8 from the 'Encoding' list.

Komodo Invalid License error

Question: 

I get an 'Invalid License' error message when starting Komodo. Why?

Answer: 

Ensure that the version of Komodo you have downloaded and installed matches the license you have purchased (i.e. Komodo Personal vs. Komodo Pro -- the licenses are not interchangable).

You can check the version of the the installed ActiveState license here:

Windows XP:

%USERPROFILE%\Application Data\ActiveState\ActiveState.lic

Windows 7:

%USERPROFILE%\AppData\Roaming\ActiveState\ActiveState.lic

Linux:

/home/%username%/.ActiveState/ActiveState.lic

Look for the line that says "Komodo". Immediately following the version number will be either Personal or Professional. Whichever it is is the version of Komodo you should install. If you have the appropriate license installed, try removing the license file (specified above) and reinstalling the license.

Installers for all versions of Komodo (including older releases) can be downloaded from:

http://downloads.activestate.com/Komodo/

Komodo User Preferences

Question: 

I want to re-install Komodo. How do I keep my user preferences?

Answer: 

User preferences are stored in the following directories.

On Windows 7 and Vista:

C:\Users\\AppData\local\ActiveState\KomodoIDE\\

On Windows 2000 / XP:

C:\Documents and Settings\<username>\Application Data\ActiveState\Komodo\3.5

On Linux and Solaris:

/home/<username>/.komodo/3.5

On Mac OS X:

/Users/<username>/Library/Application Support/Komodo

You can back-up this folder, then restore it once you've reinstalled Komodo. The one exception is the host-<hostname> sub-folder, which contains system-specific information such as your the intelligence database.