Category Archives: magento

  • -

wooCommerce vs magento

Category : magento , wordpress

WooCommerce vs Magento: Which E-Commerce Platform Is Right For You?

wooCommerce vs magento

WooCommerce vs Magento: Which E-Commerce Platform Is Right For You?

Two of the most popular e-commerce platforms on the market today are WooCommerce and Magento. A source of many blogger debates, they both have their strengths and suitability for different needs. One is a standalone product, now owned by eBay, whereas the other is a plugin for WordPress. They have the backing of their own strong communities: WordPress users for WooCommerce and eBay advocates for Magento.

The debaters feel so strongly about their e-commerce platform of choice since they’ve seen success in their own businesses. Joining them is fairly easy because online businesses are a lucrative area to get into in this digital age. The e-commerce platforms are so easy to set up and use, and come with minimal set up costs, so the barriers to entry are low.

If you’re thinking of setting up an online business, these two platforms will undoubtedly appear somewhere on your short list. So which should you go for?

The Similarities

Firstly, both WooCommerce and Magento are open source products. This means that the original code is freely available to anyone and they can build on it or modify it to create a product that works specifically for them.

One of the reasons WooCommerce and Magento have such large communities is because open source software creates an appreciation of sharing. Developers go on to share their own versions of the open source software to carry on this aspect of giving.

What this means for you as a new business owner is 1) the initial product is free to use and 2) you’ll have an abundance of help from the community.

Community

The way WooCommerce and Magento make their money is through the extras you’ll likely need to purchase over time as your business grows. This “freemium” business model can catch the unaware, so consider your future needs.

For instance, you’ll want to customize the branding of your website to your business and you’ll need to unlock this ability through plugins or a developer’s time. It’s worth keeping in mind that being able to customize your site is only achievable because both WooCommerce and Magento are self-hosted.

If you opt for a hosted solution, for example through Shopify, you’ll have the benefits of quickly building an online store through a few clicks of buttons, plus you won’t need to worry about managing the security of your checkout. However, your customization options will be severely limited. Therefore, WooCommerce and Magento are both brilliant for making your e-commerce shop your own.

Finally, what’s most important when building an online store is, of course, the products and communication with your customers. Both WooCommerce and Magento allow you to upload unlimited products and manage them effectively. You can also add a blog to add a friendly voice to your e-commerce site and help with SEO.

Blog

Differences

Setting Up

Starting up any business will come with hurdles but you don’t want the e-commerce platform you choose to be one. Obviously if you’re already a WordPress user and want to add an e-commerce element to your site, it makes sense to choose the e-commerce plugin, WooCommerce. Therefore you won’t need to get used to another interface or migrate your site to another platform.

Even if you don’t already have a WordPress site, WooCommerce is perfect for beginners. WordPress is so easy to use and WooCommerce is simply an extension of that. Customizing your site through WordPress is really simple due to the number of plugins available. Plus, WooCommerce has tutorial videos to help with the set up.

Tutorial video

Magento’s interface is also really easy to use and it comes with tutorial videos and documentation. It has a full installation wizard too. However, Magento’s difficulty is increased when you want to start adding extensions to your site. In this instance, you might want to think about hiring a Magento-specialist developer.

Costs

This leads us nicely onto costs. Initially, both e-commerce platforms are free (although there is an Enterprise version of Magento). You can download them and get started on building your shop straight away. However, you’ll find that certain things like a full range of payment options beyond just PayPal and bank transfers are essential if you are to grow your business. WooCommerce is limited on these basic options and the plugins and extensions that you buy will add up.

Extensions

However, adding extensions to Magento is also a necessity as you grow and offer your customers a superior shopping experience, and you’ll find that you’ll need to fork out money with Magento too. Magento developers are harder to find than WordPress developers and you do really need one to install the extensions properly, so this is another cost that needs to be considered. WordPress is easier to use by individuals of varying experience, whereas it’d take you a long time to do it yourself through Magento.

A cost that you might not have considered is hosting. WooCommerce is fine to run using WordPress’ hosting, whereas Magento is a little more complicated. You should use dedicated servers or a cloud plan of your own as your product portfolio grows, otherwise your website will run slowly. I know I get frustrated with slow websites when shopping, so think about the user experience of your customers.

Right from the beginning, you ought to be thinking about your long-term goal and your budget. The initial costs associated with setting up WooCommerce and Magento won’t be your only costs, as we’ve already established. But you should also think about your needs – would the extra features that Magento provides over WooCommerce be wasted on you? Or if you predict that you’ll need them, are you willing to put in extra budget now rather than spend the money migrating your site to Magento in the future?

Let’s take a look at those features in more detail.

Features

With any e-commerce platform, you’ll need to be able to have a shopping cart facility and upload infinite products and categorize them. You get these basic features with WooCommerce and Magento. But which allows you to further customize your shop and give your customers extra facilities when buying from you?

Magento wins on this point. You’re able to cross-sell or up-sell your products, compare products, add discount codes, and use an advanced filter to navigate your products. Plus, if you have more than one store, you can view them all on the same account. This is great for creating localized versions of your store.

WooCommerce is simpler, which can be a good thing for those just starting out. You can rate products and feature best sellers or sale items through the available widgets, but anything else more complex will require an add-on. However, keep in mind that because WooCommerce is a WordPress plugin itself, it can work with an array of other WordPress plugins. The navigation is sophisticated, but not as much as Magento’s since you can only filter by one attribute.

WooCommerce features

Either within Magento or as another WordPress plugin for WooCommerce, you’re able to view Google Analytics for both platforms. This is important to see the success of your business as a whole, or for viewing individual items and using this to work out a strategy across your product portfolio.

So, to make a choice based purely on features, Magento comes with the better basics. However to improve on your site, you’ll need to invest more. You have access to Magento Connect, which offers thousands of extensions to add to your site, but you’ll need a developer to install them properly.

Magento Connect

WooCommerce also offers extensions through the WordPress plugins, which are a lot easier to manage and some are even free. Examples of plugins include WordPress SEO by Yoast to help with your search engine rankings, Askimet to filter spam, and Gravity forms to provide a form solution.

The bottom line is cost. If you can afford to hire 3rd parties to improve your site, it’s well worth expanding on the features of Magento. You can’t really try to do it yourself and save money, since it’s more of a steep learning curve with Magento.

Themes

What makes both WooCommerce and Magento attractive to both developers and online business owners alike is how customizable they are. With hosted products, you just don’t get this flexibility. The first thing to choose when customizing is the theme of your site.

Within both WordPress and Magento, there are thousands of free and premium themes to choose from. They all come with their own features like responsive layouts across all device sizes and demo content that you can simply download and import into your own site. Many WordPress themes use their ability to integrate with WooCommerce as a selling point – the developers choose this e-commerce plugin themselves.

For instance at Elegant Themes, there are six  WordPress themes to choose from that focus on e-commerce. Looking specifically at eStore, it’s an elegant design that you can configure easily and sell your products through WooCommerce. If you chose this theme for your online store, you’d benefit from a secure and valid code, browser compatibility across all popular browsers, and easy translation so you can localize your store. You’d also have fantastic support and you would be assured that you’re always up to date since the themes are updated to the latest version of WordPress. It’s incredibly easy to use – you simply design and manage your site through the page templates and ePanel, rather than messing around with code and PHP files. See the live theme demo here.

eStore

The Final Choice

Magento tends to be popular with larger businesses or agencies who manage e-commerce sites on behalf of clients. Magento is scalable, so it’s perfect for those with grand plans or an existing successful online store. It has a few more basic features and once installed by a developer, the extensions are brilliant too. However, you’ll need a big budget to set this kind of store up.

WooCommerce through WordPress is perfect for smaller businesses and those with less developing experience. It does the job of selling your products and as you grow, you can add the many plugins available to build a better experience for your customer. It’s also the best solution if you’re used to the WordPress interface or already have a domain set up and you now want to make products available to buy through your site.

One thing to remember is that Magento was designed specifically for e-commerce stores. However, that doesn’t make the plugins and extensions to a WordPress site any less effective. WooCommerce isn’t a standalone CMS, but it works within WordPress, and as a WordPress enthusiast, that makes it an even better choice for me!

