alain-schlesser
Forum Replies Created
-
Forum: Plugins
In reply to: [Polylang] Warning: Illegal string offset 'taxonomy' error!Hi,
This error comes from the new ‘relation’ query parameter that’s been introduced by WP 4.1.
Here’s an excerpt from the codex:
Taxonomy Parameters Show posts associated with certain taxonomy. {tax} (string) - use taxonomy slug. Deprecated as of Version 3.1 in favor of 'tax_query'. tax_query (array) - use taxonomy parameters (available with Version 3.1). relation (string) - The logical relationship between each inner taxonomy array when there is more than one. Possible values are 'AND', 'OR'. Do not use with a single inner taxonomy array. taxonomy (string) - Taxonomy. field (string) - Select taxonomy term by ('term_id'(default), 'name' or 'slug') terms (int/string/array) - Taxonomy term(s). include_children (boolean) - Whether or not to include children for hierarchical taxonomies. Defaults to true. operator (string) - Operator to test. Possible values are 'IN'(default), 'NOT IN', 'AND'. Important Note: tax_query takes an array of tax query arguments arrays (it takes an array of arrays). This construct allows you to query multiple taxonomies by using the relation parameter in the first (outer) array to describe the boolean relationship between the taxonomy arrays.So, any plugin or theme could use this functionality now. The Warning appears because the ‘relation’ parameter is not an array, it is a simple string.
I think that the plugin using this on my site is Views by onTheGo Systems.
Forum: Plugins
In reply to: [Polylang] Warning: Illegal string offset 'taxonomy' error!I made a temporary fix to my site like follows. (NB: this is not a correct fix, and something might still be broken. This only removes the warning that is being displayed on the site, until the plugin author can provide a real fix.)
Edit frontend/fronted.php and change the section:
$has_tax = false; if (isset($query->tax_query->queries)) foreach ($query->tax_query->queries as $tax) if ('post_format' != $tax['taxonomy']) $has_tax = true;to the following:
$has_tax = false; if (isset($query->tax_query->queries)) foreach ($query->tax_query->queries as $tax) if( is_array( $tax ) && array_key_exists( 'taxonomy', $tax ) ) { if ('post_format' != $tax['taxonomy']) $has_tax = true; }Forum: Plugins
In reply to: [Polylang] Warning: Illegal string offset 'taxonomy' error!Hi,
I’m having exactly the same problem here. It appeared after WordPress update to 4.1.
I suppose it is due to the changes that were done to the taxonomy queries for 4.1…
@doctormicro: Hmm, strange, it should work with PHP >5.3. Have you verified that you are indeed using this exact version. There are often several versions installed on a server, you have to verify that WordPress is using the correct one.
The cause seems to be an old version of php (< 5.3), which is essentially deprecated.
You should verify with your hosting provider to update to supported version of php.If, like me, you use HostGator, here’s how to change to a supported version:
http://support.hostgator.com/articles/hosting-guide/hardware-software/php-5-3The cause seems to be an old version of php (< 5.3), which is essentially deprecated.
You should verify with your hosting provider to update to supported version of php.If, like me, you use HostGator, here’s how to change to a supported version:
http://support.hostgator.com/articles/hosting-guide/hardware-software/php-5-3Forum: Plugins
In reply to: [CommentLuv] CommentLuv & AntiSpam Bee conflictOkay, I take back was I posted yesterday. It is indeed possible to get them to work together without changing the code. Check out the corresponding article here.
Sorry, Andy, and thanks for the additional feedback and a great plugin!
Forum: Plugins
In reply to: [CommentLuv] CommentLuv & AntiSpam Bee conflictNo, this does not work. The thing is, the text “comment” that is configured is already correct. But CommentLuv uses the field with the NAME “comment”, but it should use the field with the ID “comment”. This can’t be configured in the settings atm.
Same here…
Wordpress version 3.4.1
Wordpress SEO by Yoast upgrade from 1.2.7 to 1.2.8Thanks for the fix, Mike, this does the trick now.
I googled around, and there seem to be other people having this same problem, too. Tom Ewer here in your support section mentioned something like this, and many other people with different wordpress versions (even freshly installed vanilla ones without any plugins) have been having this issue.
Of the top of my head I can’t think of any reason why this text should start out in white, so maybe this is something that should be adressed in core?
Hi Mike,
Thanks for the fast response! Your css fix is now active in my editor, however you changed the white text to… white! Should have chosen black instead 😉
Should be interesting to know, though, why it is white in the first place in the wordpress includes…