9
Generating the checkboxes
Take a good look at what you're trying to achieve, and what you're actually doing. You want a list of checkboxes that contains all options for a given Checkboxes field. So, for example, say your mbr_fieldname contains 3 checkboxes for primary colors. In that field's settings, you've added the three colors in the Multi-Select ...
5
Your question is not very specific, so we can't give you specific answers... however EE can handle all of this stuff, but it does take some planning. Here are a few comments in no particular order that may help...
Firstly I'd recommend ditching Structure, as you'll be fighting it at every step for control of your URLs and you could also find that it hinders ...
4
I made a flowchart to visualize the implementation
Basically it comes down to these steps:
Add product to cart (Store)
Cart overview - proceed to checkout (Store)
New vs. returning customer / Login - Registration form (Visitor)
Final checkout, here you will pass the visitor member data into hidden store checkout fields
Done :)
4
The most likely culprit is an extension using the entry_submission_end hook (http://ellislab.com/expressionengine/user-guide/development/extension_hooks/api/channel_entries/) that is getting hung up. (It'd be after the entry_submission_start/ready hooks, since it's saving the entry)
Your best bet is to disable all the extensions, and to see if the problem ...
4
"When updating username, screen_name or password inside the update form providing the current password is always required except for super-admins and the parameter does not have to be specified." Source: http://ee-zoo.com/docs/visitor/tags/update.html
Even though the user may not explicitly be updating their username, for example, since the field appears in ...
4
I have recently completed a build using Store 2 and Zoo Visitor, I ran into this issue but came up with a working solution.
{exp:store:checkout
next="cart/review"
register_member="yes"
disable_javascript="yes"
require="name|order_email|address1|city|state|postcode|country"
error_handling="inline" error_delimiters='<div>|</div>'
}
...
4
Probably you have some broken conditional tag. The conditionals are more strict since 2.9.
3
I've done it on a site I worked on a while back. My memory isn't fresh, since it's been handed off to the client and my hands are completely off it, but I can tell you that it does work — it's just a bit tricky.
As powerful and awesome as Zoo Visitor is, you have to remember that you are basically duplicating data from EE's native member database into its ...
3
Go to Add-ons --> Modules --> Zoo Visitor --> Troubleshooting, it should be there.
[edit]:
In Add-ons --> Modules --> SafeCracker, always check to see if anonymous registrations are allowed.
3
There isn't anything built in, but not too long ago John Henry Donovan did a little write-up on implementing something similar with jquery plugins that might help you.
http://johnhenry.ie/articles/chained-selects-for-expressionengine
3
I have nearly the same setup (Store 2.0.3, EE 2.7.2, Zoo Visitor 1.3.29) — and I'm still unable to get Store's billing info fields to become pre-filled with an already-registered, currently-logged-in member.
For the time being, I'm grabbing that data from ZV, like so:
<input type="text" name="billing_last_name" value="{if logged_in}{visitor:global:...
3
This was a bug in Store, where mapped Zoo Visitor member fields were correctly saved after placing an order, but they were not loaded for new carts.
This has been fixed in Store 2.1.0:
Fixed mapped Zoo Visitor member fields not being loaded for new orders
https://exp-resso.com/docs/release_notes.html#store_210
3
Unfortunately you can't make the required fields conditional. The Store/Zoo Visitor/Channel Form fields provide an option to set specific fields as being required but if you set these then they will always be required on form submission regardless of which option the user selected.
For this reason the best solution is to NOT set them as required fields in ...
3
Create a hidden template that is just the logged in username only. Then load it in via jquery ajax .load(); Once login is complete as well.
if (event.success) {
member_favourites = "5";
//do something
$("div#username").load("_username.html");
}
2
From OP in comments above:
Just wanted to follow up and take credit for a simple mistake that monopolized more time than I'll ever admit. Turns out in my zoo form I had "new_row_0" in one of my hidden fields where it should have been "row_new_0".
2
This will most likely be to do with parse order. EE templates get processed in layers rather than top to bottom and you're using a complex conditional. To move it up the parse order try this:
{if logged_in}
{embed="myfig/upload-view"}
{/if}
{if logged_out}
{exp:stash:set name="login_form_return" scope="user" save="yes"}{segment_2} {/exp:stash:set}...
2
So after going to EEUK13 and seeing Ben Croker's talk, we're going to be using his lovely Open API module to deal with this stuff. If anyone wants to check it out, here's the link:
https://github.com/putyourlightson/open-api
2
Does this help from the Zoo Visitor docs?
http://ee-zoo.com/docs/visitor/tutorial/mailchimp-integration.html
2
I disabled MX Notify Control and everything began working again. It looks like that was the culprit!
2
Ben Croker of PutsYourLightON has been working on an API specifically designed for CRUD functionality. You should take a look at it here... http://www.putyourlightson.net/open-api
And here is the repo for it... https://github.com/putyourlightson/open-api
I have messed with this some and it has some great potential.
2
It turns out the issue was that in a checkbox field, neither "Populate the menu manually" or "Populate the menu from another channel field" was selected. I'm not sure how I managed to not have either radio button ticked, but that was the problem.
2
You can do this using
{exp:zoo_visitor:details url_title="{segment_3}"}
{exp:channel:entries channel="blog" author_id="{member_id}"}
<h2>{title}</h2>
{body}
{/exp:channel:entries}
{/exp:zoo_visitor:details}
But by performance I would choose query:
{exp:query sql="SELECT author_id FROM exp_channel_titles ...
2
I have answered this question asked previously
I have recently completed a build using Store 2 and Zoo Visitor, I ran
into this issue but came up with a working solution.
{exp:store:checkout
next="cart/review"
register_member="yes"
disable_javascript="yes"
require="name|order_email|address1|city|state|postcode|country"
...
2
Visitor channel fields can be mapped to native EE member fields when you prefix them with "member_" and the field_name has to match http://ee-zoo.com/docs/visitor/tutorial/working-with-native-member-fields.html
2
Whilst I'm keen not to see this site become a 'do-my-homework-for-me' -type thing, I quite fancied having a go at this and had both some spare time and magnanimity... so please try out Perfect.
It's very basic at the moment, but let me know via the Devot:ee forum of any extra features you need to make it useful.
2
I think, Customer Account Number would be unique for each member so based on the Customer Account Number, the member id can be fetched. That member id can be used for manually login a member.
You should see here: Manually login a member in ExpressionEngine
There is another way also. As you can get member's username also with Customer Account Number so just ...
2
Natively it would be tough. You could set their member group to have access only to a particular status, but that would take the member entry out your "regular" loop (since it would affect the status on an existing entry and not be doing version control, leaving the previously approved version in place).
Since with visitor members are entries, Better ...
2
It would be good to see the template code you are using.
Whilst the Addon may appear to be working for you on the site, it is highly likely that it is incompatible with that version.
Read upwards of the improvements and in particular to File upload, authorisation methods and Safecracker changes:
http://ellislab.com/expressionengine/user-guide/about/...
2
Per the comments in the question you linked to, Store doesn't support mapped member fields during registration with Zoo Visitor (due to ZV not correctly handling member registration hooks).
So your only option is to use the workaround in that thread, or craft your own workaround.
Alternatively, as I mentioned in your last question, you can simply create a ...
2
If you are updating the users member data stored in Zoo Visitor outside of the normal checkout process of Store you should be using the {exp:zoo_visitor:update_form} tag pair instead of the {exp:zoo_visitor:details} tag pair. The update tags allows for:
The update form tag can be used to update native member fields like
password, username, screen_name, ...
Only top voted, non community-wiki answers of a minimum length are eligible
