Help for Aimeos

The shop provides courses for acting students. One type of course can be tought by different teachers at different dates and times, so we decided to create a separate product for each of these courses.

But in the backend we would like to somehow be able to select the teacher from a prepared list, instead of always typing it out. It would also be great to have this teacher connected with some text that could be shown as a popup.

To get a better idea of what I mean: this is the current "shop" using formhandler which shall be exchanged with aimeos:
https://www.schauspielschule.at/29/

What would be the best way to do that? (I was thinking about mis-using "supplier for that, but this field does not show up in the product creation interface.)

(This "selection" should only be available in the backend; we do not want the customer to choose from select boxes in the front end. Unless you recommend us to do so, because it is the better way?)

Thank you!

Using suppliers for that isn't a "mis-use" but a perfect match instead

There's currently no sub-panel for adding suppliers to products but that's rather easy to implement if you use the "Categories" panel as reference for copy&paste. A pull request on Github for that is very welcome!

Hmm... I really would like to try that. But I encounter another problem:

I follow the git workflow you provide here: https://aimeos.org/docs/Developers/Git_workflow

I fork the aimeos-typo3 repo
Then I clone my aimeos-typo3 repo to a local place on my computer.

But how do I install the extension into TYPO3? And how do I manage all the git related workflow in the installed extensions? How can I require a package from a local storage?

Special case (not concerning me at the moment, but would like to know): How would all that work in a TYPO3 environment that itself might be a clone with its own git repo at the root?

Thank you!

Having tried out quite a lot (see Slack https://typo3.slack.com/archives/C025BQ ... 6766254500), I came to the point, that you at aimeos should provide a clear instruction on how to setup a proper composer-based development setup that is good for providing PRs. Your current instructions in the docu are by far not sufficient, and I for myself could not come up with a useable solution. But you are the pro's, so i count on you! Even though I have to say that my guts tell me this is actually not possible (with composer and git and no overrides on all those pulls once a manual change was done...).

This is very discouraging, to be honest. I wish you could provide better instructions, if you expect PRs...

What are you missing to create a successful PR for the Aimeos core in https://aimeos.org/docs/Developers/Git_workflow?