X-Cart forums

[sabinudash]

Hello,

I would like to turn off the 'Quick view' that appears on mouse-over on product pages on Crisp White template. I could not get the css for this.

Could anyone please kindly help me?

Thank you.

[qualiteam]

You should create a custom module that "decorates" the \XLite\View\Product\ListItem class and makes the isQuickLookEnabled() method always return "false":

PHP Code:

// ...

    /**
     * Return true if quick-look is enabled on the items list
     *
     * @return boolean
     */
    protected function isQuickLookEnabled()
    {
        return false;
    }

// ... 


[ElegantXMods.com]

Hi Alex,
please check my attempts and see where I am most closer to a working code

PHP Code:

<?php
 
namespace XLite\Module\modx\NewArrivalsPage\Controller\Customer;



//abstract class AntiQuickLook extends \XLite\View\Product\ListItem implements \XLite\Base\IDecorator
////no result

//abstract class AntiQuickLook extends \XLite\Module\modx\NewArrivalsPage\Controller\Customer\AntiQuickLook implements \XLite\View\Product\ListItem
////XLite\Module\modx\NewArrivalsPage\Controller\Customer\AntiQuickLook cannot implement XLite\View\Product\ListItem - it is not an interface

abstract class AntiQuickLook extends \XLite\Module\modx\NewArrivalsPage\Controller\Customer\AntiQuickLook implements \XLite\Base\IDecorator
/////no result
{
    /**
     * Return true if quick-look is enabled on the items list
     *
     * @return boolean
     */
    protected function isQuickLookEnabled()
    {
        return false;
    }
}

[qualiteam]

The class that you should extend is \XLite\View\Product\ListItem, not any of those that you used in your example.

And your class is to be \XLite\Module\Modx\NewArrivalsPage\View\Product\Li stItem, not \XLite\Module\Modx\NewArrivalsPage\Controller\Cust omer\AntiQuickLook

[kevinrm]

I have to agree, the "Quick View" is very confusing on the Crisp White. As a customer, when you hover over the product you see "Add to Cart" and "Quick View" easily. It's not clear at all how to navigate to the product to see more information. Even when you click "Quick View", the link to the product details is hard to find.

I would appreciation more information on how to remove the "Quick View" link...

[kevinrm]

Either the "Quick View" button should be removed, or a "Product Details" button should be added. It's not clear to a first time customer how to navigate to product details at all.

[Triple A Racing]

As an interim measure whilst you write and test your module to operate on CWS, pretty sure you could achieve what you want via Custom CSS:

.products-grid .quicklook, .products-list .quicklook {
  display: none;
}
.products-grid .quicklook button, .products-list .quicklook button {
  display: none;
} 

Working with a standard CWS setup, this should remove the functionality and the button we think.

You'll retain the 'greying out' effect i.e. the current active selection of any particular product indicator, but depending on which view you're using at the time, only the 'add to cart button' etc should remain. You can then add any additional guidance notes for visitors on your FAQ page if you think you need it

[kevinrm]

That worked good, thanks!

[sales@webosusa.com]

A better option is to setup the html in it as blank so prevent loading of unnecessary code that would make your page slower to load.
For instance in the custom JavaScript under "Look & Feel" > "Custom CSS & JS" > "Custom JavaScript"


Code:


$('.quicklook').html('');

[Triple A Racing]

Originally Posted by sales@webosusa.com

A better option is to setup the html in it as blank so prevent loading of unnecessary code that would make your page slower to load.
For instance in the custom JavaScript under "Look & Feel" > "Custom CSS & JS" > "Custom JavaScript" Code: $('.quicklook').html('');

Totally agree. Unnecessary code is well worth avoiding, so we applied this ^^ to our own dev store to test it, but after we had done that, all the "Quick View" nonsense remains, even after a "just in case" dev store re-deployment. Quite why Custom CSS works perfectly, but Custom JS doesn't, when both are applied in order to achieve the exact same end result is still a mystery at present. Did you test this against the XC5 "Quick View" function yourself @webosusa ? If you did, was your Custom JS literally, just that one line:

$('.quicklook').html('');

with no other supporting reference code?