Today is “Black Friday” in the States, which signals the start of our holiday gift shopping season. This means tomorrow is “Small Business Saturday,” also sometimes referred to as “Shop Small Saturday.”
“Shop Small Saturday” is an effort to drive holiday shoppers to smaller businesses, which rely on holiday spending for their survival. I selfishly think it’s a great way to find gifts that are more interesting and unique than what I find in mega-stores.
I just finished preparing the gench site for “Shop Small Saturday” and thought I’d share some handy resources I found. Continue reading
For the music label site I’m creating, the client wants to prevent people from ordering items no longer in stock, but he wants to continue displaying them as they represent his discography.
For a high-volume Drupal Commerce site, you’re going to want to write or use a custom module for inventory control (like Commerce Stock), but that seemed like overkill for this project.
I decided to deploy a solution that doesn’t require any additional modules – just a little jQuery and the addition of a status field to my product variation type.
I wanted to change the message of the add-to-cart confirmation popup message on the gench site.
I’m using the Commerce Kickstart distribution of Drupal. Utilizing the Theme Devel module, I can see that a contributed module named commerce_add_to_cart_confirmation is delivering the message text I want to change.
Thanks to my newly minted DrupalizeMe knowledge, I know I can override a contributed module’s function(s) from the theme layer. So I find the function responsible for the message in profiles/commerce_kickstart/modules/contrib/commerce_add_to_cart_confirmation/commerce_add_to_cart_confirmation.rules.inc. I copy & paste the function into my theme’s template.php file. I preface the name of the pasted function with the name of my theme followed by an underscore (genchstyle_). I change the message text, save my new function, clear my cache and load the confirmation message: no change. Why? Continue reading
I’m excited to see this white paper on PCI compliance published today. This couldn’t be better timing for me, as I plan to spend the next few days on final shopping cart QA and security checks for the gench site.
It looks like most of the recommendations are pretty straightforward, but the big take-away is that I have to make sure the shared hosting service for the new gench e-commerce site is PCI DSS compliant. Something tells me earthlink probably isn’t compliant (their support guy once asked me for my password!!!).
My client is reluctant to move the gench site to another hosting provider, but we may have to if we want to avoid the huge fines and headaches non-compliance could entail.
Is it just me or is it the case with Drupal that the things that seem like they ought to be really hard, end up being super easy, and that, conversely, things you figure will be a slam dunk end up taking a week to figure out?
Case in point: I just spent three days I will never get back setting up two simple shipping rates for the gench site. I had smugly budgeted about 15 minutes for this task. It’s shipping – not rocket science – right?
I did finally figure it out, but it turned out there was one major barrier to overcome: my innate stupidity. Continue reading