Changes between Version 1 and Version 2 of Ticket #12696, comment 5


Ignore:
Timestamp:
Mar 20, 2016, 2:49:04 AM (8 years ago)
Author:
Ryan J Ollos
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #12696, comment 5

    v1 v2  
    33Plugins are [trac:browser:tags/trac-1.0.10/trac/loader.py@:72,73#L36 auto-enabled] if their location is the [trac:browser:tags/trac-1.0.10/trac/loader.py@:114#L105 Environment plugins directory]. If migrating from $env1 to $env2, or even for an in-place migration in which $env2 will be an environment in the temp directory, the plugin will be loaded into memory from location $env1/plugins. The location won't match $env2/plugins so the plugin won't be auto-enabled in the destination environment.
    44
    5 The only direct workaround I can imagine would be to unload the plugins, but it looks like that isn't possible. Perhaps a better indirect workaround is to determine all the autoenabled plugins and temporarily enable the components explicitly in the destination environment.
     5The only direct workaround I can imagine would be to unload the plugins, but it looks like that isn't possible. Perhaps a better indirect workaround is to determine all the auto-enabled plugins and temporarily enable the components explicitly in the destination environment.
    66