Active
Project:
Media: Video Flotsam
Version:
6.x-1.0
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
22 Oct 2010 at 20:57 UTC
Updated:
31 Oct 2010 at 00:16 UTC
I enabled the module on modules page and I got the blank page with this error:
Fatal error: Cannot redeclare _emvideo_zzz_custom_url_default_types() (previously declared in /web/htdocs/www.mysite.com/sites/all/modules/media_video_flotsam/providers/zzz_custo...) in /web/htdocs/www.mysite.com/sites/all/modules/emfield/contrib/emvideo/providers/zzz_c... on line 11
Comments
Comment #1
bennos commentedsame error
not a support request, seems to be a bug.
Comment #2
aaron commentedYou cannot use this module with emfield version 6.x-1. It must be 6.x-2 or greater.
Comment #3
bennos commentedah. ok. checked and for me it is version 2.2 installed.
Comment #4
aaron commented@bennos: please ensure you follow all the steps at http://drupal.org/node/672472 when updating any module. in particular, please follow step 6, where you first delete the old directory. if you don't do that, you will break your site in an update from 6.x-1 to 6.x-2. (alternatively, if you use cvs, you won't run into this problem, assuming you do so with -dP.)
Comment #5
aaron commentedotoh, since you've already updated the module, here's the quick fix:
delete the /emfield/contrib/emvideo/providers folder entirely. that's what's causing the problem.
Comment #6
brightboldSame error here, using emfield 6.x-2.1 and video flotsam 6.x-1.0, and having upgraded according to the recommended procedures. Deleting the providers folder did indeed solve the problem, but that folder was included in 6.x-2.1, not a holdover from 1.x.
Then I realized that by accident I hadn't upgraded to the most recent version of emfield and replaced 2.1 with 2.3, which does not include the providers directory. No error this time.
So this isn't necessarily a failure to have upgraded correctly from emfield 6.x-1.0, it's that this module appears to only be compatible with emfield 6.x-2.3+. @bennos if you upgrade to 2.3 (which, now that I notice it, didn't exist when you filed this issue), you should be all set.
Comment #7
bennos commentedworked now. wiped the complete folder and replced it with the new version 2.3.
works.