Sam Pohlenz

The current releases of Rails (including 7.0.x) don't seem to play well with ActiveStorage when used from an engine. It looks like this may be fixed in 7.1 but in...

1. For your first issue (using Trestle authentication from a non-Trestle controller), you'll need to include the trestle-auth authentication concerns, and then add the relevant before_action: ```ruby class LabelsController <...

> However, I should mention one behavior in the resultant solution that I wasn't sure if it was intentional or not, is that `before_action :require_authenticated_user` turned out to be unnecessary...

The generator for trestle-auth both generates a default model as well as injects (mostly commented) configuration code into an existing `config/initializers/trestle.rb`. If you are using an existing model, then you...

I need to correct the README there -- it should be `config.auth.authorize_with`.

Make sure you are also using the authorization branch of trestle-auth from GitHub. In your Gemfile: ```ruby gem 'trestle-auth', github: 'TrestleAdmin/trestle-auth', branch: 'authorization' ```

Overriding `config.tinymce.base` should allow you to do this a little cleaner. However this shouldn't be necessary when using relative URLs. Do you have `config.relative_url_root` defined in your `config/application.rb` or `config/environments/production.rb`?

Please try out tinymce-rails 4.1.2 (just released) which contains a fix for protocol-relative asset hosts. You may also need to run `rake tmp:cache:clear` which is possibly why the master branch...

Hi @kayluhb. I've been working for some time on a new asset compilation method which is currently in the [compile assets branch](https://github.com/spohlenz/tinymce-rails/tree/compile-assets). I still need to finish off a few...

I've added the version string to the plugin URLs in the 5.0.5 release (by way of the [cache_suffix option](https://www.tiny.cloud/docs/configure/integration-and-setup/#cache_suffix)).