search

themangoemoji / DFD

The new and improved website for the Spartan Dischords, MSU premier a Capella group
http://www.thespartandischords.com/
1 stars 0 forks source link

creating members is inconsistent on Heroku #7

Closed c-lliope closed 9 years ago

c-lliope commented 9 years ago

Hey, @wrightmhw – I tracked this down using git bisect, and I think I found the problem. I left a few comments here.

Also, you should read about git bisect. It's awesome and makes your life a lot easier when something was working before but now it's not.

themangoemoji commented 9 years ago

screen shot 2015-01-20 at 12 02 49 pm

@graysonwright

I fixed the destroy code I had before; but the routing is still. Everything seems normal when I am not logged in as an admin. When I am it seems like the id's cant be found.

c-lliope commented 9 years ago

Try to install the binding_of_caller gem, and then visit that page again – whenever you hit an error your app like that, it'll automatically give you a debugging prompt in the browser.

also, maybe try: <%= link_to "Delete member", member_path(@member.id), :method => :delete %>?

themangoemoji commented 9 years ago

Hey, @graysonwright. I had to change it to

<li class="member-link"> <%= link_to "Delete member", member_path(@members.find(member.id)), :method => :delete %> </li>

Does that make sense to you why we couldnt do the other ways?

themangoemoji commented 9 years ago

@graysonwright so.... I just dont quite understand why heroku is displaying like this right now

screen shot 2015-01-20 at 3 12 07 pm

do I have to pay for it? Is this because it is snoozing? I dont see any css be loaded. on the other hand my local app seems to be pretty much exactly how I want it (woo!)

c-lliope commented 9 years ago

Hey, Michael! Whenever something goes wrong on the page, check the JS console. Here's what I'm seeing:

screenshot 2015-01-20 14 00 11

Also, you should probably open another issue for the CSS problem, because it isn't related to deleting the members.

c-lliope commented 9 years ago

The CSS problem should be taken care of with #11.

c-lliope commented 9 years ago

This issue is solved with 53698f0

themangoemoji commented 9 years ago

^^ "issue solved with ####"... This is a good workflow habit. Thanks!