cancan | A scalable video sharing service | Video Utils library

The only ways in which your chill(), suffer() and death() functions differ are in the range of the random integer as well as the array used (chooseDeath, timeToSuffer or walkInThePark), both of which you could pass to the function as an argument instead to unify them into one function.

I have finally did it, the problem is when I just created the objects and didn't add them to the main window, they all have default sizes and values, and the value changes when they are added to the window.

So I just need to calculate their sizes and resize them AFTER I have added them to the window.

In my observation, the QVBoxLayouts in the QGroupBoxs always have margins of (9, 9, 9, 9), and all the layouts where the widgets actually are don't have margins, and the QGroupBoxs themselves have margins of (3, 20, 3, 3) in my main script, so I could just explicitly set these margins and use these values.

This is how I have done it:

The recommendation to move invitations_controller.rb into an app/controllers/users folder is the correct one. That's the path that matches your route:

I did finally figure out what this was.
The older versions of rails in this case v4.2.1 used the javascript_include_tag for the line that deals with application:

= javascript_include_tag "application"

In the newer versions of rails in my case v6.1.3.1 you have to use javascript_pack_tag

= javascript_pack_tag

This solved the issue and the views all started working. I did mention above I was working on a PC running Rails v6.1.3; however I noticed I didn't make it clear that I was also having to upgrade this program from Ruby v2.2.2 and Rails v4.2.1 to Ruby v 2.7.2 and Rails v6.1.3, that might have helped to have made that more clear. Apologies if that confused anyone. I am still VERY new to Rails and using StackOverflow.com. I am happy to report I have only 1 single issue left on this program and the rest of the program is all working properly. I will be posting another question in fact because the last issue deals with a complicated scope query and it uses different syntax again due to the newer version of rails and I haven't been able to figure it out. In any even if you are running an older version of Rails and you are trying to get the program to work on a newer version (my case as I couldn't get rails v4.2 to run or work on ANYTHING, PC, Linux nothing) then you have to change the include_tag to a pack_tag. I do not pretend to say I fully understand why. I know it has to do with webpacker but beyond that I am still learning Rails. Perhaps someone with more knowledge than myself can shed some insite as to why the syntax changed. Oh and in addition the line ended up needing to read as follows:

= javascript_pack_tag "application", "data-turbolinks-track": "reload"

I didn't have the turbolinks reference either.

I hope this helps someone else in a similar situation that I was in, it was not easy to find. I only discovered it when I went through some tutorials on making other generic apps and saw the difference on that line.

In your project directory, try installing rails gem install rails -v 4.1.6 and removing the version from the failing gems like (liquid_markdown, gon, etc..) then try running bundle update then bundle clean --force

I think this might be an issue because all the version of these gems are locked inside your Gemfile

Yes :new is an alias of :create

See here:

https://github.com/CanCanCommunity/cancancan/wiki/Action-Aliases

The rails way to do this would be to use a nested route instead of passing conversation_id through the request body:

i think you miss the check that should raise the unauthorized response. In your action, you should have something like this:

Try updating your Gemfile to use json@1.8.2 instead of 1.8.1 - according to this thread Ruby 2.2.x is incompatible with json 1.8.1.

1.8.2 should be functionally similar and not affect any of your other dependencies.

You can also run bundle update json to let bundler try to fix it for you - but that may put you at a much later version than 1.8.2, I'm not sure.

No harm in trying a couple things and reverting your changes.