John
Forum Replies Created
-
Forum: Plugins
In reply to: [Stream] Select2 js errorI ran into this same issue myself. It looks like it’s because Stream 3.1.1 is not using the “full” version of select2. A similar issue is described here: http://stackoverflow.com/questions/30235909/using-select2-get-error-error-no-select2-compat-query
Fortunately it looks like this was fixed in the GitHub repo, so I’m expecting this will be fixed in the next release: https://github.com/xwp/stream/commit/67274aee0bb9dffa5345c8c2e7d93c35feed5ec0#diff-1eea398e7896ba5b5dd5a6f93862c89a
I believe this could be an issue with asking Relevanssi to index all visible or simply all custom fields, and having a theme or plugin that stores PHP objects in the post meta.
I wrote up a detailed blog post about it here: http://jolekpress.com/php-catchable-fatal-error-object-of-class-could-not-be-converted-to-string/
My recommendation would be to have Relevanssi explicitly check that the meta data it’s about to index is a string or an array of strings before treating it as such.
I ran into this exact same issue myself recently. In my case, I tracked it down to having set Relevanssi to index all “visible” custom fields, and on my site, I was storing some serialized PHP objects in custom fields.
This causes an issue because all custom field values are passed to relevanssi_tokenize, which only knows how to handle strings and arrays.
This could either be fixed by updating the plugin to ignore custom field values that are objects, or to change which custom fields are being indexed.
I wrote up a more detailed post about this here: http://jolekpress.com/php-catchable-fatal-error-object-of-class-could-not-be-converted-to-string/
- This reply was modified 9 years, 7 months ago by John.