Moodle

When exporting a single file, can we please have the chance to rename that file?

Details

  • Type: Sub-task Sub-task
  • Status: Open Open
  • Priority: Minor Minor
  • Resolution: Unresolved
  • Affects Version/s: 2.0
  • Fix Version/s: 2.0.8
  • Component/s: Portfolio API
  • Labels:
    None
  • Affected Branches:
    MOODLE_20_STABLE
  • Fixed Branches:
    MOODLE_20_STABLE

Description

It would be pretty necessary for people to be able to rename an exported file if they want to, and doing it on the plugin options screen would be extremely convenient.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Penny Leach added a comment -

Implementation notes:

While callers are busy setting their supported formats, they could also set a $singlefile member variable in their parent class, which can then be used in the options screen.

Martin - note that this will always add the config screen for this case, even if there are no other config options. Is that acceptable?

Show
Penny Leach added a comment - Implementation notes: While callers are busy setting their supported formats, they could also set a $singlefile member variable in their parent class, which can then be used in the options screen. Martin - note that this will always add the config screen for this case, even if there are no other config options. Is that acceptable?
Hide
Permalink
Penny Leach added a comment -

Thinking about this a bit more, there are a few options for single-file exports:

1. Always show the rename field in the config screen. This will force the config screen to be shown even when there's no other config.

2. Only show it if there's already export config.

3. Allow the plugin to decide whether to show it or not. This hooks into MDL-16414 - where I was thinking perhaps about letting the plugins be able to say that the confirmation screen shouldn't be shown if it only consists of information about previous exports (this is for the download plugin)

I want to find the right balance between convenience of being able to rename a file, against making the export as quick as it can be. For example right now most of the exports to mahara go straight through with no extra screens and I wouldn't want to add a 'rename' screen in there, I can rename it in the remote system later, and it already goes into an 'incoming' folder that I want to move it out of. Forcing a whole new screen here wouldn't work in that situation.

Show
Penny Leach added a comment - Thinking about this a bit more, there are a few options for single-file exports: 1. Always show the rename field in the config screen. This will force the config screen to be shown even when there's no other config. 2. Only show it if there's already export config. 3. Allow the plugin to decide whether to show it or not. This hooks into MDL-16414 - where I was thinking perhaps about letting the plugins be able to say that the confirmation screen shouldn't be shown if it only consists of information about previous exports (this is for the download plugin) I want to find the right balance between convenience of being able to rename a file, against making the export as quick as it can be. For example right now most of the exports to mahara go straight through with no extra screens and I wouldn't want to add a 'rename' screen in there, I can rename it in the remote system later, and it already goes into an 'incoming' folder that I want to move it out of. Forcing a whole new screen here wouldn't work in that situation.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Moodle. Try JIRA - bug tracking software for your team.