Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Depending upon the area(frontend or adminhtml), frontend or adminhtml router are dispatched. <br /> So you need not need to worry about getting it messed up as long as you are using different controller files for frontend and adminhtml, frontend controller extending from <code>Mage_Core_Controller_Front_Action</code> &amp; adminhtml extending from <code>Mage_Adminhtml_Controller_Action</code>.</p> <p>Frontend / Adminhtml routers can be defined as (just a syntax):</p> <pre><code>&lt;frontend&gt; &lt;routers&gt; &lt;[module]&gt; &lt;use&gt;standard&lt;/use&gt; &lt;args&gt; &lt;module&gt;[Namespace]_[Module]&lt;/module&gt; &lt;frontName&gt;[module]&lt;/frontName&gt; &lt;/args&gt; &lt;/[module]&gt; &lt;/routers&gt; &lt;/frontend&gt; &lt;admin&gt; &lt;routers&gt; &lt;[module]&gt; &lt;use&gt;admin&lt;/use&gt; &lt;args&gt; &lt;module&gt;[Namespace]_[Module]&lt;/module&gt; &lt;frontName&gt;[module]&lt;/frontName&gt; &lt;/args&gt; &lt;/[module]&gt; &lt;/routers&gt; &lt;/admin&gt; </code></pre> <p>And you can create frontend controllers under: <code>app/code/[codePool]/[Namespace]/[Module]/controllers/</code> <br/>For example:</p> <pre><code>&lt;?php //file: app/code/local/MagePsycho/Testmodule/controllers/IndexController.php class MagePsycho_Testmodule_IndexController extends Mage_Core_Controller_Front_Action { public function indexAction(){ } } </code></pre> <p>In order to access it from url: <code>http://your-magento-url/testmodule/index/index</code><br/> and adminhtml controllers under: <code>app/code/[codePool]/[Namespace]/[Module]/controllers/Adminhtml/</code> <br/>For example: </p> <pre><code>&lt;?php //file: app/code/local/MagePsycho/Testmodule/controllers/Adminhtml/IndexController.php class MagePsycho_Testmodule_Adminhtml_IndexController extends Mage_Adminhtml_Controller_Action { public function indexAction(){ } } </code></pre> <p><br/> In order to access it from url: <code>http://your-magento-url/testmodule/adminhtml_index/index</code><br/> (You can see the Adminhtml folder for separating adminhtml controllers)</p> <p>Hope this gave you some info.<br /> Thanks</p>
    singulars
    1. This table or related slice is empty.
    1. POMagento Module with Frontend and Admin functionality
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USMagePsycho
    1. USMagePsycho
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POMagento Module with Frontend and Admin functionality
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI'm sorry I thought I had this but I don't. What I suppose I'm lost by is what do I call my admin controller and where do I put it in the directory structure? As you say I need a standard index controller that extends Mage_Core_Controller_Front_Action and an admin controller that extends Mage_Adminhtml_Controller_Action.
      singulars
      1. PO
      1. USRobDW1984
    2. COMagePsycho so my directory structure for my admin controller would look like /Module/controllers/Adminhtml/IndexController.php..?
      singulars
      1. PO
      1. USRobDW1984
    3. COYeah you are correct. Also, I have updated my post. Please check once.
      singulars
      1. PO
      1. USMagePsycho
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload