10sexyapples

Okay, I turned off all plugins, and the result was the same.

I did notice however, probably unrelated, but, when I have the QMT debug code activated and I click on an authors name/link the resulting url is https://cotaprogram.org/cotadev/author/danielle/ and that is where I get the headers already sent error.

If I remove that code, and hover over an authors name, it shows the url the same as above, but, when clicked the url that is returned is https://cotaprogram.org/cotadev/author/danielle and there is no error.

I also found that the code that I am using to create the custom post type archives is the offending code causing the illegal offset errors when trying to implement the code below for injecting custom post types into author.php … you may recognize it from mine and Krusty Tuffles topics regarding pre_get_posts etc. on the hacker’s list …

// Get custom post types into loops
function my_request ( $request ) {
// Check for proper indexes. An empty $request means we are on the main blog index.
     if ( empty ( $request ) || isset ( $request['author_name'] ) || isset ( $request['year'] ) )
     $request['post_type'] = array ( 'lesson','howto' ); //Modify the $request
     return $request;
}
add_filter ( 'request', 'my_request' );

I’m going to disable the code that is creating my custom post type archives and will report back again with the results of the QMT debug~

Okay, I’m an idiot. I forgot where I was at in the midst of everything, and the info that I was giving you above was with the canonical redirect canceled, which, of course, returns accurately.

Here is the info of what happens with canonical redirect in place. The goal being of course to click on a term, have it redirect to the taxonomy.php template, whereabouts it gets a conditional styling pending the post_type query var.

url:
https://cotaprogram.org/cotadev/lessons

Type-Lesson.php Debug:

Array
(
    [post_type] => lesson
)
Array
(
)
bool(true)

url:

https://cotaprogram.org/cotadev/lessons?grade=grade-one

Taxonomy.php Debug:

Array
(
[post_type] => lesson
[grade] => grade-one
[taxonomy] => grade
[term] => grade-one
)
Array
(
[grade] => grade-one
)
bool(true)

Warning: Cannot modify header information – headers already sent by (output started at /home/cotapr5/public_html/cotadev/wp-content/themes/cota/functions.php:583) in /home/cotapr5/public_html/cotadev/wp-includes/pluggable.php on line 890

I used your debug to take a look at what’s returning for the author.php page as well, just to see if I could round up another clue as to why I am getting illegal offset warnings there when trying to get the custom post types into the query, and I get the same modify header warning on that page as well. These are the only two pages that I am getting this warning, so, I’m going to turn off all plugins except QMT right now and see if one of them is causing this. I know there are no spaces or anything that would typically cause this at the end of my functions file.

I’ll report back in a bit.

Darn. I didn’t see your message before, sorry for the delay~

Url:
https://cotaprogram.org/cotadev/lessons

Debug:

Array
(
    [post_type] => lesson
)
Array
(
)
bool(true)

url:
https://cotaprogram.org/cotadev/lessons?grade=grade-one

Debug:

Array
(
    [post_type] => lesson
    [grade] => grade-one
    [taxonomy] => grade
    [term] => grade-one
)
Array
(
    [grade] => grade-one
)
bool(true)

Well, looking at this, I’m thinking that perhaps it is the rewrite rules for my custom_post_type that are directing this?

Nice. I’m going to give it a shot right now. Thanks as usual Scribu ??

Hi Scribu – I really hope I’m posting in the right place this time.

I’m not sure if you recall, but, I was using the earlier dev version of QMT and had some specific functionality that I needed.

You helped me to get that all sorted with some filters, but, now I am trying to go ahead and use the newer version, which does things a little differently, and maintain the same functionality.

Problem is, like the person above, I need to use the post type in order to customize the reset.

Here is what I have been using for the QMT version I am on:

//I realize with the new version I don’t need this first function, as I can call it with the widget now——————-//

function my_qmt_post_type() {
	global $wp;
	global $wp_query;

    if ( get_query_var('post_type') === 'lesson' ) {
return 'lesson';
}
	if ( get_query_var('post_type') === 'workshop' ) {
return 'workshop';
}
	if ( get_query_var('post_type') === 'howto' ) {
return 'howto';
}
}

add_filter('qmt_post_type', 'my_qmt_post_type');

function my_qmt_base_url($base) {
	$ptype = get_post_type_object(QMT_Core::get_post_type());
	$plural = sanitize_title_with_dashes($ptype->label);

	return get_bloginfo('url') . '/' . $plural;
}

add_filter('qmt_base_url', 'my_qmt_base_url');

What I have are 3 custom made archives of 3 different custom post types using template_redirect and new rewrite rules.

The sidebar of each of these custom archives is where the taxonomy drilldown widgets live.

When drilldown add/remove is clicked it goes to multitax template, where it currently only shows post types from the custom post_type archive page which sent it there. It then resets back to that custom post_type archive.

Multitax is using get_query_var to know what header to show and what sidebar QMT widget to bring in ( also according to post_type )

All three of my custom post types ( lessons, howtos, workshops ) share the same subsets of taxonomies … art subject, academic subject etc.

When filtering lessons, I need to be able to stay within the lesson post type and filter by multiple taxonomies.

I can do that now, but, would like to take advantage of the newer code to regain my category functionality etc.

Is there any way to do this reset now?

So sorry Scribu. Still getting used to using forums believe it or not. Will post appropriately~

Me again, I just wanted to let you know fwiw, I went ahead and tested this, ’cause like I said, it’s good to know, but, the registration didn’t work. It still ignored it. It works if I register a taxonomy to link that isn’t associated with the CMS Press code though.

