Integration with Virtuemart login

Myshoppings,
I just got into the site. You did have a template override for the Login/Register page. I renamed the following file:
/sr/templates/gk_mystore/html/com_jfbconnect/loginregister/default.php
to default_disabled.php

Once I did this, the extra fields showed up on the Login/Register page, I filled out the fields that were there and registered. My user (sourcecoast77) was properly added to the Shopper/Registered group and my profile was imported (fields from Facebook and the ones I filled out).

I would recommend you create a new template override for the loginregister form and make any new modifications you need to it. If you need help with how to do that, just let me know. I am glad to see it working on your site though

Ronen,
Your next..

Ronen,
Just did a little more checking on your site. You look to be using the SVN version of K2 v2.5. The most recent stable version of K2 is v2.4.1, which we test with. I tried putting the tools module on the Login/Register page with K2 2.4.1 without any issues.

We haven't tested with the SVN version at all, but can try to soon. Do you know when you got the snapshot from their repository? The modules have date of March 29th, which looking at the SVN log for K2, there's been a huge amount of changes in April and May, which may have already fixed this issue.

Let us know, and also, if there's a specific reason you're using K2 v2.5, that may help us with the background of why you're using it as well.

Thanks,
Alex

You can read more about what a template overrides is, and why to use it, below:
www.sourcecoast.com/jfbconnect/product-overview

Basically, you'll want to copy /components/com_jfbconnect/views/loginregister/tmpl/default.php to
/sr/templates/gk_mystore/html/com_jfbconnect/loginregister/default.php

Once it's there, you can make any modifications you want to the login/registration form. If you don't have any modifications to make, you don't need the template override. It's simply a way for you to make changes to the layout of a component without having it be overwritten when you upgrade. The caveat though is that if we make changes to that file in a newer version, you should try to re-integrate those changes into your override.. or else issues like you ran into with the VM integration can occur.

Hope that helps, and good luck!

Selwyn (or anyone else in reading through this thread),
It's probably best to start a new thread for new questions about integration with Virtuemart. This thread's become a little untamed with discussions going in new directions. However, as to your questions:
1) Yes, we've tested JFBConnect quite extensively with Virtuemart and think it's working well. We're helping a few users in this thread work through some teething issues, but so far, nothing's been directly related to JFBConnect. However, please note that the current implementation of Virtuemart integration requires the Full Joomla User setting in JFBConnect, which will present a shorter registration form to the user. That's simply because to create a user in VM, we need some specific fields filled out, and it's information we can't get from Facebook.
2) As with every extension, there is a little overhead, and there are lookups to Facebook both server and client side. This will slow things down. However, it shouldn't be noticeable in really anyway. With JFBConnect in general, we rarely (maybe ever 3 months) get posts about slow-downs. When we do get those posts, it's usually do to a site configuration or server issue.
3) The Like button is not automatically added to products yet. We're working on adding this ability, but for now, it's easy to use the {JFBCLike} tag in the VM template or description for the products, or the JFBCLike module for VM menu items.

If you have any further questions, please start a new topic

Thanks,
Alex

Ronen,
I think re-installing K2 fixed the issue you were seeing. Last I was on the site, it was still showing the K2 error.

As for the Login button not working on product pages, it's because you're double-including the Facebook Javascript API (all.js) with the Like/Recommendations button. You should either switch that out for the JFBCLike module, which should do the same, or modify that extension to remove the script call to all.js (which JFBConnect is already including.

I'll look into the admin issue shortly. Never heard of that before, or can't fathom why JFBConnect would do that (if it is), but hopefully should be easy to debug.

Thanks,
Alex