Databases
StackOverflow2013
Postsdbo
POMagento : how to properly move custom simple products options in the right column on product page?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POMagento : how to properly move custom simple products options in the right column on product page?
    primarykey
    data
    text
    <p>i am desperately looking to move the custom options ( type: radio inputs ) for simple products ( only have simple products ) to the right column.</p> <p>Right now, it seem like they are showing in a container called "container2" which is at the bottom of the page, and it is called within the view.phtml as follow:</p> <pre><code>&lt;div class="clearer"&gt;&lt;/div&gt; &lt;?php if ($_product-&gt;isSaleable() &amp;&amp; $this-&gt;hasOptions()):?&gt; &lt;?php echo $this-&gt;getChildChildHtml('container2', '', true, true) ?&gt; &lt;?php endif;?&gt; </code></pre> <p>Container2 is also in the layout file catalog.xml , within the content block.</p> <p>So what I did is simply move the options wrapper from the reference name="content" block, the a new one: reference name="right" .</p> <p>For some reason the code is acutally not formated well here and it's also missing some bits so I pasted it here: <a href="http://pastebin.com/nhCUXcF4" rel="nofollow">http://pastebin.com/nhCUXcF4</a></p> <p>Basically I can see my options in the right column, but it is like the radio input is not checked when I click on it, because it asks to chose an option again (they are required)</p> <p>If I leave the options to be in the content block, at the bottom, in the container2 , they work fine as if I click on one, it is checked correctly. If I do not check any and click add to cart, it ask to select a required option.</p> <p>I think the problem comes from the container1 , container2 thing which I don't really understand. also I see in the catalog XML they are bits of code like </p> <pre><code>&lt;block type="core/template_facade" name="product.info.container2" as="container2"&gt; &lt;action method="setDataByKey"&gt;&lt;key&gt;alias_in_layout&lt;/key&gt;&lt;value&gt;container2&lt;/value&gt; &lt;/action&gt; &lt;action method="setDataByKeyFromRegistry"&gt;&lt;key&gt;options_container&lt;/key &lt;key_in_registry&gt;product&lt;/key_in_registry&gt;&lt;/action&gt; &lt;action method="append"&gt;&lt;block&gt;product.info.options.wrapper&lt;/block&gt;&lt;/action&gt; &lt;action method="append"&gt;&lt;block&gt;product.info.options.wrapper.bottom&lt;/block&gt;&lt;/action&gt; &lt;/block&gt; </code></pre> <p>So basically my question is how can I properly move the required options from the content of view.phtml (product page) to the right column ? Any help would be absolutely appreciated right now. Thanks.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USmlclm
    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. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POMagento : how to properly move custom simple products options in the right column on product page?
      1. This table or related slice is empty.
      1. VTUpMod
    1. COCould it be simply a CSS issue?
      singulars
      1. POMagento : how to properly move custom simple products options in the right column on product page?
      1. USYogesh Nath
 

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