Chiming into this a bit late... but I don't think there's good reason to call out to a CC API for the WP plugin. Licenses change very infrequently, there is no reason to introduce a dynamic call of any kind at runtime just to populate the license options.
As for 4.0 changes, there are no infrastructure changes required by 4.0 per se, but I do think that (apropos the above as well) we need to take a more critical look at all the stuff we host and shut down / archive the pieces that are not widely used and are unmaintained. Dan On Mon, Oct 21, 2013 at 5:08 AM, BjornW <[email protected]> wrote: > Hi Maarten, > > No, not as far as I know. For now I've decided to continue with the > partner url method for this plugin. Any news on (technical) changes with > regards to CC 4.0? > > grtz > BjornW > > On 21-10-13 14:04, Maarten Zeinstra wrote: >> Has there been an answer to this yet? >> >> Best, >> >> Maarten >> > > > -- > > met vriendelijke groet, > Bjorn Wijers > > * b u r o b j o r n .nl * > digitaal vakmanschap | digital craftsmanship > > Werkdagen: > Van maandag t/m donderdag vanaf 10:00 > Vrijdag is voor experimenteren en eigen projecten. > > Postbus 14145 > 3508 SE Utrecht > The Netherlands > > tel: +31 6 49 74 78 70 > http://www.burobjorn.nl > > _______________________________________________ > cc-devel mailing list > [email protected] > http://lists.ibiblio.org/mailman/listinfo/cc-devel _______________________________________________ cc-devel mailing list [email protected] http://lists.ibiblio.org/mailman/listinfo/cc-devel
