Marco

The fix: In lib/Stylesheet.class.php, line 91, replace WP_CONTENT_URL with content_url()

Understandable.
Not sure I’ll make a plugin of it since it makes more sense to have the second checkbox next to the current one.
And just to clarify, the mod would make the force ssl deep – it checks all ancestors for the force_ssl_subpages.
I felt it had some usability going for it, not requiring additional code in the functions file for a feature I believed many people would want. I agree that the regular expressions would scratch the same itch, but it is also a bit codey for a lot of people.
Although, if a regex is too codey, one might argue that the user shouldn’t dabble with certificates..

That’d be really nice. Anyway I can convince you to use this in 2.0 until you implement (or in addition to) the regex fields? I am just thinking that I’d love to be able to use the normal update channels in case you, me or anyone finds a serious bug, and at the same time I find my solution very adequate in many situations. I suspect a lot of people see their pages as a tree-structure, and kind of expect a ‘secured’ page to have their children secured as well…

Yeah, I was wondering about authentication to for the create_post. I will have to implement it at some point, but if anyone already have an implementation I’d be glad to see it.

So do I:) Will try that solution for now…

Sorry, it’s RC2 — using nightly tester, so I’m at the last version… As I said, it could be any of the many other plugins I have that interfere… I’ll see if I can replicate on a fresh blog soon..

Um, seems to not be the case. Rather some mixup with nginx not passing the right parameters… Sorry for the alarm…

Just updated and it works like a charm! Great also to find I can get json out of custom posts in the new release!

I think I got the problem – yes, the file is there, but I realized some mod_security rules prevents files with cookie in the name. I renamed the file jquery.chocolatechip.js and fixed the include in functions.php and it all works.