Hi !

I use Context 2.x on a site. As this version is marked as "not maintained", I would like to upgrade my installation to Context 3.0.

One of the problems I encounter is the complete change between context and context_get/set. In 2.x branch, my site heavily uses the context_get function which in turns relies on the context definitions. Upgrading to 3.0 branch changes everything. As an example, if I define a context with namespace="a", key="b" and value="1", the upgrade turns it into a context with name "a-b-1".

With 2.x branch, you call context_get("a","b") and you get the value ("1" or another value if you have multiple values for a particular namespace/key couple). With 3.0 branch, you cannot do it anymore and can only know whether or not the context is set.

The attached module creates a reaction plugin which adds the possibilty to call context_set with a namespace, key and value. Thus a migration 2.x→3.0 is simplified as you can mimic the old behaviour using this module. It may need some checks and corrections.

Is there a way to integrate it with Context ?
Is there a way for Context to take it into account and automatically create the reaction when upgrading an old installation ?

Thanks

CommentFileSizeAuthor
context_reaction_variable-6.x-1.0.zip2.19 KBAnonymous (not verified)