Romain Tripault

Hi! Just wanted to confirmed we faced the issue as well, and the proposed new pattern indeed solved the issue (disabling pcre.jit also worked, but better have a more efficient...

Thanks for pointing that out. I completed get this has been deprecated (and if get the code comments correctly, will be removed in Revo 3.3). But to be honest, as...

> Not sure how else to smoothen this upgrade path, the submodels have always been a little weird to me. Agreed on the weirdness... regarding the approach to smooth that...

A solution would be to use the `default_context` setting

I'll follow Jay on that one (while understanding the need). If those fields become editable as default, i would have to hide those on most (if not every) project (but...

Still against this idea since i almost never had the use of this. But since i had the need for it lately, here is a sample plugin, in case that...

That's an old one indeed! Not sure what was the old me thinking back then... i guess ease of being able to render pictures in the frontend then... but having...

Indeed, but schema are already somehow engine specific (we need 1 schema per DB engine/type)... the other problem being : those aliases would need to be read-only (ie. how would...

Well, that's somehow what i meant, if the code, i would have expected `$r->set('relationship_object_id', $object2->get('id');` to "kill" that relationship from parent object1 to object2

I guess i did not make it understandable enough, let's rewind :) object1 & object2 are different objects (same class, let's say `x`). those objects can have relationships (composite, let's...