New Content Type does not appear

Hi,
I created a new content type based on 'story' using the export/import into a new content type. The name and machine readable defitions were changed, everything else is the same as story. Once the new content type was created, it did not have the 'channel' menu which determines which channel the content type would be visible. Once a new field from the 'existing fields' was added to enable this taxonomy (channel) availability, this new content type still does not show up under its selected channel. Is there a settings somwhere which determine which content types are part of the story lists in a channel. Thanks.
Zarrar Sheikh Media Developer New York, NY

Hi Beng,
Thanks for the quick reply, I will try this out and post the results here.
Zarrar
Zarrar Sheikh Media Developer New York, NY

Hi Beng,
That worked beautifully, thanks very much. The next requirement is to not show the title of the 'page' in the channel listing, and make it so that it is not a link to the full display of the page. This entire process is being attempted to reduce using 'blocks' which I have too many. A 'page' without a title serves the same function. Thanks.
Zarrar Sheikh Media Developer New York, NY

Beng,
I suppose I should mention the objective: it is to have a content area at the top of every channel that is unique to that channel, kind of like a 'home page' per channel, but without having to use blocks, which are tedious and slowdown the admin work, I already have 700 or so blocks. I know there is better way to do this, I haven't come across it. Thanks for the great software.
Zarrar Sheikh Media Developer New York, NY

Zarrar Sheikh Media Developer New York, NY
For edition nodes, there is can already add the Introduction textarea you can use.
For story listings, there is no such capability. I would say this is a bug. I should be displaying the channel's Description (from channel settings from .../admin/content/channels) at the top of the page. I'll try to get this into the next version of ProsePoint, hopefully soon.
I think the method of using Page nodes is the long way to solving this issue.

Zarrar Sheikh Media Developer New York, NY
If you want the channel descriptions to appear without having to wait for a new release, you can make the following changes:
In the file .../profiles/prosepoint/modules/prosepoint/prosepoint_channel/pp_ch.pages.inc, at line 9, change the function pp_ch_latest_edition() to be as follows:
function pp_ch_latest_edition($term) {
drupal_set_title(t('@channel', array('@channel' => $term->name)));
$output = '';
if (!empty($term->description)) {
$output .= '<div class="channel-term-description">' . $term->description . '</div>';
}
if ($view = views_get_view('channel_editions_archive')) {
$view->set_arguments(array($term->tid));
$result = $view->execute();
$latest = array_shift($view->result);
$view->destroy();
$node = node_load($latest->nid);
if ($node->nid) {
// set $page to true so the node title doesn't show
$output .= node_view($node, FALSE, TRUE, TRUE);
}
else {
$output .= t('There is no edition scheduled for this channel. You probably want to !link for this channel.', array('!link' => l(t('create a new edition'), 'node/add/edition')));
}
}
else {
drupal_set_message(t('ProsePoint error: Missing view %view', array('%view' => 'channel_editions_archive')), 'error');
}
return $output;
}Then, in the file .../profiles/prosepoint/modules/prosepoint/prosepoint_channel/views/pp_ch.views.inc, add the following new function at the bottom of the file:
/* Alter story_view to insert channel description */
function pp_ch_views_pre_render($view) {
if ($view->name = 'story_view' && !empty($view->args[0]) && in_array($view->current_display, array('page_3'))) {
$term = taxonomy_get_term($view->args[0]);
if (!empty($term->description)) {
$view->display_handler->options['header'] = '<div class="channel-term-description">' . $term->description . '</div>';
$view->display_handler->options['header_empty'] = 1;
}
}
}When you do these edits, use copy and paste.
This change will be incorporated into ProsePoint for a future release (ie. after 0.19), so it's safe to patch your copy now.

Beng,
Remarkable. Thanks for the code, I will make the necessary changes. There is one last issue which I am wrestling with. I have about 700 or so blocks, most of which are channel story listings. Is it possible to have one block that displays the listing of channel stories based which channel the end user is on at that moment. Its a very simple simple thing to do, I can see that, but I can't seem to configure a block which allows the listing of channel stories per that specific channel. Im not sure if I am way off here, but perhaps there is a way around to having such a large number of blocks. Your thoughts are greatly appreciated. Cheers, and thanks for the great work.
Zarrar Sheikh Media Developer New York, NY

Beng,
I am able to see the description area without issues. However, I do not see the results of the PHP iframe code that I put in the description. Does it require the use of a PHP filter, or is that already built in. The code I am using is as follows, a simple iframe:
<iframesrc="http://www.examplesite.coml"
Frameborder=0
scrolling="no"
height="500"
width="545">
</iframe>
Thanks again for your expertise in this matter.
Zarrar Sheikh Media Developer New York, NY

1.
Visit .../admin/content/taxonomy on your site, and click on edit vocabulary for the Channel vocabulary. In the Content types fieldset, tick the checkbox for your new content type.
(Note: You may have already done this)
2. Visit .../admin/build/modules and enable the module Views UI.
Then visit .../admin/build/views and edit the view story_view. The display you probably want to change is Defaults, and you want to change the Filter Node: Type to include your content type in addition to Story.
Disclaimer: If you change these settings, you may need to revisit them when ProsePoint occasionally updates a view in a new release. Please be aware of this. I also presume you'll find your way around the Views interface, because it's probably out of scope to explain how to use it since it's advanced configuration. You may break things.