Had a chat with Alex yesterday, and we worked out a plan for emfield's module naming scheme. We need to make the module names make sense, which make code easier to work with and more consistent.
Specifically, I would like to rename video_cck to emvideo and image_ncck to emimage. Future modules should follow this scheme as possible, such as the forthcoming emtactile for Embedded Tactile Media...
This presents a few difficulties, so we'll need to have a plan for this. Unfortunately, this means that the release of the module will need to be in two phases: the first alpha release will work with the new names, but will not include an upgrade path, which is where most of the difficulties will be.
1) After renaming the modules, there will be an empty hole where the old modules were. We might take the official stance, which is that folks should delete the original directory before uploading the new module. But too many people don't actually do that, and it could lead to errors. Thus, a solution would be to have place-holder modules. (Although this may not actually be necessary, considering the old modules would have an out-of-date .info file.) However, that does mean we need to do this at the same time as the d6 release, rather than doing it later.
2) When renaming the modules, we'd also need to rename the field types and view formatters to match. That's where things get tricky. It won't matter for a new installation. However, it makes things sticky when upgrading: we'll need to search through the database and change table data to match the new naming scheme. Thus, why I'm opening this issue.
This issue is specifically for the upgrade path. It's just a heads up at this point; as I've indicated, we'll get a basic installation working first before we get an upgrade path.
Sorry about the additional delay that will force. However, I think it's the best thing at this point.
Thanks,
Aaron Winborn
Comments
Comment #1
aaron commentedComment #2
alex ua commentedThe renaming is now done- anyone helping to test will currently probably have to reinstall the module.
Comment #3
alex ua commentedNow that we have a working version of Emfield for Drupal 6, we need to fix this so that we can make an alpha release. Just putting it back on top to keep it on the radar...
Comment #4
aaron commentedI believe this is done. Never closed it out. Please reopen this issue if it appears to not properly update the data.
Note for future visitors to this issue: make sure to run all the d5 updates before upgrading to d6. There was a module renamed in the process.