A quick browse through your code shows that you can set options for a
product, but where were you planning on storing the information from
the user? I don't see any changes to the line_items table (or a
separate table), etc to store the personalization input from the user.
It also appears that each product can only have a single
personalization option. Is this your goal?
I have the need for something similar, but I need multiple
personalization options per product, and it needs to support more
options than a single text field (some "personalization" needs to be
radio buttons, select boxes, etc).
I would also merge your migrations right now while nobody is really
using the code. The way your migrations are currently written, if
someone was using a version that used the :personalisation_options
column inside products or variants, those changes would be lost when
you ran the 20100320220929_add_personalisable.rb migration since you
don't alter the name of the column, you drop it then re-create it. Of
course during the drop you lose any data that was entered by the admin
in that column. I assume that you are making the assumption that
nobody is using that previous version so it is ok to make the drop,
but if that's the case then you may as well clean up the migrations to
create the proper column to begin with. (Just my $0.02 on the
migrations)
-Chris
On Sat, Apr 3, 2010 at 6:24 AM, peachygifts <m.ward@leythers.com> wrote:
> The admin side of my extension is now working: an admin can set a
> product to be personalisable, and can then set personalisation options
> against a product.
>
> Now I would like to display these results of these options to
> customers:
>
> The product has a personalisable? attribute. The product may also have
> many personalisation_options associated with it. Each
> personalisation_option has name, title and max_length
>
> Step 1 now has me a little flummoxed: I need to build fields on the
> product page for each personalisation_option associated with a
> product, rendered as a label with title as its contents, and a text
> field that limits to the number of character specified in max_length.
>
> How do I go about this in spree / rails?
>
> For anyone interested in helping, the current extension can be found
> in its current gestation at git://github.com/peachygifts/spree-personalisation.git
>
> Thanks for your help!
>
> Michael
>
> --
> You received this message because you are subscribed to the Google Groups "Spree" group.
> To post to this group, send email to spree-user@googlegroups.com.
> To unsubscribe from this group, send email to spree-user+unsubscribe@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/spree-user?hl=en.
>
>
--
You received this message because you are subscribed to the Google Groups "Spree" group.
To post to this group, send email to spree-user@googlegroups.com.
To unsubscribe from this group, send email to spree-user+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/spree-user?hl=en.
No comments:
Post a Comment