-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Release Notes 2.0
Image ID: 7ae2382c68b3
- File Outline.
- TexLive 2020 is now available.
- Mongo version updated to 4.0 (see upgrade instructions).
- Fixed anonymous read/write project links redirecting to the login page.
- HTML code in SHARELATEX_LEFT_FOOTER is now correctly displayed.
- Fixed SHARELATEX_CUSTOM_EMAIL_FOOTER not working.
- This will be the last CE/SP release where we officially support IE11. The next release in Q1 2021 will no longer be tested on IE11.
Image ID: 83c76915b65a
- Fixed anonymous read/write sharing
- Fixed html links in left footer
Image ID: 6cf8c22f2903
No changes from 2.4.0. This release is just to keep the version numbering consistent between Server Pro and Community Edition.
Image ID: 6cf8c22f2903
- Audit log for users' account settings updates
- This release fixes an important security issue: previously, it was possible for a specially crafted websocket request to bypass project authorization checks. https://github.com/overleaf/real-time/pull/177
- Many small improvements and bugfixes
Image ID: 6fc8c7709df6
Image ID: feb1b349654b
-
TexLive version selector
- (when using sandboxed compiles)
- Show latexmk output in compile logs
- Fixed broken LuaLatex builds when not using sandboxed compiles
- Fixed PDF/A validation broken when not using sandboxed compiles
- Fixed project uploads from zip files with many large text files
- gravatar.com service is no longer used
- Deleted documents no longer count toward overall project file limit
- Improvements to dashboard tag management
- Many small improvements and bugfixes
Image ID: 11dce4970997
- TexLive image not being persisted in project entities (
project.imageName
field)
Image ID: 4b4d9f8d4fad
- Incorrect template layout is now fixed
- Node upgrade to fix CVE-2019-15605, CVE-2019-15606 and CVE-2019-15604
- reCAPTCHA is now disabled
- Removed external access to Google Fonts.
- Other minor improvements and bugfixes.
Image ID: 23f9a28eeef2
- Fixed unable to share projects via email address.
Image ID: 61a994c2584f
- Email confirmation banner can be disabled with the new environment variable
EMAIL_CONFIRMATION_DISABLED: 'true'
- New Archival/trashing workflow
- Project ownership can be changed from the admin panel.
- Admin: improved search using regular expressions
- Other minor improvements and bugfixes.
Image ID: d29f5373eca9
2.0.3 is a Server Pro-only release, no Community Edition has been published.
- Fixed unable to share projects via email address.
- Reenabled recaptcha, which was the root cause of the issue above.
Image ID: 9907ccc100e5
- Fixed link sharing for anonymous users when
SHARELATEX_ALLOW_PUBLIC_ACCESS: 'true'
andSHARELATEX_ALLOW_ANONYMOUS_READ_AND_WRITE_SHARING: 'true'
. - Fixed read-only access to shared projects.
- Fixed SAML logout (Server Pro only).
- Fixed sync between editor and pdf with
synctex
(Server Pro only). - Fixed track changes slow to commit.
- Disabled recaptcha (Server Pro only).
- Importing external files is disabled by default.
-
IMPORTANT: A new
SYNCTEX_BIN_HOST_PATH
is required when using Sibling Containers. Check the setup instructions in the wiki: https://github.com/overleaf/overleaf/wiki/Server-Pro:-sandboxed-compiles#mapping-the-location-of-synctex-in-the-host.
Image ID: cb014e03204a
- SyncTeX not working on Sandboxed Compiles (see workaround instructions).
Image ID: 8fdd3419f5a5
A lot has changed in the last few years, with ShareLaTeX joining forces with Overleaf to create one incredible authoring platform. Now that the merge is complete it's time to release a new version of ShareLaTeX Overleaf Community Edition and Server Pro!
This release brings Community Edition and Server Pro up to date with the cloud-based version of Overleaf. A lot has changed since the last release, with too many bug fixes and small improvements to count, but here are a few highlights:
- A brand new user interface theme
- Improved project dashboard
- A new interface for creating (or uploading) files in a project
- Linked Files: import a file from another project.
- Improved History view
This release of Server Pro includes a few new premium features:
- Rich Text mode: write your document like a rich-text document, backed by nice clean LaTeX
- Improved Sandboxed Compiles: no more fiddling with group permissions (see below)
- Improved Admin Interface: now you can inspect the state of a project from the Admin page, plus many more small improvements
This release adds a few new options to the docker environment. We recommend using our updated example docker-compose.yml file and updating it to reflect your old configuration where necessary.
The new variables are:
-
ENABLED_LINKED_FILE_TYPES
: a comma-separated list-keys, which controls which types of "linked file" are available in the New File modal. Defaults to'url,project_file'
, as in the example file. -
ENABLE_CONVERSIONS
: If set to'true'
, will enable on-the-fly file preview conversions using ImageMagick. Set to another value to disable this feature -
REDIS_HOST
: should be set to the name of the Redis host, same as theSHARELATEX_REDIS_HOST
variable. In the case of a simple docker-compose based deployment, this will just be'redis'
. This duplication is, unfortunately, necessary in the short term while users migrate to the new Community Edition and Server Pro images, and will be resolved in a later release. -
REDIS_PORT
: In case we desire to use the port for Redis other than the default, we need to set the value inREDIS_PORT
to be the same as inSHARELATEX_REDIS_HOST
, for the same reason described above.
And for Server Pro:
-
DOCKER_RUNNER
: set to'true'
when enabling Sandboxed Compiles with sibling containers. See the updated documentation on Sandboxed Compiles. -
SYNCTEX_BIN_HOST_PATH
(introduced in2.0.2
): set to<your_sharelatex_data_directory>/bin/synctex
. Check Sibling Containers documentation for extra context
We've made some changes to the way the Sanboxed Compiles work. In previous versions, the administrators often needed to fiddle with user and group permissions on the docker socket to get Sibling Containers to work. In this release, we've changed all that so it's handled automatically inside the Server Pro container, so it should just work in the majority of cases.
From this release onwards we will no longer support the old "Docker-In-Docker" method of sandboxed compiles, as it has become more and more difficult to get this to work as time goes on. We strongly encourage admins to consider the newer Sibling Containers method as an alternative.
You can now opt-in to a new version of TeX Live. The default is still TeX Live 2017, but you can find instructions on how to get TeX Live 2018 or later here: https://github.com/overleaf/overleaf/wiki/Server-Pro:-sandboxed-compiles#changing-the-texlive-image
Before updating to a newer version of TexLive we strongly recommend backing up your data and update to the latest version of Server Pro available.
The following database migrations have been added, and will run automatically:
- Alter the structure of the User model to support future work
- Change structure of
project.tokens
, to enforce uniqueness on the numeric part of a read-and-write sharing token
Administrators and end-users should not notice any change in behaviour due to these migrations.
If anything seems out of place, or you run into any problems while upgrading, please
get in touch with us via email at support@overleaf.com
- Quickstart Guide (Overleaf Toolkit)
- Hardware Requirements
- Database & Dependencies
- Creating and managing users
- General configuration
- Configuring Email
- SSL & Nginx reverse proxy
- Data and Backups
- Configuring Headers, Footers & Logo
- Password Restrictions
- i18n Languages
- Logging
- Common Config Options
- F.A.Q
- Troubleshooting
- Full Project History Migration