Peter Brock
Forum Replies Created
-
By the way, thanks for the help. I don’t know if what you suggested works because I found joy in a copy of an older Connections version which I assume was customized (and I overwrote when updating). So not perfect but it works.
Ummm, I forgot to change MY_PASSWORD to my password. Hope my goof helps someone!
Adam1567, I tried your modification to password-protected.php but unfortunately I couldn’t make it work.
I pasted your code according the instructions but I am not sure if I placed it correctly.
Can you please copy the code starting at line 299 or from
function maybe_show_login
down to the next few lines of orginal code? If I can see the neighboring code surrounding your modification, that would really help.Forum: Plugins
In reply to: [WooCommerce] Password confirmation in woocommerce 2.1.x releaseThank you, ewroman. Your code solves my problem. I have my password confirmation field back.
Forum: Plugins
In reply to: [WooCommerce] Password confirmation in woocommerce 2.1.x releaseIn previous versions, this code added to functions.php created a password confirmation field.
add_filter( 'woocommerce_checkout_fields', 'custom_checkout_fields' ); function custom_checkout_fields( $fields ) { $fields['account']['account_password']['label'] = 'Choose a password'; $fields['account']['account_password']['class'] = 'form-row-first'; $fields['account']['account_password-2']['class'] = 'form-row-last'; $fields['account']['account_password-2']['placeholder'] = 'Confirm password'; return $fields; }
Alas, it no longer works. In 2.1 it messes with checkout in a fatal way and I had to comment it out.
I don’t know what’s wrong or why there is a conflict.
Suggestions welcome.
Forum: Plugins
In reply to: [WooCommerce] Custom order fields changed in WooCommerce 2.1Thank you harpo1984. You saved the day. My order details pane came back to life with your new code.
However, I still had trouble with the last function. The Member Number label in the order details pane was there, but the actual number was missing. To fix that, I replaced this piece of code:
function my_custom_checkout_field_display_admin_order_meta($order){ echo '<p><strong>'.__('Trade Account No').':</strong> ' . $order->MyField. '</p>'; }
with this:
function my_custom_checkout_field_display_admin_order_meta($order){ echo '<p><strong>'.__('Member Number').':</strong> ' . get_post_meta( $order->id, 'Member Number', true ). '</p>'; }
Obrigado to Gabriel Reguly for the solution.
Forum: Plugins
In reply to: [WooCommerce] Custom order fields changed in WooCommerce 2.1I realize this topic was resolved, but not for me or harpo1984.
I have edited my code to to replace
$order->order_custom_fields
with$order->meta_key_name
but I still don’t see my custom fields on the order page or in the admin email.The fields look fine in checkout.
Forum: Plugins
In reply to: [Page Meta] Extra code appearsThanks Steve. I could not duplicate the problem in the search results.
I must have had double vision when I saw two entries.
I will try Page Meta again on another site. Your design approach makes good sense to me.
Forum: Plugins
In reply to: [Page Meta] Extra code appearsThanks Steve. I installed the plugin yesterday from the admin panel. i seem to recall seeing two entries for Page Meta when looking for it.
The theme is Primo WP, with Easy Translation Manager installed. It could well be a plugin conflict.
As an aside, I got used to the page meta that Justin Tadlock made available for his Hybrid theme. Your plugin looked like a good replacement for themes that lacked it. I didn’t want anything bloated or baffling like so many SEO plugins appear to be.
Can you recommend any to me?
My widgets also disappeared after updating.
In addition, my custom CSS for
.srp-widget-title
stopped working because the selector is now.srp-post-title.
Another selector that changed was#wdg_specialrecentposts
. It’s now#wdg_specialrecentpostsfree
.The name of this plugin is too long now to fit in the WP Settings flyout. I would appreciate not seeing the words “FREE Edition”. (I know that already.)
Thanks.
Forum: Fixing WordPress
In reply to: Backing Up Your Database with phpMyAdmin 3.4.x interfaceI agree with Cambo. I’ve been at a loss trying to find any help with the new phpMyAdmin interface.
I hope this knowledge gap doesn’t mean people are ignoring their backup chores.
Any help appreciated. I’m so tempted to leave it set at the default ‘quick’.
Me too. The next/prev overlays are missing but I can advance the slides or go back by clicking in the usual places. Please fix this soon though.
Forum: Fixing WordPress
In reply to: 3.3 HTML editor now uses monospaced fontThank you, fodden and clnewbill. The HTML editor has been restored to its readable self.
Ipstenu, I must have installed your plugin incorrectly. I put it in the regular plugins folder.
Forum: Fixing WordPress
In reply to: 3.3 HTML editor now uses monospaced fontI noticed the change too. For WP 3.2 I changed mine to Verdana with a fix by Justin Tadlock. Now 3.3 has done something to undo the fix, and the monospaced font is back.
No luck with Ipstenu’s plugin. (I tried…fatal error).
Thanks be to TheNIghtRider. The space trick worked for me. I put a space in the first field to defeat the default. Then I started with a space in second field, followed by “of”.
Now I get “1 of 3”.