Closed (fixed)
Project:
D7 Media
Version:
7.x-2.x-dev
Component:
Media Browser
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
30 Sep 2011 at 03:49 UTC
Updated:
5 Jan 2012 at 19:23 UTC
Jump to comment: Most recent file
Comments
Comment #1
paulgemini commentedHere's the code starting on line 34:
Comment #2
paulgemini commentedAnd here's the commit where the code changed:
Comment #3
CarbonPig commentedSubscribe - same issue
Comment #4
jonathanmd commentedSubscribing. Same issue as well.
Comment #5
szantog commentedAgree, missing path in media_internet_ctools_plugin_api. But I think, this is critical, because of media_internet module is completly unusable without this patch.
The original error message:
Comment #6
szantog commentedHmm.. This is interesting.. I've reimport a database of my work, then I get this error message too. Applied the patch doesn't solved the problem soon.. When I commented the complete class MediaBrowserInternet extends MediaBrowserPlugin {} declaration, I could clear all caches. Then I removed the comment, and everythings worked well.
After this with and without this patch, I can't reproduced any error.
So I'm not sure, need this patch really..
Comment #7
aaron commentedi think it might be related to #1294498: 7.x-2.x UPGRADE PROCEDURE (Sept. 29, 2011) actually.
Comment #8
paulgemini commentedYeah - looks like it. I'm going to keep this open though because at some point there will need to be a clean (normal) upgrade path between versions, right?
Comment #9
bforchhammer commentedI marked #1295522: Fatal error: Class 'MediaBrowserPlugin' not found as a duplicate of this issue.
Comment #10
dave reidI'm not able to duplicate this either with an upgrade or a fresh install.
Comment #11
dave reidComment #12
afsolano commentedComment #13
shiva7663 commentedsubscribing -- same issue
Comment #14
dave reidPlease try using http://drupal.org/project/registry_rebuild to rebuild your file registry. This may solve this issue.
Comment #15
dave reidAfter more discussion in IRC today, I thought this might be a problem because we have the class in the .module file and update.php is trying to do a full bootstrap before it can rebuild the registry. So I committed http://drupalcode.org/project/media.git/commit/5261856 which moved the class to includes/MediaBrowserInternet.inc to hopefully fix this issue. Please test the latest code once the 7.x-2.x-dev release rebuilds in about 12 hours and check if you can run update.php successfully.
Comment #16
dave reideffulgentsia confirmed that the latest commit resolves the issue. We'll roll an unstable3 release in the near future.
Comment #17
girishmuraly commentedFunny, we spent a lot of time trying to solve this problem yesterday at my workplace. We ended up inserting this line into the 'registry' table, before running update.php and it worked, as luckily media.browser.inc was an already existing file. If only we could have just waited for the patch in #15!
Comment #18
mesr01 commentedJust for the records, I got this problem while trying to upgrade from 2.0-unstable1 to unstable2. So I cleared the cache, applied the patch from @szantog in #5 and have my registry rebuilt as recommended by @Dave Reid in #14 and I got back my site up and running.
Thanks guys!
Comment #19
aandreux commented#5: 1295448_4__missing_plugin_path.patch queued for re-testing.
Comment #20
dave reidComment #21
BeaPower commentedFollwed #18, but it didnt work. I get:
DRUPAL_ROOT is C:\xampp\htdocs\b20e1.
Bootstrapping to DRUPAL_BOOTSTRAP_SESSION
Doing registry_rebuild() in DRUPAL_BOOTSTRAP_SESSION
Bootstrapping to DRUPAL_BOOTSTRAP_FULL
Fatal error: Class 'MediaBrowserPlugin' not found in C:\xampp\htdocs\b20e1\sites\all\modules\media\modules\media_internet\media_internet.module on line 39
Comment #23
joshmillerI just upgraded from media-1.x to media-2.x and got this fatal error.
#17 was the most straightforward fix for me. I modified it to this:
INSERT INTO registry(name, type, filename, module, weight) VALUES('MediaBrowserPlugin','class','sites/all/modules/media/includes/media.browser.inc','media',0);TODO: There should be a note on the module homepage that a 1.x => 2.x upgrade needs at least this patch to work.
Josh
Comment #24
dave reidWe just need to roll an unstable3. We don't re-open fixed issues though.