Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I'm trying to do a similar thing, but the layout only works if I put into one of the following directories:</p> <pre><code>app/design/frontend/base/defaut/layout/[MYMODULE].xml app/design/frontend/[PACKAGE]/defaut/layout/[MYMODULE].xml </code></pre> <p>I don't want to put it into the former because I read that base/default should stay the same, always. I don't want to put it into the latter because it's my theme package folder, which is not the correct place for an unrelated module.</p> <p>I'm running 1.4.1.1. Where should I put this file?</p> <p>EDIT: Got an answer on #magento</p> <pre><code>&lt;Groenleer&gt; mattalexx: you should not modify wiles in app/design/frontend/base i (personally) see no problems in adding XML files. Hence it is the only directory you can trust on is present on the user system. &lt;rooty&gt; mattalexx: place it in base (or default if your still coding 1.3) &lt;mattalexx&gt; rooty, 1.4.1.1 &lt;rooty&gt; it will bubble up &lt;mattalexx&gt; I've heard I should completely not touch that folder, as if it were part of the core. &lt;rooty&gt; well thats true if your writing a customer module &lt;rooty&gt; but if its a community module your planning on releasing to everyone &lt;rooty&gt; thats the place to put it in &lt;mattalexx&gt; rooty, I like to write customer modules as if I am to be releasing it to the world later. Usually it means that they're more portable &lt;mattalexx&gt; Hm, okay, that's great. Thanks rooty &lt;Groenleer&gt; then go with the base/default &lt;Groenleer&gt; but don't change any existing files to make yours work. </code></pre> <p>TL;DR: Use app/design/frontend/base/defaut/layout/[MYMODULE].xml</p>
    singulars
    1. This table or related slice is empty.
    1. PONot parsing layout xml in Magento
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USmattalxndr
    1. USmattalxndr
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

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