Hi Michael,

Thanks for that info, it’s good to know. I’ve already begun rebuilding everything to roll my own, but, perhaps having that info here will help someone else that finds themselves in my position.

For me, it’s just preferable to either have it all in a gui or all in my functions. I’m just a clean freak about stuff like that … what can I say.

Thanks for the response though.

Okay, I’m just going to go ahead and remove the code and roll my own again. Thanks anyway.

Yes, but, then aren’t you going to have multiple ids on a single page? This will break your validation and may make for display errors on your page in some browsers. I’m having all kinds of problems with this plugin, but, haven’t experienced the error you’re having. I think you might want to take a deeper look into what might be causing your issue. I could be wrong, but, I don’t think WP requires an id on a select.

@justinendler

I have the plugin configured on a site I’m currently developing, have been for six very long months as it is heavily based around custom post types and taxonomies. I had to turn off the pretty permalinks as well, and as I see no one has answered you back so you can troubleshoot, wanted to offer you entry to look around in here and see if anything clicks before we go live with the site. I’m also having the issue of the latest version upgrade not showing anything in the list view, the listing not showing up on the calendar itself, just the hover, the random appearance of a child-cat under the events category, and there are no listings showing up in the list view when paging either. Was all working before.

I’m just now getting into doing some debugging on it myself, but, thought it might give you some good insight to see it in action here … since I’m experiencing a lot of the issues I’m hearing others have.

Oh, and just a quick fyi, the use of hex code ← doesn’t validate, so, you guys might want to consider using the more friendly &larr. I changed it on my end, but, would be nice to have in core for upgrade sake. And the use of & in some of the strings should be switched to & as well. ??

If you’re interested, just send me an email at angelia{at}10sexyapplesdotcom

Alright, playing around a bit more trying to work this out, and it seems that primarily I just need to get my post_type query var back.

I see that query->set for post_type is set to “any”, so that’s creating post titles that all now say “any” instead of their respective post types.

I’m trying to get pretty much the same functionality I have now with the old version and the extra functions. Can you tell me if I should just stick with the old version, or try to get my query var working again, and implement this new one?

Here’s the functionality I’d like to have:

Currently my clicks on an individual taxonomy term go to taxonomy.php, and I have it styled differently to make it more obvious that the user is no longer sequestered within a specific post type. However, I love that when you click the term directly from the drill_down_widget now it does maintain the post type seclusion and goes to multitax. Problem is, it also does this from anywhere else, so there is never that differently styled list. It would be perfect to be able to keep the functionality of going to multitax if coming from the drill_down_widget, but, have it so that if an individual taxonomy term is clicked outside of the drill down widget it goes where intended … to taxonomy.php.

The add/remove filters to still direct to multitax, or even better, to the respective custom post type archives from whence they came before being clicked.

And of course, I still need to have the no results direct back to that custom post type archive via $base_url.

What do you think?

Hey there Scribu~

Okay, so, I’m going forward with trying to implement the new version of QMT, and the first issue I’m running into is that I have rewrites in place for custom archive pages for my custom post types.

Previously, I was using this method in my functions file to take care of the $base/now $base_url:

function my_qmt_base_url($base) {
	$ptype = get_post_type_object(QMT_Core::get_post_type());
	$plural = sanitize_title_with_dashes($ptype->label);

	return get_bloginfo('url') . '/' . $plural;
}

add_filter('qmt_base_url', 'my_qmt_base_url');

This method creates a fatal error now as it no longer exists, and I’m wondering how I should go about inserting my base_url now?

I need for the filtering functions of each drill_down to maintain their seclusion from the other custom post types. In other words, if I’m drilling down results in workshops, I need to stay in workshops.

Help?

Hi Michael, I understand if you’re too busy, or perhaps don’t care to add this functionality to the plugin, but, please if you get a chance, can you perhaps at least take a look at maybe altering the plugin code to allow me to still register this on my own in my function file? As is, I can’t do this …

register_taxonomy_for_object_type('art', 'link');

… while my art taxonomy is registered via CMS Press.

I will have to re-register all of my custom taxonomies and post types outside of CMS Press and re-enter thousands of terms if I can’t get at least this option.

Any response would really help at this point~

Hey Michael, I’m hoping I explained that sufficiently enough. Please let me know if I didn’t, because I’m getting a little panicky right now.

Just in case:

register_taxonomy(
		'$name', // internal name = machine-readable taxonomy name
		'$object',		// object type = post, page, link, or custom post-type

I’m referring to being able to use object types of post, page, link, or custom post-type.
With CMS Press right now, link is not an option.

I’m at the tail end of a six month long project and the last thing I have to do for completion is to assign the links on the site to the same taxonomies that my custom post types are assigned to … and EEgads there is no link object type checkbox in the form.

I’ve spent all day trying to work it out and haven’t been successful. In your old code I was able to add it in myself … when the supports array wasn’t up to date or what have you, but, you’ve coded the creation of the checkboxes on the form now to happen dynamically via a conditional, and no matter what I try, I can’t get that link checkbox to show up there.

I am able to hand code a taxonomy in functions.php to be registered for the “link” object type with no problem, so, I thought I might be able to just add support for the link object type to my existing taxonomies created with CMS Press, but, that’s not happening either.

So, I’m kind of begging at this point because if I can’t work this out by tomorrow, I’m going to have to ditch all the work I’ve done with CMS Press and hand code it all … again. Help?