Extension repository
Prev Chapter 4. Professional Version Next

Extension repository

Joomla! strenght relies in its extensions: there is almost an extension for everything you need. Sadly, when you have to manage several websites, it becomes quite hard to keep everything updated or to find the correct version to use.

Since version 2.0 TrackTime offers a useful extension repository, allowing you to organize them.

Manage extensions

Here are listed all your extensions. As you can see, you can search them for Joomla! version, whether they're free or commercial, their expiration date or part of the title.

There is a download link to the latest file version, too, so you can grab it directly from the search list.

Add/edit extension

Name

Extension name

Category

Extension category

Type

Extension type: Component, Plugin, Module or Other

Parent

Is this extension related to another one? For example a component and its plugins (ie Phoca Gallery and its content plugin)

Commercial

Is this extension commercial?

Key

Please insert here the key used for downloading the product (only Akeeba Release System method is supported)

Valid until

Extension expiration date. If you want you can create an event to remember this date.

Version

Latest available version. If left blank and the update url is provided (see below), it will be directly fetched from the update server.

Check updates

Should TrackTime consider this item while automatically fetch the latest version?

Update URL

The public url where you can find the update information.

At the moment these two systems are supported:

  • Joomla! standard system You can find the update url inside the manifest file (look for the element named updateservers)

  • Akeeba Release System (through Akeeba Live Update). This is a little more difficult to find.

    Inside the extension backend folder, there should be one named liveupdate, open the file named config.php. Search for _updateURL, the url assigned to this variable is what you're looking for.

    [Note]Professional versions on ALU

    If the extension you're adding offers a pro version, high probably they're using the same config.php file, changing the update url from the standard (free) one to the pro one.

    In this case you should look for something like this: 

    if(PRO_VERSION)
{
  $this->_updateURL = 'http://www.example.com./pro_version_url';
  $this->_requiresAuthorization = true;
}

    and add this URL.

    I know it's quite annoying, but sadly there's nothing we can do to automate the process.

Import latest version

If the update url is provided, you can automatically download the latest version.

Projects and extensions

In the pro version, the edit project view will have another tab, reserved for extension management:

Add extensions

Surf your extension repository and add the extensions you need

Installed on, Updated on

Installation and last update date

Version

Installed version

Notify updates

Should TrackTime notify if a new version of this extension is available?

Usually you want this option set to 'On', but if you hacked it (or the customer doesn't pay the maintenance anymore), you can switch it off.

Update needed

Is the installed version outdated?

Automatic tasks

Probably this is the most interesting feature. How do you know if a new version comes out, or any of your sites are using an outdated version?

Let TrackTime do the dirty job!

You can set these automatic task using server chronjobs. On your server management page, you have to create a chronjob pointing to this file:

your/server/root/cli/tracktime.php [options]

These are the available options:

  • v Queries every extension update url and fetches the last version number (no download)

  • n Notifies if any site is using an outdated version

  • f Actually downloads the latest available version

You can combine the options in this way:

your/server/root/cli/tracktime.php -nf

[Important]To download or not to download? (this is the question)

You can use the v flag OR the f one, but you can't use them together; otherwise your extensions won't be downloaded.

Infact the v updates the version number, and the f updates and downloads the latest version only if there is a newer available.

As you can see, combining them together will prevent the download, since it will never find a newer version: you just updated it few seconds before!

[Note]Why chronjobs?

Why chronjobs and not a simply system plugin triggered when a user visit the site?

These tasks can take several time, so it's not recommended to rely their execution on a "standard" page visit. Using chronjobs you can spare you a lot of problems and system errors.

If your hosting doesn't offer chronjobs, you can try this service: www.webcron.org/. It's quite cheap and easy to use.

Prev Up Next
Akeeba Subscriptions integration Home Download tokens