Magento custom designed gallery plugin contains two modules.
You can guess, one is for displaying images on frontend and second one is for handling images and categories in backend.

I will not write too much about this modules because there are too much files and it will take too much time to describe.
Most of things used in this modules are already described by my working colleagues.

Backend module is based on interface for adding images of products in magento shop.
When you integrate it into your shop it will install two additional custom tables in database which will store data of your gallery (categories and images)

Here’s a quicky one How do you change page title of every Magento page if some titles are hardcoded into controller?

Since some controllers in Magento likes to force page titles like

we can’t go with setTitle through layout, since controller is setting title right before rendering.

There is a simple solution for this, use another variable for title display

In page/html/head.phtml template replace default

with

or if you don’t wish to use title prefix/sufix added from Magento admin, simply with

and now just set “forced” title for pages through layout files

lthough it is fairly simple to do, many Magento users offer encounter difficulties when attempting to use the import functionality built in to Magento. We see a fair number of inquiries about this here at the Magento Enterprise Support Desk, so we’ve decided to write a little tutorial to help you better understand and use Magento’s Import Profile.

First, let’s take a look at how to create an import file, which will include all the data we want to bring into Magento. To get the correct fields and values, we recommend exporting a product, i.e. a simple product or configurable product, through the Admin. This is done through ‘System -> Import/Export -> Profiles’.

In the out-of-the-box Magento configuration, there are a couple of default “Export profiles” that you may use depending on which data you would like to export.  This depends on the data which you wish to export, and there are options for customers, products, stock, etc.  Running the profile will open a new window or tab which will show the progress of the export profile, as you can see in the example below:

Introduction

The Magento Community Edition Version 1.4 facilitates the use of custom frontend extensions by introducing a new concept of customizable widgets, which can provide more control over the frontend behavior and visual block placement to store owners.

Developing a widget doesn’t differ much from developing a regular Magento extension which provides some frontend functionality. Each Magento extension can have any number of widgets. You can also develop extensions which add configuration options and placement control to the functionality which already exists in other extensions.

Widget Basics

We’ll start by creating a sample module which provides 3 simple widgets. Every widget outputs a link to a corresponding bookmarking service or a social network on the page.

Create an empty module

To start a new Magento module, you have to create a module code folder under an appropriate code pool (we’re going to use local code pool for our samples here). The folder should contain a module configuration file called config.xml and a default module helper. You should also add a small “enabler” file under the app/etc/modules folder, which lets Magento know that the new module is available and resides in the specific code pool.