error on checkout proccess at userpoint.php

-- url of the page with the problem -- : on development
-- HikaShop version -- : 3.0.1
-- Joomla version -- : 3.7.0
-- PHP version -- : 7.1.4
-- Browser(s) name and version -- : any
-- Error-message(debug-mod must be tuned on) -- : Too few arguments to function plgHikashopUserpoints::onCheckoutStepDisplay(), 3 passed in /home/olfaaply/gp/libraries/joomla/event/event.php on line 70 and exactly 5 expected

Once I tested my localsite online with a PHP 7.1.4 powered server I found this error message:

This message shows once I do checkout having some product selected in the cart.

I fixed it going into to the file plugins/hikashop/userpoints/userpints.php

and changing line 741

by


Best regards,

Carlos.

Hi,

Thank you for your feedback. We'll add the patch. This should only happen with the legacy checkout activated. With the new checkout of HikaShop, these parameters are always provided.

Same here,

Testing my new servers (php7 instead of 5) and transfered a client with a backupsite.

Removing the legacy solved the issue, however some items (buttons f.e.) loose their layout so I need to fixed that in css. That's a little annoying cause this is an longrunning webshop, Everything is uptodate (joomla, Hikashop,etc).

Hello,

And did you test in legacy with the patch provided by @PeterChain ?

Regards,

Jerome wrote: Hello,

And did you test in legacy with the patch provided by @PeterChain ?

Regards,

Hi Jerome,
No, I didn't do that.

But sometimes something that seems annoying can be good.

I switched of legacy-mode and now I see you changed some css classes, but seems that the setup is improved now for making stylesheets .
So it gives me some work, but better to go with the setup of your new, improved, version. So I will adjust my css files.

Thanks for your response.

p.s.: is there somewhere a list of ccs classes used bij Hikashop ?

Hello,

HikaShop 3 now comes with new CSS files ; the "frontend_default" has been completely clean up and the old "frontend_default" is now "style_default".
If you're using a customized version for "frontend", we recommend to move the content into a "style" so you would be able to change more easily your CSS with the new rules from the "frontend" file in the same time

Afterwards no, there is no list of CSS class we are using because it would be very difficult to list and "explain".

Regards,