Source


  • -

Magento vs wordpress what to choose for better seo

Category : magento , wordpress

Magento vs wordpress what to choose for better seo

Magento vs wordpress what to choose for better seo
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Every website owner spends time and money in brining the website to the top of search engines. With several online platforms like WordPress and magento, the present generation is a little bit confused about which one to select. Google is the world favorite search engine and the rakings on the same plays a good role in attracting the customers and to double the business. Search algorithm of google is a secret and it is not known outside the Google. But the experts on the basis of results generated by Google studies about the search criteria of the search engines. SEO value of the articles plays a good role in the creating the impact. Most of the people look for the points related to Magento vs. WordPress to select the best one.

Exact idea about your need

Search criteria of the search engines differ with the nature of your website. Different approach is taken by the search engines for ecommerce page, general pate, blog page, article page, forum page etc. You should have clear cut idea about your need before selecting the best form of open source to publish your content. Otherwise your page will rest in the bottom of search engine results making your efforts in vain. Once you have succeeded in selecting the right source as per your needs, you can certainly add SEO value of the articles.

Magento and Ecommerce

Most of the present people prefer Magento for ecommerce based web pages and articles. This shows that search engine gives importance to Magento platform for ecommerce based articles and applications. So if your article or website is for ecommerce, it is certainly a good idea to go for Magento instead of WordPress. WordPress ecommerce users are turning to Magento to get quick and positive results for their ecommerce needs online.

WordPress and blog articles

If you love to make an extension for your website or to submit just a blog article about your product or service, then WordPress is the best platform to use. Search engines give importance to WordPress blogs when searching for general information on products and services. WordPress pages take short time to get it in to top of the search results with their SEO value for articles. Hence, if you are looking for the best platform to publish a blog or article, then go for WordPress platforms.

Maintenance

Since both are open source platforms, it is so easy to maintain and the make the changes in the contents as you wish. Ecommerce people can make use of both WordPress and Magento. WordPress can be used to publish articles and blogs and Magento for online business purpose.

Hence, how we select is what brings the real SEO value for articles and the best in Magento vs WordPress.

Source


  • -

Which cms is best for ecommerce website

Category : magento , wordpress

Which cms is best for ecommerce website

Which cms is best for ecommerce website
 
 
 
 
 
 
 
 
 
 
 
 
 
 
So you’ve decided to rebuild your company website to improve the user experience… now the question is: WordPress or Magento, What platform should I build my e-Commerce site in?

These days, there are literally hundreds of e-Commerce solutions to choose from – all with their own advantages and limitations. The most popular among them includes Magento, WordPress, BigCommerce and Shopify, just to name a few.

But what suits one company will not necessarily work for another. To make an informed decision, you really need to decide what it is you want to achieve and then match the capabilities of each.

We’re going to look at the key difference between the two most popular platforms, Magento and WordPress. By the end of this article you will be more equipped with the knowledge to make the right decision.

 

EVALUATING YOUR OWN BUSINESS

 

Before delving into the pros and cons of each platform, the first step is to work out exactly what you are looking for in an eCommerce solution.

Based on the complexity of your services, you may opt for a dedicated eCommerce platform (such as Magento) or a content management system (Such as WordPress) that includes an eCommerce component (like Woocommerce).

The best way to do this might be to simply list your primary objectives and goals for business and the project at hand.

Below are a few things to consider that will eventually help you make a decision:

 

  • Current revenue from online sales – if the overall business revenue is driven through online sales, or you solely have an online presence, then the CMS option may not be the right for you. The specific eCommerce solutions are designed to address the more complex process of high-level transactions.
  • Amount of products and catalogues – in a lot of cases, the amount of products and scalability can be the decisive factor in choosing the right solution. There is no rule of thumb but generally, if you have more than 500 Stock Keeping Units (SKUs) then the dedicated eCommerce solution will be the better option.
  • Complex purchasing process – how much customisation is required to make the checkout process fit your online store? By default, most solutions provide a similar cart/checkout experience.  However, if your business model requires customising the checkout then choosing a platform that has flexibility is imperative. As a helpful rule, it’s always better to find a solution that suits 100% rather than purchase a 90% fit that requires 10% customisation.

It can often be hard to determine a stand-out leader amongst the eCommerce platforms and CMS solutions available – as they all offer a range of different features. Just be careful, as too many irrelevant features can make your website confusing, slow down the load-time and become an absolute nightmare from a developer’s point of view.

Let’s take a look at some of the pros and cons of two of the most popular solutions, WordPress and Magento…

WORDPRESS

Although WordPress began as a simple blogging platform, over the last decade it has matured into a solid CMS solution with many plugins available to enhance your website with a range of fully-functional eCommerce capabilities.

Today we’ll be specifically looking at WooCommerce, a popular plugin created for WordPress.

WooCommerce is ideal for small and medium-sized online stores.  It’s a free open source eCommerce plugin and in the last few years has seen incredible growth.  It has had over 5.7 million downloads (at the time of writing this post) and due to this overwhelming popularity, is considered one of the fastest growing shopping carts available.

Out of the box, WooCommerce isn’t as powerful as Magento but there are plenty of really good plugins available to meet additional requirements, including:

  • Very easy to install and configure
  • Highly customisable
  • Backend management and reporting is very easy and simple to operate, without the knowledge of any coding
  • Products and categories are easy to add and manage
  • It’s one of the most secured eCommerce solutions (and has been approved by Sucuri Security)
  • Search engine friendly
Some of the disadvantages and considerations include:
  • Frequently large updates may cause a significantly lower version to break your site
  • Some extensions come from third parties, and don’t have great support
  • Some extensions are also little pricey

WooCommerce is a perfect system for small to medium-sized online retailers, and of course for any developer or business that is already familiar with the WordPress interface.

If you’re starting out, then WooCommerce is definitely the place to start, as it’s very simple to use, however it does lack functionalities that may be beneficial for an enterprise eCommerce solution.

MAGENTO

Magento is the most popular eCommerce solution for most online shopping stores – mainly because the platform offers a lot of flexibility and customisation.  Like WordPress, Magento is open source, which means it allows developers to easily customise the look and functionality as required.

Magento development requires a higher level of coding skills, which means you need some experience with programming in order to setup your website. As a result, development costs can get expensive because of the complexities involved with customisation.

There are many themes available to purchase for Magento, but like all websites, we always encourage clients to build a customised design from scratch – to create the ultimate experience for users.

Here are some of the main features and benefits of the Magento platform:

  • Open Source Solution – you can host Magento on your own server, however it’s recommended you try and find a Magento hosting specialist
  • Develop highly-creative and responsive web designs – Magento has great flexibility with all templates and themes
  • A large number of payment gateways and shipping options can be included – including integration with major Australian banks and Australia Post
  • It has a really good product and order management system – there are good bulk uploading features available to help manage catalogues
  • Good marketing and promotional tools – includes related products, coupons, multi-tier pricing and product bundles
  • Search engine friendly – ‘out of the box’ Magento needs a little configuration, however it’s very search engine friendly
  • Manage multiple stores from the same account – this makes multiple websites easier to manage centrally

Larger retailers and international brands choose Magento because it offers a stack of ‘out of the box’ features that can be enhanced with plenty of third-party apps and modules.  It also provides endless possibilities for future growth.

For a full list of Magento Features visit:  Click Here

PRICE COMPARISON

The WooCommerce solution is a much more affordable solution for those that are price conscious.  WooCommerce is also very easy to manage and quite often will not require a developer other than any future template changes.  Compared with Magento which will be far more to develop and maintain.

It’s best to make sure with both WooCommerce and Magento that your developer is custom building the website from scratch and not using templates.  Although the template can be a quick solution, they are often jam packed with extra features that will slow down your site and make updating the platform a nightmare at a later date.

WHAT NEXT?

If you are planning on building a new website or just want to improve the look and functionality of your existing website, then it’s important you choose the eCommerce solution that is right for you.

