<p>That’s a tricky one, because right now the {% cache %} tag is only focussed on the actual HTML that gets output between its tags, but when you include Javascript using <a href="http://buildwithcraft.com/classreference/services/TemplatesService#includeJs-detail" rel="nofollow">TemplatesService::includeJs</a>, etc., that’s actually queuing up the Javascript to be output later on.</p>

<p>So, the trick here will be to make sure any JS that is included within the {% cache %} tag is also output within the {% cache %} tag:</p>

<pre class="lang-twig prettyprint-override"><code>{% cache %}
    {% for entry in craft.entries.section('news') %}

        {{ craft.googleMaps.data('map', entry.map) }}

        {# Output any queued-up JS #}
        {{ getFootHtml() }}

    {% endfor %}
{% endcache %}
</code></pre>

<p>This isn’t a perfect solution because that tag will also output any Javascript that was already queued up before the {% cache %} tag. If there is any, then it will end up getting output twice on requests where the {% cache %} tag already has cached HTML to return. Might be something we can address in a future update though.</p>

CC BY-SA 3.0
2014-10-01T16:46:47.173Z
Thanks for the reply. I would definitely be interested in a little cleaner solution if it's possible. Let me know if I can be any help with testing or anything. This is definitely a unique use case in that most plugins won't use scripts in this manner, but given the nature of Google Maps, this is really the best way to handle it.
Justin Kimbrell
CC BY-SA 3.0
2014-10-01T13:59:50.147Z
2014-10-01T13:59:50.147Z
Brandon Kelly
<p>I am posting this answer in addition to Brandon's. His answer is "correct", but this answer shows the correct code to get the caching using the method Brandon mentioned. Like he said, all the JS that is cached must be included inside the cache tags. So if one wants to cache the output of a map, you must use code similar to the following:</p>

<p><em>Note, the entire map and loop are included in the cache, not just the loop. If you the map isn't included in the cache, you will get a JS error saying the Google Maps API has been instantiated twice (which breaks the whole thing).</em></p>

<pre><code>{% cache %}

    {% set options = {
        id: 'map', 
        width: '400px', 
        height: '300px',
        clustering: true
    } %}

    {{ craft.googleMaps.map(options) }}

    {% for entry in craft.entries.section('news') %}

        {{ craft.googleMaps.data('map', entry.map) }}

        {{ getFootHtml() }}

    {% endfor %}

{% endcache %}
</code></pre>

CC BY-SA 3.0
2014-10-01T16:56:18.877Z
2014-10-01T16:56:18.877Z
Justin Kimbrell
<p>Google Maps for Craft outputs data into script tags to add markers to map with Javascript. Everything works great until a user goes to cache the output of an entries loop. It works upon first page load, but all subsequent page loads do not contain any of the JS at the bottom of the page as it should.</p>

<p>Here is a simple example to duplicate this issue. I am not sure what to do about it. In my mind, there should be a way to output JS that can be cached and output to the page without the query running.</p>

<pre><code>{% set options = {
    id: 'map', 
    width: '400px', 
    height: '300px',
    clustering: true
} %}

{{ craft.googleMaps.map(options) }}

{% cache %}

    {% for entry in craft.entries.section('news') %}

        {{ craft.googleMaps.data('map', entry.map) }}

        test&lt;br&gt;

    {% endfor %}

{% endcache %}
</code></pre>

<p>Within my add-on all the methods that use <code>includeJs</code> behave the same way. But this is just a simple example of what I am doing. I just instantiate an object with some data and include it in the JS.</p>

<pre><code> craft()-&gt;templates-&gt;includeJs('new GoogleMaps.MapData('.$id.','.$data-&gt;toJson().','.$this-&gt;jsonEncode($options).');');
</code></pre>

<p>For additional information you can see it here in this support thread on the Github repo.</p>

<p><a href="https://github.com/objectivehtml/Google-Maps-for-Craft/issues/12" rel="nofollow">https://github.com/objectivehtml/Google-Maps-for-Craft/issues/12</a></p>

<plugin-development><custom-fieldtype>
How does a plugin output JS that can be used within a cache tag?
# How does a plugin output JS that can be used within a cache tag?

(Asked by: username_0 on 2014-10-01)

Google Maps for Craft outputs data into script tags to add markers to map with Javascript. Everything works great until a user goes to cache the output of an entries loop. It works upon first page load, but all subsequent page loads do not contain any of the JS at the bottom of the page as it should.
Here is a simple example to duplicate this issue. I am not sure what to do about it. In my mind, there should be a way to output JS that can be cached and output to the page without the query running.
{% set options = {
    id: 'map', 
    width: '400px', 
    height: '300px',
    clustering: true
} %}

{{ craft.googleMaps.map(options) }}

{% cache %}

    {% for entry in craft.entries.section('news') %}

        {{ craft.googleMaps.data('map', entry.map) }}

        test

    {% endfor %}

{% endcache %}

Within my add-on all the methods that use includeJs behave the same way. But this is just a simple example of what I am doing. I just instantiate an object with some data and include it in the JS.
 craft()->templates->includeJs('new GoogleMaps.MapData('.$id.','.$data->toJson().','.$this->jsonEncode($options).');');

For additional information you can see it here in this support thread on the Github repo.
https://github.com/objectivehtml/Google-Maps-for-Craft/issues/12

**Tags:** plugin-development, custom-fieldtype

---

## 2 answers

### Answer by username_1 on 2014-10-01. Score: 3

That’s a tricky one, because right now the {% cache %} tag is only focussed on the actual HTML that gets output between its tags, but when you include Javascript using TemplatesService::includeJs, etc., that’s actually queuing up the Javascript to be output later on.
So, the trick here will be to make sure any JS that is included within the {% cache %} tag is also output within the {% cache %} tag:
{% cache %}
    {% for entry in craft.entries.section('news') %}

        {{ craft.googleMaps.data('map', entry.map) }}

        {# Output any queued-up JS #}
        {{ getFootHtml() }}

    {% endfor %}
{% endcache %}

This isn’t a perfect solution because that tag will also output any Javascript that was already queued up before the {% cache %} tag. If there is any, then it will end up getting output twice on requests where the {% cache %} tag already has cached HTML to return. Might be something we can address in a future update though.

> **Comments:**
> **username_0**: Thanks for the reply. I would definitely be interested in a little cleaner solution if it's possible. Let me know if I can be any help with testing or anything. This is definitely a unique use case in that most plugins won't use scripts in this manner, but given the nature of Google Maps, this is really the best way to handle it.  

---

### Answer by username_0 on 2014-10-01. Score: 2

I am posting this answer in addition to Brandon's. His answer is "correct", but this answer shows the correct code to get the caching using the method Brandon mentioned. Like he said, all the JS that is cached must be included inside the cache tags. So if one wants to cache the output of a map, you must use code similar to the following:
Note, the entire map and loop are included in the cache, not just the loop. If you the map isn't included in the cache, you will get a JS error saying the Google Maps API has been instantiated twice (which breaks the whole thing).
{% cache %}

    {% set options = {
        id: 'map', 
        width: '400px', 
        height: '300px',
        clustering: true
    } %}

    {{ craft.googleMaps.map(options) }}

    {% for entry in craft.entries.section('news') %}

        {{ craft.googleMaps.data('map', entry.map) }}

        {{ getFootHtml() }}

    {% endfor %}

{% endcache %}


---

