Warning message in results after choosing categories

Support has been upgraded!



The Support Forum is closed. Not to worry!  Providing the top quality support you expect and we're known for will continue! We're not ending support, just changing where you submit requests. This will provide you with the best experience possible.

Premium Support

Have you purchased an addon for Connections such as one of our premium templates or extensions with a valid license and you need help?

Please open a Support Ticket in your user account.

Click here to open a support ticket.

Free Support

Are you using the free Connections plugin? Don't worry, you are still very important to us! We are still providing you with the same high quality support that we're known for.

Please open a new support topic in the WordPress support forums for Connections.

Click here to open a support topic.

This topic is: resolved

Tagged: , ,

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • 11/08/2013 at 11:22 am #273258
    IT Department
    Participant

    Since the last connections update I have this warning message when I select one or more categories in cMap and press the send button:

    Warning: explode() expects parameter 2 to be string, array given in /var/www/domain.com/wp-content/plugins/connections/includes/class.seo.php on line 301

Warning: explode() expects parameter 2 to be string, array given in /var/www/domain.com/wp-content/plugins/connections/includes/class.seo.php on line 375
    11/09/2013 at 12:09 pm #273305
    Steven Zahm
    Keymaster

    @ roy

    Can you share a link so I can see?

    11/11/2013 at 4:28 am #273353
    IT Department
    Participant
    This reply has been marked as private.
    11/11/2013 at 12:58 pm #273366
    Steven Zahm
    Keymaster

    @ roy

    Ok, I see the issue. I’ll make sure this is fixed in the 0.8 release. Temporarily, disable the Page Title and Page Description options under the SEO tab on the Connections : Settings admin page.

    08/26/2014 at 12:40 pm #302023
    Steven Zahm
    Keymaster

    @ roy

    I believe this is fixed … don’t remember fixing it and I didn’t mark the issue resolved in my issue tracker, lol … but I can no longer replicate the error and looking at the code, it shouldn’t be possible. Any way let me know if you still encounter this error. I’m going to mark this as resolved.

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

You cannot reply to this support topic. Please open your own support topic.