Buying Points for Alphauserpoints

Hi,

We are developing a restaurant guide community portal and with the help of Hikashop 1.6 and AlphaUserPoints, we are building our payment structure as well. We know there is a payment plugin so that users can make payment using their AlphaUserPoints. We want to give the possibility to users who do not have point to purchase points from the website as well, in other terms, users should be able to purchase points from Hikashop using another payment option such as bank transfer, moneybookers etc. and then these points are automatically added to the users point account so that he can use such points to make purchase throughout the website for other services?

Thanks,

Tomy

Hi,

In the AUP plugin's options, you can configure points gains per product on a category basis (you can always have extra unpublished categories in your products in order to configure the points differently for several products of a same category). Then, the points will be added automatically to the user when the order of these products would be confirmed.

Can you explain a little more on the procedure for creating a couple " products "
that would really be points ? for instance, to sell 100 points for 75.00 or 150 points 100.00 as 2 separate products

These would go into a category called say "points" BUT in the AUP plugin
What are the exact options ( settings), because you only have 1 plugin to edit .
The points awarded; wouldn`t they have to be the same no other place to have several ?

ALSO I don`t want system to auto hand out points for purchases

Or am I missing something as usual ?

Hope explained ok and not too obvious of an answer ...

Thank YOU ! again ......

Hi there,

As Nicolas said, you just have to create specific products in Hikashop (in a category Points for example) and put them in a Category on which you apply the ratio you want.
For example you can in the configuration of the AlphaUserPoint payment method, specify the created category and give it a ratio.
So if someone buy a product in you category (the price doesn't matter), he will earn the specified number or point for this category, so he concretely "bought" points
Do not hesitate to look at the documentation and make some tests:

OK Eliot
I appreciate you getting back ..
Just want to clarify ...

If I have say 3 products 50 points, 100 points, 200 points
I NEED to have 3 CATEGORIES 50 points, 100 points, 200 points
and assign the each category a ratio (or amount) of points earned.

That the idea ?

Yes, that's the idea.

OK Thanks again ...
Just wanted to make sure had right ..

Thank You Nicolas ...

Nicolas,
I saw a previous post #55890
Talking about the options....
I tried what you all spoke of there... but no luck ..
I simply want the options to default to YES all the time.

We do a video clip store.. Videos are broken into clips..
Clips are sold as options under a product. We need it by default add all 3 clips
with the option to say no. Not the other way around ..

Am happy to provide access if easier for you....

thanks as always ..

Hi,

The solutions I'm talking about in that thread are for when you use characteristics in your option products. You probably must not be doing that which would explain why it didn't work. That, or you didn't modified the view file for the correct template, so you should check that.


If you don't have characteristics in your option products, you should add the line:
$value = $optionElement->product_id;

after the line:
$this->values[] = JHTML::_('select.option', $optionElement->product_id,$text);

in the file "option" of the view "product" via the menu Display>Views.

Hey Nicolas,
Thank you for your idea.
However after editing the file, there was no change...

The options still load by default as NO as opposed to YES

We Do NOT use characteristics as you thought.
Simply the options.

1 main product, 3 child products for each. buyable via the options.
Any Ideas ?

Again.. if you can/ like access can be provided if easier for you..

Hi,

The modification I talked about IS for when you don't have characteristics for your options as I thought actually so the modification should work. Please make sure that you're editing the view file for the correct template of your frontend, otherwise, you won't see any difference.