Jason Judge

Apologies for late response – I had got unsubscribed from this support forum.

This looks like a bug – thanks for the files – I will use those to test.

Thank you, I will take a look.

Apologies for the late response – I had no idea WP had unsubscribed me from this support forum. It seems to do that randomly.

Interesting one. So the file (which presumably could be anything) would be attached to the post once the post is imported. Or do you mean *only* import files?

Hi. If you could send me a copy of a failing CSV, I’ll take a look and see if there is something that can be fixed. I suspect it will be related to international character sets and BOMs (a Microsoft thing).

[email protected]

• This reply was modified 8 years, 5 months ago by Jason Judge.

Taxonomies are a strange thing in WP, since taxonomy items share underlying values even when they are in different lists. So a category of “Status Black” with a value of “black” is the same underlying value as “Product Colour Black” also with an underlying value of “black”. Bets just to avoid this happening – do not reuse taxonomy values.

Rant out of the way, could you send me an example of CSV that you are trying to import?

Do you have a file you could send me to look at? [email protected]

Do you have any details of which encoding you are using? If you just strip out the BOM (e.g. using Notepad++, by saving without a BOM) does the data import?

It does not take account of the BOM at all at the moment, but it would make sense if it did, so it could import data from a wider variety of sources. For now, convert in an editor as workaround.

For some reason I have not been getting notifications for this plugin, and have just found there are new tickets raised here. I’ll aim to work through them.

I’ll close this now. It won’t work with Storefront, because that plugin does not use the “woo framework” so there is little that can be done about it. Storefront has its own way to add custom fonts.

You could try a lighter colour to get at least the same density in the design.

Try it in typecast:

https://typecast.com/preview/google/Quicksand

The “#” glyph is simply not there for the light (300) version of the Quicksand font. Raise that as a bug with Google – it certainly looks like someone has overlooked it. I think the only way around this in the meantime will be to use a different font.

In theory you could deliberately NOT load the 300 font from Google but still tell the browser to display it with a 300 weight. Some browsers may make a good attempt at lightening the normal (400) font; some may not do it well and some may not even try to. Might be worth trying, but probably not worth the effort as results will not necessarily be consistent.

Or you could try a similar looking character (until the font is fixed) such as ? (Viewdata Square 0x2317) which does seem to work with that font and weight – try out the brilliant https://shapecatcher.com/ site to find unicode characters that look like something you need.

“?” is NOT “#” – try copying from this post. Best of luck!

Hi Joe,

Do you have any examples of a specific font that happens with? Is the expected font actually displaying? Is the # even in the page (checking the source) or could it have been removed from the content by another plugin?

Send me a link to a problem page if you like.

See here for some notes on how to change fonts in the theme:

https://support.woothemes.com/hc/en-us/articles/203105907-How-do-I-change-the-fonts-in-my-theme-

Basically, use the admin screens (which links to the Woo Framework) or do it in CSS (which is low-level manual work – no settings pages for that and so nothing this plugin can do to inject additional fonts into non-existent theme settings pages).

So where in Storefront are you seeing drop-down lists of fonts, if at all?

Looking into Storefront it seems that it does not use the “Woo Framework”. I suspect those files are reserved for premium themes only, while Storefront is designed to be a lot lighter – much less to configure through the admin screens, and more to do through child themes instead.

Let me mull this over this weekend and we can see how easily this plugin can be adapted to Storefront, or even other non-WooThemes themes.

I’ve just upgraded to the Woo Framework 6.2.6 and it is still working for me on my Canvas theme. I’m wondering if Storefront no longer uses – or never did use – the same Woo Framework for its back-end functionality? I’ll upgrade my Canvas theme to see if anything has changed there.

This plugin talks to the Woo Framework, which is a set of libraries that all Woo themes have in common. The error means it is not finding the framework storing its list of fonts in the normal place.