cdonner

Some problem with the Give plugin. Cannot import donations anymore.

Ditto. CSV import of donations no longer works.
The “Disable Real MIME Check” plugin allowed me to work around this, but it needs to be deactivated after each use, so not a real solution.

• This reply was modified 6 years, 2 months ago by cdonner. Reason: was wrong about what caused the issue

senseicorner, were you ever able to figure this out? I have the very same problem.

You are missing a bunch of closing </label> tags.

The Kaffeesatz UltraLight font is a barely legible on any background, even if you increase the font size. I do like the font, but I had to replace it with the Light version. You can do that by downloading the font files from the font website of your choice, placing them (for example) into the /fonts subfolder of your child theme, and putting the following into your child theme’s style.css:

@font-face {
font-family: ‘kaffeesatzthin’;
src: url(‘fonts/YanoneKaffeesatz-Light-webfont.eot’);
src: url(‘fonts/YanoneKaffeesatz-Light-webfont.eot?iefix’) format(‘eot’),
url(‘fonts/YanoneKaffeesatz-Light-webfont.svg#webfontiVAlVXNY’) format(‘svg’),
url(‘fonts/YanoneKaffeesatz-Light-webfont.woff’) format(‘woff’),
url(‘fonts/YanoneKaffeesatz-Light-webfont.ttf’) format(‘truetype’);
font-weight: normal;
font-style: normal;
}

I had to rename the yanone_kaffeesatz folder in the Asteria theme’s font folder – the @font-face construct does not really support overrides. This means that an update of the Asteria theme will bring back the Ultralight version, but I can live with this limitation.

It turned out that this was caused by the Advanced Custom Fields – Taxonomy Field add-on and not by WCK. This plugin isn’t even needed, because ACF handles taxonomy fields already. Once I disabled the plugin, things started to work normally. Why this plugin worked for a while and what broke it I cannot say. I still believe it was data-related. I tried to remove individual posts and postmeta rows from the database that I thought could be causing it, but this did not lead anywhere.

It is a bit unfortunate that there is not a more meaningful error message and that diagnosis is very cumbersome. It appears that many people saw similar symptoms after the WordPress 3.5 upgrade. There is much chatter in the forums from about a year ago, but no meaningful advice. This post ultimately made me go about it in a more methodical way.

Wouldn’t you want to see the desktop theme on the iPad? My problem is rather that on Android tablets I get the mobile theme.

@fonglh: Both excellent points. Would someone care to delete my post from this forum please? I dont see a way to do this myself.

Try checking the “Do not use search API for screen names”. It resolved this issue for me.