Mark

I just stumbled across a couple of things that I think are good resources as far as this topic of conversation goes.

The first is on Ozh blog (how came I haven’t been subscribed there until now? geebus), and is a little more in depth on the code you posted: http://planetozh.com/blog/my-projects/wordpress-hooks-filter-flow/

It’s oldddddd, but it still does the trick, I ran it on a local copy with absolutely no quirks. This, and what you wrote, proves my assumption that there was probably a way to retrieve this list easily enough.

The second, relating more to what you’ve been mentioning, was just recently posted on WordPress Tavern: http://www.wptavern.com/is-a-plugin-validation-team-a-pipe-dream

Definitely worth checking out if anybody is out there looking at this thread.

Thanks guys, but I’m not new to PHP. 🙂 PHP variables and member properties are case sensitive, functions are not. That is why the following code;

function test () {
    echo 'test';
}
function Test () {
    echo 'Test';
}

Will return; Fatal error: Cannot redeclare test() (previously declared in ***.php:1) in ***.php on line 3

So not the issue, though I’ll make sure I double check my semantics in the future. In the meantime I’ve discovered using get_cat_ID was pointless anyways as inside of the foreach loop I had access to $category->cat_ID.

Nonetheless I still get some odd business with get_cat_ID() – I turned on paging for my custom loop, and for some reason previous_posts_link() was working but next_posts_link() wasn’t. So I took the body of my function which created and displayed the custom loop, and placed it directly in the page just to see if there was a global missing somewhere. Upon doing so, get_cat_ID failed again, this time for gawd knows what reason.

Not sure, but I think I’ll start by looking at the functions body itself.

What version of WordPress are you both running? Worked flawlessly for me the second time when I deactivated the original plugin.

That’s a snazzy solution, but still doesn’t seem to work with add_shortcode().

function init_codex ()
{
	if (is_page('theme-codex')) {
		include (TEMPLATEPATH.'/lib/codex/theme/theme_codex.php');
		add_shortcode('theme_codex', array($kats_theme_codex, 'shortcode_func'));
	}
}

I even tried this function as a plugin, and no go there either. It won’t parse the shortcode if it’s added this way.

Looks like you can’t use the built in functions to do this, which is okay. The alternate solution is fairly eloquent in it’s simplicity though I suppose;

if (strpos($_SERVER['REQUEST_URI'], 'theme-codex')) {
	include (TEMPLATEPATH.'/lib/codex/theme/theme_codex.php');
	add_shortcode('theme_codex', array($kats_theme_codex, 'shortcode_func'));
}

Which seems to work just fine. 🙂

Everybody really needs to stop getting retaliatory when somebody offends their plugin. If you release something into the widespread community, no matter how fantastic it is, it will get some poor feedback. I’m sure there’s places where people hate WordPress itself, maybe even posted on these forums, but I doubt you’ll see Matt come in here and tell them they’re being ridiculous.

Take the bad with the good, and grow with it, or at least roll with it. 😉
</soapbox>

Honestly, some of us are just plain frustrated and speaking for myself only, I’m still frustrated, but dealing with it better now. 🙂