If after reading this you’re still not sure about what solution is right for you, feel free to contact the friendly team at DigitalThing. We’re always excited about taking on new projects and we’ll take to assess your needs and create a tailored solution.

Source


  • -

Magento comparison with wordpress

Category : magento , wordpress

Magento comparison with wordpress

Magento comparison with wordpress
 
 
 
 
 
 
 
 
 
 
 
 
 
 

With so many eCommerce platforms available, it is hard to figure out which one is right for you. Many platforms offer different functionality which is necessary for some eCommerce stores, while simple functionality may be your piece of pie. Our experience has been stores that have invested in a simple functioning eCommerce platform but as time goes on, their business grows and they want to offer more customization, they eventually migrate their eCommerce site to Magento.

From our experience, choosing an eCommerce platform that your business is able to grow into is the best route (unless you don’t want business to grow). This route is better than investing in one eCommerce method may do the trick for your business at its infancy stage, and then needing to migrate your whole site to a new platform that can handle all your desired functionality and customization.

At Customer Paradigm our general rule of thumb for deciding if your site should be run on Magento or a WordPress Plugin is the question of what is the goal of your site?

If your goal is to sell products we highly recommend Magento. If your goal is to post content and blog then WordPress CMS is recommended. Generally, when the amount of products you have to sell are more than 25 it is a smart move to switch to Magento.

First we will go through the Magento and WordPress similarities, then we will look at the functionality that Magento has that WordPress does not, then the functionality that WordPress has that Magento does not.

 

Magento and WordPress Similarities

 

  • They are both Open Source platforms – they are both free (Magento Community version)
  • Ability to integrate blogging into their functionality
  • Ability to easily add products
  • Ability to use themes to design and personalize the look of your website
 

Magento vs. WordPress eCommerce Plugins

 

One advantage of Magento vs. WordPress eCommerce plugins is the fact that Magento was developed specifically for eCommerce. The Magento Logooverall functionality is going to be more tailored towards a business structure for sales.

  • Customization of shipping options
  • Various payment integration
  • Custom Shipping methods
  • Dynamic pricing functionality
  • Order fulfillment
  • Gift Cards
  • A more secure eCommerce platform than WordPress third party plugins
  • Ability to add more functionality than a WordPress Plugin
  • Great forums available on the web if you run into problems because Magento is the most widely used eCommerce platform
 
WordPress eCommerce Plugins vs. Magento

 

WordPress is ideal for your eCommerce needs if you are only selling a few products. If you mainly have a site that is driven by content and news updates and you sell a few t-shirts or tickets to an event then the WordPress eCommerce Plugin will work for you. Unfortunately I can not cover WordPress eCommerce plugins in one bullet point list, because the functionality is dependent on the 3rd party plugin you choose. Below is a list of the general well known facts about WordPress eCommerce. Wordpress Logo

  • Tons of eCommerce 3rd party plugins to choose from to fit your needs
  • Easily integrate your eCommerce into your existing WordPress theme
  • Not as secure as Magento, WordPress has been frequently hacked.
  • Unfortunately, 3rd party plug-ins are less reliable which isn’t good when it comes to selling products or tickets.

Source


  • -

WordPress vs magento: which is better for my website

Category : magento , wordpress

WordPress vs magento: which is better for my website

 

Wordpress vs magento: which is better for my website
 
 
 
 
 
 
 
 
 
 
 
 
 
 

If you are thinking about opening up a new e-commerce site – or if you are advising someone who is thinking about it – you are going to be faced with a key decision from the very first moments: Will you use WordPress or Magento?

There’s no one set answer, of course, but there are a few basic things to keep in mind.

Underpinnings of WordPress and Magento

While both platforms have similar functionality now, it’s important to keep in mind the background. WordPress, created by Matt Mullenweg, is a blogging platform. It’s a hugely popular platform, and by some estimates is now the single largest platform for content creation. That is to say that more blog posts are written on WordPress sites than any other platform, especially when you combine the similar – but distinct – WordPress.org and WordPress.com platforms.

With a huge base, WordPress has created a marketplace for creating plug-ins. Many of those plug-ins enable people to turn a blog into an e-commerce site.

Magento, on the other hand, was an e-commerce site first. It started as open source software that was relatively easy to launch and quickly grew to a point that there’s actually more money spent on Magento-run sites around the world than is spent on Amazon. That’s certainly part of why eBay bought Magento.

Analogous to WordPress being a blogging platform that moved into e-commerce, Magento is an e-commerce platform that added blogging as a plug-in.

Which platform is best?

Of course, there’s never a perfect solution for any problem, but understanding the background of the two platforms may help make the decision.

Is this site that you (or your client) wants to set up going to be strictly an e-commerce play, perhaps with a blog attached just to help with visibility, SEO and customer engagement?

Or is it more of a content play? Is it going to be a collection of writers, posts and customer interactions with an element related to that hoping to sell goods that are directly tied to the content that’s created?

With a pure e-commerce site, Magento (with the backing of eBay and PayPal) may be the best answer. If it’s more of a content play then WordPress may be the way to go.

Not matter what decision you make, deploying a self-hosted WordPress or Magento site on AN Hosting unlimited web hosting plans literally takes less than a few clicks to launch the platforms using the Softaculous auto-installer found in inside your cPanel dashboard.

Source


  • -

WordPress vs magento for ecommerce

Category : magento , wordpress

WordPress vs magento for ecommerce

 

Wordpress vs magento for ecommerce
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Working with Magento vs WordPress for eCommerce

If you use WordPress as a publishing platform with which to operate your website and find yourself with the need to incorporate some eCommerce functionality in order to support or enable your business’ growth, you may be asking yourself which solution is better for you and your business? Will you use WordPress or Magento?

Furthermore, if you have some experience with developing for WordPress, Magento’s complexity in comparison may be somewhat intimidating. In this entry to our eCommerce blog, we highlight why Magento is the preferred eCommerce solution for your business and provide some tips on how to use Magento, while thinking like WordPress.

On the surface, the two platforms may seem similar. They both are highlycustomizable, are very SEO friendly, can be extensively themed, and feature a strong online support community. In addition, of course, they are both essentially content management systems, enabling you to add, modify, and manage your content in a simple yet effective manner. However, the differences become apparent when you examine their core purpose.

WordPress

WordPress is a popular open source publishing tool and content management system. Upwards of 17% of the Web, or over 60 million websites, is powered by WordPress. Even eBay Inc., which owns Magento, uses it to publish their blog. It is notable for featuring a plug-in architecture and template system in addition to being very user friendly. WordPress can be extended to support some basic eCommerce functionality through a number of third party plugins.

Magento

Like WordPress, Magento is built on open source technology. It is a feature-rich eCommerce platform trusted by more than 150,000 online retailers, including some of the world’s leading brands, ranging from small websites to large multinational businesses. Magento offers a level of functionality and customizability that provides merchants with the flexibility and control to create online stores that fit their business needs while also supplying powerful features like marketing, multi-store management, mobile commerce, business reports, search engine optimization, and catalogue-management tools. Magento’s CMS facilities also support the creation of complex content pages, version control, and menus – much like WordPress.

What is your site’s purpose?

 

While both platforms are content management systems, it is clear that Magento was developed specifically for eCommerce. Its functionality overall is tailored towards a business structure and selling online. If your goal is to sell products, then using Magento is highly recommended. If the purpose of your website is primarily to post content or blog, and you don’t expect to offer for sale more than twenty different products, then WordPress may be an acceptable choice. However, the functionality that is provided by WordPress’ eCommerce plugins is limited. Maybe you want to support different shipping options or multiple payment methods; WordPress would not be tailored for this purpose. Just by navigating through the Magento Admin Panel, you’ll notice that an overwhelming majority of it is devoted to eCommerce capabilities like shipping options, payment integration, inventory, price management, gift cards, or order fulfilment. Magento is also more secure than using WordPress third party plugins.

If your business is growing, or if you want to support its growth, then Magento should be your platform of choice. Magento is the WordPress of eCommerce.

Development Differences

