We've moved discussions to Discord

Properly deactivate Jumpstart features

Pierre-Loïc
Hi there,

I just purchased a license for my website, which require less features than Jumpstart has to offer, at least for now.

For example, the multiple Accounts feature remains out of the scope. I will probably make use of it later, but I do not want to confuse my users with such feature for now. This goes the same with the API.
What would be the proper way to deactivate these features? A lot of routes, controllers and views are involved, I don't want to break things that early.

Thank you!
Chris Oliver
The best way is to just comment them out in the UI. Then you can still merge in updates with minimal changes and can easily enable them again.
John Quarto-vonTivadar
Note that it may be worth commenting them out from a Ruby standpoint where you can (rather than a HTML comment). Just in case someone looks at the HTML Source and tries to follow one of the UI links to a route that still exists.

so, prefer <%#= %> 
to <!-- -- >
Pierre-Loïc
Thank you both!
Notifications
You’re not receiving notifications from this thread.