Development talk:Resource module file API migration: Difference between revisions
| Line 5: | Line 5: | ||
New local files module - contrib - ???? --Eloy Lafuente (stronk7) 16:21, 19 May 2009 (UTC) | New local files module - contrib - ???? --Eloy Lafuente (stronk7) 16:21, 19 May 2009 (UTC) | ||
mod/resource/type/file/localfile.php is a win32 only hack which is not maintained much these days Petr Škoda (škoďák) | mod/resource/type/file/localfile.php is a win32 only hack which is not maintained much these days Petr Škoda (škoďák) | ||
==Extracted from HQ chat, pending to confirm (Y/N)== | |||
I liked the : | |||
* 0 = native 2.0 | |||
* 1= flagged as migrated | |||
* 2= pending to migrate | |||
* lastmodified = for still being migrated-on-demand resources | |||
- so, anything with flag > 2 is susceptible to be marked as migrated (1) by any process (manual/automatic or whatever we can implement) and, at the same time, we keep native (0) and flagge (1) d separate, helping to know the orgin of the resource in case we need it later. | |||
- so, on upgrade... I'd mark everything as pending to migrate (2) | |||
- and then, think on possible ways to perform the 2/lastmodified => 1 conversion | |||
- (but never to 0. it's reserved for native 2.0) | |||
Revision as of 09:36, 28 May 2009
Current problems
embedded images are lost during backup & restore which moves the course to a new site. -- Matt Gibson 08:53, 18 May 2009 (UTC)
Separate contrib modules
New local files module - contrib - ???? --Eloy Lafuente (stronk7) 16:21, 19 May 2009 (UTC) mod/resource/type/file/localfile.php is a win32 only hack which is not maintained much these days Petr Škoda (škoďák)
Extracted from HQ chat, pending to confirm (Y/N)
I liked the :
- 0 = native 2.0
- 1= flagged as migrated
- 2= pending to migrate
- lastmodified = for still being migrated-on-demand resources
- so, anything with flag > 2 is susceptible to be marked as migrated (1) by any process (manual/automatic or whatever we can implement) and, at the same time, we keep native (0) and flagge (1) d separate, helping to know the orgin of the resource in case we need it later. - so, on upgrade... I'd mark everything as pending to migrate (2) - and then, think on possible ways to perform the 2/lastmodified => 1 conversion - (but never to 0. it's reserved for native 2.0)