The differences also become clear, between WordPress and Magento, as you begin development. Magento is a complicated platform to learn, especially if you are previously familiar with WordPress due to differences in terminology and thinking. However, as both platforms are content management systems, learning Magento may be easier if you try to recognize where the platforms are similar.

WordPress is made up of a series of editable Posts and Pages. When developing template files, Loops and function tags are used to call the Page or Post content. Custom template files can also be added and applied on a per-page basis. Magento features CMS Pages and they largely function the same way as a WordPress Page. However, as is often the case in Magento, something that can be accomplished through WordPress in a few quick clicks is done in a more programmatic fashion by following Magento best practices. For instance, to set up additional CMS Page templates you do not simply create a new template file; in Magento you must also create a new module that updates the list of templates available to it. The equivalent content call within these templates is performed through a PHP method as follows:

WordPress Magento
<?php the_content(); ?> <?php echo $this->getChildHtml('content') ?>

CMS Static Blocks in Magento act somewhat like a combination of Posts and Widgets in WordPress. CMS Static Blocks are good for placing images and/or text on a CMS Page or in a template file. They can be a useful way to separate content from markup or feature a list of editable links. They act similarly to Widgets in WordPress, which control design, and structural elements in a theme. It should be noted that Magento does offer true Widget functionality as well, which provides a greater level of functionality than using Static Blocks. In WordPress, you must first register a “widgetized” sidebar as well as the widget itself in the functions.php file in order to be editable through the CMS front end. In Magento, a CMS Static Block can be created in the front end, but before it can be used in a template file it must be registered as a block in the theme’s local.xml file. For a Widget to be used within a Page’s content in WordPress, some code must first be added to the functions.php file to enable the use of a shortcode in the front end. With Magento, such shortcodes are active by default:{{block type="cms/block" block_id="your_block_id"}}

The greatest difference between the two is that WordPress has its programming contained within a set of sequenced PHP scripts while Magento is object-oriented and spread across a great number of files and folders. Further, whereas WordPress has relatively unique naming conventions for template files, and those files are largely contained within a single theme directory, Magento has several folders and files that share the same name. In WordPress, a theme is contained to one folder. With Magento, there are a series of nested folders. Template files and skin files are also located in separate directories. Lastly, unlike WordPress where themes are independent of one another, Magento features fall-back logic and relies upon its default theme.

Magento > WordPress for eCommerce

Presented here were just a few tips and techniques for WordPress developers who are struggling to familiarize themselves with Magento. Being able to develop for Magento, or ultimately use Magento for your business, is beneficial due to the functionality offered from using such a robust eCommerce solution with the focus of selling products. I hope we have demonstrated how Magento is a more fully featured and recommended alternative to using WordPress eCommerce plugins when you want to enable and support the growth of your business online.

Source


  • 0

Steps for showing magento products images

Category : magento

Steps for showing magento products images

 

 

 

 

 

 

 

 

 

 

Steps for showing magento products images

My magento product images are not showing

what should i do now if magento website does not show product images

How to show magento website product images

Follow these easy steps, they might work for you.
1-Make sure my memory in PHP was set to 128MB
2-Make sure my “Media” folder was writeable
3-Delete and clear the cache
4-Rebuild the indexes
5-Erase the htaccess file from the “Media” folder
6-Shrink the image to make sure it was below the correct file size limit

Magento tutorials

  • 0

magento theme development basics

Category : magento

magento theme development basics

magento theme development basics

Read all notes about magento theme development and go through all procedures ; you would get familiar soon with how to develop magento theme .
How to setup a new theme in administration area
After creating the folders we need to switch the theme from the administration area.
Step 1. Go to System > Configuration > Design via the top navigation bar
Step 2. Under “Themes” and in the “Default” text field, type: new_theme
Step 3. Press the “Save config” button in the upper right corner

magento design theme characteristics:
a single layout file, named local.xml, where all layout updates are placed.
no layout files with the same name as any layout file in the base theme
 no css files with the same name as any css file in the default skin
 no .phtml template files, except for those that were modified to support the new theme.

create new folders as follows there:
/app/design/frontend/default/new_theme/ – our new theme
/app/design/frontend/default/new_theme/layout
/app/design/frontend/default/new_theme/templates
/skin/frontend/default/new_theme/ – our new skins folder
/skin/frontend/default/new_theme/css/
/skin/frontend/default/new_theme/images/

create new files :
/app/design/frontend/default/new_theme/layout/local.xml
/skin/frontend/default/new_theme/css/local.css

add following code in your local.xml

<?xml version=”1.0″ encoding=”UTF-8″?>
<layout>
<default>
<!– Remove callouts and rarely used stuff –>
<remove name=”right.poll”/>
<remove name=”right.permanent.callout”/>
<remove name=”left.permanent.callout”/>
<!– add the local stylesheet –>
<reference name=”head”>
<action method=”addCss”>
<stylesheet>css/local.css</stylesheet>
</action>
</reference>
</default>
</layout>

Adding custom stylesheets and js libraries (part I)
Any additional external stylesheet files (css) or javascript/ajax libraries (js) that we want to include in our new project must be also
copied to the proper folders.
Stylesheets Copy the files to /skin/frontend/default/new_theme/css/ folder. To link these files in, you can either modify local.xml to
add the new file, or add an import in local.css, like this:
@import url(‘my_new.css’);
Javascript / AJAX libraries Create a new folder under /js/ named new_theme and copy your files to it. If you are using javascript libraries
then this is also a good place to put the library files.
The Javascript files can be added to your theme by adding the following to local.xml:
<?xml version=”1.0″ encoding=”UTF-8″?>
<layout>
<default>
<reference name=”head”>
<action method=”addJs”>
<script>varien/js.js</script>
</action>
</reference>
</default>
</layout>

