| Prio | Original string | Translation | — |
|---|---|---|---|
| ↑ | Extra advanced version of Genesis Featured Page Widget: Custom Content, Images, URLs etc. -- Only for (premium) Genesis Framework 2.0+! | You have to log in to add a translation. | Details |
Original untranslated
Extra advanced version of Genesis Featured Page Widget: Custom Content, Images, URLs etc. -- Only for (premium) Genesis Framework 2.0+!
You have to log in to edit this translation. Meta |
|||
| ↑ | Genesis Featured Page Extras | You have to log in to add a translation. | Details |
Original untranslatedMeta |
|||
| --> You now can use conditionals like that: | You have to log in to add a translation. | Details | |
Original untranslated
--> You now can use conditionals like that:
CommentFound in faq paragraph. You have to log in to edit this translation. Meta |
|||
| <em>Note:</em> Be careful with the function name 'is_language' - this only works if there's no other function in your install with that name! If it's already taken (very rare case though), then just add a prefix like <code>my_custom_is_language()</code>. | You have to log in to add a translation. | Details | |
Original untranslated
<em>Note:</em> Be careful with the function name 'is_language' - this only works if there's no other function in your install with that name! If it's already taken (very rare case though), then just add a prefix like <code>my_custom_is_language()</code>.
CommentFound in faq paragraph. You have to log in to edit this translation. Meta |
|||
| With the following language detection code you are now able to make conditional statements, in the same way other WordPress conditional functions work, like <code>is_single()</code>, <code>is_home()</code> etc.: | You have to log in to add a translation. | Details | |
Original untranslated
With the following language detection code you are now able to make conditional statements, in the same way other WordPress conditional functions work, like <code>is_single()</code>, <code>is_home()</code> etc.:
CommentFound in faq paragraph. You have to log in to edit this translation. Meta |
|||
| You can use the awesome <a href="http://wordpress.org/plugins/widget-logic/">"Widget Logic"</a> plugin (or similar ones) and add additional paramaters, mostly conditional stuff like <code>is_home()</code> in conjunction with <code>is_language( 'de' )</code> etc. This way widget usage on a per-language basis is possible. Or you place in the WPML language codes like <code>ICL_LANGUAGE_CODE == 'de'</code> for German language. Fore more info on that see their blog post: http://wpml.org/2011/03/howto-display-different-widgets-per-language/ | You have to log in to add a translation. | Details | |
Original untranslated
You can use the awesome <a href="http://wordpress.org/plugins/widget-logic/">"Widget Logic"</a> plugin (or similar ones) and add additional paramaters, mostly conditional stuff like <code>is_home()</code> in conjunction with <code>is_language( 'de' )</code> etc. This way widget usage on a per-language basis is possible. Or you place in the WPML language codes like <code>ICL_LANGUAGE_CODE == 'de'</code> for German language. Fore more info on that see their blog post: http://wpml.org/2011/03/howto-display-different-widgets-per-language/
CommentFound in faq paragraph. You have to log in to edit this translation. Meta |
|||
| You can now also place the "Language Switcher Widget" at the bottom of your site :). | You have to log in to add a translation. | Details | |
Original untranslated
You can now also place the "Language Switcher Widget" at the bottom of your site :).
CommentFound in faq paragraph. You have to log in to edit this translation. Meta |
|||
| (2) Usage with the "WPML" plugin:↵ Widgets can be translated with their "String Translation" component - this is much easier than adding complex footer credits logic for a lot of languages to your functions.php... | You have to log in to add a translation. | Details | |
Original untranslated
(2) Usage with the "WPML" plugin:↵
Widgets can be translated with their "String Translation" component - this is much easier than adding complex footer credits logic for a lot of languages to your functions.php...
CommentFound in faq paragraph. You have to log in to edit this translation. Meta |
|||
| (1) In general: You may use it for "global" widgets. | You have to log in to add a translation. | Details | |
Original untranslated
(1) In general: You may use it for "global" widgets.
CommentFound in faq paragraph. You have to log in to edit this translation. Meta |
|||
| All the custom & branding stuff codes above can also be found as a Gist on GitHub: https://gist.github.com/deckerweb/8511594 (you can also add your questions/ feedback there :) | You have to log in to add a translation. | Details | |
Original untranslated
All the custom & branding stuff codes above can also be found as a Gist on GitHub: https://gist.github.com/deckerweb/8511594 (you can also add your questions/ feedback there :)
CommentFound in faq paragraph. You have to log in to edit this translation. Meta |
|||
| <strong>Final note:</strong> I DON'T recommend to add customization code snippets to your child theme's <code>functions.php</code> file! <strong>Please use a functionality plugin or an MU-plugin instead!</strong> This way you can also use this better for Multisite environments. In general you are not abusing the functions.php for plugin-specific stuff and you are then also more independent from child theme changes etc. If you don't know how to create such a plugin yourself just use one of my recommended 'Code Snippets' plugins. Read & bookmark these Sites: | You have to log in to add a translation. | Details | |
Original untranslated
<strong>Final note:</strong> I DON'T recommend to add customization code snippets to your child theme's <code>functions.php</code> file! <strong>Please use a functionality plugin or an MU-plugin instead!</strong> This way you can also use this better for Multisite environments. In general you are not abusing the functions.php for plugin-specific stuff and you are then also more independent from child theme changes etc. If you don't know how to create such a plugin yourself just use one of my recommended 'Code Snippets' plugins. Read & bookmark these Sites:
CommentFound in faq paragraph. You have to log in to edit this translation. Meta |
|||
| <em>Note:</em> Other plugins could still (independently from my plugin) enable shortcode support within (text) widgets or anywhere else. | You have to log in to add a translation. | Details | |
Original untranslated
<em>Note:</em> Other plugins could still (independently from my plugin) enable shortcode support within (text) widgets or anywhere else.
CommentFound in faq paragraph. You have to log in to edit this translation. Meta |
|||
| Some webmasters could need this for security reasons regarding their stuff members or for whatever other reasons... :). | You have to log in to add a translation. | Details | |
Original untranslated
Some webmasters could need this for security reasons regarding their stuff members or for whatever other reasons... :).
CommentFound in faq paragraph. You have to log in to edit this translation. Meta |
|||
| Of course, it's possible! Just add the following constant to your child theme's <code>functions.php</code> file or to a functionality plugin: | You have to log in to add a translation. | Details | |
Original untranslated
Of course, it's possible! Just add the following constant to your child theme's <code>functions.php</code> file or to a functionality plugin:
CommentFound in faq paragraph. You have to log in to edit this translation. Meta |
|||
| Character limits for Page Title and Content Teaser: only integer values are allowed, plus: cutoff is always after the full word not within it! | You have to log in to add a translation. | Details | |
Original untranslated
Character limits for Page Title and Content Teaser: only integer values are allowed, plus: cutoff is always after the full word not within it!
CommentFound in faq paragraph. You have to log in to edit this translation. Meta |
|||
Export as
Comment
Short description.