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?

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.

Thanks for reporting this issue.

We have detected that this issue has been inactive for over a year. It was reported as affecting versions that are no longer supported.

If you believe that this issue is still relevant to current versions (2.5 and beyond), please comment on the issue. Issues left inactive for a further month will be closed.

Michael d.

TW9vZGxlDQo=

I'm closing this issue as it has been inactive for over a year has been recorded as affecting versions that are no longer supported.

This is being done as part of a bulk annual clean-up of issues.

If you still believe this is an issue in supported versions, please create a new issue.