Using XML to change layout
With the use of XML we can change almost every aspect of our new_template. For example we can set an alternate column layout for
particular pages, change META information, page encoding, block types used on each page etc. To accomplish this, you will simply add
various sections to your local.xml file. A good place to look at to understand this is:
app/design/frontend/base/default/layout/page.xml
In 1.3.x and earlier, this is located at::
app/design/frontend/default/default/layout/page.xml
Changing META section
(Isn’t this section horribly obsolete?) The main file used to control values for META tags and other miscelaneous details is config.xml
which is located in the /app/design/frontend/new_template/default/etc/ folder.
Below is a short description of every META tag and possible values:
<title>Magento Commerce</title>
This is the name of our ecommerce site. This text will appear in the browser’s title bar or the browser tab for the site. This text is also
highly important for search engine keyword optimization.
<media_type>text/html</media_type>
This is default page header encoding so we should leave this as is.
<charset>utf8</charset>
UTF8 is a variable-length character encoding for Unicode. It is able to represent any character in the Unicode standard, yet the initial
encoding of byte codes and character assignments for UTF-8 is backwards compatible with the ASCII table. For these reasons, it is
steadily becoming the preferred encoding for e-mail, web pages, and other places where characters are stored or streamed.
Of course we can change it to any other encoding (ex. ISO-8859-1 or ISO-8859-2) but there is no need as long as we’re saving our
files with proper UTF8 encoding.
More information about UTF8 is in the Wiki: http://en.wikipedia.org/wiki/UTF-8
<description>Default Description</description>
The description tag controls the description meta tag and allows us to enter a short description about our site. It’s often a way to get a
nice description of your page to show up in the search results if your page does rank highly in a search engine. Your best bet is to write
a succinct sentence or two that uses the keyword phrases that sum up the page content.
<keywords>Magento, Varien, E-commerce</keywords>
The keywords tag controls the keyword meta tag and is the place to put the most important words that refer to the site content. Best
practices suggest to enter no more than 500 characters in no more than 20 words for best results.
<robots>*</robots>
The robots tag controls the robots meta directive and is a simple mechanism to indicate to visiting web bots and search engine spiders
if a page should be indexed, or links on the page should be followed. The content of the Robots meta tag contains directives separated
by commas. The currently defined directives are index, noindex, follow and nofollow. The two index directives specify if an indexing
robot should index the page or not. The two follow directives specify if a robot is to follow links on the page or not. The defaults are
index and follow. The values all and none set all directives on or off: all=index,follow and none=noindex,nofollow We can simply
override Magento’s default directive by placing one of the four following lines here, however it’s not recommended. The options are:
• index,follow
• noindex,follow
• index,nofollow
• noindex,nofollow
The file config.xml also contains two additional tags, not connected with any meta tags but used as a default settings for every page in
our shop.
<logo_src>images/logo.gif</logo_src>
The logo_src tag sets up a reference to the logo file we wish to use on our site. The image logo.gif is located in the folder
/skin/frontend/new_template/default/images/ so if we want to change it we must copy a new logo file to that folder. We can also
create a new folder inside the images folder (ex. new_images) and put all our new files used by new template into it and change this tag
appropriately. The easiest way to customize the logo it to simply overwrite the default logo.gif file with a new logo.gif file.
<logo_alt>Magento Commerce</logo_alt>
The logo_alt tag defines the alt attribute for our logo image and is mostly used by screen readers or browsers with images disabled. If
one of our customers uses a screen reader or has images disabled he will see the alt text instead of image.
Understanding layout XML files
Introduction
Using xml instead of other methods (JSON, .ini files, include / require functions) allows us to change many aspects on our page without
manually changing the .phtml files. This chapter refers to our default theme so after changing the theme (as we have done above) the
paths will also change.
Layout / page structure
The core Layout is defined by page.xml which is located in
/app/design/frontend/base/default/layout/page.xml
There are two large tasks layout carries out.
First it defines the visual layout for your store. By default Magento uses a 3-column layout, so it defines use of 3columns.phtml
(Located in your template/page/ folder):
<block type=”page/html” name=”root” output=”toHtml” template=”page/3columns.phtml”>
If you wanted to change your store a 2-column layout, for instance, you would reference this section in local.xml, and use an action to
change to the .phtml you’d like to use (in this case, 2columns-left.phtml or 2columns-right.phtml).
1. <reference name=”root”>
2. <action method=”setTemplate”>
3. <template>page/2columns-right.phtml</template>
4. <!– Mark root page block that template is applied –>
5. <action method=”setIsHandle”>
6. <applied>1</applied>
7. </action>
8. </action>
You could also add a new custom layout:
1. <new_layout translate=”label”>
2. <label>New Layout</label>
3. <reference name=”root”>
4. <action method=”setTemplate”>
5. <template>page/new-layout.phtml</template>
6. </action>
7. <!– Mark root page block that template is applied –>
8. <action method=”setIsHandle”>
9. <applied>1</applied>
10. </action>
11. </reference>
12. </new_layout>
More information about the action tag and associated methods is located in section d of this chapter.
Secondly it creates “block containers” filled with application data for output to your .phtml template files. First, if take a look at your
standard 3column.phtml file you’ll see it calls the method (function) getChildHtml() a number of times:
(excerpt from 3columns.phtml – Starting at line 56):
1. <?=$this->getChildHtml(‘header’)?>
2. </div><!– [end] header –><!– [start] middle →
3. <div class=”main-container”>
4. <div id=”main” class=”col-3-layout”>
5. <?=$this->getChildHtml(‘breadcrumbs’)?>
6. <!– [start] left –>
7. <div class=”col-left side-col”>
8. <?=$this->getChildHtml(‘store’)?>
9. <?=$this->getChildHtml(‘left’)?>
10. </div>
11. <!– [end] left –>
Each of these references point towards the “block containers” defined in your page.xml and subsequent Module .xml files. You’ll notice
a container for the “left” column, for the “right”, for “content”, and other standard areas. It serves up output for your .phtml template
files to use. Take a look at it:
/app/design/frontend/default/default/layout/page.xml
1. <block type=”page/html_breadcrumbs” name=”breadcrumbs” as=”breadcrumbs”/>
2. <block type=”core/text_list” name=”left” as=”left”/>
3. <block type=”core/messages” name=”global_messages” as=”global_messages”/>
4. <block type=”core/messages” name=”messages” as=”messages”/>
5. <block type=”core/text_list” name=”content” as=”content”/>
6. <block type=”core/text_list” name=”right” as=”right”>
So basically page.xml creates Data Blocks, your .phtml Outputs that data where you want it. Hence, the names for left, right and so
forth in your .phtml.
To add, remove, or modify blocks in your theme, use your local.xml file, not a copy of page.xml. The reference tag allows you to define
what part of the theme you are working with, then you can declare additional blocks, or use actions to modify or remove blocks.
You’re aware now that page.xml contains a handle called “<default>”. The XML commands nested within the <default> layout sets up
the default layout for the whole site. The subsequent handles(as listed in the top of page.xml), simply updates the default layout with
the according layout for the page.
1. <layoutUpdate>
2. <reference name=”top.menu”>
3. <block type=”catalog/navigation” name=”catalog.topnav”>
4. <action method=”setTemplate”>
5. <template>catalog/navigation/top.phtml</template>
6. </action>
7. </block>
8. </reference>
9.
10. <reference name=”right”>
11. <block type=”catalog/product_compare_sidebar” name=”catalog.compare.sidebar”>
12. <action method=”setTemplate”>
13. <template>catalog/product/compare/sidebar.phtml</template>
14. </action>
15. </block>
16. </reference>
If you read the code and think about whats going on it makes sense. <layoutUpdate> is UPDATING your code with new blocks. How
does it know where to put the new blocks? Well remember in your default you defined “block containers” for left, right, etc. So when it
says
<reference name = “right”>
it’s telling Magento to insert the following block into the RIGHT column when you get into “Catalog” view. (Remember, its located at
layout/catalog/) so it appears once you’ve entered the catalog section of the shop. It also defines a TEMPLATE for the new block to use,
so for the example above the compare box has its own template located at catalog/product/compare/sidebar.phtml (in your template
folder).
These same handles can be used in local.xml to restrict the scope of a particular update.
For instance, let’s say you want a wishlist everywhere in your store, but you don’t want it in the customer account pages. You would
look for the handle used on account pages (it is in customer.xml) and add that handle to local.xml. Then remove the wishlist so it does
not load in the account pages.
The example below removes “Login” and adds “Register” instead, but only if the customer is not already logged in:
1. <customer_logged_out>
2. <reference name=”top.links”>
3. <action method=”removeLinkByUrl” module=”catalog”>
4. <url helper=”customer/getLoginUrl” />
5. </action>
6. <action method=”addLink” translate=”label title” module=”customer”>
7. <label>Register</label>
8. <url helper=”customer/getRegisterUrl”/>
9. <title>Register</title>
10. <prepare/>
11. <urlParams/>
12. <position>100</position>
13. </action>
14. </reference>
15. </customer_logged_out>
Reference name values/attributes:
As we’ve seen, the references can use different attributes for displaying blocks on our page. Possible values are:
• root – we will change it mostly to set up another .phtml file as a root template ex. (1column.phtml , 2columns-left.phtml ,
2columns-right.phtml etc.)
• head – as this reffers to our <HEAD> section on page, we will use this reference name to reflect our changes in this section
• top.menu – defines our content for top menu section
• left – defines our content for left column
• right – as above but for right column
• content – defines blocks placed in main content of our page
• before_body_end – is used to add a block before end of our page so before </BODY>
There are more reference names that we could use but they are more page-specific than for global use for example:
customer_account_navigation
customer_account_dashboard
are used on our clients account page
product.info.additional – sets up additional block for placing related items, shipping estimator etc.
Action methods:
Action methods allow us to change many theme settings without appending manual changes to our .phtml files. The method listed in
the method attribute refers to a method in the Model that is associated with the particular block in question. The most important
methods are described below.
setTemplate
Action method setTemplate allows us to change the default .phtml file used in particular block. For example by navigating to
app/design/frontend/default/default/layout/catalog/product/view.xml we can see the reference:
1. <reference name=”root”>
2. <action method=”setTemplate”>
3. <template>page/2columns-right.phtml</template>
4. </action>
5. </reference>
and by using another <template> value we are allowed to change default .phtml file used on our products page. Possible values are:
• 1column.phtml
• 2columns-left.phtml
• 2columns-right.phtml
• 3columns.phtml
• one-column.phtml
• dashboard.phtml
As we see in app/design/frontend/default/default/layout/checkout/cart.xml , there also additional 2 values for empty and non-empty
cart
1. <action method=”setCartTemplate”>
2. <value>checkout/cart.phtml</value>
3. </action>
4.
5. <action method=”setEmptyTemplate”>
6. <value>checkout/cart/noItems.phtml</value>
7. </action>
8.
9. <action method=”chooseTemplate”/>
The method chooseTemplate is used to set a template (setCartTemplate / setEmptyTemplate) depending on quantity of items in our
cart. If we have more than 0 than the
1. <action method=”setCartTemplate”>
2. <value>checkout/cart.phtml</value>
3. </action>
is used. If we have no items in cart then the following will be used.
1. <action method=”setEmptyTemplate”>
2. <value>checkout/cart/noItems.phtml</value>
3. </action>
The function provided by the Model is shown below:
1. public function chooseTemplate()
2.
3. {
4. if ($this->getQuote()->hasItems()) {
5.
6. $this->setTemplate($this->getCartTemplate());
7.
8. } else {
9.
10. $this->setTemplate($this->getEmptyTemplate());
11. }
12. }
That should clarify how we can use this particular switch. Depending on our needs we can write custom functions in our blocks and
than assign a template depending on parameters returned by a function.
addCss
This method allows us to add an additional CSS file to our page on per-page basis or globally for our template. If we use a reference
name “head” and action method addCss by using
1. <reference name=”head”>
2. <action method=”addCss”><link>style.css</link></action>
3. </reference>
then our page will have an additional line of code to attach the CSS file, for example:
1. <link rel=”stylesheet” type=”text/css” media=”all”
href=”http://www.ourstore.com/skin/frontend/default/default/css/style.css” ></link>
As we can see, the <link> path refers to the /skin/frontend/default/default/css/ folder.
addCssIe
This method is very similar to the above but it will output a css file when a User-Agent (browser) is Internet Explorer or Maxthon. So
using this method we can attach a specific css file for those browsers. This is very helpful if our page will requires changes in css
dependant on a specific browser.
Usage:
1. <reference name=”head”>
2. <action method=”addCssIe”><link>style.css</link></action>
3. </reference>
Output in page source:
1. <!–[if IE]>
2. <link rel=”stylesheet” type=”text/css” media=”all”
href=”http://www.ourstore.com/skin/frontend/default/default/css/style.css” ></link>
3. <![endif]–>
addJs
The below method allows us to attach a .js script in the same way as we attached a CSS file. The script path refers to the /js/test/ folder
but you can specify any subdirectory of /js/
Usage:
1. <reference name=”head”>
2. <action method=”addJs”>test/script.js</action>
3. </reference>
It will add a script to our page with src attribute of
1. <script src=”http://www.ourstore.com/js/test/script.js” />
addJsIe – adding a .js file to head section of page and using it if User Agent (browser) is Internet Explorer.
If we can add different css files depending on User-Agent we can do the same with our .js files. Than we can use different scripts for
our IE/Maxthone users and another for other browsers.
Usage:
1. <reference name=”head”>
2. <action method=”addJsIe”>our/script.js</action>
3. </reference>
It will add a script to our page with src attribute of
1. <script src=”http://www.ourstore.com/js/our/script.js” />
but also inside IE comments
1. <!–[if IE]><![endif]–>
setContentType
This method can override default headers sent by our page to the browser. So we can set a text/xml instead of text/html (or another as
we wish).
Usage:
1. <reference name=”head”>
2. <action method=”setContentType”><content>text/xml</content></action>
3. </reference>
setCharset
allows us to override default page encoding on per-page basis or globally. As long as we are saving our files with proper encoding this
will not be necessary.
Usage:
1. <reference name=”head”>
2. <action method=”setCharset”><charset>ISO-8859-2</charset></action>
3. </reference>
So in this case our page will have Central European encoding instead of default UTF-8
addLink
addLink methods can be used to set a setting to which we can refer in our .phtml template files also without manually changing the
.phtml files.
Example usage :
Warning, this example requires account.xml to be duplicated, which can break things after updates. Someone should rewrite this to use
local.xml instead. By adding a block which was found in app/design/frontend/default/default/layout/customer/account.xml into our
<reference name=”content”> in app/design/frontend/default/default/layout/checkout/cart.xml we can allow the customer to skip to
the account information directly from the cart.
<block type=”customer/account_navigation” name=”customer_account_navigation” before=”-“>
<action method=”setTemplate”>
<template>customer/account/navigation.phtml</template>
</action>
<action method=”addLink” translate=”label”>
<name>account</name>
<path>customer/account/</path>
<label>Account Dashboard</label>
</action>
<action method=”addLink” translate=”label”>
<name>address_book</name>
<path>customer/address/</path>
<label>Address Book</label>
</action>
<action method=”addLink” translate=”label”>
<name>account_edit</name>
<path>customer/account/edit/</path>
<label>Account Information</label>
</block>
The cart.xml file should look like below
1. <layoutUpdate>
2. <reference name=”root”>
3. <action method=”setTemplate”>
4. <template>page/1column.phtml</template>
5. </action>
6. </reference>
7.
8. <reference name=”content”>
9. <block type=”customer/account_navigation” name=”customer_account_navigation” before=”-“>
10. <action method=”setTemplate”>
11. <template>customer/account/navigation.phtml</template>
12. </action>
13.
14. <action method=”addLink” translate=”label”>
15. <name>account</name>
16. <path>customer/account/</path>
17. <label>Account Dashboard</label>
18. </action>
19.
20. <action method=”addLink” translate=”label”>
21. <name>address_book</name>
22. <path>customer/address/</path>
23. <label>Address Book</label>
24. </action>
25.
26. <action method=”addLink” translate=”label”>
27. <name>account_edit</name>
28. <path>customer/account/edit/</path>
29. <label>Account Information</label>
30. <base>{{baseSecureUrl}}</base>
31. </action>
32. </block>
33.
34. <block type=”checkout/cart” name=”checkout.cart”>
35. <action method=”setCartTemplate”>
36. <value>checkout/cart.phtml</value>
37. </action>
38.
39. <action method=”setEmptyTemplate”>
40. <value>checkout/cart/noItems.phtml</value>
41. </action>
42.
43. <action method=”chooseTemplate”/>
44.
45. <block type=”checkout/cart_coupon” name=”checkout.cart.coupon” as=”coupon”>
46. <action method=”setTemplate”>
47. <template>checkout/cart/coupon.phtml</template>
48. </action>
49. </block>
50.
51. <block type=”checkout/cart_shipping” name=”checkout.cart.shipping” as=”shipping”>
52. <action method=”setTemplate”>
53. <template>checkout/cart/shipping.phtml</template>
54. </action>
55. </block>
56.
57. <block type=”checkout/cart_crosssell” name=”checkout.cart.crosssell” as=”crosssell”>
58. <action method=”setTemplate”>
59. <template>checkout/cart/crosssell.phtml</template>
60. </action>
61. </block>
62. </block>
63. </reference>
64. </layoutUpdate>
Of course according to the previous references we can also change
1. <action method=”setTemplate”>
2. <template>page/1column.phtml</template>
3. </action>
in the above code to suit our needs. I’ve used for example
1. <action method=”setTemplate”>
2. <template>page/one-column.phtml</template>
3. </action>
to show only our cart without other blocks.
Layout blocks
As we’ve seen before, most of our xml files have a <block> tag. It defines a type of block, its name and alias “as” so we can refer to it
on our page. Basic block structure looks like this:
1. <block type=”catalog/product_view_super_config” name=”product.info.config” as=”super_config”>
2. <action method=”setTemplate”>
3. <template>catalog/product/view/super/config.phtml</template>
4. </action>
5. </block>
type=”catalog/product_view_super_config” – defines the type of our block on page. This example would refer to the file
/app/code/core/Mage/Catalog/Block/Product/View/Super/Config.php which defines the class
Mage_Catalog_Block_Product_View_Super_Config name=”product.info.config” – defines a name for our block and should be unique
as=”super_config” – defines a shortname for our block which can we use with getChild function on particular page
Blocks used in our XML files can change or override most every aspect of our design. We can use them to simply change used phtml
files on per-page basis, to add additional scripts, stylesheets to our page , to move particular sections of page without needing to
change phtml files.
Understanding .phtml files
Introduction
Phtml files are template files that handle the output to browser. They are nothing more than html files with nested php tags. We use
them to style our page and the look of our site.
Changing .phtml files requires basic knowledge about XHTML, CSS and understanding how to use PHP functions on a page.
IMPORTANT: Before changing a .phtml file, it has to be copied from the base (or default) theme, into the new theme. When Magento
finds one of these files in your new theme, it will ignore the .phtml file from the base theme, so it is important to ONLY copy over the
files that you absolutely need to modify. This will minimize errors when updating Magento. The additional effort required to individually
copy the 4-5 files you eventually modify will more than make up for itself the first time Magento needs to be updated.
Let’s have look at header.phtml placed in templates/page/html.
1. <div class=”header-top-container”>
2.
3. <div class=”header-top”>
4.
5. <h1 id=”logo”>
6. <a href=”<?=$this->getUrl(”)?>”>
7. <img src=”<?=$this->getLogoSrc()?>” alt=”<?=$this->getLogoAlt()?>”/>
8. </a>
9. </h1>
10. <p class=”no-show”><a href=”#main”><strong><?=__(‘Skip to main content’)?> &raquo;</strong></a></p>
11. <div class=”quick-access”>
12. <div class=”account-access”>
13. <strong><?=$this->getWelcome()?></strong> <?=$this->getChildHtml(‘topLeftLinks’)?>
14. </div>
15.
16. <div class=”shop-access”>
17. <?=$this->getChildHtml(‘topRightLinks’)?>
18. </div>
19.
20. </div>
21.
22. </div>
23.
24. </div>
25. <?=$this->getChildHtml(‘topMenu’)?>
In this file we see basic XHTML tags, usage of CSS classes but most important – Magento functions used to get layout XML blocks and
render it in our phtml file.
Mostly in our template we’ll see <? ?> tags used for functions calls. Basing on above example: <?=$this getUrl(’‘)?> – used withou→ t
parameters will return base path of our store <?=$this→getLogoSrc()?> – will render a logo image based on path used in
etc/config.xml <logo_src>images/logo.gif</logo_src>
If we’d like to change our logo we can do this in two ways. First possibility is to change <logo_src> path to anything else. Second
possibility is to hardcode the path directly in phtml file so
1. <img src=”<?=$this->getLogoSrc()?>” alt=”<?=$this->getLogoAlt()?>”/>
but this resolution isn’t recommended since we should use core functions and learn their usage.
<?=$this→getLogoAlt()?> – this function will allow us to change the alt tag for our logo so if it will be unavailable , the alt tag will
appear. Any changes we can also append by changing <logo_alt>Magentso Commerce</logo_alt> or setting it direclty in phtml file up.
<?=__(Skip to main content)?> – all tags that look like this will be used to dynamically translate page content to other languages. We
should understand it as <?=__(‘English text to translate’)?>
<?=$this→getChildHtml(’topLeftLinks’)?> – The getChildHtml() function is the most important function used in our template. It calls
particular block defined in XML file and renders it as HTML , then outputs it to the browser. We can call blocks from everywhere and
from corresponding XML files.
To use getChildHtml(’topLeftLinks’) we must have defined first the child “as” so take a closer look at page.xml (layout/ folder). Here’s
what you should see:
1. <block type=”page/html_toplinks” name=”top.left.links” as=”topLeftLinks”/>
As we see, getChildHtml(’topLeftLinks’) uses its alias “as” and calls it from the XML. The getChildHtml() function only allows Magento to
call a block if that block was defined in the corresponding XML file.
We can also override this mechanism by using another function call:
<?=$this→getLayout()→getBlock(’top.left.links’)→toHtml()?>
This structure will call the top.search block (based on its name, not its alias “as”) from anywhere in any of our templates so we do not
need to define it everywhere in our XML files. Remember to use the “name” attribute instead of the “as” attribute with this workaround.
We must be aware that every phtml file and every function will always refer to the corresponding XML file or files. We can identify used
phtml files simply by searching for the following:
1. <action method=”setTemplate”><template>wishlist/sidebar.phtml</template></action>
which tells us which phtml file will be used.
Folder structure
Every View used in our application has separate folders and subfolders to store template files. Let’s have a look at the folder structure:
• callouts – folder where are files for our callouts and ads are placed
• catalog – folder to store files used on our category, layered navigation, product, comparision pages
• catalogsearch – here we find files that are used to skin our search engine and result pages
• checkout – all the pages utilised during checkout and shopping in our shop. Here we’ll also find the shopping cart templates
and blocks for cross-selling and coupons.
• cms – folder for static pages templates.
• core – folder containing store-switching templates (not yet active)
• customer – all customer pages (ex. account dashboard, address forms, orders list and reviews)
• datafeed – folder to store our csv, txt, xml files, used for comparision engines and other external applications
• directory – here we find currency switcher for our shop
• email – here we’ll find all pages that require email transport so for example order, password recovery, newsletter signup
• install – template files for Magento’s installer
• newsletter – subscribe.phtml placed in this folder will allow us to change the look of newsletter signup box on our page
• page – the most important folder in which we’ll find all main files used to style our site. More about it will be described in
following subchapter.
• payment – templates used to style our payment forms (ex. CC payment.)
• poll – 2 files to change the look of our poll depending on state (didn’t vote yet / show result)
• rating – rating block used on our products pages
• review – all files used to render the blocks used by reviews
• sales – pages for order details, invoices, recent orders
• searchlucene – result output for Zend_Lucene controller used in Magento
• tag – product tags templates are stored here
• wishlist – template files to handle the output of our wishlist actions.
Appending basic changes to our templates
Every file used to skin the basic look of our template is placed in template/page folder. Here we’ll see
1column.phtml 2columns-left.phtml 2columns-right.phtml 3columns.phtml one-column.phtml dashboard.phtml
These are essentially the HTML skeleton files for our pages. By changing those files we can set up a new look of the page structure.
There is also an html subfolder placed under template/page in which we can change footer, header and links blocks of our template.
Every one of them uses simple function calls (ex. getChildHtml() ) so we can also identify the block by searching in layout XML files .
For example when we’ll see
1. <reference name=”root”>
2. <action method=”setTemplate”>
3. <template>page/2columns-right.phtml</template>
4. </action>
5. </reference>
this tells us that the page will use 2columns-right.phtml as a skeleton for our page.
Calling layout blocks using Magento functions
As it was described above, there are two ways of calling blocks .
<block type=”page/html_toplinks” name=”top.left.links” as=”topLeftLinks”/>
<?=$this getChildHtml(’as’)?> – by using the block alias “as” from the XML file we can display a block on our page providing that → it
was defined already in the corresponding XML file
<?=$this→getLayout()→getBlock(’name’)→toHtml()?> – by using the block name from the XML file, we can call any block whether or
not it was already defined in corresponding XML file
e. Adding custom CSS and JS files to a layout (part II)
There are 2 ways of adding custom js and css files to our template. The recommended way is by extending the head section in the
default XML file. But you also have the ability to add the files directly in the particular root template file.
1. <script type=”text/javascript” src=”<?=$this->getJsUrl()?>varien/js.js” ></script>
2. <script type=”text/javascript” src=”<?=$this->getJsUrl()?>varien/form.js” ></script>
3. <script type=”text/javascript” src=”<?=$this->getJsUrl()?>varien/menu.js” ></script>
As we see here , we can also use getJsUrl method which adds a scripts path to our src attribute. This should output
http://yoursite.com/js/ so the source will look like the following:
1. <script type=”text/javascript” src=”http://yoursite.com/js/varien/js.js” ></script>
2. <script type=”text/javascript” src=”http://yoursite.com/js/varien/form.js” ></script>
3. <script type=”text/javascript” src=”http://yoursite.com/js/varien/menu.js” ></script>
Adding a css file isn’t harder than adding a js file. We do this also by using a function that outputs a path to our skins folder.
1. <link rel=”stylesheet” href=”<?=$this->getSkinUrl(‘css/styles.css’)?>” type=”text/css” media=”all”/>
And the output will be
1. <link rel=”stylesheet” href=”http://yoursite.com/skin/frontend/default/default/css/styles.css” type=”text/css”
media=”all”/>
so getSkinUrl() sets actual path to our skins folder : http://yoursite.com/skin/frontend/default/default/
Opening .phtml files in Dreamweaver
By default, Dreamweaver cannot read PHTML files. You can add the file type to the “Open in Code View” section of the preferences if you
wish to have fast access, however you cannot view the file in design view if you do that. So if you use Dreamweaver (versions 4, MX,
MX2004, 8, or 9, aka CS3) to design your sites, and you wish to open Magento’s Template files (they have .phtml extensions) in
Dreamweaver, you can follow these steps to add support for .phtml and make Dreamweaver render PHP code (with coloring, hinting, et
al) as well as allow you to see the design in code view if desired. Below are three steps to follow.*
IMPORTANT NOTES: This guide is for Dreamweaver on Windows (XP or Vista) or Mac OS X. Note: I have excluded version numbers from
the file locations shown, and if you are using a version older than Dreamweaver 9 (CS3) replace “Adobe” with “Macromedia” in the file
locations shown. Some spaces have also been removed to keep the references on one line.
* Dreamweaver 4 users: if you are using the archaic Dreamweaver 4, you only need to follow step one. However, it’s highly
recommended that you just upgrade to version 8 or newer for superb CSS and Web Standards support.
Step One: Add .phtml to the extension.txt configuration file
Open the following extension configuration file in a notepad and change the lines as specified below:
XP, Vista: C:Program FilesAdobeDreamweaverConfigurationExtensions.txt
Mac OS X: Applications > Adobe Dreamweaver CS3 > configuration > Extensions.txt In the first line add PHTML like so:
HTM,HTML,SHTM,SHTML, … ,TXT,PHP,PHP3,PHP4,PHP5,PHTML,JSP,WML,TPL, … ,MASTER:All Documents
In the PHP Files line add PHTML like so:
PHP,PHP3,PHP4,PHP5,PHTML,TPL,PHTML:PHP Files
Step Two: Add .phtml to extension.txt in your Application Data
This file is pretty much exactly like the extensions.txt file located in Dreamweaver’s configuration folder, except it is in your users
Application Data folder (AppData folder for Vista users). Just as in Step One, find the file and change the lines as specified below.
XP: C:Documents and Settings[user]Application DataAdobeDreamweaverConfigurationextensions.txt
Vista: C:Users[user]AppDataRoamingAdobeDreamweaverConfigurationExtensions.txt
Mac OS X: Users > Library > Application Support > Adobe > Dreamweaver 9 > Configuration > Extensions.txt
In the first line add PHTML like so:
HTM,HTML,SHTM,SHTML, … ,TXT,PHP,PHP3,PHP4,PHP5,PHTML,JSP,WML,TPL, … ,MASTER:All Documents
In the PHP Files line add PHTML like so:
PHP,PHP3,PHP4,PHP5,PHTML,TPL,PHTML:PHP Files
Step Three: Add PHTML to MMDocumentTypes.xml
This file is an XML file which should be located in:
C:Program FilesAdobeDreamweaverConfigurationDocumentTypesMMDocumentTypes.XML
Mac OS X: Applications > Adobe Dreamweaver CS3 > configuration > DocumentTypes > MMDocumentTypes.XML
Add PHTML to this line (approx. line 75) twice, like so:
1. <documenttype id=”PHP_MySQL” servermodel=”PHP MySQL” internaltype=”Dynamic”
winfileextension=”php,php3,php4,php5,phtml” macfileextension=”php,php3,php4,php5,phtml” file=”Default.php”
writebyteordermark=”false” />
Restart or Open Dreamweaver and you shouldn’t have any problems with PHTML files any longer.


  • 0

