I upgraded Media recently to the latest 7.x-1.0-beta4 and then proceeded to use the media_gallery latest dev version. This causes me to be able to use the gallery but not be able to add any media to a new gallery or after creating my first gallery I cannot add any more.

Comments

dwalker51’s picture

Title: Cannot add media after upgrade to media_gallery 7.x-1.0-beta4 » Cannot add images after upgrade to media_gallery 7.x-1.0-beta4
alanburke’s picture

Subscribe.
Hit the same problem, running latest from git for both Media and Media Gallery.

Cogito’s picture

Status: Active » Needs work

I was having this (or a very similar) issue. I was getting a 404 POST error when trying to add images to a gallery, because it was trying to use a clean-URI address to POST to. When I enabled clean URIs (required me allowing rewrites on apache) the adding of media to galleries worked.

scottiedude’s picture

1. I think I have the same issue. I can see the gallery. (No images yet) However, the option to 'add photos' into that gallery are not there. Anyone else got this issue?

2. Also when I open the gallery, the css breaks for that page too. Anyone know have this one too?

Cogito’s picture

1. Make sure that you have added the 'add media' item to the content view that you are using to display the gallery. I think by default 'full view' or similar is used when you are logged in.

2. The css breaking was fixed for me when I updated to the latest dev build. I believe there is an issue with the formulation of the header.

Not sure why not having clean URLs enabled breaks the media upload, but its possibly to do with the media module rather than this one. Needs more investigation.

effulgentsia’s picture

@dwalker51: Do you have clean URLs enabled or not? I'm trying to understand if you're running into the same issue as Cogito or a different one.

dwalker51’s picture

They are enabled.

David_Rothstein’s picture

Status: Needs work » Active

Note: The clean URLs problem is #1000702: Ajax Callbacks fail if Clean URLs are not enabled, and I just committed a fix for that. It does have very similar symptoms as the problem originally reported here, but since @dwalker51 had clean URLs enabled I guess it must be something else.

Can someone clarify if there is still an issue here with the latest release (7.x-1.0-beta6), and if so, what are the steps to reproduce it?

I'm also setting this back to "active", since there is no patch.

lsolesen’s picture

Status: Active » Postponed (maintainer needs more info)

Setting status to postphoned as the developer needs more info.

lsolesen’s picture

Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)

Cannot reproduce in 1.x-beta7.