Nicholas Turbanov

Hey John,

Okay, thanks, sounds just perfect!

1. GREAT!
2. Yeah, that’s what I meant, simply providing a copy/paste of the register_post_type with the determined parameters. This makes migration easy. Or alternatively a plugin dependent export/import.
3. and 4. Understandable. I was simply “thinking out loud”, ie. I don’t quite understand why plugin devs haven’t exposed all the features. Someone might argue that you can already do that directly with the function but in my mind that renders the plugin somewhat pointless.

As stated, this sounds great, please keep working on your plugin, it’s much appreciated.

Hey Rachel,

No worries, I’ll look into it when I have the time and post updates if I can find some resolution.

Hi,

This is exactly what I’d need, but unfortunately your function does not seem to work for me.

Any ideas?

Yeah okay, I’m using custom slugs. Thanks!

Cheers, that does fix it. Up until now I’d just renamed the js-file itself.

Just installed 1.1 and this bug still lingers…

Well as far as I understand (and have used) that’s not how in_category() works.

https://codex.www.ads-software.com/Conditional_Tags#A_Category_Page

What you’ve defined is is_category(), which is only true on category archive pages. That’s not the same thing as checking if the current single post belongs to a category.

Agreed on the latter part. Some flexibility is missing at the moment and that’s understandable, but if you add the ability to add code as well I will definitely make the switch from the original plugin.

Just to give you an example, at the moment there’s not way to specify the ‘in_category’ conditional and thus I cannot define a widget to be visible only on a specific categories single views. So basically:

`is_single() && in_category(array( ‘thiscat’, ‘thatcat’ ))’

Cheers.

Oops, I made a mistake there, should be
$title = $attachment->post_title;
of course.

Anyways, thanks for the plugin!

Ugh, how’d I miss that while going through your code yesterday.

Thanks Alex!

I’m also having the same issue, but I’ve noticed people mentioning the update breaking the feature and asking for older versions. However I cannot locate this setting at all in 1.3.6 so I’m wondering what exactly people are referring to?