Well, turns out for now, I’m going to go ahead and use a post type post as well, so, my urgency dissipated, but, it still would be great to have it be fully compatible with what we can do on our own, instead of being limited in our options if we want to use the CMS Press interface.
I know there are a few things you’ve got hanging around back there that were waiting for 3.0 completion in order to see if they were merged or not as well. I’m sure your eager to get all that settled finally too ?? … I know I am.
I’ve had to do some hacky stuff with rewrites in another function file to interact with the rewrites in your code in order to get an archive page of custom type posts, and I can’t wait to clear out that mess and have it all handled neatly from one place.
On the bug I’ve come across, it’s not a registration problem. I can register fine, and the registration that I’m speaking of is there on my site still at the moment. Will be removing it tomorrow. This is the registration that I’ve had to make manually in my functions file to replace ( tomorrow ) the one that I registered in CMS Press.
// Register glossary terms custom post type
function create_post_types(){
$labels = array(
'name' => _x('Glossary Terms', 'post type general name'),
'singular_name' => _x('Glossary Term', 'post type singular name'),
'add_new' => _x('Add New', 'glossary term'),
'add_new_item' => __('Add New Glossary Term'),
'edit_item' => __('Edit Glossary Term'),
'new_item' => __('New Glossary Term'),
'view_item' => __('View Glossary Term'),
'search_items' => __('Search Glossary Terms'),
'not_found' => __('No glossary terms found'),
'not_found_in_trash' => __('No glossary terms found in Trash'),
'parent_item_colon' => ''
);
$args = array(
'labels' => $labels,
'description' => 'Indexed definitions for commonly used glossary terms within the site',
'public' => true,
'publicly_queryable' => true,
'show_ui' => true,
'query_var' => true,
'rewrite' => array('slug' => 'glossary-term'),
'capability_type' => 'post',
'hierarchical' => false,
'menu_position' => null,
'supports' => array('title','editor','author','thumbnail','excerpt'));
register_post_type('glossary_term',$args);
flush_rewrite_rules();
}
add_action( 'init', 'create_post_types');
?>
As you can see, I’m registering on the init as well.
The problem arises when this code:
function red_glossary_parse($content){
//Run the glossary parser
if (((!is_page() && get_option('red_glossaryOnlySingle') == 0) OR
(!is_page() && get_option('red_glossaryOnlySingle') == 1 && is_single()) OR
(is_page() && get_option('red_glossaryOnPages') == 1))){
$glossary_index = get_children(array(
'post_type' => 'glossary_term',
'post_status' => 'publish',
));
if ($glossary_index){
$timestamp = time();
foreach($glossary_index as $glossary_item){
$timestamp++;
$glossary_title = $glossary_item->post_title;
$glossary_search = '/\b'.$glossary_title.'[A-Za-z]*?\b(?=([^"]*"[^"]*")*[^"]*$)/i';
$glossary_replace = '<a'.$timestamp.'>$0</a'.$timestamp.'>';
$content_temp = preg_replace($glossary_search, $glossary_replace, $content);
$content_temp = rtrim($content_temp);
$link_search = '/<a'.$timestamp.'>('.$glossary_item->post_title.'[A-Za-z]*?)<\/a'.$timestamp.'>/i';
if (get_option('red_glossaryTooltip') == 1) {
$link_replace = '<a class="glossaryLink" href="' . get_permalink($glossary_item) . '" title="Glossary Term: '. $glossary_title . '" onmouseover="tooltip.show(\'' . addslashes($glossary_item->post_content) . '\');" onmouseout="tooltip.hide();">$1</a>';
}
else {
$link_replace = '<a class="glossaryLink" href="' . get_permalink($glossary_item) . '" title="Glossary Term: '. $glossary_title . '">$1</a>';
}
$content_temp = preg_replace($link_search, $link_replace, $content_temp);
$content = $content_temp;
}
}
}
return $content;
}
//Make sure parser runs before the post or page content is outputted
add_filter('the_content', 'red_glossary_parse');
attempts to add the javascript to the links that it creates with the custom post type terms found.
It finds the glossary_term terms, and it assigns the css, and html
to them, but, it will not run the javascript on them.
It’s really baffling to me why this is happening, but, alas, it is, and the only constant is CMS PRess.
If I register the post type in my functions file manually, the javascript works. If I register the post type within the plugin that the code above is taken from, it works. If I register it in CMS Press, the javascript hover function does not work.
I’m really stumped on this as it makes no sense to me whatsoever. I thought you might have some insight?
Like I said, if I have to, I’ll keep it manually coded, but, it just bums me out because I wanted to have a clean interface. I did have all of post types manually coded and was updating them daily as new things were coded in core, but, at a certain point and when it looked like CMS Press was going to be THE one that would handle all of this the best … and because you were doing so much of the coding in core anyway … I removed everything that I had done and redid it all through CMS Press. Long story, but, I’m sure you know what I’m talking about ??
Who knows, maybe you’ll take one look at this and immediately know what’s wrong … I can dream no?
