modus

Aside, as it was me starting this thread

I spent some more time researching the issue since and found there’s a lot of paranoid interpretations of the law. According to 1&1 session cookies as such are not the problem, as they are regarded as ‘necessary’.

Certain cookies that are considered ‘strictly necessary for the delivery of a service requested by the user’ don’t have to be declared, because they are of far higher benefit to the user than the company. This includes cookies used to track shopping carts in e-commerce and to store important login information that the user requires. …

… For the use of most cookies, website operators in the EU now require permission from the user. This covers all cookies that don’t meet the requirement mentioned above of being ‘necessary’. This means that advertising cookies for retargeting, analysis, and social media cookies now require permission from the user.
German version here

My guess is a hosting business their size has consulted their lawyers before publishing info with the potential to harm their own customer base on a big scale.

As long as there’s only cformsII used, the data not stored in the db and no third party cookies for tracking and targeting involved on a site, I decided to take the risk.

I doubt that in case somebody is willingly transmitting personal data to you via your contact form, he could sue you for using this info for the sole purpose of fulfilling the request he himself submitted. Therefore such a checkbox on a contact form reminds me of “fat-free”-labels on water bottles I saw in California. Afaik, there’s no such kind of over-protective “consumer protection”-laws in the EU.

Sorry to interrupt, your views on the topic may vary.

@satoristudio
Thanks for your reply. I have to apologize, in fact it seems like my browser was having kind of a hiccup and didn’t use the fonts I chose to render the texts. But weirdly it did use Open Sans, so I came to the false conclusion all other but the default font weren’t working. At least I could help Jonathan a little bit.

Sorry for hijacking your thread, but same here (on local development), the only font working is the default font Open Sans.

I had the footer menu problem, too. Add
.footer-menu li {
text-transform: none;
}

to your additional CSS to fix this.

All other fonts than Open Sans seem to be referenced incorrectly by the theme, in your case only the greek glyphs are being returned, while it should be at least the latin font subset.

It would be nice, if somebody could have a look and provide a fix for this.

Very good, thanks a lot for filling in the details!

Hi Ravan and thanks for your interest in the matter.

I only set up a local site at the moment. The primary language can be reached via the domain, English as the secondary language resides in a subdirectory /en/. I didn’t plan to redirect visitors, but I’m not through considering the pros and cons, yet.

How would you configure the settings? If I understand your description right, I could set up a distinct sitemap for each of the sites and add a link to the subdirectory’s sitemap to the domain’s sitemap?

Really cool would be, to be able to define or edit a default stylesheet. For the most people this should suffice, as in general a site has a styleguide. To be able to override this for a single table would be nice, too, in case one needs a different kind of table.

But a really cool feature would be, to add attributes to the cells of a cpolumn, thar way one could use CSS like Pure CSS Responsive Accordion Table“, that collapes into single segments on small screens.

Just dreaming, thanks for a cool and very usable plugin.

Just some findings I can share: excluding content, thumbnails and text-widgets from lazyloading (I use BJ Lazy Load) already did the trick for me. Imho it doesn’t make much sense to delay the rendering of content or pure text, anyway. At first I didn’t think about that at all, because it seemed to work well with the default settings. The problems only showed up later in the rare case of a post containing a small gif thumbnail, that got base64 encoded by Autoptimize. So I’d recommend to check your lazy load or other conflicting script’s settings first. But your mileage may as well vary.

Anyway: praised be Frank and Autoptimize! It was the first plugin of its kind that just worked out of the box for me, while all others were throwing errors like hell. This thing is robust. Thanks a lot.

Thanks a lot, I’d have one more question, you said:

It’s set only in the filter callback used for the metabox addition.

Looking around in the wiki I found a code snippet that seems to do what I need, but just to be sure: can you tell me, if this will still work the same way in CMB2?

'show_on' => array(
			'key' => 'taxonomy',
			'value' => array(
				'category' => 'cat-2',
				'rotator-location' => …
			)
		),

(found in https://gist.github.com/billerickson/070476e584b04a20c770)

Then do yourself a favor and either use the new magic fields version 2 as up ’til today there hasn’t been any forthcoming concerning a script to migrate v1 data to v2.

Or choose an alternative that is supported at the time of writing: Meta Box.

Or if you’re familiar with PHP, go and create your own, like in this tutorial.

Sorry for any notification. I should’ve looked closer at your post. Thanks for the solution.

Hi Ramon,

I’m not completely sure anymore that it is this plug-in, that causes the effect alone. I activated/deactivated various plugins during my research and there might as well be a conflict with others or some of my theme’s functions. I posted this when i found, that deactivating it helped – but then it occured again some time later. I’m still a bit riddled about this and will definitely stop posting error reports before i have completely sorted out the cause of a problem. Sorry and thanks,
modus

Sorry for the alarmism, in the end the problems disappeared, when i removed a function from my theme. Thanks again!

…but breaks for me in 3.1.1.:
– Dashboard returns our beloved white screen

Didn’t check other stuff in the backend, debug.log doesn’t contain any reference to wp-pagenavi.

Thanks, too, works perfect in 3.1.

Thanks, I definitely get your point and unfortunately just commenting out ‘flush_rules’ doesn’t solve the issues with 3.1 and permalinks (links to tags and categories broken and permalink structures containing %category% causing to redirect cycles). I had hoped for relief ?? . This plugin seems to have reached it’s eol.