Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You've already have the answer, you've just misidentified the problem. </p> <p>Magento only looks in the <code>base</code> package once it's looked for a file in the current theme. So first Magento will check</p> <pre><code>frontend/package/theme/template/test.phtml </code></pre> <p>THEN it will check</p> <pre><code>frontend/base/default/template/test.phtml </code></pre> <p>and if it still doesn't find anything, then it logs the error. </p> <p>If you want to debug where Magento is trying to load the initial file from, add some temporary <code>var_dump</code> or <code>Mage::Log</code> debugging code to the design package file</p> <pre><code>#File: app/code/core/Mage/Core/Model/Design/Package.php public function validateFile($file, array $params) { $fileName = $this-&gt;_renderFilename($file, $params); $testFile = (empty($params['_relative']) ? '' : Mage::getBaseDir('design') . DS) . $fileName; if (!file_exists($testFile)) { var_dump($testFile); Mage::Log($testFile); return false; } return $fileName; } </code></pre> <p>Also, include the actual code you're using on your system here and people will be better able to help you. There's a discrepancy between what you say you're setting your template path as</p> <pre><code>helloworld/test.phtml </code></pre> <p>and what you're actually setting is as (per the Magento errors)</p> <pre><code>test.phtml </code></pre> <p><strong>Update</strong>: Based on what's in the additional logging, it looks like something is adding spaces to your template path, which means Magento can't find your template in it's initial location</p> <pre><code>E:\webserver\xampp\htdocs\magento\app\design\ frontend\default\default \template\mymodule\test.phtml ex. design\ frontend \default \template </code></pre> <p>Also, I don't think it's the root cause, but don't use <code>DS</code> in template paths. PHP will take care of that fore you.</p>
    singulars
    1. This table or related slice is empty.
    1. POGet frontend PHTML template's output inside a model method in Magento
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USAlan Storm
    1. USAlan Storm
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POGet frontend PHTML template's output inside a model method in Magento
      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
    1. COThank you for answering. It seems that Magento doesn't care what theme is currently enabled and searches for the template in the "base" theme. Is there any way to "tell" Magento which template should be used (and where the template is located)?
      singulars
      1. PO
      1. USzitix
    2. CO@zlitix — Unless you're dealing with a heavily modified system, I don't think that's possible. Check your names and paths again, and add the logging/debugging I suggested to your design package.
      singulars
      1. PO
      1. USAlan Storm
    3. COIn my current samples paths are fine. If I put my template where Magento expects it: _frontend\base\default\template\mymodule\test.phtml_ then all works fine. I was just wondering if it can be improved. :) But if it can't be, then current solution is fine. Thank you very much for helping.
      singulars
      1. PO
      1. USzitix
 

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