Thread

As a SuperAdmin I have set up a single image gallery with Image and Batch paths set up correctly. I even posted an image, which shows up as should. Now I’d like to set up a Moblog to post to this gallery as I have for several weblog sections. I find though, that upon choosing ‘Gallery’ instead of ‘Weblog’ in the Moblog set-up page, the drop-down menu below.. changes to Choose Gallery. However, no image galleries are showing up to choose. Please see attachment. Any suggestions?

What build and version are you running- should be in the footer.  Let’s see if I can replicate.

ETA- and… not replicating on the latest.  What browser are you using- and do you see any javascript errors?

ExpressionEngine 1.6.0 - Build:  20070724

Tested using Safari and Firefox on Mac.

No errors of any kind are shown as all drop downs change to apply to Gallery items upon changing the radio button choice, yet they do not appear to be collecting contents of gallery schema.

Hm- any chance I can see this in action?  I’d like to turn ‘show queries’ on, see what query is generating the gallery dropdown- see why it’s failing.  Should be:

SELECT gallery_id, gallery_full_name FROM exp_galleries WHERE exp_galleries.is_user_blog = 'n'

Which- can’t see why that would fail.  And if it did, I’d imagine you’d have trouble in the gallery control panel- are you?

Anyhoo- if you want me to go in and take a look- pm me superadmin access- url, username and password.

I turned SQL query display on and gallery_id does not show up anywhere (upon find in page of 25 queries). Queries remain static while changing the radio button… Remains as weblog_id same as previous, yet the form changes… but not the queries. Your select statement is nowhere in sight. If this is a quandary still, I will supply you access info.

It’s not ajaxy- so flipping the radio won’t cause new queries to occur.  But that gallery query should be there on page load- it grabs all of that at one go, the js just flips out the options.

You’re maybe one build behind, are you up for doing a build update?  They’re quick and easy- and it would eliminate file corruption as an option.  It’s also possible there was a bug fix- but I’m not spotting one related to this, and I don’t recall other reports of it.

Still- a build update wouldn’t hurt.  If it’s still an issue- then I can log in and take a closer look.  Sound good?

Yup… the new build solved the problem… Thanks so much for your help!

Glad that was it- it was an odd little quirk!