- Issue created by @apmsooner
- π§πͺBelgium svendecabooter Gent
This change might need a warning that it depends on ai 1.2.x, and including it into custom_field might need to be timed together with the first (stable?) release in that branch...
I don't suppose it would be possible to both support 1.1.x-style FieldTextExtractor plugins, as well as 1.2.x-style... - πΊπΈUnited States apmsooner
We can document the module version requirement on the project page but I would prefer we stick with the 1.2 version as the source of truth. Otherwise, someone could make their own patch for 1.1 compatibility if really desired. I don't think there is even enough users that are going to be affected anyhow since ai_translate & custom_field usage together is likely gonna be very low at least for now until more people adopt AI.
- π§πͺBelgium svendecabooter Gent
Tested this update, and it works well with β¨ Add text extractor plugins for image and link field types Active .
- π§πͺBelgium svendecabooter Gent
Tested this MR with the newly released 1.2.0-alpha1 release of the AI module, and everything works as expected.
-
apmsooner β
committed e09c73f8 on 3.1.x
Issue #3533534 by apmsooner, svendecabooter: Create custom_field_ai...
-
apmsooner β
committed e09c73f8 on 3.1.x
-
apmsooner β
committed e09c73f8 on 4.0.x
Issue #3533534 by apmsooner, svendecabooter: Create custom_field_ai...
-
apmsooner β
committed e09c73f8 on 4.0.x