#HOW TO USE THE MODEL RESOURCE HOW TO#
#HOW TO USE THE MODEL RESOURCE INSTALL#

$this->_setActiveMenu('photo/photograph') We create an empty helper class which inherits the core helper class allowing us to translate our text, if we decide to do so at a future date. We also need to make our module aware that weвЂ™ll be using helpers and blocks from this point onwards.ДЄs with a standard adminhtml.xml file weвЂ™re just adding our menu item and then specifying ACL permissions so that admin users can see it, and other users must be specified. We need to declare a path to our layout updates XML file for adminhtml (which we havenвЂ™t created yet). The first is to declare our controller path, which is using the adminhtml module and must be loaded before the adminhtml module. WeвЂ™re going to add a few lines to our config file within our config node.

Specifying layout XML updates to show the grid on your controller action.

Adding the controller path to your admin menu and setting ACL permissions.

Updating our config to declare our new blocks, helpers, controllers.

HereвЂ™s part 2 which goes through the basics of making your model editable in the Magento administration. Mage::getResourceModel('photo/photograph_collection') Mage::getResourceModel('photo/photograph') YouвЂ™ll then be able to actually get some data when you instantiate your model inГ‚В theГ‚В following ways:

#HOW TO USE THE MODEL RESOURCE HOW TO#

In part 2, IвЂ™ll be going through how to make this model editable in your Magento admin so that you can add new data to the collection. We now have a model, but no data to make instances of this model.

#HOW TO USE THE MODEL RESOURCE INSTALL#

Your install script needs to be equal or higher than your Magento module version to run. If itвЂ™s not there, check your versions match. If not check the вЂcore_resourceвЂ™ table for your вЂphoto_setupвЂ™ record. Check your database for the table to ensure that it has worked. Load a page in your admin or frontend to run the install script. $installer->getConnection()->createTable($table) >addColumn('timestamp', Varien_Db_Ddl_Table::TYPE_TIMESTAMP, null, array( >addColumn('img_path', Varien_Db_Ddl_Table::TYPE_TEXT, null, array( >addColumn('title', Varien_Db_Ddl_Table::TYPE_TEXT, null, array( >addColumn('entity_id', Varien_Db_Ddl_Table::TYPE_INTEGER, null, array( $table = $installer->getConnection()->newTable($installer->getTable('photo/photograph')) We donвЂ™t need to change anything in the original core setup class so you can leave it blank. We start by creating a setup class so we can create an instance of the install object. WhereвЂ™s the data? Well, remember the photo_setup config that we set earlier? WeвЂ™re going to give it what itвЂ™s asking for by creating our install file, which will create the database table вЂcreare_photoвЂ™. We can now use our resource model to create the ability to grab a collection of our models, which we can do by simplyГ‚В initialising our collection class.ДЄlmsot there! We now have our model setup and configuration pretty much done, but with one problem. We simply pass in the model name and the database table primary key (which we havenвЂ™t created yet). We have now initialised our resource model, allowing our model to interact with the database. Always extends the Mage_Core_Model_Abstract class. From this point onwards we have a model type called вЂphoto/photographвЂ™. This model initialisation class is as simple as it looks. Using the resources node, you can then call the inside node anything you like вЂ“ just remember that youвЂ™ll need to use this name in your setup path later on (inside the sql directory). We just need to make Magento aware if our install/upgrade scripts. When working with models, everything is pretty much scoped globally. The final bit of configuration we need to do is again in our node. After this we use our newly defined resource model name inside a self-titled node where we declare its class (again the file path), and database table name (which weвЂ™ll look at later). Inside this we put our model class name which is simply the directory path to your model folder. Next we declare our model name within the node, which in this case be вЂphotoвЂ™. To start with, within your node we need to declare the module version so that later we can create install/upgrade scripts. These are the initial steps that you need to follow when creating a model, and this is what IвЂ™ll cover in this post: Namespace: Creare Module: Photo Part 1 вЂ“ Creating Your Model For the sake of simplicity IвЂ™m only going to use a text field for image paths rather than an upload function. In this example IвЂ™m going to create a photograph model because I want to store photographs in my Magento admin. Creating and manipulating models is a fundamental part of Magento development, so hereвЂ™s my all-in-one mini-series on the basics of setting up a new custom model for your Magento store.

How to use the model resource