[PuntaCanaTours]

Awesome! Thanks for the clarification. That is just what I was looking for. I’ll be making the purchase later today.

[PuntaCanaTours]

Let me give you an example relating to what I do, then you can give me the solution.

Example:

I resell 20 different products. Some products have a margin of 5%, some have a margin of $50%. Because of this, there is no way I can pay affiliates 10% commission on everything they resell. If I was to do that, I would loose money on some products, while still making money on others. Because of this, I need to set my commission payout on a per product basis.

It is my understanding that the Affiliate plugin is incapable of doing this. The only way to accomplish this is within the shopping cart. Within eStore, I can set my commission rate on a per product basis.

Maybe I should have posted this in the eStore forum even though it is related to your Affiliate plugin.

1. Can I set a fixed $ amount on a per product basis by using your Affiliate plugin in conjunction with your eStore plugin? (Remember I have 20 products so I will be paying 20 different fixed amounts)

2. Is there a way to show the affiliate the amount they will make, either $ or %, on all 20 different products, realizing that each product will have a different payout?

Thanks

[PuntaCanaTours]

Thank you for your explanation.

[PuntaCanaTours]

Found the problem. It wasn’t CSS at all. It was another a filter. Just FYI, this messes with your code:

remove_filter( ‘the_content’, ‘wpautop’ );

add_filter( ‘the_content’, ‘wpautop’ , 12);

[PuntaCanaTours]

I just changed the theme of my site to twentyeleven, and I see what you are talking about. So there must be some CSS in my theme that is messing with your code

[PuntaCanaTours]

Can you please explain a bit more? I have looked at eStore-extra-shortcodes/shortcode_include2.php In that file you have functions that wrap the variable in brackets. $product_name .= “(“.$var1.”)”; Can’t I just do this $product_name .=$var1; to at least remove the brackets? I understand that file will be overwritten when an upgrade does occur.

Thanks

[PuntaCanaTours]

The only code I tinkered with is the custom.css for fancy4. There have been no tinkering or changes to the code or css on fancy1. And you can see the problem still exists on fancy1. What you see is exact how it looks after a new install. I have read the forum rules (3rd point) and dont see how that applies to me.

I agree that there should be equal spacing for variations, that is why I created this post. On my install, this is not the case. Does it have anything to do with the fact that when you look at the code you see variation1, variation2, and variation4? There is no variation3. And the extra space is between variation2 and variation4.

Thanks again

[Author]

Posts