The name of the imported projects does not match the name of the original projects
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
Research direction
Start at the New Project > Upload Project entry point for .zip archives in a Docker-based Overleaf Community Edition instance, then trace how the archive's project name is obtained during import. Reproduce with a downloaded Overleaf.com archive and verify that the created project retains its original name instead of being called "large".
Written by the indexing model from the issue text.
Description
When exporting projects from the public instance of Overleaf.com and importing them into a self-hosted Overleaf Community Edition (running in Docker), the name of the imported project is set to “large” instead of keeping the original project name.
This occurs when using the “Upload Project” function with a .zip archive of a project obtained by downloading the zip with sources from Overleaf.com.
Steps to Reproduce:
- Export a project from Overleaf.com as a .zip archive. The project should have a name other than "large" (e.g., "MyProject", "Thesis Project", etc. )
- On a self-hosted Overleaf Community Edition instance (running in Docker), navigate to the project list.
- Click the "New Project" button.
- Select "Upload Project".
- Choose the .zip archive downloaded in step 1.
- Observe that the newly created project is named "large" instead of "MyProject" (or the original project name).
Expected Behavior:
The imported project should retain its original name from Overleaf.com (e.g., "MyProject"). The filename in Overleaf Community Edition should match the original project's name.
- Dominant language
- Shell
- Stars
- 1.3k
- Forks
- 310
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 1
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from overleaf/toolkit
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
All issues in overleaf/toolkit
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
danielmiessler/LifeOS#2218 ·
-
docs(agents): strengthen the no-backslash-escaped-backticks rule with an issue-creation example Open
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
technical-debt
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
ll7/robot_sf_ll7#9560 ·
-
package-update
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
oSoWoSo/vOid_Community_repOsitory#148 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100