Paul_N

Forgive me for asking but have you pasted your style.css copy into your theme folder correctly?

The delivery notes plugin has a templates folder…

woocommerce-delivery-notes/templates/print-order/style.css

But when putting a copy into your theme there should be no templates folder…

mytheme/woocommerce/print-order/style.css

Is it the ‘quickly change the font’ method that you are using?

Have you tried this method?

How do I customise the look of the invoice and delivery note?

for full control, copy the file style.css from woocommerce-delivery-notes/templates/print-order to yourtheme/woocommerce/print-order and start editing it.

Note: Create the woocommerce and print-order folders if they do not exist. This way your changes won’t be overridden on plugin updates.

I use this method for full design control and it works very well.

Are you running WP-spamshield?

See this…
https://www.ads-software.com/support/topic/update-1904-woocommerce-new-customer-account-checkout-problem

This has fixed the problem for me.
Many thanks for the swift response.

Hi Scott,

I’ve submitted a support request.

Paul

Thank you.

cveronese,

I’ve already encountered css problems like this, in fact I always have to adjust assets/css/frontend.css on each upgrade to ensure my preference that thumbnail arrows are permanently displayed instead of appearing on hover only.

To effect the change you need you would have to add .pp_expand {display:none;!important} to the core file yith-woocommerce-zoom-magnifier/assets/css/frontend.css.

Not ideal but it works.

Personally though I’m holding fire on this upgrade for my live site until the developer responds.

Well the link I gave tells you all about it:

https://yoast.com/wordpress-seo-security-release/

also here:

https://searchengineland.com/yoast-wordpress-seo-plugin-vulnerable-to-hackers-216656?utm_campaign=socialflow&utm_source=twitter&utm_medium=social

But really this should have been announced on the dashboard IMO, in large capitals.

Personally I test all plugins thoroughly before updating so I was very concerned to see an unauthorised update with no explanation to be found.

I’ve been trying to nail the cause of this myself.

I would have expected some sort of notification on the dashboard or something, somewhere. It would have saved me an hour or two of trying to figure out who updated the thing without my say so.

There is a security vulnerability in the Yoast SEO plugin that needed to be fixed urgently so WordPress forced an automatic update.

https://yoast.com/wordpress-seo-security-release/

Issue resolved here, thank you Mike.

https://github.com/woothemes/woocommerce/issues/7679

I see that this behaviour is the result of this ‘fix’

https://github.com/woothemes/woocommerce/issues/7371

I’m not entirely sure I understand the need for this fix, one removes the ratings HTML and yet still requires that a rating be given? am I misunderstanding something here?

This code change stops admin’s ability to reply to a review, it requests that they supply a rating for their own product from within admin, which is impossible.

So at the moment my client cannot respond to any of their customer reviews from within admin.

The problem seems to be with class-wc-comments.php

If I use the Woocommerce 2.2 version of this on my dev site the problem goes away.

Is there a fix needed here?

I can see that it is likely this code that is the reason:

/**
	 * Validate the comment ratings.
	 * @param  array $comment_data
	 * @return array
	 */
	public static function check_comment_rating( $comment_data ) {
		// If posting a comment (not trackback etc) and not logged in
		if ( 'product' === get_post_type( $_POST['comment_post_ID'] ) && empty( $_POST['rating'] ) && '' === $comment_data['comment_type'] && 'yes' === get_option( 'woocommerce_review_rating_required' ) ) {
			wp_die( __( 'Please rate the product.', 'woocommerce' ) );
			exit;
		}

		return $comment_data;
	}

	/**

I’m wary of making any such change to my live site unless someone can confirm it will do no harm.

Good idea, I think I will look into making it a custom plugin, Thanks for the reassurance.

Yes that’s fixed the problem for me, thanks for the prompt response.

I did a little research on this and Yoast and others suggest that this sort of error is a whitespace issue. I did try the standard twentyeleven/thirteen/fourteen themes and had the same error.

https://www.ads-software.com/support/topic/plugin-wordpress-seo-by-yoast-xml-parsing-error-xml-or-text-declaration-not-at-start-of-entity

My local WAMP dev site is WordPress 3.9.1 running twentyfourteen_child theme.

with these plugins:

Bundle Rate Shipping Module for WooCommerce 1.3.5
Easy FancyBox 1.5.5
Facebook Like Box 2.7
jQuery Vertical Accordion Menu 3.1.2
Slideshow 2.2.21
Testimonials by Aihrus 2.19.5.1
Ultimate Tag Cloud Widget 2.7.2
WooCommerce 2.1.9
WooCommerce – Custom Order Statuses 1.0
WooCommerce Menu Cart 2.5.2
WooCommerce Print Invoice & Delivery Note 3.2
WooCommerce Product Add-ons 2.5.5
WooCommerce Sequential Order Numbers 1.3.1
Wordfence Security 5.0.7
WordPress SEO 1.5.3.2
WP-ShowHide 1.00

The live site is currently – WordPress 3.9.1 on a twentyeleven child theme and using the same plugins except that WordPress SEO is version 1.5.2.8 and Woocommerce is version 2.1.8.