magento basic interview questions

Category : magento

magento basic interview questions

 

 

 

 

 

 

 

 

 

magento basic interview questions

 

Magento uses various caching types. Why?
Caching uses less resources
The cache must be cleaned each time an order is placed
Magento uses a single cache type
Caching types allow magento to clear cache more efficiently
Select the correct handle for the Product View page.

<catalogs_product_view>
<catalog_product_view>
<catalog_products_view>
<view_catalog_product>

If you sell different products in a bundle, Where do you add a new options to a bundle product?
The Bundle Products section of the Product Edit Page
The Associated Products section of the Product Edit Page
From the products management grid
The Catalog section of the System Configuration

Magento allows you to use multiple themes within the same layout and template.
False
True

If you have a product that comes in different sizes, Where do you add a new size for the configurable product?

The CMS Page section of the System Configuration
The Catalog section of the System Configuration
The Associated Products section of the Product Edit Page
The Bundle Products section of the Product Edit Page

Inside a .phtml file, what does “$this” refer to?

A class inheriting from Mage_Core_Model_Abstract
A class inheriting from Mage_Core_Block_Abstract
A class inheriting from Mage_Core_Helper_Abstract
The absolute path of the .phtml file
$this is not defined in a .phtml file

A Magento theme is stored in which directory in the Magento file system?

