codeAddict
Forum Replies Created
-
Forum: Reviews
In reply to: [Gutenberg] WordPress Gives Zero FsCompletely agree with Julia on this
Forum: Reviews
In reply to: [Gutenberg] Just terribleI hear ya! Its such a shame.
None of this would be a major issue if they had kept it as an optional plugin.
My gut tells me this will change…it has to. It would be insane if they completely ignored all the negative feedback, and there is loads by the looks of it.
Forum: Plugins
In reply to: [WooCommerce Multiple Free Gift] more than one condition removes free giftsIm having the same problem with the Pro version (Sounds similar anyway). Initially i thought it was the way i was setting it up, but im trying to have multiple conditions running at the same time.
For example:
1. Buy a product from category X and get Free Product A.
2. Spend over £30 get Free Product B.It seems that it adds one of the conditions only, normally the condition thats met first. So if i have spent over £30, the correct free gifts are added to the cart, but when i then add a product from category X it wont add in the free gift for that condition?
It would be great to get an answer on this if possible, running out of ideas ;o)
Forum: Plugins
In reply to: [Contact Form 7] date format in mailtagsThanks buzztone, although i am aware that the date tag has only limited support, i was testing using a browser that does. My apologies though…i completely missed the bit that said you could only have YYYY-MM-DD format using this html5 tag. I just assumed that they wouldn’t be so daft as to only have one date format?!
Forum: Plugins
In reply to: [Contact Form 7] date format in mailtagsApologies, i know this was marked as resolved… but nothing seems to work for me.
I am trying to get the date format as dd-mm-yyyy in the email that is received (showing correctly on the web form as dd-mm-yyyy).
I have changed the general wordpress settings and used “date format” in the shortcode but it still shows as yyyy-mm-dd in the email we get?
Cheers ;o)
Forum: Themes and Templates
In reply to: CSS: div#comments shows when comments are offI found a simple work round for this. Just update your comments.php file to the following. All it does is move the div#comments into the if statement. This will stop the div#comments showing when comments are turned off ;o)
<?php /** * The template for displaying Comments. * * The area of the page that contains both current comments * and the comment form. The actual display of comments is * handled by a callback to twentyten_comment which is * located in the functions.php file. * * @package WordPress * @subpackage Twenty_Ten * @since Twenty Ten 1.0 */ ?> <?php if ( post_password_required() ) : ?> <div id="comments"> <p class="nopassword"><?php _e( 'This post is password protected. Enter the password to view any comments.', 'twentyten' ); ?></p> <?php /* Stop the rest of comments.php from being processed, * but don't kill the script entirely -- we still have * to fully load the template. */ return; endif; ?> <?php // You can start editing here -- including this comment! ?> <?php if ( have_comments() ) : ?> <div id="comments"> <h3 id="comments-title"><?php printf( _n( 'One Response to %2$s', '%1$s Responses to %2$s', get_comments_number(), 'twentyten' ), number_format_i18n( get_comments_number() ), '<em>' . get_the_title() . '</em>' ); ?></h3> <?php if ( get_comment_pages_count() > 1 && get_option( 'page_comments' ) ) : // Are there comments to navigate through? ?> <div class="navigation"> <div class="nav-previous"><?php previous_comments_link( __( '<span class="meta-nav">←</span> Older Comments', 'twentyten' ) ); ?></div> <div class="nav-next"><?php next_comments_link( __( 'Newer Comments <span class="meta-nav">→</span>', 'twentyten' ) ); ?></div> </div> <!-- .navigation --> <?php endif; // check for comment navigation ?> <ol class="commentlist"> <?php /* Loop through and list the comments. Tell wp_list_comments() * to use twentyten_comment() to format the comments. * If you want to overload this in a child theme then you can * define twentyten_comment() and that will be used instead. * See twentyten_comment() in twentyten/functions.php for more. */ wp_list_comments( array( 'callback' => 'twentyten_comment' ) ); ?> </ol> <?php if ( get_comment_pages_count() > 1 && get_option( 'page_comments' ) ) : // Are there comments to navigate through? ?> <div class="navigation"> <div class="nav-previous"><?php previous_comments_link( __( '<span class="meta-nav">←</span> Older Comments', 'twentyten' ) ); ?></div> <div class="nav-next"><?php next_comments_link( __( 'Newer Comments <span class="meta-nav">→</span>', 'twentyten' ) ); ?></div> </div><!-- .navigation --> <?php endif; // check for comment navigation ?> </div><!-- #comments --> <?php else : // or, if we don't have comments: /* If there are no comments and comments are closed, * let's leave a little note, shall we? */ if ( ! comments_open() ) : ?> <p class="nocomments"><?php _e( 'Comments are closed.', 'twentyten' ); ?></p> <?php endif; // end ! comments_open() ?> <?php endif; // end have_comments() ?> <?php comment_form(); ?>