Ask A Question

Notifications

You’re not receiving notifications from this thread.

Forms With Multiple Submit Buttons Discussion

Nice :)

Reply

Pretty cool!

Though will this work with translatable strings too? It doesn't seem like a really solid solution to this problem.

Reply

If you use the localize method in both places, it will work just fine for translatable strings. You just want to make sure you always keep them the same.

Reply
Евгений Арасланов Евгений Арасланов
Reply

Hi! Learn to cause stored procedures in Rails please

Reply

Is this a good method? - What if you are using i18n so the commit message will show different languages?

Reply
Adam Cooper Adam Cooper

At around 8 min he explains how to use the f.button instead of f.submit. Here the commit value has to be set manually. This way the button text can change, leaving the commit value the same,

Reply
Kohl Kohlbrenner Kohl Kohlbrenner

@excid3:disqus published_at is a column in your db. Is "published?" a rails method that looks at published_at as a boolean and returns true or false depending on if it is nil or not?

Reply

Yes, published_at is a column and published? Is just a method delegating to published_at? so it's more readable.

Reply

love it great job

Reply

Question, is it best practice to be putting the published? and save_as_draft? methods in your post controller? Or are you doing that for the sake of explaining it?

Reply

how can I add the validation of a field (unpublishing reason) by pressing the button unpublishing?

Reply
Join the discussion
Create an account Log in

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

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

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

    Screencast tutorials to help you learn Ruby on Rails, Javascript, Hotwire, Turbo, Stimulus.js, PostgreSQL, MySQL, Ubuntu, and more.

    © 2024 GoRails, LLC. All rights reserved.