Plans and pricingTemplatesUser docsGo to Overleaf

Release notes 0.x.x

The standard Server Pro license allows you to run the application in a production environment as well as one in a non-production/sandbox environment; it is highly recommended that you provision a non-production environment for testing.

Release notes 0.6.x

Server Pro 0.6.3

  • Fix bug in Sibling Containers feature

  • Basic auto-complete for \ref{} commands

  • Assorted bug fixes

Server Pro 0.6.2

  • Fix bug with login redirect flow

  • Enable Track Changes for all users

  • Various bug fixes

  • Protect user settings pages with "Sudo Mode", Users will be prompted for their password when accessing the settings page.

Server Pro 0.6.1

  • Handle errors in History feature

Server Pro 0.6.0

Release notes 0.5.x

Server Pro 0.5.11

Server Pro 0.5.9

  • Fixed an issue where logins were not being counted for LDAP users

  • Internal improvements to page rendering

Server Pro 0.5.8

  • New Launchpad page to help with first setup: (/launchpad)

  • Fixed an issue with project invites and Saml

  • Various bugfixes

Server Pro 0.5.4

Server Pro 0.5.3

  • Fix a bug where the /register link in nav-bar was not being hidden when using an external auth source.

Server Pro 0.5.2

  • Correct an issue with LDAP configuration, requiring upgrade to a new configuration format.

  • Add an option to restrict project invites to existing user accounts

Server Pro 0.5.0

  • New SAML integration option, link ShareLaTeX to SAML/Shibboleth/etc.

  • Improved LDAP integration, no configuration changes required

  • Option to have user details updated on every login (LDAP and SAML) SHARELATEX_LDAP_UPDATE_USER_DETAILS_ON_LOGIN

0.5.0

  • Code Check mode, shows tex errors in the editor

  • Improved support for plain-text emails

  • Show the current user email in the "Account" dropdown

  • Improved project search

  • Better cookie expiry behaviour

  • Improved spell-check underline effect

  • Old user accounts are automatically upgraded to modern feature set

Release notes 0.3.0

  • All configuration of ShareLaTeX is now done via Environmental variables.

  • Much better LaTeX error parsing, include errors in .bbl files

  • Snappier feedback when changing image

  • Tags/folders can be deleted and renamed via side menu

  • Clone and zip uploads speed improvement

  • User is warned about overwriting files

  • Synctex is more acurate.

  • Prevention against massive projects effecting system

  • Multiple small bug fixes

Release notes 0.2.0

  • Documents are now stored in their own collection, making projects thiner

  • Word count

  • lots of stability work including:

    • Better handling of poor connections over websockets

    • Seperation of web and api routes

Release notes 0.1.3 and 0.1.4

0.1.3 was mostly bug fixes. The notable thing for users running upgrading from old versions in 0.1.4 is user management, and the addition and removal of some settings parameters:

User Management

Public registration is now removed in the open source version. It is a significant security risk to allow public access to a LaTeX installation on your server, and most users have request some for of private user management. See [[Creating and managing users]] for an overview of how it now works.

Added settings

  • appName - This should be set to the name of your ShareLaTeX install. E.g. "Acme Inc's ShareLaTeX Server".

  • adminEmail - The contact email address of whoever is responsible for running the server.

Deprecated settings

  • websocketsUrl - This was the source of most problems with 0.1.2 and 0.1.3 so has been removed. The web service now proxies to the real-time service so the client does not need to know where to find it.

Release notes 0.1.2

The most significant change in this update is the inclusion of a new real-time service which handles the editor websocket connections. These were previously handled by the web service. If you are upgrading from a previous version of ShareLaTeX, there are some things you may need to update to get it all working:

Installing the real-time service

First make sure you actually have the real-time service installed:

$ grunt install:real-time

websocketsUrl

You should add a new line to your config file to include the new websocketsUrl parameter:

# settings.coffee
modules.exports =
    ...
    siteUrl: "http://sharelatex.example.com"
    websocketsUrl: "http://sharelatex.example.com"
    ...

This should be the same as your siteUrl.

Reverse proxy settings

In development the editor connects to the real-time service at http://localhost:3026, a separate end point from the web service, hence the need for a configurable parameter. In production you likely have a reverse proxy set up, and need to forward any requests to /socket.io onto the real-time service rather than the web service.

See the [[Nginx as a Reverse Proxy]] page for an Nginx example, particularly the location /socket.io block.

PreviousRelease notes 1.x.xNextBefore you start

Last updated

Was this helpful?