Something is still not working as you think it is.
You're right about that, especially the practice of setting @xxx in
one controller and (correctly) referencing it's value in second
(unrelated by hierarchy) controller. I think that can only work by
meta-programming magic. I'm going to post a question about that at
some future time when I'm not consumed by the need for a deliverable.
... there should be no need to reset it for another action.
I left the conclusion out of my description of the problem, which
stated in full is:
Failure to employ this reset leads to, e.g.
clicking "New Expense" in app\views\expenses\new.html.erb,
clicking "Vendor" in app\views\expenses\new.html.erb
clicking "Show" on any of the vendors displayed in app\views\vendors
leads to three links, "Edit | Back | New Expense" where there should
only be two: "Edit | Back"
Adding the reset clause led to correct behavior in a couple of tests,
I believe. In light of your misgivngs, I thought I should remove all
the params I introduced earlier. Now, the extra link appears again
at times I deem to be inappropriate. So either I was wrong before or
introduced another error.
In any case, I can't spend any more time on this. As I just posted
Hassan, I'll get back to this issue after I finish adding
authenticated users and package a "ver. 1" deliverable.
I have just seen your next post in reply to Marnen's suggestion on
testing. I suggest you run for cover.
I'm a mere needle in a haystack comprised hundreds of millions of
Americans. Finding me to inflict punishment for violating "good
practices" will be inordinately difficult
Thanks again for you continued contribution to my Rails education. I
hope you don't find me incorrigible nor ineducable.