Thread

Hi,

I’m running EE 2.2.1 and ran into a strange error.

When trying to add a simple search form to a page it get this: “M00o93H7pQ09L8X1t49cHY01Z5j4TT91fGfr” instead of the actual search form.

This search form tag is not nested in some other EE tag.

Any ideas?

Kind regards,

Bart

Code:

{exp:search:simple_form channel="producten" status="open" search_in="titles" where="word" no_result_page="zoeken/geen-resultaten" result_page="zoeken/resultaten"}
    <div id="search">
            <input type="text" name="keywords" id="keywords" value="" size="18" maxlength="100" class="text" />            
            <input type="submit" value="search" id="searchbutton" />
    </div><!-- /#search -->        
{/exp:search:simple_form}

bartblau,

I just inserted that code into a site that I have and the search form appeared as expected. Is that what you are having issues with? The search form is being replaced with those characters?

Hi Marcus,

That’s right, the search form is just replaced with that code.
I have seen in the forums that this piece of code appears in various other occasions, but nothing similar to this.

Any ideas?

Can you create a new template and place only the code for search in it and see if it still converts to the gibberish?

It does. The exact same thing happens.

Have you re-uploaded the Search Module? Or if possible can you update to 2.2.2 and see if that clears out this issue?

Hi Marcus,

I updated to version 2.2.2 and checked the search module folder.

I’ve found this weird piece of code in the forums in others cases, but none match my case. So for a part it’s a known problem… This site has to go live by friday, so I would love to hear some further answers.

Thanks in advance,

Bart

Hi, Bart,

That is a template marker - essentially it is code EE sees but still needs to parse; for some reason the rest of that parsing cycle is not happening.

For instance, other search tags like the search results tag?  If you could try it on an otherwise totally empty template, that might give us a hint as to where to focus the troubleshooting.

Thank you.

Hi Lisa,

I pasted this in an empty template:

Zoeken naar <strong>'{exp:search:keywords}'</strong> levert {exp:search:total_results}{total_results}{/exp:search:total_results} {if "{exp:search:total_results}" == 1}resultaat{if:else}resultaten{/if} op.
            
<ul>
{exp:search:search_results}
<li><a href="http://{auto_path}">{title}</a></li>
{/exp:search:search_results}

This was the result:

Zoeken naar ‘M00o93H7pQ09L8X1t49cHY01Z5j4TT91fGfr’ levert M10o93H7pQ09L8X1t49cHY01Z5j4TT91fGfr resultaten op.

  M30o93H7pQ09L8X1t49cHY01Z5j4TT91fGfr

Dear support staff,

I’m having this problem for over 6 days now. This site has to go live tomorrow…

Can you please check this once more?

Kind regards,

Bart

Hi bartblau!

I saw your plea on Twitter and thought I’d jump in. Lisa is right about the markers. For exp: tags, EE places a little marker in the code that it will come back to later in the parsing process. The reason that it is not getting back to it in your particular code sample, is because you are opening up the exp:search:total_results tag in the conditional and not closing it again. The parser is getting confused and cannot properly locate the marker to parse it out.

Try replacing this:

{if "{exp:search:total_results}" == 1}resultaat{if:else}resultaten{/if}

with this:

{if "{exp:search:total_results}{total_results}{/exp:search:total_results}" == 1}resultaat{if:else}resultaten{/if}

and your troubles should be over. 😉

Hi all,

Thanks for the help. After reuploading the search module for some reason it seems it was uninstalled. When I just reinstalled it, everything works fine.
So there was/is no problem with the code or tags.

Still this seems to be a weird error handling when the module isn’t installed.

Don’t really know how this problem occurred, but for now it’s solved.

Thanks,

Bart

That is a bit odd, Bart.  I don’t think I’ve seen another report of a marker showing just because the module wasn’t installed.  But we’ll keep a look out for a repeat.

Thanks for letting us know how you got this fixed.  If you have any other questions, please do start a new thread.