35% OFF EVERYTHING
WordPress 21st BIRTHDAY SALE
Buy Now

Warning: Illegal string offset 'htmlvar_name'

This topic contains 9 replies, has 2 voices, and was last updated by  Guust 8 years, 3 months ago.

We have moved to a support ticketing system and our forums are now closed.

Open Support Ticket
  • Author
    Posts
  • February 28, 2016 at 1:53 am #129557

    Greg Lennon
    Expired Member
    Post count: 18

    Some of my entries display this error. An example can be found at:

    http://coshomebuilders.com/builders/neighborhood

    I have the latest versions of GeoDirectory Framework (1.5.8), Custom Post Types (1.2.6) and Location Manager (1.4.4).

    Suggestions?

    February 28, 2016 at 2:29 am #129584

    Guust
    Moderator
    Post count: 29970

    You can suppress these warnings, see https://wpgeodirectory.com/docs/faqs/help-i-get-a-php-warning-on-my-pages/

    But can you post your WP admin details in a private reply so we can have a look at your settings.

    February 28, 2016 at 2:45 am #129585

    Greg Lennon
    Expired Member
    Post count: 18
    This reply has been marked as private.
    February 28, 2016 at 5:30 am #129678

    Guust
    Moderator
    Post count: 29970

    You had spaces behind the commas in your options for the multiselect field.
    I removed them but that did not fix it.
    https://wpgeodirectory.com/docs/core-place-settings/#multiselect

    I thought it might be because you use ( and ) in your options so I tried to remove that too, but did not help.
    It might just be because your database now has invalid data, so maybe deleting all the data and fields and starting again might solve it, but I am not sure.
    Can you post your phpMyAdmin details so we can have a look at your database, unless you want to delete the fields and try again.

    February 28, 2016 at 9:06 pm #130040

    Greg Lennon
    Expired Member
    Post count: 18
    This reply has been marked as private.
    February 28, 2016 at 10:46 pm #130070

    Guust
    Moderator
    Post count: 29970

    You can have that data, but
    do not put spaces behind the comma of the options.
    I still am not sure which of the 3 custom fields gave you trouble, so just try adding custom fields and options slowly and test at every little step. Then you know when there was something wrong.

    How did you export your listings? There are quite a lot of”invalid” characters, like 

    it when it�۪s finished.�۝

    https://wpgeodirectory.com/docs/core-export/

    February 28, 2016 at 10:49 pm #130071

    Guust
    Moderator
    Post count: 29970
    This reply has been marked as private.
    February 28, 2016 at 11:08 pm #130076

    Greg Lennon
    Expired Member
    Post count: 18

    I exported them through GeoDirectory Import/Export. Figured that was the most reliable way.

    A lot of the content came from the vendor websites…I didn’t really do any editing. Figured it would prompt me if I exceeded any limits. Having said that, I only stripped HTML formatting from them if it appeared to be a problem. I must have missed a few. I’ll go through the data and clean up the option data and see if that helps.

    I’ll re-post if that fixes the problem. Thanks for your help…

    February 29, 2016 at 3:44 am #130179

    Greg Lennon
    Expired Member
    Post count: 18

    That worked. Pain in the butt to have to parse all that data and remove the crud, but once I did the import was successful. Thank you…

    February 29, 2016 at 6:24 am #130218

    Guust
    Moderator
    Post count: 29970

    You’re welcome 🙂

  • Author
    Posts
Viewing 10 posts - 1 through 10 (of 10 total)

We have moved to a support ticketing system and our forums are now closed.

Open Support Ticket