All add-ons currently require PHP 7.4 or greater.

On July 4th 2024 PHP 8.2 will be the new minimum requirement for all add-ons. Expect any add-on released after that date to require 8.2 or greater. Some releases may not immediately take advantage of 8.x specific features in PHP, which means you might, be able to continue using new releases in PHP 7.4, however, if you experience an error the first thing you should do is update to PHP 8.2 then create a support ticket if the error persists.

Publisher does not support the Fluid field type. Please do not contact asking when support will be available.

If you purchased an add-on from expressionengine.com, be sure to visit boldminded.com/claim to add the license to your account here on boldminded.com.

Ticket: Escaping

Status	Resolved
Add-on / Version	Speedy 1.8.1
Severity
EE Version	7.3.14

Harold Kuiper

Dec 12, 2023

Hi Brian,
We use Speedy but we seem not to get the escape working.

We have a navigation where we use this code:
{exp:speedy:fragment ttl="0" key="nav-top" global="yes"}

BoldMinded (Brian)

Can you add the code example back in a comment and use the <pre><code> tags so I can see it in full? It’s not parsing very well in your initial report. Thanks.

Harold Kuiper

This is the code I use in the navigation. There are other places where I need stuff from an exp:channel:entries but want to place the exp:speedy:fragment outside of that. That implies I need to use the escape. But it does not run…

This is a part of the code for the navigation: {exp:speedy:fragment ttl=”0” key=”nav-top” global=”yes”}

<nav class="navbar-main navbar navbar-expand-lg py-1 mt-lg-auto" aria-label="ING THINK navigation">
  <div class="container">
    <div class="navbar-name position-fixed top-0 end-0 d-lg-none”>Brand</div>
      <ul class="navbar-nav w-100 mb-2 mb-lg-0 d-none d-lg-flex pb-1">
        <li class="nav-item me-4">
          {exp:speedy:escape:home}<a href="/%22class=%22nav-link" class="nav-link fs-large py-0{if segment_1 == ">Home</a>{/exp:speedy:escape:home}
        </li>

Best regards, Harold

BoldMinded (Brian)

That’s not a full example, I don’t see where the entries tag starts and ends or where the fragment tag starts and ends.

Create a very basic bare bones example with only EE tags, leave out all the other HTML that isn’t necessary to illustrate the issue.

BoldMinded (Brian)

Could you be running into this issue? https://boldminded.com/support/ticket/2789

Harold Kuiper

Hi Brian, Here is my code (I’ve removed style clutter). It is pretty obvious piece of code, but can’t get it to work so I can see the active state change. As I said, I need the escape to work on other place too, but this one is the part that is the simplest to work with.

{exp:speedy:fragment ttl="0" key="nav-top" global="yes"}
<nav class="navbar-main navbar navbar-expand-lg py-1 mt-lg-auto" aria-label="ING THINK navigation">
  <div class="container">
    <ul class="navbar-nav">
      <li class="nav-item">
        {exp:speedy:escape:home}<a href="/%22class=%22nav-link{if" class="nav-link{if segment_1 == ">Home</a>{/exp:speedy:escape:home}
      </li>
      <li class="nav-item">
        {exp:speedy:escape:forecasts}<a href="/forecasts/%22class=%22nav-link{if" class="nav-link{if segment_1 == ">Forecasts</a>{/exp:speedy:escape:forecasts}
      </li>
    </ul>
  </div>
</nav>
{/exp:speedy:fragment}

Best regards, Harold

BoldMinded (Brian)

I need more information. What cache driver are you using? Redis, database, static?

BoldMinded (Brian)

Did you try anything else to debug it? Did you try setting a TTL other than 0? Changing it from global=”yes” to global=”no”?

BoldMinded (Brian)

I ran a few tests locally and it’s working fine for me. I simplified your code and made a couple of different examples:

{exp:speedy:fragment ttl="300" key="nav-top" driver="file"}
    {exp:channel:entries channel="pages" limit="1" dynamic="no"}
        <h1>{title}</h1>
        {exp:speedy:escape:home}
            {if segment_1}segment 1 is {segment_1}{/if}
        {/exp:speedy:escape:home}
        {exp:speedy:escape:forecasts}
            {if segment_2}segment 2 is {segment_2}{/if}
        {/exp:speedy:escape:forecasts}
    {/exp:channel:entries}
{/exp:speedy:fragment}

{exp:speedy:fragment ttl="0" key="nav-top-no-entries-tag" driver="file"}
    {exp:speedy:escape:home2}
        {if segment_1}segment 1 is {segment_1}{/if}
    {/exp:speedy:escape:home2}
    {exp:speedy:escape:forecasts2}
        {if segment_2}segment 2 is {segment_2}{/if}
    {/exp:speedy:escape:forecasts2}
{/exp:speedy:fragment}

The first fragment resulted in caching the following, which is expected and correct:

{!-- ra:0000000000000d170000000000000000 --}
        <h1>Simple Grid in Bloqs Test</h1>
        
            {if segment_1}segment 1 is {segment_1}{/if}
        
        
            {if segment_2}segment 2 is {segment_2}{/if}

And the second fragment resulted in caching the following, which is expected and correct:

{!-- ra:0000000000000d2a0000000000000000 --}
        {if segment_1}segment 1 is {segment_1}{/if}
    
    
        {if segment_2}segment 2 is {segment_2}{/if}

Harold Kuiper

Hi Brian, I played around with different options and this is what came out: - If I put your code in my snippet, nothing is displayed from that snippet. - If I put your code in the layouts/_html_wrapper it doesn’t work either. - Only if I put your code in the actual entry or in an embed, does it work. What I have now done is moved the navigation from a snippet to an embed and now it is indeed working fine. Solved as far as I’m concerned. Kind regards, Harold

#10

Harold Kuiper

Hi Brian, Strange is that on my development server the embed works: the {if segment_2} etc appears in the template. On the production server the escaping is not working so had to head back to the navigation without the segment conditional. Do you have any clue where I should be looking to find why this difference can happen? Best regards, Harold

#11

BoldMinded (Brian)

If it works in one environment and not another, then there is something going on in that environment causing a different behavior, and it could be any number of things that I’m not privy too.