[solved]FC 1.5.6 (r862)-itemview (blog) values not displayed

mmmm,
in item view, the following will work if you place favourites in any position

$this->fields->display;
$this->item->fields->display;

in category view, the following will work if you place favourites in any position

$this->items[2]->fields->display;


I have tested this. Also why you say item view for template blog. The blog template does not have an item view.

The items displayed in blog when clicked will be displayed in some other template that has item view.

Regards

ggppdk wrote: Rehne, I see what you mean, no the template blog (in FC 1.5.6 (r862) ) was supposed to work properly,
so must check and fix this, thank for reporting

hi ggppk

well
I have tested it again
when I use the original blog template (SVN 862)

i can even put fields in positions only for the categories layout in the template manager
there is no position 'renderonly'
not even in the item layout
right?

so, when i use it (without changes) to view an item
no field values like title, text, created_by, modified_by, voting, favourites, categories, tags
set in the template parameters will be shown (see the attachment FC-1-5-6-r862_tpl_blog_item_original_missing_values)

with my changes that I have described in the previous post
it works (attachment FC-1-5-6-r862_tpl_blog_item_modified_with_values)

Regards

ggppdk wrote: Rehne, I see what you mean, no the template blog (in FC 1.5.6 (r862) ) was supposed to work properly,

so must check and fix this, thank for reporting

Hi ggppdk,

the FC 1.5.6beta
is still contain this bug
the item view (item.php) from the blog Template shows nothing

Regards

Rehne wrote: i can even put fields in positions only for the categories layout in the template manager

You are right this is a bug, because of exactly what you say above.

There is no editable ITEM LAYOUT for the blog template, thus we cannot enter fields in positions, thus the fields are not created and as a result they are displayed.

Solutions:
1. Always create CORE fields (their html display) in item view since the effect on performance is really small. (item view of blog template only has core fields, that are enabled via configuration parameters, (Globally) in type edit form and (per item) in item edit form

2. Use your suggestion to create fields (their html display) on demand calling the function echo FlexicontentFields::getFieldDisplay($this->item, 'fieldname');

3. Add an editable item Layout to the blog template, this will have the bonus of that we will be able to also add custom fields to the item view of the template.

But we for item view of blog we have CORE fields being displayed not by positions but configuration parameters, so i will see how it is better to do without breaking compatibility , maybe use

Fixed, core item fields will always be created in items view, also added 2 custom positions to the item layout of blog template, making it editable ...

great ... thanks

If you notice anything, feel free to post back. I did not see your reported bug because i read your POST in a hurry and i was not so well educated about item layout of blog template, you clearly stated that problem was in item layout (for item view) of blog template, unlike some other posts in this forum that give no information at all ...

The newly added positions for the item layout of blog template
-- also allows to use custom fields besides core one for the item view
-- plus it warns that some fields are chosen in Type parameters (for types that use blog template to display items), and can be overridden by individual item parameters.

Regards