Forum Replies Created
-
AuthorPosts
-
devongroupMember
Yes all single posts appear with blog/ in front, then making sure all CPT's and TAX's are registered w/
'with_front' => false),
so blog does not appear in the URL for these.Seems to be working thanks I would say it is resolved.
devongroupMemberAs a side note I was worried changing the permalink structure would change general page url's as well for example site.com/page and make it site.com/blog/page but this seems to only change posts and custom post types which is a good thing in my case.
devongroupMemberok so you are saying http://www.site.com/blog/%postname%
I did this and it works great but I had custom post type and taxonomies that it added blog/ in front of too so after research when registering a CPT or TAX for the rewrite(url) I did:
'rewrite' => array( 'slug' => 'custom_post_type_name/', 'with_front' => false),
and it takes out blog bc/ it goes back to http://www.site.com/ for example http://www.site.com/promotions/
Thanks for this! Is this how you would accomplish this or do you have a simpler approach?
devongroupMemberStill searching for a solution!
devongroupMemberit was something the previous developer did with an htaccess file, I just removed the code, it was not the wpsupercache plugin.
devongroupMemberI worked with the studiopress team and it seems some supercaching I had setup was not updating my view of the admin, once I refreshed the caching it is now showing, so simply adding ‘genesis-scripts’ to the support line when registering a CPT does work!
devongroupMemberAnyone ever come across a solution to add the post info (author, date, etc.) to pages in the search results?
Thanks!
devongroupMemberThanks for this, had to complete a different assignment, I hope to rewrite the way my scripts are loaded following your advice, I will get back to you with the results. I do have a question, this is the first time seeing
$js_loc = CHILD_URL.'/lib/js/';
Can you explain or lead me to an article which does, thanks so much.
devongroupMemberUsing a not so satisfying method I did get the script into the head and to interact with IE8 correctly, would you be able to give me some tips on how to best enqueue scripts in wordpress so I can place scripts in both the header (close to the bottom if not the bottom) and also into the footer. Here was the kind of hack but it is good to know it atleast works, and heck IE8 better be on it's way out anyways. I sent Nick from studiopress and email about this to see if the team working on Genesis could resolve the issue.
add_action('wp_head', 'company_head_content');
function company_head_content() { ?>
<script src="/wp-content/themes/company/lib/js/modernizr-2.6.2-respond-1.1.0.min.js"></script>
<?php }devongroupMemberSorry I think your single quotes copied incorrectly as it just errors when I try your code. Below is how I am working with it. I have been informed that modernizer running in the head is having issues with the Genesis framework and support is not given as it is a 3rd party script.
Are you not having the same issue as I am if you place modernizr.js in the head?
if (! is_admin() ) {
wp_register_script( 'modernizr', CHILD_URL.'/lib/js/modernizr-2.6.2-respond-1.1.0.min.js', array(), '1.1.0', false );
wp_enqueue_script( 'modernizr' );
}devongroupMemberUnderstood and much appreciated. Hate to add more than needed to a forum post but for an ambiguous topic I have clear answers.
devongroupMemberNick thanks this clears the fog. Rebuild a stylesheet ok with me, but this may be a premature question: Will the hooks (I suppose actions) be the same. I would hope Studiopress considers this a fair question knowing to update a framework anything can change ( especially due to a reliance on the wordpress core) and this is where the support of previous versions increases the difficulty.
devongroupMemberI have a local(testing) version running so when 2.0 comes out I will locally disable my HTML5_functions file and see what I can hook onto as far as css/html is concerned and take it from there. Is that the gist of what your comment was meaning?
devongroupMemberAgreed a "switch" at this point in the game to HTML 5 must be a terribly difficult task especially when considering Studiopress/Genesis theme is trying to support past versions in the upcoming 2.0 version. Nick can you confirm the method above for removing actions and then adding back in the HTML5 actions will work seamlessly with 2.o? To dig deeper I have a separate HTML5_functions file, so if 2.0 is HTML5 compliant we should be able to remove these actions that create the Header and Footer (also aside) as 2.0 should include these and if we would like to change meta such as viewport and chomeframe settings ( I realize this may truly not be meta but it gives us something to hook onto) , as well as load our own specific stylesheets such as normalize.css we should be able to just add actions to genesis_meta and genesis_load_stylesheet. I hope I touched all bases here.
Summary: This is a time of change in the web world, we are all in the same boat, and apparently this boat has not yet charted a specific course.
devongroupMemberSorry All I know that is a lengthy forum post and I will open a pastebin in the future. At our company we worked out a filter for the comment form that works with WordPress 3.5 and Genesis 1.9.1
After some research it seems that filtering the comment args and not comment fields is the preferred approach.
* Please if anyone sees any downside to the below code please respond with feedback. Also I want to be able to tab from name fields to the submit button but currently it just tabs to the top of the page after the website field. If there is a way to filter the submit button code so I can add a tab index using the code below please let me know!
Working Code:
/** Edit comments form text **/
function modified_comment_form_args($args) {
$args['title_reply'] = 'Leave a Comment / Join in the Discussion';
$args['comment_notes_before'] = ' <p class="comment-policy">All comments are moderated and will be displayed upon approval</p>';$args['fields']['author'] = '<p class="comment-form-author">' .
'<input id="author" class="required" name="author" type="text" value="' . esc_attr( $commenter['comment_author'] ) . '" size="30" tabindex="1"' . $aria_req . ' />' .
'<label for="author">' . __( 'Name', 'genesis' ) . '<span class="frm_required"> *</span>'. '</label> ' .
( $req ? '<span class="required">*</span>' : '' ) .
'</p><!-- #form-section-author .form-section -->';$args['fields']['email'] = '<p class="comment-form-email">' .
'<input id="email" class="required email" name="email" type="text" value="' . esc_attr( $commenter['comment_author_email'] ) . '" size="30" tabindex="2"' . $aria_req . ' />' .
'<label for="email">' . __( 'Email:', 'genesis' ) . '<span class="frm_required"> *</span>' . '</label> ' .
( $req ? '<span class="required">*</span>' : '' ) .
'</p><!-- #form-section-email .form-section -->';$args['comment_field'] = '<p class="comment-form-comment">' .
'<textarea class="required" id="comment" name="comment" cols="45" rows="8" tabindex="4" aria-required="true"></textarea>' .
'<label for="comment">' . __( 'Comments' . '<span class="frm_required"> *</span>', 'genesis' ) . '</label>' .
'</p><!-- #form-section-comment .form-section -->';
return $args;
}
add_filter('genesis_comment_form_args', 'modified_comment_form_args'); -
AuthorPosts