I upgraded from 7b to 7c and now my catalog is totally messed up. when i click on a first level category is shows all first level categories and then when i click on a sub category it uses the number of the first level category in the address bar instead of the name of the first level category. Thanks in advance.
Fri, 09/14/2007 - 15:20
Re: Alpha 7c upgrade messes up catalog
The catalog paths changed in this version to make for less error-prone code. Are you using the Catalog block, or did you make menu links manually? If you made the links yourself, you're going to have to figure out what the new ones are. (I know I've said this to someone before, but I don't remember to whom or where I said it.) Sorry if you have a lot of categories, but I promise it's an improvement.
OK, thank you . I had some
OK, thank you 
. I had some primary links at the top of the page that pointed to catalog/top_level_category. I'll just update the links. just curious, is the number in front of the category the category id in the database?
Re: OK, thank you . I had some
I changed the links, now i get a bunch of warnings:
* warning: Illegal offset type in isset or empty in /home/4/a/c/12017/12017/public_html/modules/taxonomy/taxonomy.module on line 1150.
* warning: Illegal offset type in /home/4/a/c/12017/12017/public_html/modules/taxonomy/taxonomy.module on line 1151.
* warning: Illegal offset type in /home/4/a/c/12017/12017/public_html/modules/taxonomy/taxonomy.module on line 1154.
* warning: Illegal offset type in isset or empty in /home/4/a/c/12017/12017/public_html/modules/taxonomy/taxonomy.module on line 1150.
* warning: Illegal offset type in /home/4/a/c/12017/12017/public_html/modules/taxonomy/taxonomy.module on line 1151.
* warning: Illegal offset type in /home/4/a/c/12017/12017/public_html/modules/taxonomy/taxonomy.module on line 1154.and the subcategories aren't the correct ones, they're from a different top level category.
Re: Re: OK, thank you . I had some
the breadcrumbs don't work correctly either.
when i upgraded i removed everything from the ubercart directory and ran update.php and then emptied the menu_cache table.
Hi,
If you theme your
Hi,
If you theme your catalogue by taking the theme_ function and putting them in your template.php it generate the following errors.
You need to take the new theme_ functions in the new catalogue module and retheme it.
Re: Hi,
If you theme your
i don't quite follow, shouldn't it do that right out of the box? what should i re-theme?
Re: Re: Hi,
If you theme your
if you defined theme_uc_catalog_browse() in your template.php, you need to retheme it by taking this function in the catalog.module because it changed between alpha 7b and alpha 7c.
If yo have the catalog grid module, you need to wait an update of it because it know the same problem.
Re: Re: Re: Hi,
thank you zmove! the catalog grid module was messing everything up. i'm going to work on it later today and try and get it updated. btw, what do you mean by taking the theme_uc_catalog_browse function in the catalog.module?
Re: Re: Re: Hi,
If you theme your
what changed in theme_uc_catalog_browse() between 7b and 7c? the api page on this function doesn't help very much.
Re: Re: Re: Re: Hi,
If you theme your
The main problem that 7c causes is that the URLs to the catalog pages have a different format than before. Any modules that relied on the catalog pages being a certain way need to be updated for the new version.
theme_uc_catalog_browse() hasn't changed much more than to reflect this. There's also the category descriptions, but that wouldn't break anything.