[Plugin: Media Library Assistant] Bad Parent / Orphan possibly wrong?

i think this may likely be the culprit, as i have docs elsewhere, not in the [expand] that show a healthy parent. Look forward to your findings.

I have a similar issue, with images showing up as correctly parented in the library list but as orphaned/bad parent in assistant. In one case, it’s because I’ve uploaded the image to a sidebar callout that is set up using Advanced Custom Fields. In another, it’s because several images are within a post, but set to display (in a lightbox) only when a link is clicked. Are these types of uses something you might incorporate into an upcoming update, or do you have any recommendations for changes I might make?

Thanks!

First, my humble apologies to UaMV – your 1/10/13 post got lost in my shuffle and I apologize for the long delay in responding! Your suspicion that the [expand] shortcode was involved is exactly right. I downloaded Collapse-O-Matic, ran some tests and reproduced your problem. My plugin did not properly handle [gallery] and [mla_gallery] shortcodes embedded within another shortcode such as [expand]. I have fixed this issue and it will be in my next release (probably 1.40). Thanks for posting your page source and the link to your example.

On to new business (brpubs). It’s possible that your “lightbox” issue is the same as the [expand] issue. Are there shortcodes-within-shortcodes involved?

It would be helpful of you could post the Text/HTML from your page/post, as UaMV did above. I can try to reproduce your specific problem if I have more information about how you set up the sidebar callout and the lightbox display. A link to the page, if possible, might be helpful as well.

Thanks for checking that. No worries that it has taken some time to do so. It’s been displaying fine on the front end and I’ve not had to work with the back end too much since. It will be nice it have that working properly in the next release though. Thanks for your work!

Hi David —

Sending page link by email. And yes, it does seem that the issue is essentially the same. One photo is within a “callout” field created through Advanced Custom Fields plug-in, called within a sidebar widget created using Enhanced Text Widget. So there’s a the_field shortcode to pull in the sidebar text the client enters. And the text widget itself is within an aside shortcode.

The other photos are within the body of the page but within a hidden div, referenced by links that open a lightbox, using Lightbox Plus Colorbox. So I guess if Lightbox is using a shortcode both for the link and for the id of the hidden div that the link opens, it also qualifies as a shortcode within a shortcode.

Like UaMV, though, this really isn’t a significant problem since it all displays fine on the front end. I just wanted to figure out what the issue was so that I could explain it to my client when I turn this over to them in a couple of weeks.

Thanks so much for the quick response — and for the plug-in, which is a huge help.

brpubs – Thank you for sending the additional information regarding your example. Further analysis revealed that Lightbox Plus Colorbox was not the problem, and that the images on your page were being picked up by the MLA “Inserted in” logic. In this case, the images had been uploaded twice (not uncommon) and stored with subtly different file names (appending “1” to the name on the second upload). Removing the duplicate items cleared up the confusion.

The sidebar widget containing the image is still an issue. MLA searches the body of every post/page, but does not search widgets, custom fields and other places where an image reference might be found. I am looking into this as a future enhancement.

Thanks again for using the plugin, for bringing these issues to my attention and for working with me to resolve them.

Thanks so much for your help with this — really appreciate it!