Forum Replies Created
-
AuthorPosts
-
Ah, I’ve got it to work now and finally tested it before posting here…
Forked to this: https://gist.github.com/4512672
—> removed dynamic_sidebar… at the bottom — changed/added stuff on top of file. For me this worked, I hope for you too

Great
I understand what you mean! Please try to add this line of code before the first code line where it says “get_header”:
remove_action( 'genesis_sidebar', 'genesis_do_sidebar' );Does that work?
Ok, I have commented out the add_action within if statement — just uncomment for real usage of course

Go and add some code to your child theme’s functions.php file, a functionality plugin or even via the “Genesis Simple Hooks” plugin.
Tools you’ll probably need: Genesis Hook Reference: http://my.studiopress.com/docs/hook-reference/ and Genesis Visual Hook Guide: http://genesistutorials.com/visual-hook-guideWith that in mind you could do something like that:
add_action( 'genesis_meta', 'your_custom_wrapper_function_name' );
function your_custom_wrapper_function_name() {
if ( is_search() ) {
// add_action( 'genesis_before_content', 'custom_function_for_search_display' );
} // end if
} // end function
Choose the best hook for your site within the if statement.
It’s untested but I use similar stuff on a lot of projects. I hope this helps you go your way

Per default you have no chance of editing — but you always could do add a custom “404.php” file to your child theme’s root folder. You could copy the file from the “/genesis/” folder and customize.
But wait, there’s a better way to do that: I’ve made a plugin just for this where you could place in Widgets of your liking for the 404 error page. Just install this plugin: http://wordpress.org/extend/plugins/genesis-widgetized-notfound/ — activate it and place in some widgets and you’re done.
In the Gist code snippet I can see no reference of a sidebar for displaying. There’s currently no “get_sidebar( ‘id-of-sidebar’ );” function or for just a widget area, no “dynamic_sidebar( ‘id-of-sidebar’ );” function.
You need to add on or the other to your template to get an registered sidebar or widget area displayed.
There’s the community plugin “Gensesis Favicon Uploader” http://wordpress.org/extend/plugins/genesis-favicon-uploader/ — works for the frontend. I do not know of another lightweight plugin for frontend & backend at the moment.
But you still can manage all locations via code snippets into your child theme’s functions.php file or a functionality plugin:
Copy code from here: https://gist.github.com/4511610
What this does:
The first block works for the frontend only, and only for Genesis: place a favicon image named “favicon.ico” in your child theme’s “/images/” folder.The second block works for WordPress in general, for backend and WP login page: place a favicon image named “favicon_backend.ico” in your child theme’s “/images/” folder.
Hope that helps

In the end you decide which breakpoints you implement for several viewports or devices. However, it’s recommended to implement the most common widths of popular devices, see the below tool for a great example of that:
There are some helpful tools out there, one is from StudioPress itself, a responsive tester: http://www.studiopress.com/responsive/
Another one: http://bueltge.de/test/media-query-tester.php
Also, when using the latest Firefox browser there are some web deloper tools integrated, such as an viewport testing tool, located in the menu under Extras > Web Developer Tools.
The Translation plugin from Remkus is powered by the community, therefore not an official release. Remkus collects updated translation files for Genesis 1.9.x at the moment. So shortly there should be an update out.
Please do consider contributing missing strings for your language: see @Remkus reply above for more info or have look at this post: http://www.studiopress.com/forums/topic/genesis-translations/
THANKS!
@GaryJ:
That’s not true, maybe in the .pot file you has, but it’s in the actual PHP files!
For 1.9.x:
#@ genesis
#: lib/structure/search.php:23
msgid "Search this website"I rely not on .pot files but rather on scanning the actual framework files with each version — as these matter in the end what gets displayed and what not.
I don’t own these plugins and therefore have no experience with them on Genesis powered sites. From the demo and description I would not recommend them for the multilingual setup because all works with Javascript on the frontend and you don’t seem to have URLs for different languages. It also seems to work more automatically as it pulls translations from external services like “Google Translate” or Bing. In the end this could be useful for single sites to offer a translation alternative but for REAL multilingual sites I would only use a Multisite setup which is the currently best option overall. WPML might be a great option for small sites and less languages, mostly 2-3, but it adds overhead and seems to lock user in regarding your site experience in the long end.
Also have look at this thread here for more discussion on this topic: http://www.studiopress.com/forums/topic/multi-lingual-translation-plugins/
Sorry for the late reply!
Yes the first mentioned plugin by you works like an “more comfort for the admin/ editor & user” plugin. It doesn’t add overhead that locks you in later but rather adds some additions to the admin workflow. And for the frontend it mostly adds the language switcher – similar to that from WPML.
A similar plugin compared to “Multilingual Press” is this one, “Multisite Language Switcher” which is a little more basic/simple but has a solid switch as well as some other basic settings on a per site basis: http://wordpress.org/extend/plugins/multisite-language-switcher/
WPML itself is a great concept and it works — but it adds lots of overhead and needs lots of additional plugins if you’re working with WooCommerce, EDD, BuddyPress and so. The internal workflow can also be complicated for editors because of the many additions on the edit screens. Also for more than 2 languages and lots of pages and/or posts it may lead out of order sometimes…
At first sight, Multisite may look like it’s “too much” for that task but if you already worked with multilingual sites then it’s the currently best option overall, especially when you just keep all with WordPress default stuff
What @Remkus said!
The search placeholder string definitely changed from “Search this website %s” in 1.8.x to “Search this website” in 1.9.x!
The search button string did not change as of my comparing — but if the language file for your language was not properly made then this still could lead to non-loaded/non-displayed translated strings.
Also, like @wpsmith said, if you have modified such strings via functions.php — like suggested by the tutorials regarding “Search” on StudioPress here, then this will be used instead of language file string.
To speed things up anyway, just jump in on the community translation portal mentioned above and @Remkus will add all these to the Genesis Translations plugin.
–David Decker, community translation helper
Premise landing pages and WordPress pages with the “Landing Page” page template are 2 totally different things! The included page template in Prose is just a small alternative for small & simple landing pages. Otherwise, landing pages with Premise are full featured and are fully independent from your current theme! You can only use one or the other for a specific landing page. If you’re using Premise anyways I am wondering why you still want to use a page with that template?
@mtalley:
These instructions might be regarding the old Prose 1.0 version which had such a file. In spring of this year updated version 1.5/ 1.5.1 of Prose was released which no longer features a “custom.css” file. Instead, it has a custom CSS section which you’ll find directly under Genesis Settings as a submenu. There you can add your custom rules or override existing rules (with added “!important”).
In the case of Prose, it is NEVER recommended to touch the downloaded files! With version 1.5 and higher Prose has the ability for automatic updates included. In case of an update you’ll lost all customizations. So only use the provided sub settings page and add your CSS and custom functions (there’s an extra field for that too
there.Hope that clarifies this a bit. Dave

-
AuthorPosts