Release notes 0.x.x
Last updated
Was this helpful?
On-premises
Last updated
Was this helpful?
Fix bug in Sibling Containers feature
Basic auto-complete for \ref{} commands
Assorted bug fixes
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.
Handle errors in History feature
New Track Changes feature
Various bug fixes
Sandboxed Compiles with Sibling Containers
Various bugfixes
Fixed an issue where logins were not being counted for LDAP users
Internal improvements to page rendering
New Launchpad page to help with first setup: (/launchpad)
Fixed an issue with project invites and Saml
Various bugfixes
Fix an issue with SHARELATEX_HEADER_NAV_LINKS option
Fix a bug where the /register link in nav-bar was not being hidden when using an external auth source.
Correct an issue with LDAP configuration, requiring upgrade to a new configuration format.
Add an option to restrict project invites to existing user accounts
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
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
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
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
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:
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.
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.
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.
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:
First make sure you actually have the real-time service installed:
You should add a new line to your config file to include the new websocketsUrl parameter:
This should be the same as your siteUrl.
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.
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.