Databases
StackOverflow2013
Postsdbo
POUnable to run a simple install script
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POUnable to run a simple install script
    text
    copied!<p>I am trying to follow <a href="http://www.magentocommerce.com/knowledge-base/entry/magento-for-dev-part-6-magento-setup-resources" rel="nofollow">This tutorial</a>, somewhat unsuccessfully!</p> <p>I have got to the point where my script should display "Running This Upgrade: Myname_Weblog_Model_Resource_Setup Exit for now". This does not happen.</p> <p>I believe it is something to do with my config file but looking though it I cannot work out what is wrong.</p> <p>I have put a die statement into the setup.php file and that killed the script as expected. I then removed the die statement from setup.php and placed it into mysql4-install-0.1.0.php, this had no effect and the script continued on to render data from my controller.</p> <p>I have added the code which I have been looking at to try and find the solution (as well as the full folder structure, hopefully its clear enough), could someone please advise me where the problem is or where else I should be looking to resolve this issue. </p> <ul> <li>Myname</li> <li><ul> <li>Weblog</li> </ul></li> <li><ul> <li><ul> <li>Model</li> </ul></li> </ul></li> <li><ul> <li><ul> <li><ul> <li>Resource</li> </ul></li> </ul></li> </ul></li> <li><ul> <li><ul> <li><ul> <li><ul> <li>Blogpost</li> </ul></li> </ul></li> </ul></li> </ul></li> <li><ul> <li><ul> <li><ul> <li><ul> <li>-Collection.php</li> </ul></li> </ul></li> </ul></li> </ul></li> <li><ul> <li><ul> <li><ul> <li>-Blogpost.php</li> </ul></li> </ul></li> </ul></li> <li><ul> <li><ul> <li><ul> <li>-Setup.php</li> </ul></li> </ul></li> </ul></li> <li><ul> <li><ul> <li>-Blogpost.php</li> </ul></li> </ul></li> <li><ul> <li><ul> <li>controllers</li> </ul></li> </ul></li> <li><ul> <li><ul> <li>-IndexController.php</li> </ul></li> </ul></li> <li><ul> <li><ul> <li>etc</li> </ul></li> </ul></li> <li><ul> <li><ul> <li>-config.xml</li> </ul></li> </ul></li> <li><ul> <li><ul> <li>sql</li> </ul></li> </ul></li> <li><ul> <li><ul> <li><ul> <li>weblog_setup</li> </ul></li> </ul></li> </ul></li> <li><ul> <li><ul> <li><ul> <li>-mysql4-install.0.1.0.php</li> </ul></li> </ul></li> </ul></li> </ul> <p>Myname/Weblog/etc/config.xml</p> <pre><code>&lt;config&gt; &lt;modules&gt; &lt;Tonysimpson_Weblog&gt; &lt;version&gt;0.1.0&lt;/version&gt; &lt;/Tonysimpson_Weblog&gt; &lt;/modules&gt; &lt;global&gt; &lt;models&gt; &lt;weblog&gt;&lt;!--group name, matches the module name--&gt; &lt;class&gt;Tonysimpson_Weblog_Model&lt;/class&gt;&lt;!--Base name allmodels in the weblog group will have--&gt; &lt;resourceModel&gt;weblog_resource&lt;/resourceModel&gt;&lt;!--indicagtes which resource model should be used--&gt; &lt;/weblog&gt; &lt;weblog_resource&gt; &lt;class&gt;Tonysimpson_Weblog_Model_Resource&lt;/class&gt; &lt;entities&gt; &lt;blogpost&gt; &lt;table&gt;blog_posts&lt;/table&gt; &lt;/blogpost&gt; &lt;/entities&gt; &lt;/weblog_resource&gt; &lt;/models&gt; &lt;resources&gt; &lt;weblog_setup&gt; &lt;setup&gt; &lt;module&gt;Tonysimpson_Weblog&lt;/module&gt; &lt;class&gt;Tonysimpson_Weblog_Model_Resource_Setup&lt;/class&gt; &lt;/setup&gt; &lt;/weblog_setup&gt; &lt;/resources&gt; &lt;/global&gt; &lt;frontend&gt; &lt;routers&gt; &lt;weblog&gt; &lt;use&gt;standard&lt;/use&gt; &lt;args&gt; &lt;module&gt;Tonysimpson_Weblog&lt;/module&gt; &lt;frontName&gt;weblog&lt;/frontName&gt; &lt;/args&gt; &lt;/weblog&gt; &lt;/routers&gt; &lt;/frontend&gt; </code></pre> <p></p> <p>MyName/Weblog/Model/Resource/Setup.php</p> <pre><code>class Tonysimpson_Weblog_Model_Resource_Setup extends Mage_Core_Model_Resource_Setup { } </code></pre> <p>Myname/Weblog/sql/weblog_setup/mysql4-install-0.1.0.php</p> <pre><code>echo 'running this upgrde: ' . get_class($this) . "\n &lt;br /&gt; \n"; die("exit for now"); </code></pre>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

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