Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Resource SaveAs broken when only Module projects (no Course projects) are available #305

Open
jweath opened this issue Feb 28, 2014 · 2 comments

Comments

@jweath
Copy link
Contributor

jweath commented Feb 28, 2014

If a course doesn't have any Projects of its own but rather includes only projects from an associated module, when trying to SaveAs a Resource, no Projects filter into the modal. Users can create, work on, and save a doc created this way, but then it doesn't display anywhere in the course.

Ideally, the SaveAs modal would include Resource projects.

@jweath jweath added the Bug label Feb 28, 2014
@rlbaltha
Copy link
Contributor

Please clarify this issue. I don't follow.

@jweath
Copy link
Contributor Author

jweath commented Sep 12, 2014

Let's try again:

  1. A course can be set up to include a) only Project Folders as defined in the specific course (Class Project 1, Class Project 2, etc.), b) Project Folders from both a specific course AND any associated modules (Class Project 1, Class Project 2, Module Project 1, Module Project 2, etc.), or c) only Project Folders from associated modules (Module Project 1, Module Project 2, etc.)—that is, with all the Project Folders from the specific course deleted (No Project Folder 1, Project Folder 2, etc.)

  2. If you're viewing a Resource, there's the option to click "Save As," which will open a modal window to name the new copy of the Resource, label it, and choose which Project the new copy will be associated with

  3. If you try to do 2) in a course set up as 1c), everything appears to work—you're able to edit the SaveAs copy of the Resource and save it, but when you save and close and then try to find the file, you can't

In writing all this out, I'm beginning to think that this might actually be a fairly complicated bug to sort out. It also brings to light some of the potential complications (or confusion) surrounding how Projects/Resources/files are handled in Marca. But, that aside, does the description of the bug at least make sense?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants