BackEnd support, old vs. current

On Backend | RapidWeaver Elements Docs I found some pointers that I could embed some of the backend code we need to use if I wrap the described PHP around and basically where it says " // Process data […] " call (exec) a shell script and reach out to a Python interface, etc., BUT …

The projects I work on have a clear “rule” : for any new stuff we do, PHP is no longer allowed. And can only be used with extra approval process, lots of forms, meetings, … and that would sort kill the argument of introducing Elements to make things smoother, modern, bla, bla, …
(you can tell these are backend people, looking for tools to help them prototype frontend things, right?)

I am currently still in the phase of “just started with reading the documentation”, so feel free to respond with “yes, you have not found that doc yet, just read this …” or “that should basically work, there just is no documentation (yet), but if you try …” :-).

This is brand-new and still being documented. It will likely change a little, but should be available in beta 35 - due the week of the 3rd.

If you have any specific questions, @bon and @tpbradley will be able to help you get going with this!

Hi Dan, thanks for the response.
Will reach out to @bon and @tpbradley later. I do have quite some ideas I am looking forward to share and see what they think :slight_smile:
Oh, and I think I noticed a typo in the documentation: submit.php vs. process.php. Would that be yours to look into? Or either of them?

Looking forward to hearing more! (and I’ve fixed the typo).