@alejandror Thank you for prompt response. It actually does fix the issue. To reproduce the issue and resolution:
1- Download Bitnami's Weblate stack for your favorite environment. In my case a VM image.
2- ssh into the "machine"
3- Go visit the weblate "instance" and login
4- Create a project
5 - Attempt to create a component and scroll all the way down to File format
6 - Attempt to change the File format from auto detection to PHP string
7 - Face the issue that PHP string is not an option.
8- Go back to the machine and activate weblate python's virtual enviroment
9- pip install phply
10- Restart the "machine"
11- repeat steps 5 & 6
12- Choose PHP string since it now exists as an option
Sadly I'm not the administrator of our AWS infra and I can't apply that change myself on there. I would love it if you guys could fix it so me and other users could benefit from this fix. So I'll be waiting for you guys to fix the AMI before instructing the our boys to update it.
Thanks a lot
Regarding version 3.4, it might be a bit of a misunderstanding on my side; but doesn't the documentation list https://docs.weblate.org/en/latest/changes.html#weblate-3-4 as a valid version ? Not sure maybe they haven'ty release it yet.