All threads / Debugging & Fixing a Bug in Rails 5.2 Active Storage Discussion

Ask A Question

Notifications

You’re not receiving notifications from this thread.

Debugging & Fixing a Bug in Rails 5.2 Active Storage Discussion

Great episode Chris! This really makes me want to dive into more source code, I admit that I'm always hesitant to do it
Reply

Hi Chris,
I've been struggling with the idea of combining ActiveStorage and a rich-text editor. Do you have any suggestions? I planned to use Ckeditor and it's not working yet. I've defined the active_storage.rb inside app/models/active_storage.rb and added some custom codes to use ActiveStorage instead of some other like Paperclip, Carrierwave, Dragonfly, etc that Ckeditor 's already supported. The problem is the uploader is not working through ActiveStorage yet.

Reply

Sometimes your application goes wrong. Fortunately there are a lot of tools that will help you debug it and get it back on the rails.

First area to check is the application log files. Have “tail -f” commands running on the server.log and development.log. Rails will automatically display debugging and runtime information to these files. Debugging info will also be shown in the browser on requests from 127.0.0.1.

You can also log your own messages directly into the log file from your code using the Ruby logger class from inside your controllers.
https://jiofilocalhtml.run
https://forpc.onl/nox-player-for-pc/

Reply
Join the discussion

Want to stay up-to-date with Ruby on Rails?

Join 49,439+ developers who get early access to new tutorials, screencasts, articles, and more.

    We care about the protection of your data. Read our Privacy Policy.

    logo Created with Sketch.

    Ruby on Rails tutorials, guides, and screencasts for web developers learning Ruby, Rails, Javascript, Turbolinks, Stimulus.js, Vue.js, and more. Icons by Icons8

    © 2021 GoRails, LLC. All rights reserved.