Tschallacka
Tschallacka
@mjauvin Nobody would download a theme that's dependent on all the other themes, I would hope.. And this way you can sandbox, whilst still giving some flexibility.
@alekseyp i would rather go with a "final" flag, that the default is extendable, in the spirit of open source projects building on top of eachother.
I simply added HTTPS=On to the .env file and it works like a charm. No need to mess with the proxy config.
I would suggest adding the https=on in the .env to the documentation for use in proxied servers asa solution
This should be reopened.
I had the same issue. The solution is thankfully relatively simple, but also involves the user needing to edit their ~/.bash_profile or ~/.bashrc file In your ~/.bashrc or ~/.bash_profile add...
This is caused by a racing condition. The author has used $(document).ready but the moment tinymce is loaded the document is long ready because all these things are added dynamically....