Neither App/Design Directory or Skin Directory
Skin Directory
Both App/Design Directory and Skin Directory
App/Design Directory

In Magento a Coupon is also known as?

Shopping Cart Price Rule
Bundled Product
Physical Item
Promotional Chart

When is it acceptable to edit app/code/core/Mage files?

When there is a conflict with an off the shelf extension
When I find a bug in the code
When I would like to change Mage modules
Never

What is the setting that determines that product will show on the search page and not on the category listing?

Product Attribute Manager
Product Status
Product Inventory Status
Product Visibility

If cache needs to be cleared by other means to the admin back-office, which directories would you delete?

{ $site } var/cache
Both directories are correct
/tmp/magento/var/cache/

Which of the following is considered to be part of Magento’s backend?

General JS architecture
Shopping Cart
Wishlist
View Product

The __________ holds the whole product configuration and is used as a compact record to move a product from one
list to another.

buyRequest
stopRequest
holdRequest
sellRequest

unaswered basic magento interview questions-evaluate yourself at what level you are standing and find out these given magento questions- answers


  • 0

magento odesk test answers

Category : magento

magento odesk test answers

 

 

 

 

 

 

 

 

magento odesk test answers

The best place to edit the product configuration in Magento 1.4 is the
Checkout page
View Product page
Home Page
View Cart page
For items where inventory is not tracked, what is the setting to shut inventory management off?
Manage Stock, under Inventory section
Set the price to 0
Category Management, under the Catalog Menu
Set the order increment to 0

