Acumen

I have considered this previously, but it complicates things like purchase verification and it requires moderation. I’m building some internal tools to help me offer better support and communicate with buyers better. In the future I may look at tying a forum in.

Cheers!

See the documentation section “Categories”. You have to set the category as an anchor. Then refresh the cache and indices. Magento will display the sidebar if there are enough products to filter.

See the documentation section “Snippets” and look at the example code for “Snippet: Nav Before”. Just create that static block and copy/paste the code into the Magento admin.

You need at least 3 products in each product slider to generate a second slide. Otherwise there’s nothing to slide to and it doesn’t initialize correctly.

The “Featured Products” slider draws from a category. So it’s limit is the same as the default set for categories. You can raise this limit from the admin, but keep in mind it will affect category listings also.

This happens automatically if too many sub-categories exist. You can force all the menus to stack using this CSS:

#nav .cols-1 { width:150px; }
#nav .cols-2 { width:150px; }
#nav .cols-3 { width:150px; }
#nav .cols-4 { width:150px; }
#nav .cols-5 { width:150px; }
#nav .cols-6 { width:150px; }
#nav .cols-7 { width:150px; }

#nav ul.level1,
#nav ul.level0 .view-all
    { display:none; }

The doctype is HTML5 because it’s the most compatible HTML version available, and it’s future-proofing for widgets/code that do use of HTML5’s new elements and APIs.

All elements (whether introduced in HTML 1, HTML 2, HTML 3, HTML 4, and HTML 5) are used semantically and Acumen rigorously improves Magento’s HTML code quality. This is what’s important, not whether an element is being used because it exists.

The new HTML5 elements (section, header, footer, aside, etc) can be used but they’re not required. In no way does this undermine the semantic value of every other element on the page.

The only relevant elements that are new are header/footer/section, and I chose not to replace their HTML4 equivalents in Acumen because this would add a script dependency for IE8. There isn’t a significant benefit to converting code that already validates with both doctypes.

so as you said only doctype ?

Using the HTML5 doctype provides the most tangible benefits. Acumen does use HTML5 form types and attributes as well.

Now I see. The problem is you’re using Magento 1.4.2.0, which Acumen 1.3.4 is not designed for. If you must continue using Magento 1.4.2.0 then Acumen 1.2.4 is the latest release you can use. See the changelog: http://acumen-magento.gravdept.com/tour/changelog/

OK, we’ll upgrade Magento to 1.7.0.2. Thanks for your support.

Cheers!

Thanks for the suggestions!

Yes, the markup for “add to cart” buttons is commented out in the template file. You can uncomment it to display them. See: /app/design/frontend/gravdept/acumen/template/catalog/product/list.phtml

The functions related to downloadable products are disabled in Acumen because the vast majority of stores don’t use this functionality, and it’s confusing for their customers to see. Out of thousands of buyers you’re the third to enquire about downloadable product support, so implementing this has not been a priority.

You can edit the layout and template files to include this functionality, but keep in mind it’s not fully tested with Acumen’s other customizations. Since this affects less than 0.3% of all Acumen users, I need to focus on improvements that have a more universal impact.

Make sure your changes to the config are for the correct website/store/storeView, and then refresh your cache and indices.

I’ve been working on responsive eCommerce (for Magento and clients running Magento) for almost a year now. See: http://gravitydept.com/blog/skinny-ties-and-responsive-ecommerce/

Good things come to those who wait

I see you’ve done a great job. I’ll wait for your responsive template.

You’ll have to post a URL demonstrating the problem so I can examine the markup + CSS together.

I’ve put the slider in the body while I tried to figure it out so I don’t have a URL to show you. I will create one when I get the chance.

Okay.

I just tested the Acumen demo with PayPal Express and it’s working. If you change anything on the review page (after PayPal returns the token), then Magento disables the “Order” button until you click “Update Order Data”. This is confusing but required because of the way Magento + PayPal are integrated. I always recommend stores use Authorize.net instead of PayPal because it is a significantly more streamlined checkout flow.

We use Authorize.net, always have. Just trying to give customers more ways to buy. Nothing changed on the review page, I thought maybe something had to be changed or added, like a phone number, but it just reloads the page. Nothing on the server log either.

Your environment, configuration, and account are of course unique so I can’t say exactly what’s happening. A quick Google for “magento paypal problem” shows you’re far from alone experiencing PayPal issues though.

Best advice: don’t use PayPal Express with Magento. It’s simply not a good user experience and correcting it in Acumen would require rewriting/maintaining a major portion of the module’s core code, which isn’t feasible. Magento has to be the one to improve this.

In the meantime, don’t integrate something that will confuse users simply to offer another payment method. Nearly everyone has access to a credit/debit card.

I’ve been working on responsive eCommerce (for Magento and clients running Magento) for almost a year now. See: http://gravitydept.com/blog/skinny-ties-and-responsive-ecommerce/

Good things come to those who wait

You can hide some elements by CSS alone, but the sure-fire way is editing the template PHTML and layout XML files.

This question is a duplicate. See answer in previous comment.

This is an easy fix, but your account is not a verified purchaser. Unless you contact me via the account used to license Acumen I will not be able to provide support.