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: Issue with form and weird search/mod.search.php error

Status	Resolved
Add-on / Version	Publisher 1.2.0
Severity	Trivial
EE Version	2.8.1

Toby Callinan

Jul 15, 2014

Hi ya,

I have an odd error that I can’t seem to sort out. I have a profile area where punters can naturally change their info as needed. I am using Profile:Edit, but have also tried channel:forms and the result is the same.

I’ve noticed that the form has: data-publisher-updated=“true” appended. Can you please explain what this is doing?

This issue is only present if I add the URL prefix.

A PHP Error was encountered
Severity: Notice
Message: unserialize(): Error at offset 0 of 448 bytes
Filename: search/mod.search.php
Line Number: 403

A PHP Error was encountered
Severity: Notice
Message: unserialize(): Error at offset 0 of 448 bytes
Filename: search/mod.search.php
Line Number: 403

Line 403 of search/mod.search.php is

$this->_meta = unserialize($meta_array);

I have tried uninstalling the search module and that results in a server malfunction. I am using Low Search.

I’m a little lost. Any pointers would be gratefully recieved.

Cheers

BoldMinded (Brian)

Can you post your full template code somewhere? Maybe as a gist or pastie? Also, what does the HTML look like after the page is loaded? Post that somewhere too.

Toby Callinan

No probs.

This is what I have.

This is the EE code: http://pastie.org/9393289

This is the parsed HTML: http://pastie.org/9393320 (I’ve had to remove some of the parse HTML due to size in pastie).

Cheers

BoldMinded (Brian)

data-publisher-updated=”true” means Publisher has parsed the <form> tag and tried to update any hidden form fields, specifically the params field with the encoded data so the urls are prefixed with the language code properly.

BoldMinded (Brian)

Your template code doesn’t have low:search in it… are you sure you’re using Low Search? It looks like you’re using the native search based on the <form> tag output.

Toby Callinan

Ahh, crap. Sorry. Yes. You are right. I was using Low search, but it was causing issues so I have disabled it. Sorry - This project has been going on for ages!

Low search is disabled. I had the Publisher Low Search ext enabled. Just uninstalled that and the issue persists.

Could something there be causing it you think?

Cheers

BoldMinded (Brian)

What happens if you remove the profile:edit forms from the page? Have you tried to replicate this in a template that has ONLY the search form tag?

As it stands right now I can’t reproduce this. All my search:form pages are working and adding the prefix properly. Can you submit the support form in the Publisher module page in the CP so I can see what your settings are?

Toby Callinan

If I remove the both forms: Channel:forms and Profile:edit, it works fine, without error. Other pages that have the search on are all fine. It only seems to be this one page that has the forms that post to the db. Well, saying that Cartthrob is working OK.

I’ve just removed the search in the profile area for now until I get a little more time to delve into it.

Man thanks for the speedy support as always. It really makes a difference. Thanks.

BoldMinded (Brian)

Ok, so that narrows it down a bit. Thanks for the info. I don’t have a copy of profile:edit, so I’ll ask them for a dev/test copy to see if I can replicate it. I have family in town right now so I may not be able to spend more time on this until Wed or Thursday, but I’ll keep you posted.

BoldMinded (Brian)

I still have not received a copy of Profile:edit. If you want to speed things up a bit you can email it to support at boldminded dot com so I can look into this.

#10

BoldMinded (Brian)

Toby, I got Profile:Edit setup locally using the example templates and it worked just fine. It saved the form data fine, even in 2 languages. Having never tested Publisher with PE I’m actually pleased it worked so well. The PE install process left a lot to be desired though… what a confusing add-on.

The only thing I changed in the example template was add some hidden fields for Publisher:

{exp:profile:edit return="profile" publisher_lang_id="{publisher:current_language_id}"}
 <input type="text" name="publisher_view_status" value="open" />
 <input type="text" name="publisher_save_status" value="open" />
 <input type="text" name="publisher_lang_id" value="{publisher:current_language_id}" />

#11

BoldMinded (Brian)

Have not heard anything in over a month. Closing this ticket.