Peculiar issue. Trying to create a content type which includes an image file, using the module's media file selector. Previously uploaded some images in bulk using plupload module. When I go to populate the field and choose library. it only shows me about one older dozen images, not the images I had previously uploaded in bulk (of which there were several dozen). Even stranger: the images will show up when I browse the library in other content types which use the same image field, just not the new content type.

All the settings are the same as all the other content types. I haven't been able to discern a difference in terms of settings.

Can anybody think of why this might be happening? I can't release this site until I get this fixed, and it is truly weird.

Comments

RKopacz’s picture

Bumping this. Sorry, but it persists, and I'm under a bit of pressure. Now, whenever I create a new content type with the media file selector as the widget for the image field, I cannot see my full library when I browse to try to populate the field.

I've tried-
Turning off JS aggregation;
disabling the dev module;
disabling and uninstalling media and plupload and reinstalling;
clearing all caches several times;

etc. Still no luck.

Either this is a bug, or I am missing something obvious in the settings. Note that this is stopped working just for new content types. For older content types, such as the Article content type, it is using Media's media selector widget and I see the entire library when browsing.

Any suggestions on how to solve this would be greatly appreciated.

lias’s picture

I believe I am experiencing a similar issue but with 2.x dev version. I have files uploaded in the media directory which I uploaded prior to using media module. On one site the media library using views displays the older images but as generic thumbnails. Another site doesn't display the thumbnails at all, but, the images that I have currently uploaded do display in the media library.

I am using Views 3x.

spanners’s picture

Issue summary: View changes

I know this is an old post, but just throwing this in there. In your content type settings, ensure that your Allowed URI schemes are set correctly.

I'm running dev versions of both media and file_entity, as per this Drupal Answers post.

We use an S3 bucket for our website's content and RKopacz's post led me to check my Article content type and another custom content type. When I created an Article, all the pluploaded files were available in the Library, but then my other content type didn't display them. So when I checked the Allowed URI schemes, and made sure that my image field settings were the same as my everywhere settings (at the bottom of the field's settings page). I set them to be the same, and then all my bulk-uploaded assets were available in the library.

So to summarise, check your Allowed URI schemessetting on your image field in your content type, and ensure it's the same as the settings down the bottom in the Image field settings everywhere section.

chris matthews’s picture

Version: 7.x-1.2 » 7.x-1.x-dev
Status: Active » Closed (outdated)

Closing this issue as outdated. However, if you think this issue is still important, please let us know and we will gladly re-open it for review.
sincerely,
- the Drupal Media Team