Forum Replies Created
-
AuthorPosts
-
detroitwidgetMember
You might try a different view:
Chrome > Inspect > Elements
You can also "unminify" the CSS:
July 15, 2016 at 10:51 am in reply to: Remove darkening gradient effect on Altitude background image #189540detroitwidgetMemberMarcia,
On or about CSS line 1316, change this:
.front-page-1 .image-section { padding-top: 75px; }
To this:
.front-page-1 .image-section { padding-top: 75px; background-image: none; }
This won't remove your background image, but should override the background gradient overlay.
Example here:
I hope this helps.
detroitwidgetMemberJohn,
You're not the first person to get tripped up by Genesis page templates. I suggest you read the following article. It's long, but well worth reading if you plan on doing any WordPress development using Genesis:
http://www.billerickson.net/dont-use-genesis-blog-template/
Also, the WordPress Template Hierarchy:
https://developer.wordpress.org/themes/basics/template-hierarchy/
For reference, the development site below uses Centric Pro and was configured as follows:
Settings / Reading / Front page displays: A static page (select below)
Front page: Home (new page, default template)
Posts page: News (new page, default template)Appearance / Widgets: All Home page widgets configured per the Centric Pro theme setup instructions.
A simple CSS rule removes the page title from the new Home page:
.home .page-title {
display: none;
}Note: If no widget areas are active in any of the front page specific widget areas, a blog-style front page will be displayed. If you wish to use a static page set under Settings > Reading for your front page, do not add widgets to the front page widget areas, since doing this will override the static page. (In the case above, that's the exact behavior we are counting on.)
I hope this helps.
detroitwidgetMemberJohn,
You're not the first person to get tripped up by Genesis page templates. And you're not doing anything wrong -- What you describe is normal Centric Pro behavior.
I suggest you read the following article. It's long, but worth reading:
http://www.billerickson.net/dont-use-genesis-blog-template/
I hope this helps.
detroitwidgetMemberThe following is a pretty accurate overview:
https://cometcache.com/kb-article/why-doesnt-comet-cache-remove-query-strings-from-static-resources/
detroitwidgetMemberI'd be cautious about removing version number query strings until you have a complete understanding of their function, and the consequence of their removal.
detroitwidgetMemberApparently there isn't one, except at the top of the Community Forums landing page. Real helpful. As is the dinky font size.
January 24, 2016 at 2:02 pm in reply to: Strange page loading issues when Genesis framework is active #177376detroitwidgetMemberHave you tried a page speed analysis?
By the way, your photography is superb.
detroitwidgetMemberHello Robin,
I've had good luck with the TinyMCE Advanced plugin:
https://wordpress.org/plugins/tinymce-advanced/
Cheers.
detroitwidgetMemberYou're right. It is horrible.
Even worse is that paying members are not notified via email about upcoming updates, update issues, and update solutions. At the very least, you would think that they would diligently convey this information via the StudioPress blog.
Apparently, we're supposed to fumble around on Facebook looking for the GenesisWP group, request to become a member, then wait for Nathan Rice to provide a short-term fix that will soon be replaced by another update.
Ugh.
December 10, 2015 at 1:56 pm in reply to: Genesis Admin .postbox is messed up after 4.4 update #173470detroitwidgetMemberI can confirm that this is indeed a problem. Does anyone have an expectation as to when it will be fixed?
October 20, 2015 at 7:11 pm in reply to: Background image in AgentPress Pro not appearing for secondary domain names #168632detroitwidgetMemberAre you using a plugin called Background Manager?
If so, it could be choking on your alias and refusing to load properly.
Also, that plugin has been deprecated by its author -- You might consider a different solution.
(Note: If not configured correctly, domain forwards and aliases can cause a lot of problems. Not to mention a possible negative impact on SEO if you're not very careful.)
Cheers.
detroitwidgetMemberThe border is currently applied to the anchor (a), not the image (img).
Try:
.aligncenter a { border-bottom: none; }
Cheers.
October 8, 2015 at 4:58 pm in reply to: Move Header Titles || Remove Header Title from homepage #167700detroitwidgetMemberOops. This might be better:
.home .entry-title { font-size: 36px; font-size: 3.6rem; display: none; }
October 8, 2015 at 4:11 pm in reply to: Move Header Titles || Remove Header Title from homepage #167697detroitwidgetMemberIn your style.css file, try:
.entry-title { font-size: 36px; font-size: 3.6rem; display: none; }
Note the addition of "display: none;".
detroitwidgetMemberTry changing "background-color" to "border-color".
September 16, 2015 at 8:49 am in reply to: Font in Navigation Different on Firefox and Chrome #165754detroitwidgetMemberAngela,
On or about line 1043 of the Altitude Pro default style sheet (style.css), change this:
.genesis-nav-menu > .menu-item > a { text-transform: uppercase; }
To this:
.genesis-nav-menu > .menu-item > a { text-transform: uppercase; -webkit-font-smoothing: subpixel-antialiased; }
If you're feeling brave you can also experiment with the default body settings around line 141. Deleting or changing the WebKit font smoothing value may generate some interesting results:
body { background-color: #fff; color: #000; font-family: "Ek Mukta", sans-serif; font-size: 20px; font-weight: 200; line-height: 1.5; -webkit-font-smoothing: antialiased; }
Consistent font rendering across all browsers is always a challenge. And font smoothing is a notoriously unpredictable property. As Dave suggested, my first approach is to play with the font weight and font size properties.
("WebKit" is just the name of the page rendering engine used by the Safari web browser. A modified version of WebKit is also used in Google Chrome; hence these two browsers frequently exhibit similar behavioral "quirks.")
I hope this helps.
Phil
September 14, 2015 at 9:44 am in reply to: Font in Navigation Different on Firefox and Chrome #165437detroitwidgetMemberHi Angela,
Ditto Dave's suggestions above.
I've also had luck on occasion by adding one of the following CSS declarations:
-webkit-font-smoothing: antialiased;
-webkit-font-smoothing: subpixel-antialiased;I hope this helps.
detroitwidgetMemberHi Guys,
For what it's worth, I've spent considerable time with both Parallax Pro and Altitude Pro. In the end I chose Altitude because it was just a better fit for my project.
Keep in mind that the parallax background image "look" was hot about a year ago, but it's current popularity is declining rapidly. Also, it can be a real challenge to find suitable images that benefit from the effect.
Though lacking the parallax element, the Altitude theme does have an interesting "scroll fade" feature for the home page background images.
I hope this helps. Cheers.
detroitwidgetMemberGreat tool. Thanks for sharing Victor.
-
AuthorPosts