Only one product column after update

-- url of the page with the problem -- : flashingroller.nl
-- HikaShop version -- : 3.0.0
-- Joomla version -- : 3.6.5
-- PHP version -- : 5.6
-- Browser(s) name and version -- : All

Hi,

We've updated the site from Joomla 3.6.4 to 3.6.5 and updated Hikashop to 3.0.0
Now all products are in 1 column instead of the 2 columns that we configured. The menu still says 2 columns. Even when we set it to 3 or more there is nog change.

Also the "go to checkout" button in the shopping cart lost it's button layout and is now a normal link.

When we switch to no CSS in the product page the 2 columns seem to return but al lot of other styles are lost.
The CSS options seem to have changed since the update.
Do you have any ideas on how to get the columns back and how to get the checkout button back?

Kind regards,

Bastiaan

Hi,

You have a customized CSS which interfere with the new HikaShop CSS.
And specially the rule line in the line 42 of the HikaShop frontend CSS that you should delete.

For the rest and if you have other styling issues, please check that documentation page :
www.hikashop.com/support/documentation/1...the-display.html#css

Regards,

I have the same problem on my test-site after updating to Hika 3.0

any advice ?

Hi Jerome,

Thank you for this solution it fixed the columns. I will try to look for the checkout button CSS myself.
The custom CSS was not customised by us. I guess it's an old Hikashop CSS file or something.

Kind regards,

Bastiaan

I had the same issue, but only one the home page.

Tracked it down to having Front-end CSS File set to Custom & this was the old 2.6.4 file.
Changed it to default & it works fine

Hi,

@bastiaan - maybe you didn't modify the CSS but you maybe wanted to and the result is that you were using your "custom" css, a copy of an old CSS of HikaShop.

@hkymre- thanks for your feedback

@river - Please check my previous message and the explanation given by hkymre

Regards,

And today it's back to one column so not sure why it suddenly worked last night.

Hi,

You have to check your CSS rules directly in the DOM to see what rule is overriding the HikaShop responsive grid system.
www.hikashop.com/support/documentation/1...the-display.html#css

Regards,

I am having the same issue but don't know how to fix it. You don't expect users to just modify files... It was working and now it is not with the new version, any quick solution here as it is affecting my business?
Very disappointing

My customised css is purchased from HikaShop and it is not working well.

Hi,

HikaShop 3 is a major version of HikaShop. It's the biggest update version since the first version of HikaShop.
We gave 1 month of beta test time so that anyone could install it on a copy of their website and report any issue so that we could fix it before the final release.
No one reported such 1 column issue in that time frame...
Also, for such important update, you're supposed to test it on a copy of your website, not directly install it on your live website.
You can't expect that to work. It's like if you update Joomla 2.5 to Joomla 3 and you expect it to work without changing anything. It's impossible.
We're doing our best but we can't fix what we don't know about.

And yes, for that 1 column issue, you should be able to fix it by editing the CSS files in the configuration page of HikaShop, looking for the CSS code Jerome gave in his message and removing it. It should be easy to do even without knowing how CSS works.

Finally got to the bottom of my issues..

1st problem was because the old 2.6.4 was pulled in
2nd one was I added the code from above to my RocketTheme template override css as I misunderstood - found it using the CSS inspector, removed it and all is good

This may help someone.
This had me stuck for a bit until I discovered that in the configuration "Styles for the Frontend" was set to none after the upgrade instead of default because I had previously not used styles. Changed to default and all seems good. I'm guessing this is only an issue on upgrades, not new installs which is why none of us noticed when testing as a new install.
One of those DOH! moments.