[Invalid cats r1454 - some bugs/errors/problems

Hi,

i do some new more tests

ggppdk wrote: Also upgrade your local site or enable error-reporting on remote site to check for the other notices you have mentioned before, tell me if they appear and provide specific backend/frontend URLs so that i can test

Now everything seems to be OK

Rehne wrote: (the item text (description) is not displayed -AGBs and all others )

i found the problem after long search
and i'm a little confused (i think maybe otherone too in this situation)
in the global config of FC you can choose for
Always create field HTML the option Never unless in a template position
i understand what that means
but for the Standard Template blog (item view)
it should have no impact
ok for the readonly positons 'fields_top' and 'fields_bottom' there also seems to be so
also when the setting Never unless in a template position is use
but NOT for the 'description' that does not appear ussing this setting
I think that should be changed

ggppdk wrote: but what i can not understand
the navigation (breadcrumb) path is not updated
if i change the category of an item
there remains always the same old category
until I change in the menu the link to another item (save) and then change back :

I do not understand ...
however, it is always as described
the breadcrumb is not updated automatically

Regards and thanks for all

1. The pathway is created inside view.html.php of the item view e.g. for itemK

2. but it gets current category id via the menu item variable cid, e.g. catA

3. You have changed the itemK so that catA is no longer ONE OF the categories of the itemK

4. but the menu item pointing to itemK is unchanged so it cid variable is still catA

5. solution: the item model check is the current category (variable cid) is assigned to the item ...
so in view.html.php

replace line:
$cid = JRequest::getInt('cid', 0);
with
$cid = $model->_cid ? $model->_cid : $model->get('catid');

This will use item's main category if current category is no longer assigned to the item

thanks for reporting, i will commit fix,

Hi,

thanks for your detailed explanation
i'm always happy to learn new thing

what do you think about this matter

Rehne wrote: i found the problem after long search
and i'm a little confused (i think maybe otherone too in this situation)
in the global config of FC you can choose for
Always create field HTML the option Never unless in a template position
i understand what that means
but for the Standard Template blog (item view)
it should have no impact
ok for the readonly positons 'fields_top' and 'fields_bottom' there also seems to be so
also when the setting Never unless in a template position is use
but NOT for the 'description' that does not appear ussing this setting
I think that should be changed

Regards

mmm, yes it is done deliberately, it does what it says, but now, that you point this out ...

i think i must add a warning of this, so that people will be informed what to expect ...

If something is not obvious or documented, then it is problematic !!! mmm

Hi George,

i still noticed something
perhaps a similar problem as with the breadcrumbs (previously explained)

within the item edit form
i can make a 'Layout Selection'
normaly 'Type default :: blog ::' will be used
(blog as example)
when i choose now instead of 'Type default :: blog ::'
' :: blog :: ' i can make make changes in the 'Layout Configuration for : blog' like a) show Author name yes or no etc.
ok ... this work fine
but when i change back the 'Layout Selection' to 'Type default :: blog ::' the settings that I have made e.g. a) will be retained
and not the params which i set for the item-Typ using 'Type default :: blog ::'...
Do you understand what I mean?? my english could be really better

Regards

I see what you mean, this is not the wanted behavior, since when you set to use the Content Type Defaults, the custom template parameters that you have entered should not be used.

The problem occurs because if some parameters are not submitted instead they maintain their existing values. This was done so that it is possible to edit an item without allowing user to changes some properties or parameters

i will see how to improve/fix this one

I have opened issue 506 not to forget

Fixed this in r1459, thanks for reporting