Forum Replies Created
-
Posts
-
Hi Brian!
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)
Hi Nick!
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 🙂
You can also use the GenesisFinder to search in lots of public Genesis resources:
http://genesisfinder.com/
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?
Hi there!
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 🙂
Hi!
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!
Hi there!
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 🙂
Hi there!
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.
Hi Stefano!
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.Example:
/** 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.
-Dave 🙂
I am suggesting to set the height of these both selectors to 200px -- currently you have 240px.
#title-area #title {
height: 200px;
}and
#title-area #title a {
height: 200px;
}Since you have already a height value, just go to your style.css and test yourself 🙂
Good luck!
Hi there!
Just tested with Firefox 18 on Ubuntu Linux.
In Firebug I could see that your header logo image is too high and therefore overlapping the Nav Menu in this left area. If you would adjust the height of the logo image/header then the Nav will work properly.
My "Genesis Layout Extras" plugin does - just like the name says - offer extended layout settings. It does nothing with replacing sidebars or such.
Yeah, "Genesis Simple Sidebars" plugin is what is needed for the solution here!
You could do the following:
1) number of posts on the first page:
Is WordPress setting: "Settings > Reading" change it there!2) have posts appear as excerpts in the archives:
- not possible with Theme Settings!
- you could try this plugin, which makes archive widgetized so you could use Genesis Featured widget or other stuff: http://wordpress.org/extend/plugins/genesis-widgetized-archive/Hope that helps a bit 🙂
-Dave.
Great!
Please make a backup of your functions.php and home.php first! (Always better to have 🙂
Then add these pieces of code to the files:
The first part goes into the home.php file, at the bottom but BEFORE the closing "genesis();".
The second part goes into the functions.php, also best at the bottom.
For both, don't copy the beginning "< ?php" lines!!
What it does: it first registers a new widget area in your functions.php, then in your home.php it removes the content loop, replaces with widget stuff, but only if the area has active widgets.
I hope this helps. It could be that you have to make a few CSS minor fixes but just try if it works for you.
-Dave 🙂
Does she use a content limit -- it's on the same setting, she could leave that field blank -- then Genesis will display the full post content.
Or maybe she's having another plugin that modifies the content length or excerpt on blog and/or content archives?
I could not see any parameter in that child theme's code that has anything to do with excerpt/content limit output, so it has to something with her Genesis or WP or third-party plugin settings...
Ok, I just tested a piece of code for you, on my install it works great:
---> goes into functions.php --- best at the bottom, don't include the beginning line "< ?php" !
It's also safe if you deactivate the Co-Authors plugin! To modify your byline output you have to modify the parts on the line with "$post_info = ..." etc. be careful with the syntax though. A backup of your functions.php goes a long way 🙂
Hope that helps, Dave 🙂
@varickdesign
Sorry, no, I am just an unpaid volunteer community moderator, not StudioPress staff. here. But if you get a respond from support just point them to this thread here 🙂Thanks, Dave 🙂
Ok, thanks for your feedback, I now understand what's going on 🙂
The "issue" is that WordPress differentiates between the state "is_home()" (served via a file home.php) and "is_font_page()" when setting a regular page as the home page.
I see two alternatives to get what you want:
Using the packaged "home.php" and make it's regular content (in that case the "loop") widgetized so you could place in anything you want.Or you could re-add the stuff for the top area from the home.php to your functions.php and make a conditional statement to only do that for a page ID --- just for that page ID that you before set up as static homepage.
Both should keep the "header / top" stuff intact.
Personally I would go the "widget" way. But it's up to you. I could help with the code snippets if you want.
You should open a support ticket for the old download -- and maybe also for these other issues!
As for your style issues:
Could you please give an URL for your site?
Before Genesis 1.9 the loading of stylesheets was not done via the official, standard WordPress way! This was corrected with v1.9.x - finally!Does your child theme folder have spaces in it?
Do you load custom stylesheets - maybe you should adjust the loading priority.What child theme are you using?