Needs work
Project:
Media Browser Plus
Version:
7.x-3.0-beta1
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
17 Apr 2013 at 08:48 UTC
Updated:
10 Sep 2015 at 12:52 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
das-peter commentedPlease provided detail information:
admin/config/development/performanceIt's always a good idea to do complete cache flush:
drush cc allor useadmin/config/development/performanceComment #2
plinto commentedSorry about that:
Drupal version: 7.22
File Entity: 7.x-2.0-unstable7
Media: 7.x-2.0-unstable7
Theme: Adaptive Themes 7.x-3.1
I tried in Chrome (26) and Firefox (20) and got the same error
I only have js aggregation enabled.
I do not get any error messages,
I am also using jQuery Update and have 1.8 selected. I tried with 1.5 and nothing changed.
I checked the firebug console to see if there were any errors but there are none.
All caches were cleared.
Comment #3
plinto commentedComment #4
das-peter commentedThanks for the details.
We just figured out that the latest dev (>2012-11-21 13:00).
I've added the dependency to the list in the release notes.
Doesn't sound very likely but could be an issue.
Tested with Chrome (26), FF nightly (23.0a1) and IE (10) on Win8 64x - no errors.
That was a candidate as a cause - unfortunately it works for me even with aggregation enabled.
Before writing my initial feedback I thought that could be the issue - I've the module enabled as well. But I couldn't reproduce any error with changing the version, even with the module disabled.
That's unfortunate, because now I've not really a clue what else could be wrong :|
Comment #5
plinto commentedI was using upper-case letters and spaces in my taxonomy terms for Media Folders. I renamed the terms by lower-casing everything and replacing spaces with dashes, and now I can browse through all folders.
edit: Now that I remember, I also updated my jquery_update to the latest dev (7.x-2.3+4-dev). Not sure if it was this update or the folder renaming but it is working
Comment #6
bohemier commentedReopening this as I am getting the same behavior but the cause might be different. It happens when navigating MBP under a localized url (ex: /fr/admin/content/file or editing a media field under such an url ex: /fr/node/12/edit). Reverting to the english version of the url (ex: /en/admin/content/file) makes MBP behave correctly. Moreover, I am getting "An illegal choice has been detected...." message when refreshing the page after trying to select a folder, i.e.:
This seems to be caused by the media_browser_plus_folders view, more specifically the media_browser_plus_views_handler_area_navigation.inc function exposed_form. As suggested in http://drupal.stackexchange.com/questions/96669/how-to-avoid-an-illegal-... , setting Validated to True partly solves the problem
The first selection will be successful although the folder will not be selected properly. Subsequent selections will not work. Some more research needs to be done... I'll keep this post updated with my findings.
My setup:
Comment #7
bohemier commented... more research reveals that taxonomy_get_tree() called in exposed_form() returns null when called on the french site.
$folders = taxonomy_get_tree($root_folder->vid, $root_folder->tid);Strange... The Media Folders taxonomy is not localized (No multilingual options for terms). Perhaps this is related to entity translation which I have enabled.
Comment #8
bohemier commentedFound a solution... the call to taxonomy_get_tree() returns an empty tree if called with specifying the prent TID... I don't know why but in this case it seems useless to specify the parent TID since it will always take the root TID... Unless there's something I didn't see. Here's a patch to fix this.
Comment #10
mmelkhatib commentedI am running into the same issue with the Media Folders. Bohemier, I applied your patch but the bug is still present. If anyone has a workaround I am all ears!
Comment #11
gfed commentedHaving the same issue, the patch failed to apply, though the suggested solution did fix the problem for me. This patch does the same thing but applies cleanly against latest dev version (rev 0025c8edbfa338c3ec70de4f5e95feaca07ef5c4)
Comment #12
bohemier commentedThanks gfed. mmelkhatib I also remember having some problems with i18n/entity translation of the MBP taxonomy... can't remember exactly but it might help you to know...