Thanks for all of the feedback. I wanted to post the resolution. I
hate when people ask questions, get resolution, but fail to post what
they did to help answer the issue for other people who might be having
the same problem.
So, when I baked the view, I discovered something interesting. All of
t
Santa,
First I am using 1.2 so there might be some differences some where
with the way generateList / scaffold work. However, I guess the key
functionality and the end result should be the same.
> So why would I need a completely new model for each section?
By defining the Letter model as you /
AD7six said:
> OR consider scaffolding what it is (a development tool), bake/write
> some code and add the conditions to the generateList call as you would
> need to do for any polymorphic model definition. if you use 3 models
> opperating on the same table, just edit the model's beforeFind to add
I really appreciate all of the feedback. I must admit, there are
advantages and disadvantages to both methods. I want to keep it
positive so I won't discuss the disadvantages from my perspective, but
the things I look for.
Zonium, thanks for the information on the foreign key caveat... _id...
tha
close to how things started, but
>> instead of showing all letter_content in every drop down, I get all
>> openings in every letter_content drop down.
>>
>> It seems like cake should handle this, and I know it is due to my
>> inability to understand how it should be d
On Dec 12, 9:47 am, zonium <[EMAIL PROTECTED]> wrote:
>
> - You can try abba bryant's approach. However the main point here is:
> the naming for foreign keys and the generateList's ignorance of the
> foreginKey statements and conditions specified for $belongsTo (I dont
> see these 'secrets' do
Santa,
I have tested the option 2 and it works as expected.
- The structure of tables and $belongsTo variable that you proposed
were kept unchanged.
- Small modification: under score is used for the foreign keys (e.g.
opening_id). I reviewed the cake core and found out that generatList()
detects o
;));
> > $this->set('endings', $this->LetterContent-
> >>generateList("`letter_section` = 'Ending'"));
>
> > Now I can access the edit view and things are looking good except for
> > one issue. Now all three drop downs (Opening, Middle, E
On Dec 12, 7:31 am, abba bryant <[EMAIL PROTECTED]> wrote:
> The right way to do this would be to have 3 models each of which uses the
> same table ( letter_contents )
> with the correct conditions defined ( see finderQuery ) or place the
> conditions within the Letter model's
OR consider scaff
It seems like cake should handle this, and I know it is due to my
> inability to understand how it should be done. I don't want to have to
> strip out each table if it can be avoided. I am still sticking to my
> original thoughts that this is
I considered option 2 as I believe this is a fairly straight forward
model and it should be handled quite easily by cake. I have completed
the "baking" as per your "recipe" and here is what I have come up
with.
When I bake the controller and the views, it gives me an error in the
controller. Let
The 'problem' seems to be with generateList() which is used by
scaffolding to provide data for the 'select' construct. It ignores the
condition you set for Letter model.
You may consider 2 options:
1) if you want to take advantage of scaffolding then you might need to
break the table 'letter_cont
I have a model situation that I cannot find in the group anywhere. I
have spent nearly a day searching. I am hoping there is a model guru
that can help.
First, to help you understand, I am putting together a pre-canned form
letter tool. I will have three sections to the letter using all pre-
writ
13 matches
Mail list logo
