It's not about being able to purchase; it's preventing people from purchasing.
A customer placed an order for ~£1k only to be met by an invoice with 40 separate items on it, rather than being grouped together. When contacted, they said "I'm not paying for something on a website which clearly is having problems." They aren't the only customer who faced this.
In the ACP, make traversing between packages and package groups easier. Just like in Content, the parent folder is shown as "..." which goes up a level.
There isn't even any breadcrumbs for when you're going through the package list. When you've got products 2 or 3 levels deep this is extremely frustrating.
I've got a fairly complicated IP.Content setup going on; I'm running 3.3 and have a customised search box for my live site but I'm redeveloping it to use the default search.
I do have it set to search Pages (ccs) and the only way I can get 'tech support' to show the Technical Support page is to physically put 'tech support' as a keyword for the page. Is there any way around this?
I have a page on my site called 'Technical Support' and another called 'Geotextile Technology'.
When I use the search term "tech support" I would expect it to find the Technical Support page - due to it searching for "tech" and "support" in the page name, description and keywords. But it doesn't find anything.
I've lowered the search keywords to 3 so that searching for 'tech' finds both pages.
How does search work exactly? Is it possible to change it so it actually does look for all keywords and not just the phrase?
When you have a big list of products across a few sub-categories, navigating between them is a PITA. You can't go back to the package group; instead, you have to go right back to the beginning and start again.
A suggestion would be to include the exact same functionality as Content, where a [...] link is included to navigate back to the parent.
So I have my website setup and it's all fancy and nice. The aim at the moment is to hide the forum as much as possible (as we'll be using it later on not now). I'm using Content to power the front end of the site - is there any way I can get Nexus to move from ./community/store to just ./store or even on its own subdomain (store.domain.com)?