Not working?

Hi Julie,

I’m sorry you are having issues getting DG to working following updating to 3.0.1! I just went to verify that my own install was handling taxon-based logic correctly and it seems to be so there’s something odd going on with your system.

Firstly, can you tell me what plugin you are using to setup your taxons? I’d like to get that installed on my test system and see if I can reproduce the issues you are having.

Also, I know you said you’re working on a test site — any chance that is publically accessible? If not, can you publish the source of a page/post where you are expecting one of your galleries to be displayed (pastebin.com is a good option for this).

Finally, from the Advanced tab of the DG settings, can you paste the options array dump textbox contents?

Thanks!
-Dan

PS: If you’ve found this plugin useful, please take a moment to rate it. Thanks! ??

Hi Dan,

I am using my own code for the taxonomy – it’s on the current site with the older version of the plugin and it’s working fine. Do you still want that code?

The two test sites are local, but I have also uploaded to a live server and am getting the same thing.

From the settings, here is the array dump https://pastebin.com/R5hYuVgz

I keep thinking it’s a setting or something with Ghostscript?

Thanks for responding so quickly

I’ve looked at your options array and it looks fine. There is a new patch release (3.0.2) which resolves a bug, but I don’t believe it will be relevant for your issue.

I don’t need your PHP, but can you give me the HTML generated in a place where you’re expecting a gallery to be generated? Also, if you enable logging and attempt to generate a gallery (by viewing the page where you’ve got a gallery), are there any errors or warning logged?

-Dan

PS: If you’ve found this plugin useful, please take a moment to rate it. Thanks! ??

The page output in the spot I expect it is:
<p><!– No attachments to display. How boring! ?? –>

I remembered that for another site I have using this (the older version) and it was working fine. I still have a draft of the site, so I updated to the 3.0.2 version and am getting the same result – where there used to be thumbnails and descriptions is now empty.

Under logging, I get:
detail (DocumentGallery::doShortcode) Generation Time: 0.00 s
No errors or warnings.

What am I missing? Thanks!!

Hmm… basically that means that the parameters passed are no longer matching your content, which suggests that the taxonomy behavior has changed in this version.

Would you mind terribly trying a plugin’s implementation of attachment taxonomies? I know that the solutions here are working. If that doesn’t work then we can go back to the drawing board, but they definitely work on my system and not seeing your implementation it’s difficult to know whether something may be not quite right.

-Dan

Dan,

At your suggestion, I took out the code I was using and installed Media Library categories. I also added the code that was listed on the plugin site so that Library categories could be separate from post categories. The media taxonomy created by the plugin is called “category_media”

I added a category called ‘taxhelp’ and assigned it to the documents. I changed the shortcode to [dg category_media=”taxhelp”]. I’m getting the same result, a blank area.

Can I possibly send you a login to the testing site to see what I’m missing?

Thanks,
Julie

Hi Julie,

I’d be happy to take a look at your test system. You can email the credentials here: https://dan.rossiters.org/contact-me/

I may not have a chance to look into this until the weekend, but as soon as I do I’ll let you know what I find.

-Dan

For anyone reading this thread, the issue was resolved.

The problem was that only attachments on the page/post where the gallery was generated were being queried against when matching against the category. If you want to match attachments with a given category attached to any post, you just need to include the id=-1 property (eg: [dg category=xyz id=-1]).

-Dan

Thank you Dan for posting the solution above.

I’ve had this problem for a while after upgrading from v2.x to v3.x. I ended up reverting to v2.

Anyway I was forced today to find a solution or revert again as my hosts had logged onto the WordPress admin area and ‘helped me out’ by doing upgrades which broke the site. Just a shame that they didn’t take a backup before doing the ‘upgrades’

Anyway this is a great plugin and used extensively on our site.