jcracknell
Forum Replies Created
-
If you call
get_posts(['post_type' => ['post','page']]), you should get a_doing_it_wrongoriginating from line 160 offrontend-auto-translate.php. This should probably be refactored to always convertpost_typeto an array with anin (...)query.Per the documentation,
post_typecan be a string or an array of post types:
https://codex.ww.wp.xz.cn/Class_Reference/WP_Query#Type_ParametersXDebug gives me this (partial) backtrace:
26 1.9941 35546616 PLL_Frontend_Auto_Translate->pre_get_posts( ) .../class-wp-hook.php:298 27 1.9942 35546712 wpdb->prepare( ) .../frontend-auto-translate.php:160 28 1.9942 35547432 _doing_it_wrong( ) .../wp-db.php:1310 29 1.9942 35548136 trigger_error ( ) .../functions.php:4139- This reply was modified 8 years, 7 months ago by jcracknell.
Forum: Plugins
In reply to: [Polylang] Taxonomy term menu items are not translatedOk sorry, you can close this. Funnily enough I had never changed the admin language, because most everything else is accessible in English.
Forum: Plugins
In reply to: [Polylang] Different font size depending on languageThe language pseudo-class matches a hyphen-separated substring of the
langattribute, so it would work withen,en-US, oren-CA.Forum: Plugins
In reply to: [Polylang] Improve autoloading efficiencyGreat, thanks!
Forum: Plugins
In reply to: [Polylang] Different font size depending on languageIt will provided your theme does:
<html <?php language_attributes() ?>>Then you can
html:lang(en) h1 { font-size: 34px; }.Forum: Plugins
In reply to: [Polylang] Post language in it's css class?html:lang(fr) .post-810 { ... }Supported in IE8+.