Forum Replies Created
Just updated the plugin to version 1.1.0 http://wordpress.org/extend/plugins/genesis-extra-settings-transporter/
- added a few more plugins & child themes for support
- added/ improved help text info, also in plugin's readme
Thanks all! 🙂
January 29, 2013 at 9:20 am in reply to: Balance Theme: display featured left & right widgets sitewide #15970
I also took the code from http://pastie.org/5850228 into a "Balance" test install and placed at the bottom of functions.php and it was working immediately!
Logically all is ok with the code, so there could be something other in your install beside the syntax that is conflicting? Maybe you have other code snippets that hook in via the hook "genesis_after_content"?
Hope this helps, Dave 🙂
To add another response to the actual technical issue:
I just oversaw the source code of this plugin and IMHO there's a bug with the "order" setting option not being set, "order" means "ascending" or "descending" according to WordPress codex. The option setting for "orderby" seems all correct (that's the drop-down in the slider admin settings). In my opinion the issue herein lies this way that the order has to be enforced with the "order" option.
I'll just ping the developer...
Have you posted in the plugin's support forum yet? http://wordpress.org/support/plugin/genesis-responsive-slider
And, regarding your feedback to StudioPress, I'll suggest creating a support ticket!
Mmh, you know what? I see your buttons and the CSS seems to apply, at least I see it in Firefox 18 with Firebug inspector. If I for example disable the float for Twitter in Firebug I see changes...?
If something is not applying maybe add "!important" to the CSS values. Or, have you any cache plugin active in your install? Or any browser cache issues?
(I hope I understood your issues correct)
Thanks for the feedback!
The issue seems to be still there: it seems to happen especially when I am open a topic from the no-replies view or from a forum search. I open the topic into a new browser tab, then answer, then I get the 404...
If I go to topics with the forums hierarchy all seems to work (now).
I know it's strange but maybe you'll find out something more. If not; I could live with that, as long as no functionality itself is "broken".
Thanks for your hard work, Dave 🙂
Could you please give an URL to your site?
Also, I couldn't found any "shiba widget plugin" on WordPress.org plugin repository. Where did you have that plugin from, could please give any more details about it?
Sorry, how should we know your code snippet, we don't have any magic balls here 🙂
You won't have another chance as going through your functions.php (or anywhere else) and find out what you've placed in at some time.
If you found the code, do the following:
- backup your functions.php file (or the file the code is in)
- remove the code snippet
Only use the "Custom CSS" box in Prose --- it's like the "style.css" for THAT child theme. Adjustments to the actual style.css of Prose will overridden on updates!
Your snippet above should work. Just add it and save. Then go to the "Design Settings" at the very end and in the last meta box disable the "Minify", save and your stuff should be there. After your additions in Custom CSS the Minify should work again just enable.
Hope that helps, Dave 🙂
No the variable you should keep intact otherwise things break!
You only need to adjust this
'http://www.mydomain.com/wp-content/images/favicon.ico'to your needs. Just change the URL with full path to the favicon graphic in your project. Please keep the single quote at the beginning and the end intact. Then it should all work.
The code snippet goes into the functions.php of your child theme -- best placed at the bottom. Please make a backup of that file BEFORE any additions!
There is no other way of doing it as you've already found on this tutorial: http://pippinsplugins.com/add-custom-image-sizes-to-media-uploader/ 🙂
I am also using this approach on my site and it's working great! I just did make you a code snippet which you can use for Genesis child themes. Please note: make a backup of your functions.php file before (always best practice, hehe!). Then add this piece of code into the functions.php file of the child, should go at the bottom. Please DON'T add the beginning line where it says "< ? php" ok?
the 2 lines will add 2 new entries to the drop-down field in the uploader. Just add as many lines to this function as you need. Where the ID in the $sizes variable always is the ID of the added image size, so this has to be the same as in add_image_size:
add_image_size( 'mini120', 120, 120, TRUE );---> then the ID is "mini120". Ok? 🙂
For the Label just add a name so you could recognize it later when uploading -- for me this is very important or for clients so they know easily what it means.
I hope that helps, Dave 🙂
Since I am not from StudioPress staff and therefore I cannot (and will not) speak for themselves!
However, based on my experience and what StudioPress said here and there I suspect that something from the things you suggested will happen. StudioPress might even more simplify things on the base foundation and release any enhanced functionality as plugins. Personally, I really really like that way, as it is also the WordPress way of doing things: layout & design & styling belongs into the theme (most of) and most functionality should go in plugins, as functionality should work with any theme (mostly...).
StudioPress went that path already with AgentPress 2.0+ as the Listings functionality is in a plugin now, also their Sliders are now plugins -- the mentioned plugins saw many more updates then the child themes usually get.
The "App Themes" company does awesome things, in my opinion, but having all their stuff within a theme, really locks them and you as a user in! And that's my problem with them. If they would do their great products as high quality plugins I would expect them to have even more succes...?!
I would suggest to re-think your projects: take a high quality product from StudioPress - but not overbloated! - and then adjust your project with the right selection of high quality plugins to your needs. Do customizations with a functionality plugin at best and I believe you will have only a few issues if you ever want to switch (child) themes at any time, if you will have issues at all with that approach.
January 21, 2013 at 1:14 am in reply to: How to create a translation for a new child theme? #13424
Good topic, hehe 🙂
You're already on the right path!
You need to add the loading function for the textdomain just right after Genesis init function in child theme functions.php -- load it early before any strings are defined in child theme, that's best practice.
/** Set Localization (do not remove) */
load_child_theme_textdomain( 'your-unique-textdomain', apply_filters( 'child_theme_textdomain', get_stylesheet_directory() . '/languages', 'your-unique-textdomain' ) );
--> as you can see here's already the path for the lang files defined, "/languages/" sub folder within child theme folder -- also best practice but you can use any path within child theme of course 🙂
Actual lang files have the convention to only be named with the locale for themes & child themes, so for example: it_IT.mo and it_IT.po for Italian language. WP actually only needs the binary .mo file but it's best practice to also upload the .po file so you could edit it anytime you need it.
As for the adding of the textdomain and Gettext syntax you did all right --- just remember to only use one unique textdomain for your child theme. Best practice here is to use the theme slug as the textdomain string. Do not use variables or constants here as this is not right here.
If you did all the above you can then scan your child theme files with Poedit Editor to create a .pot file and then open the .pot catalog and create a .po file of it. Tip: enable "Create .mo file on saving" in Poedit settings so every time you hit save it creates/updates the actual .mo file.
I hope that helps.