Forum Replies Created
-
Posts
-
You might find this plugin useful:
http://wordpress.org/extend/plugins/genesis-widgetized-notfound/
Web: https://wpperform.com or Twitter: @wpperform
We do managed WordPress hosting.
Maybe what came out of this discussion would help?
http://www.studiopress.com/support/showthread.php?t=91645
Web: https://wpperform.com or Twitter: @wpperform
We do managed WordPress hosting.
Try using Nick's Genesis Simple Comments plugin, available in the WP repo.
Web: https://wpperform.com or Twitter: @wpperform
We do managed WordPress hosting.
Around line 226 of your child theme style sheet, for #header .widget-area, add
margin-top: 40px;
to the styling rules. They would then look like:
#header .widget-area {
float: right;
margin-top: 40px;
min-height: 95px;
padding: 25px 0 0;
position: relative;
width: 740px;}
Web: https://wpperform.com or Twitter: @wpperform
We do managed WordPress hosting.
The usual explanation for what you're seeing is either a) you're running a plugin for mobile (e. g., WP Touch) or b) you have redirects on your server (such as in an .htaccess file) that detect a user agent (such as a mobile one) and redirect the URL to the same URL with m. appended to the start of it.
If you know you don't have a mobile plugin, reviewing server redirects would be a good place to start.
Web: https://wpperform.com or Twitter: @wpperform
We do managed WordPress hosting.
If you're referring to resizing images in the media folder to the sizes specified by your child theme, you can use:
http://wordpress.org/extend/plugins/ajax-thumbnail-rebuild/
Web: https://wpperform.com or Twitter: @wpperform
We do managed WordPress hosting.
Seth - For some of these changes, you'll need to edit PHP code on your site. If you're not comfortable doing that, don't. Have a backup and FTP access so you can over-write any bad changes.
1) Find home.php of your CHILD theme and edit line 74 to say 'alignleft' instead of 'alignnone'; that's if you want images aligned left;
Line 74 should be the line for grid_image_class.
if ( function_exists( 'genesis_grid_loop' ) ) {
genesis_grid_loop( array(
'features' => 0,
'feature_image_size' => 'featured',
'feature_image_class' => 'post-image',
'feature_content_limit' => 0,
'grid_image_size' => 0,
'grid_image_class' => 'alignleft',
'grid_content_limit' => 250,
'more' => __( '[Read more]', 'minimum' ),
) );
} else {
genesis_standard_loop();
}2) Take a look at your Genesis settings for content archives. Are you including the featured image? Do you ALSO have the image in the post content? That would produce a duplicate.
3) The size of the thumbnail on the archives is in the drop down setting for Genesis content archives. Adjust it to suit your taste.
Hope that helps.
Web: https://wpperform.com or Twitter: @wpperform
We do managed WordPress hosting.
Here are a few pointers.
Download and activate the Genesis eNews Extended plugin. It's in the WP plugin repo and is slated to replace (but remain a plugin) the eNews widget that's with Genesis. Put the widget in your sidebar where you want it.
If you need help configuring it, just post back.
Web: https://wpperform.com or Twitter: @wpperform
We do managed WordPress hosting.
I'll try. My explanation for the "why" things evolved the way they did is just my educated guess.
Note that wordpress.com, the biggest WP network out there, doesn't run with 'www'. The early history of WP MU (the predecessor name for what is now called WP multisite or a WP network) was developed with with more attention paid to non-www domains, in part because of wordpress.com. As far back as 2006, Matt Mullenweg wrote a plugin to further support non-www domains, so maybe that's his personal preference and that preference impacted WP development.
Around WP 3.0 or so, discussion in the WP community changed to hold that you could setup a network with either www or non-www as the primary site in the network. But from my experience all of the code that could be impacted by that, especially on subdomain installs, wasn't fixed and still isn't fixed.
Here is one example. If you have your network of subdomains set up with 'www', visit Sites->All Sites when signed in as a network admin and search for a site on your network. You can use * as a wildcard. Even try searching for the exact subdomain. WP won't find it, even though it exists. Try the test searching for a site ID, and it will find it. The reason for that search failing to work is because it is searching for yoursubdomain.www.yourdomain.com (which will never be found) instead of yoursubdomain.domain.com (which is how the data is stored). In other words, the 'www' that is there should have been stripped out for the search, but it wasn't. It likely wasn't stripped out (or better yet, checked to see if it had to be stripped out) because of the legacy of WP MS recommending non-www primary domains.
Site search works fine on a network of subdomains with no 'www'. On a big network, being able to search for a site and find it is important. That's just the first thing that comes to mind of something that breaks when you run a WP network with 'www' in the primary domain. You may run a network and never stumble on another one, but changing it down the road is more work than when your network is a relative infant. I've always just stuck with WP installation recommendations (which highly recommended not using 'www') from years past and avoided 'www' so I don't have to change things later.
Web: https://wpperform.com or Twitter: @wpperform
We do managed WordPress hosting.
It might, but doesn't, since it 404's.
Web: https://wpperform.com or Twitter: @wpperform
We do managed WordPress hosting.
I took another look, and I'm not 100% convinced the conflict is with NGG and Genesis Responsive Slider.
Here's the standard demo for Executive 2.0 on our network with the Genesis Responsive Slider and NGG activated. It seems fine.
However, on your site, in IE, it is throwing a javascript error on Line 44 char 4 of shutter-reloaded.js. The error is SCRIPT14: A security problem occurred.
In my test of the link above, I also tried the Shutter effect (Gallery->Options->Effects) but didn't see a problem. You could try changing to a different effect, which then wouldn't load shutter-reloaded.js.
However, given that my test of Executive 2.0 with NGG and Genesis Responsive Slider didn't show a problem, it might be a problem with another plugin. I'd eliminate all other plugins except those 2 and see if the problem exists. If not, I'd add them back 1 by 1 until you break it.
Post back with what you uncover.
Web: https://wpperform.com or Twitter: @wpperform
We do managed WordPress hosting.
Here's what I'm seeing when using IE 10 to simulate IE 8 and 9 in standards mode.
In IE 8 - 10, the home page looks like it does in FF or Chrome except that the direction arrows and slide indicator don't display when the screen width falls below some value. I didn't narrow this down more, but it likely has to do with the responsive CSS of the slider plugin.
I didn't see any evidence of slides not appearing in any browser, so maybe you were able to resolve it. If you're still seeing the error, post back and I'll take another look.
Web: https://wpperform.com or Twitter: @wpperform
We do managed WordPress hosting.
It would be a big mistake to run WP MS with 'www' so you shouldn't try to undo that. Wouldn't it be easier to edit the links in text widgets? If you were really against doing that, you could create re-write rules that would redirect from the 'www' version of the link to the non-www. That would be more work and has slight negative SEO consequences, so you'd be better off to bite the bullet and fix the text widgets to match your current setup.
Web: https://wpperform.com or Twitter: @wpperform
We do managed WordPress hosting.
What's your site? Your version of IE, NGG, and Genesis Responsive Slider? Those details matter, so the more info you provide upfront, the better chance you have of getting good replies.
Web: https://wpperform.com or Twitter: @wpperform
We do managed WordPress hosting.
URL's, unlike email addresses, are case-sensitive. For your login URL, the actual PHP script is on your server in lowercase, so if you don't use lowercase letters, it can't be found. WP saves permalinks in lowercase, even if you attempt to enter an uppercase permalink, so I'm guessing your second example of a URL that involved uppercase characters wasn't one that involved a WP permalink.
That said, your server could have re-write rules that change a URL from one thing to another, and if that change included an uppercase to lowercase conversion, you could enter a URL in uppercase and see it converted - and found - in lowercase. Those rules aren't there by default.
Web: https://wpperform.com or Twitter: @wpperform
We do managed WordPress hosting.
If one buys Premise at the special price, does that then allow purchase of the Pro Plus package at the $209.97 price for an existing customer? Or does the $209.97 price only apply to existing purchasers of Genesis or a StudioPress child theme?
Web: https://wpperform.com or Twitter: @wpperform
We do managed WordPress hosting.