In a recent Magento project, I had to display a date when a product would be back in stock. This is fairly straight forward. Create a custom attribute of a date type (stock_due_date) and assign the attribute to the attribute set.
Users of Magento Community Edition have been inundated with security updates recently, after serious vulnerabilities were discovered in the core code. Updating to very latest Magento release (22.214.171.124) promises to plug all these security holes.
Within Magento CE you are able to display certain checkout functionality based on the location of the customer. For example, you’re might want to offer flat rate shipping only to customers in your country. To do this you just select the desired country from the Ship to Specific Countries for that particular shipping method.
You can then test this by choosing to ship to another country and making sure that the flat rate shipping option is not available in the checkout.
You are also able to do something similar with payment methods. I was recently testing that Paypal Pro was only available to customers within the EU. However, I found that Paypal was available to customers shipping anywhere in the world.
The answer was actually pretty obvious really. Paypal looks not at the chosen shipping country but rather the customer’s residential country. I’d been testing using a UK customer and Paypal was available no matter what shipping country I selected in the checkout. Testing with a non-EU customer and I got the desired behaviour – Paypal was not available as a payment method, even if I was trying to ship to the UK.
So, the Paypal Pro payment method at least tests on the customer’s country of origin rather than destination in determining whether the payment method should be available.
I’ve been working with Magento since version one was released, way back in 2008. Along the way I’ve written several bespoke Magento training courses, mostly geared toward helping merchants administer and market their web shops.
So, if you’re looking for an experienced Magento trainer, get in touch.
I’m very pleased to announce that I’ll be reprising my talk on Pricing for Freelancers (“You’re Too Cheap – & not nearly nasty enough”) at the Joomla! & Beyond 2015 (#JaB15) conference in May in Prague.
#JaB15 is the leading European conference for Joomla! developers and integrators, bringing together people from over 30 countries, and this year’s programme is stuffed with great speakers covering a broad range of subjects.
If you’re interested in Joomla! or how it can help you (whether you’re a individual programmer or company) please take a look at the programme and see what’s on offer. It promises to be a really great and inclusive event this year.
I’ll be speaking at this year’s Joomla Day UK conference on 4th October on the tricky subject of pricing. The title of my talk is “You’re too cheap & not nearly nasty enough”, which gives you some idea of what I think about the subject.
Tickets for the event are still available and there’s a great line up of talented speakers. Hopefully we’ll see some of you there.
Pinterest is one of the fastest growing social platforms and can potentially be incredibly useful if you’re selling visual type products – furniture in this example.
Speed is King
Page load speeds are increasingly important to the user experience. People want websites to load in an instance, especially if they’re browsing using a 3G mobile device or have a metered data plan.
If you have a multi website or multi-store Magento store, you will come across the issue of presenting store specific messages to your users. How, for example, do you tailor store specific messages on the 404 Page Not Found page, for example?
Today I came across a really annoying issue with respect to Magento’s search functionality. In essence, regardless of the term the user was entering, Magento returned the same 10 products, & occasionally a correct match!
Looking in the search logs of a search extension I installed, I could see that loads of results were being returned but not being displayed in the actual front end results. Could it be a stale index, or a problem with the cache?
Well, after countless command line reindexing, clearing the cache, checking the search settings in Config (Like & FullText), checking that products were visible, etc, I checked on the display values in the categories. There I discovered that the store’s root category’s “Is Anchor” was set to yes, and there were 14 products assigned to the root category. Amongst these 14 products were the usual suspects appearing in the rogue search results!
In the spirit of trying anything, I set “Is Anchor” to No and removed the products. Bang – the search results started working as expected. I’m not sure why but by this time I was past caring tbh! However, it looks like these settings were restricting the products that could be displayed on the front end. Does anyone know the reason?
I had this occur on another site I’m working on – empty search results. This time the culprit was that none of the products that had been imported via a third party system had been assigned to a website/store.