On Jan 16, Ignacio Huerta wrote:
> The model looks fine, I would check the controller (is the create
> action available?) and then the Dryml. Can you paste some code?

On Jan 16, 4:53 pm, kevinpfromnm <[email protected]> wrote:
> what's the view permission?  for create or update to be checked, the view
> has to be permitted first.

In the model that won't let me submit a form for creation (note that
it does show me fields, all of them that are defined in the DRYML, but
omits a few fields in the model definition - which makes me suspect
that something I've done is upsetting the field generation, provoking
a problem before the submit button code is yielded?):

The model:

  fields do
    primus     :string, :required
    secundus       :string, :required
    tertius :string, :required
    quartius :boolean, :default => false
    timestamps
  end


# --- Permissions --- #

  def create_permitted?
    true
    # acting_user.signed_up?
  end

  def update_permitted?
    true
  end

  def destroy_permitted?
    true
  end

  def view_permitted?(field)
    true
  end

>From the controller:

  hobo_model_controller

  auto_actions :all

end

>From the form.dryml:

<def tag="form" for="Troublesome">
  <form merge param="default">
    <error-messages param/>
    <field-list fields="primus, secundus, tertius" param/>
    <div param="actions">
      <submit label="#{ht
'troublesome.actions.save', :default=>['Save']}" param/><or-cancel
param="cancel"/>
    </div>
  </form>
</def>

I have changed the field names to protect some business logic. Happy
to share a private GitHub repository with someone who observes a basic
NDA, while I try to reproduce with a sanitised app. The "submit" line
has only had the model name changed. It's not a name likely to be a
reserved word (think "airline_ticket" or "project_office" type names
rather than "model", "return", etc).

I'm completely stumped. But if you've read some of my previous posts,
that may be no surprise. :(

This same model exhibits some other oddities, BTW. One of the fields
is a boolean, and doesn't appear in the DRYML (quartius), and tertius
is in a "has many/belongs to" relationship, like primus and secundus -
but where they offer a selection dropdown, tertius offers a string
input. I offer that info in case it triggers recollection of some
other problem where possibly some way in which fields work may cause a
failure to show the submit button?

Thanks for your pointers!

-- 
You received this message because you are subscribed to the Google Groups "Hobo 
Users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/hobousers?hl=en.

Reply via email to