Welcome in AjaXplorer 5.0

What's new?

As the changes are really major in this version, please carefully read the instructions below to see if some action is required, before refreshing this page.

Activating the new features

Applying changes for core plugins (conf & auth)

The configurations are now managed from withing the application, and for this reason, the conf/bootstrap_plugins.php file is not used anymore. But to avoid messing up your configs, until you manually remove it (or rename it to something else), it will still be loaded and read by the application. Make yourself comfortable with the new configurations management, make sure the parameters appearing in the GUI are the same as your previous configs, and then you can remove the bootstrapl_plugings file. See below for more details.

Already using a DB-based setup?

If you were already using a DB-Based setup (conf.sql / auth.sql), the tables must have been updated automatically. You may check the Upgrade Report below to see if there were errors. As explained in the previous section, the bootstrap_plugins.php file will still be the master until you delete. To make sure your configuration is up-to-date, do the following :
Also you will have to create the new ajxp_feed table if you want to activate the notifications. After reloading, you will go to the Notification Center and activate notifications here, using the "Install SQL Tables" button to upgrade your DB.

Using a standard serial setup

If you want to activate the notifications, you will require an SQL connexion. Either you have MySQL DB ready to go, or you can simply make sure your PHP has the "Sqlite3" extension loaded, and you will be able to create a lightweight Sqlite db from within the interface.

Using a "remote" setup with CMS bridges

The options have been simplified, but you'll have to manually migrate them. As explained before, your configuration will not be overriden until you manually remove the bootstrap_plugins.php file. Check the Authentication settings panel and update the parameters accordingly. The main changes is that there is a "master" URL pointing to the root of the CMS, and some of the previous values are then computed automatically depending on the CMS type.
The automatic redirection when accessing AjaXplorer as a non-logged user is now disabled by default, which allows the users to log directly from AjaXplorer, and this is particularly handy to create "shared" workspaces to third-party user that are not registered in the CMS directory.
Also make sure to update the CMS-side plugin, using the latest version of the CMS bridges.

What to do next?

You should now wipe out your browser history and cookies, and hard-refresh the gui (using Ctrl+F5 or Cmd+Shift+R, depending on your OS and browser). If you don't see the new interface after that, login and go to Global Configurations > Plugins > Gui > Client Driver plugin, and make sure the theme is switched to "vision".

Upgrade report