lkraav

I think using @import shows the theme authors are not very well versed in their business.

I am also wondering about #2, /robots.txt handling, to be specific.

My multisite installation has production and staging sites mixed, which means I don’t think I can shoot a regular robots.txt file into WP root – it would kill products sites indexing.

But right now (5.0.1) robots.txt queries get redirected to WP login screen, which is a bit too messy to my liking. Bunch of plugins get loaded, logs get spammed and other useless work stuff happens.

It’s feeling like the plugin could use a new settings field for specifying a custom robots.txt per subsite.

Any thoughts here, Jake?

Not likely. Had to get strpos based exclude working for this one project and that’s about all I got for this at the moment.

But no worries, this is the one minification plugin I care about, since looking at the code of all the others mostly makes you want to throw up. We’ll get to it all soon enough, 100% guaranteed.

Weston, this report is real, seeing the same thing.

FWIW I’m seeing this on PHP 5.2 right now. Haven’t investigated on 5.5.

This is also happening here. I’m wondering what is missing from my Apache configuration. I think there is no check because it is assumed this header is ubiquitous.

Also interested

Here’s two URL preview libraries we could use for Talk

* https://github.com/Ekito/bootstrap-linkpreview
* https://github.com/LeonardoCardoso/Facebook-Link-Preview

Definitely let everyone know here if you start any GitHub hack repo. I will probably get to it within 1 month myself.

wdym, 1.0.4 lets me like comments just fine.

Regarding the check in button, the fix is really easy. I just killed off the position:absolute CSS part that pushes the button into header area and moved the output function right below the widget title.

I wonder if this plugin is still maintained any?

I think if it could do some more dynamic stuff automatically, like pinging the server with AJAX for online status, that would be awesome.

Yes, I’m seeing the same thing. On P2 1.5.0.

While going through the P2 Check-In code, I notice several _GET[variable] occurrences, which should be _GET[“variable”].

Strange to see how this plugin ever worked with _GET queries being broken like that.

How did you resolve this? I’m also seeing [youtube=] shortcode not work in 1.5.0.

https://10up.com/plugins/restricted-site-access-wordpress/ is an up to date solution from a known quality developer.

Totally interested in this, +1 and following

I shall also post on W3TC support board to inquire about configuration options.