bobbingwide

Hi, there are two things that prevent this from working.

oik-weight-zone-shipping treats ‘/’ characters as delimiters. The latest version ( currently under development ) is stripping them out – so the span end tags gets broken.

But even when that logic has been disabled, WooCommerce is stripping tags since it attaches the sanitize_text_field function to the ‘woocommerce_shipping_rate_label’ filter.

It’s possible to implement a solution for this. Is this something you really need?

Hi Bakkie, I’ve set up your shipping rates in the Single rate weight zone shipping for Woocommerce demo site adding a shipping method called Bakkie.

https://oik-plugins.eu/oik-weight-zone-shipping/sample-oik-weightcountry-shipping-settings/

Note: In this demo site the weight unit is kg.
Add the 1kg Daldal product to your cart ( https://oik-plugins.eu/oik-weight-zone-shipping/product/1kg-daldal/ ) and adjust the quantity to achieve the desired weight.

• For shipping to the UK, up to 15kg, you’ll see three different rates.
• Between 16 and 19kg it’ll just be fee 1: ￡1.30
• 20kg – 49kg it’s fee: ￡2.05
• etc

Can you let me know what other Woo related plugins you have activated?

Hi Enrique. Can you not simply increase the rate by the percentage?
Or do you mean a percentage of the total cost of the items in the cart?

Just to confirm that this was fixed a long time ago, in v1.14.3
v1.14.4 also contains this fix.

I’ve completed my analysis of the problem I had. I can confirm that the fatal error I was seeing was exacerbated by code in my own plugin. Changing that plugin to deal with incomplete objects ( __PHP_Incomplete_Class Object ) allowed the process to run to completion. See https://github.com/bobbingwide/oik-bwtrace/issues/56 for details.

This could be a similar problem…
https://github.com/deliciousbrains/wp-migrate-db/issues/70

I had a similar problem with /wp-json/wp/v2/bigram/?filter[s-letter]=H

where bigram is a custom post type and s-letter is a custom taxonomy for the post type

The REST API team meeting notes at

REST API Team Meeting Notes, 2016-10-17

includes the following

The ?filter query parameter will be removed from the REST API plugin prior to core merge, a breaking change that improves the consistency of querying the API and eliminates a set of parameters that could introduce backwards compatibility issues were they to be committed to WordPress core. A separate plugin will be published to reinstate the filter parameter on a strictly opt-in basis.

My solution was to change the request to use the taxonomy term directly.
/wp-json/wp/v2/bigram/?s-letter=1729

where 1729 is the term_id for the term with a name of ‘H’, slug ‘h’.

I deactivated the WP REST API plugin.
The overall result was significantly better.

I didn’t try the rest-filter plugin.

Hi, I’ll look into the Order Email question.

Hi, what value for Tax Status have you chosen?
If you use a value of None then you can include the tax in your shipping costs.
If you use a value of Taxable then tax is calculated against the shipping costs.

Hi, I had the same problem and traced the response from PayPal.
It would appear that while the text of the message says:

You don’t have permission to access “https://www.paypal.com/cgi-bin/webscr” on this server.
Reference #18.106cd417.1481310868.8bf3e97

the http is a red herring.
Output from http_api_debug shows that the URL still starts with https.

Here’s an example using oik-css to write the CSS.
https://www.oik-plugins.com/shortcode_example/styling-drop-caps-div-shortcodes/

Hi, it depends on how good your CSS is.
To style a dropcap you just need some CSS. e.g.

div.dropcap:first-letter { 
        float: left; 
        color: #903; 
        font-size: 75px; 
        line-height: 60px; 
        padding-top: 4px; 
        padding-right: 8px; 
        padding-left: 3px; 
        font-family: Georgia;
 }

A variation of the CSS3 from https://css-tricks.com/snippets/css/drop-caps/

Then you can use the [div] and [ediv] shortcodes
e.g.

[div class=dropcap]The first letter will be styled as a dropcap.[ediv]

Note: You need to pair [div] and [ediv]. This is to allow shortcode nesting.

Let me know if you need more.

Hi, I’ve developed a fix for the problem in v3.1.1
For details see https://github.com/bobbingwide/oik/issues/60

Hi, would you care to specify some more requirements.

Thanks for reporting that. I’m having difficulty reproducing the problem. Can you confirm where you’re seeing this and what network page you’re looking at. Do you have other oik plugins installed?