main reasons product won’t show on Category page?
Availability,Status,SKU
SKU, Price, Description
Availablity, Status, Visibility
Price,Status,Visibility

Which of the following are front end blocks with a predefined set of configuration options?
Apps
Tabs
Widgets
Cells

Where can I find system.log and exception.log debugging log files?
application/log
/var/log/
error/log/
log/error
var/log/

Where can I find system.log and exception.log debugging?
log/debug
log/error
application/log
error/log/
var/log/

Where can you find the design configuration tab?
System/Configuration/Category/Design tab

System/Configuration/Design tab
System/Category/Configuration/Design tab
System/Catalog/Category/Design tab

 

Magento has always used fallback logic in rendering themes.
True
False
When writing a Magento module which of these files are you likely to create first?
controllers/IndexController.php
Helper/Data.php
etc/config.xml
Model/Observer.php
Block/Template.php

A new product still shows out-of-stock, even though it shows that there are 20 available. Which index should we
rebuild?
Catalog Product Rewrites
Product Flat Data
Stock Status Index
Product Prices

 

magento configuration and store questions for evaluating yourself at what level you are experienced in magento.



Fatal error: Call to undefined function weblizar_navigation() in /home/websolutionsdone/public_html/wp-content/themes/ielts-career/category.php on line 23