Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>If you can avoid it, don't bypass the cache for any blocks. It will improve your user experience in the log run. However, there's a few ways you could tackle this issue.</p> <p>I've blogged <a href="http://mikebywaters.wordpress.com/2011/12/14/disable-magento-full-page-cache-on-a-per-controller-basis/" rel="nofollow">here</a> about disabling the cache on a per controller basis. You could potentially use the same method for the moment, except with a different "if" condition.</p> <p>Where I'm checking:</p> <pre><code>if ($action instanceof &lt;controller_class_name&gt;) { </code></pre> <p>You could just as easily use:</p> <pre><code>if ($user_is_mobile == true) { </code></pre> <p>Doing it this way would only get your mobile users working in the meantime. Really, the answer isn't to disable or bypass the cache, it's to use this same method to listen for the page request and assign different layout handles for mobile and non-mobile requests. Each layout handle will then cache accordingly.</p> <p>Look into how you use handles in Layout Updates. From memory it's something like this:</p> <pre><code>Mage::app()-&gt;getLayout()-&gt;getUpdate()-&gt;addHandle("mobile"); </code></pre> <p>Then in your page.xml, add a new node called mobile, something like this</p> <pre><code>&lt;mobile&gt; &lt;reference name="root"&gt; &lt;remove name="mainHead" /&gt; &lt;block type="core/template" name="mobileHead" /&gt; &lt;/reference&gt; &lt;/mobile&gt; </code></pre> <p>Or something along those lines. This is insanely untested, but I hope you get the idea.</p> <p>You could otherwise look at using responsive css depending on screen resolution.</p>
    singulars
    1. This table or related slice is empty.
    1. POMagento full page cache & design exceptions
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USMagento Guy
    1. USMagento Guy
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POMagento full page cache & design exceptions
      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. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COThank you, Mike. Great blog, btw. Shouldn't exceptions work with FPC on out of the box? Is this a bug in 1.11? 1.12 ships with an iPhone theme, and it loads OK even with FPC on.
      singulars
      1. PO
      1. USdjdy
    2. COThanks mate! To be honest I haven't worked with 1.12 yet at all and I have no idea how it works. I should definitely get in there and have a look! With FPC, if a block is cached, then all of the blocks within that block are cached as a result. It's not really ideal for dynamic content (even though what you're describing isn't really "dynamic"). There's a technique called hole-punching that you may have heard of that bypasses this.
      singulars
      1. PO
      1. USMagento Guy
 

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