Bug in Virtuemart 1.1.9 with category module

[franzpeter]

The new update VM 1.1.9 seems to have a bug in the shop.browse.php. If the main category has no product but subcategories, where the products reside, VM tells that the category is empty. I did exchange the VM 1.1.9 shop.browse.php with the older VM 1.1.8 shop.browse.php and it works again as expected.

[Tanatus]

Has anybody found the solution?
I have the same problem 

[jenkinhill]

There are just 2 lines different between administrator/components/com_virtuemart/html/shop.browse.php in V1.1.8 and 1.1.9

Around line 36 in 1.1.8

Code: [Select]

$search_limiter= $vmInputFilter->safeSQL( vmGet( $_REQUEST, 'search_limiter', null ));
becomes

Code: [Select]

$search_op= $vmInputFilter->safeSQL( vmGet( $_REQUEST, 'search_op', null ));
$search_limiter= $vmInputFilter->safeSQL( vmGet( $_REQUEST, 'search_limiter', null ));
and around line 85 in 1.1.8

Code: [Select]

elseif( $num_rows == 0 && empty($product_type_id) && !empty($child_list)) {becomes

Code: [Select]

elseif( $num_rows == 0 && empty($product_type_id) && empty($child_list)) {(notice the missing ! in 1.1.9

Try adding in the ! and see if it fixes the issue.

[CaféTango]

The fix did the trick.  Thanks.

Cheers,
Cha

[franzpeter]

That fixes it. But it is also possible to use the shop.browse.php from VM 1.1.8. Despite of that it seems that every update produces more errors.  The '!' is a logical php operator and not an orthographic error. Deleting operators for whatever purpose does not mean a plus of functions. As far as I can see, it was only done to show the sentence that 'category is empty'. from the language file. I think it is more important to show subcategories and products. VM has by default the possibility to unpublish empty categories.

[zanardi]

I am perfectly aware that ! is not an ortographic error, suggesting that the lead developer of VirtueMart 1.1.x does not know about this is very funny :-)
Anywyay, look at this: http://forum.virtuemart.net/index.php?topic=81461.msg268327#msg268327. That is why i made this correction; other users seem to think that THIS is the correct way for it to behave.

Please note that I ASKED LOUDLY for testing of VM 1.1.9 BETA before releasing it, on this forum also, but very few responded. Maybe we could have considered more about introducing this change. Now i will think about it.

@franzpeter: saying that every update produces more errors is simply not true. Not only because this is not really a bug, but even if it was we introduced a bug while fixing other ten or more, and in a complex system like VirtueMart that is not so bad, believe me. I always like to remind that there is no "WE" and "YOU". VM is a community effort, open for everyone to contribute, fix, and bring forward. If it fails, it means that we ALL fail, not just the people who actually commit the code, but every single VM user in the world, ESPECIALLY the ones who make business with it and give back nothing.

Have a nice day everyone!

[yabadabadoo]

Had a mad fright after i updated ...(without backing up ... please dont tell anyone

Just wanted to thank you for posting the solution!!!

 

[bettondesign]

Just had a big scare when updating Virtuemart but thanks to your '!' solution I have fixed it. Thank you

[lipes]

i've got the same problem here when i've update 1.1.8 to 1.1.9 ..

I only change the new:
elseif( $num_rows == 0 && empty($product_type_id) && empty($child_list)) {

to the old line:
elseif( $num_rows == 0 && empty($product_type_id) && !empty($child_list)) {

and now it's solved..  only a problem of the ->      !
thanks to all community!

[Bruce Morgan]

Could someone post the corrected file?

Bruce

[zanardi]

Well, since everyone seems to think the old way is better, i'll just revert the change for the next release.

[franzpeter]

@zanardi,

just my opinion: If VM 1.1.9 with or without the '!' has just a few neglectable 'bugs' now, wouldn't it be better to leave it as it is. VM 1.1.9 is EOL. Investing time and brain would only be necessary, if a serious problem (security issue) would occur, like sql injection or other things.
Why: Changes in the code need often need changes in the theme or in modules or other extensions. I think the most theme and extension developers do not invest a lot of time into further developement for old (EOL) code. The idea of the oscommerce developers to declare 2.3.1 as final and invest all efforts to develop the new 3.xx version, in case of VM 1.1.xx, that would mean 1.1.9 to declare as final and put all effort on 2.xx would be the better way. But as already said, just my opinion.

[mtovarnet]

Thank you

is only dellete "!" character

Gracias

i've got the same problem here when i've update 1.1.8 to 1.1.9 ..

I only change the new:
elseif( $num_rows == 0 && empty($product_type_id) && empty($child_list)) {

to the old line:
elseif( $num_rows == 0 && empty($product_type_id) && !empty($child_list)) {

and now it's solved..  only a problem of the ->      !
thanks to all community!

[Reincha]

hi!
Had the same problem and also added ! to fix it for now, but i actually think the new code is correct. i think there is a problem with $child_list because if child_list is NOT empty e.g - !empty($child_list) - it shouldn't return that category is empty.

Correct me if i'm wrong.

update:
calling for $child_list returns:

Notice: Undefined variable: child_list in ...

[veredanet]

I try the last solution, and it works but not at all. The category tree appears but the link of the subcategory doesn't work.

i apreciate an actualization