Michael Mazour 8436b67260 Include project's v1 ID in export requests ... If a project was imported from v1, include its v1 ID when making an export request back to v1. Use case: v1 project exported via ScholarOne and then migrated to v2 needs to be linked up to its earlier v1 export records.		2018-07-02 11:12:42 +01:00
..
Analytics
Announcement
Authentication
Authorization
BetaProgram
Blog
Chat
Collaborators
Compile	fix broken test for compile controller	2018-06-20 13:44:07 +01:00
Contact
Cooldown
Docstore
Documents
DocumentUpdater
Downloads
Editor	Support project-linked-files originating from imported v1 projects	2018-06-13 10:02:54 +01:00
Email
Exports	Include project's v1 ID in export requests	2018-07-02 11:12:42 +01:00
FileStore
helpers
History
InactiveData
infrastructure	replace OldAssetProxy	2018-06-25 12:36:51 +02:00
Metadata
Notifications
PasswordReset	Send out confirmation emails on register and record confirmedAt date	2018-06-21 10:21:15 +01:00
Project	Merge pull request #655 from sharelatex/sk-linked-files-output-redux	2018-06-25 10:28:29 +01:00
Referal
References
Security	Store OneTimeTokens in mongo rather than redis	2018-06-21 10:22:08 +01:00
Subscription	Add method to import invites	2018-06-18 14:48:27 +01:00
SudoMode
SystemMessages
Tags
Templates
ThirdPartyDataStore
TokenAccess
Uploads
User	call v1 affiliation deletion endpoint with POST instead of DELETE	2018-06-28 13:48:28 +02:00