Hi.
I've not seen this reported in here or couldn't find it.

Today i upgraded my site to 4.5.2 and also installed the taxonomyblock. It uses terms to find products / nodes on my site.

But..., clicking on the node within the tax.block brings us to a url with a blank page.
Let me clarify that:

the node can only be seen with ?q=node/11

the tax.block however points to ?q=node/view/11 and results in a blank page.

What do i need to do or is this a bug?
Tim

Comments

crunchywelch’s picture

Assigned: Unassigned » crunchywelch

Oops, missed that one. Fixed in cvs. You should be able to either get the updated version from cvs, or wait a day or so and the tarball avialable on the downloads page should have the new version when it is rebuilt. Thanks for the report!

Anonymous’s picture

Anonymous’s picture

When I have a 4.5.2 installation downloaded at of 2005/02/05,
and I use the taxonomy_menu with Clean URL's enabled, then
http://host.com/drupal/taxonomy_menu/1

will show a page that works.
But

http://host.com/drupal/taxonomy_menu/1/1

Shows a blank page.

Is this the same problem as above, and the tarball is not yet updated?

Or is this a different problem?

crunchywelch’s picture

try posting this problem on the taxonomy_menu project page, what you describe is not related to taxonomy_block as far as i can tell....

Eagle-i’s picture

I just discovered that the url within the 'READ MORE' line within the taxonomy block does not refer to the right page:

/?q=taxonomy/page/or/1 (it gives me a 'couldn't find page')

instead of

/?q=taxonomy/term/1

It should be last url to refer to the category of terms within it because the tax.block contains multiple tax.terms but has only one 'READ MORE' line. so that would imply it refers to all terms within that category.

Tim

crunchywelch’s picture

Not sure what you mean, can you rephrase this? The urls are formed as taxonomy/term/2+3+1 right now, this doesnt work for you? Are you saying they are not formed like that? ... :/

crunchywelch’s picture

Status: Active » Closed (fixed)

Issue has not been replicated or reported by anyone else. Please re-open if you have more info....