Publish Cost Always Free

jadedknight - August 11, 2007 - 11:51
Project:PayPal Node
Version:5.x-1.x-dev
Component:Code
Category:support request
Priority:normal
Assigned:budda
Status:closed
Description

I did everything correctly. And the prices are attached to their according vocab. But no matter what the publish price is always free! Any suggestions?

#1

gemini - August 11, 2007 - 20:12

I confirm this. No matter what price per node is it sells it for free :)

#2

gemini - August 11, 2007 - 20:56

Here is what I found:
In the module file line 250 doesn't work
$price = paypalnode_get_price(implode(',', $tids));
It works if I take out the implode function.

Also, when multiple terms are available, the Ajax field "Publication Cost" doesn't update itself... it seams like it updates on the page load, but not on the selection of the terms. Same thing with the multiple terms - updated on the pageload when default term is selected.

#3

gemini - August 11, 2007 - 21:20

Actually, when I take the implode function out - it only shows the price in the Publication Cost field, but submits the content as free one anyways.

#4

jadedknight - August 12, 2007 - 02:01

Crap- Anyone know how to fix this?

#5

baja_tz - August 14, 2007 - 19:00

Anyone ?

#6

budda - August 20, 2007 - 22:48

Have a go with tonights 5.x-dev branch changes i justchecked in.

#7

baja_tz - August 21, 2007 - 17:12

sorry, same problem still exist

#8

drupalina - August 26, 2007 - 08:00

I got it to display different prices for different taxonomy terms. It took me a few days, but the answer is simple:

Create a new Vocabulary and associate it with the content type you want PayPalNode to work with and make it compulsory. Then create some taxonomy terms within this vocabulary, so that the end user has a drop-down choice to sellect from. Then in PayPalNode settings, what you need to do is actually CLICK on the Vocabulary name that is associated with this content type (i.e. you need to sellect it). After this you can go ahead into content fees page and set the values accordingly.

BUT... even when you get different prices for different taxonomy terms to work, still this module does not seem to work.

I then go to create a new content of this kind and I can see that it shows the price of 5.00 in the grey price field. But when I click submit it takes me to my profile page and tells me that my content has been created. It also tells me in "Unable to process the payment for your content." And in the listings I can see that my content is indeed published. There is no paypal page of any kind. So I still don't know how to get this module to work.

By the way, I'm testing it on my localhost because I'm afraid as to what it may do to my online instalation. Could it be that the reason why I cannot get this module to work is because it is on my localhost?

#9

budda - August 27, 2007 - 21:35

@matrixfighter

Check your Drupal logs. The error message you reported is due to the simple_paypal module either not installed or not configured correctly, thus it wont redirect to PayPal.

The price calculation must be working, otherwise it would not even try to redirect to PayPal.

If you want to test in a real server setup, why not backup your live site dbase and install it? No changes to other content are made during installation, and the module can happily be deactivated when you want.

#10

baja_tz - August 27, 2007 - 22:56

I tried everything, cost is free in first version or there is not cost at all in second version (5.x-1.x-dev). When I put it this way:
function paypalnode_calculate_fee($node_id)
$price =100;
//$price = paypalnode_get_price(implode(',', $tids));
//$r = module_invoke_all('nodeprice', $price, $tids, $args);
//$price = $r['price'];
It gives me price 100 and redirect me to paypal. I created several taxonomies trying diferent content types - nothing. In first version (5.x-1.0) I was able to see, just for a second, real price and then it turn to free. Maybe I'm missing something. Do I need some other modules beside Simple PayPal to get it work. However excellent idea i hope it will work. Sorry about my English.

#11

budda - September 8, 2007 - 20:20
Version:5.x-1.0» 5.x-1.x-dev
Assigned to:Anonymous» budda
Status:active» fixed

This bug was caused by me always assuming the promocode module was at least activated, the $r['price'] was always null if no modules provided a hook_nodeprice.

So in CVS is a check for the array index first. This should rectify all problems here! (fingers crossed)

#12

baja_tz - September 9, 2007 - 16:29

O yeah! It work's perfectly! Great job, thank you.
I dont' know if it's possible to put in some future releases, option for user to click on some 'publish' link which will take him on paypal again, to republish expired node, and second, which is much more difficult i think,
to associate 'Content expiration time' with taxonomy like:
taxterms-1 price:50 expiration:180 days
taxterms-2 price:100 expiration:365 days
Of course these are just suggestions, module is excellent.
I'm newbie and trying to put some site, if i ever get it works, you can count on small donation, for some beer :)

#13

baja_tz - September 9, 2007 - 17:39

Ok there is ed_classified module which provides possibility to tie expiration time with taxonomy terms, so in Paypal Node module I can put 'Content expiration time = 0' and problem solved, but is it possible to provide option for republishing?

#14

budda - September 11, 2007 - 23:31

@baja_tx:

please post new feature requests in a different post in the issue tracker so that they can be addressed in the future.

#15

mikeydee - September 15, 2007 - 05:51

Hello,

Total newbie here and I am having the problem with the publishing cost always being free. read the rior post but i still do not understand how to fix this. CVS was mentioned, can anyone tell me what exactly this is? Any help is very much appreciated.

Thanks
Mike

#16

mikeydee - September 20, 2007 - 20:23

Hi All,

Me again. I have the module installed correctly but I am still getting none in the fee field. I have set up the taxonomy ters correctly and was able to set the price for each item. Can anyone guide me in the right direction to get this fixed. I love the idea of this module and am hopeing to get it working soon.

Thanks
Mike

#17

Anonymous - October 4, 2007 - 20:31
Status:fixed» closed

#18

johnphethean - October 11, 2007 - 16:40

Hey I've finally sussed this one:
Go back to the PayPal Node module page, and you'll see a description of the module and then links to this support request and several other links. One of them is the CVS repository. This contains updated files and files in progress for this module. Get the new files from there - you'll need all the nodepromocode ones (put them in a new module folder called nodepromocode), the updated paypal node ones (replace your originals) and the .js files.

Upload all that, and also install one called 'Jquery Update' if you haven't already. This deals with automatically updating the price box. There's another small task you have to complete for this, which is copying 'jquery.js' from the modules/jquery_udpate folder to the /misc folder in your drupal installation.

At this point, I removed the module installation of Paypal Node and then re-installed it from the modules page, but I'm not sure if you have to do that.

Now you'll have to update the database schema for the revised versions of nodepromocode and paypal node. Do this by running yoursite.com/update.php. (If your installation was through fantastico, you'll have to download update.php as described here)

Or you could just wait for the next full stable version of Paypal Node!! Phew!! Hope this helps!!

#19

solutionsphp - March 9, 2008 - 05:32
Status:closed» active

I upgraded to the 5.x-1.2 version of this module, but I still get this issue with publication cost always being free.

Maybe I didn't upgrade properly? When I ran update.php, the dropdown for this module showed "1, 2, no updates available". What am I supposed to select here? (I went with what was selected by default, "no updates available".)

JQuery 1.1.2 is installed.

Please advise.

UPDATE: False alarm! It was a problem in my database.... in term_price, a $tid was not set.

#20

solutionsphp - March 9, 2008 - 05:32
Status:active» closed

#21

poseidon123 - March 17, 2008 - 16:05

Still getting same problem and I have done all the things mentioned in this thread. I am using the dev version and have upgraded jquery.

So I have manually set $price =10; in the .module file, well it is certainly not the most genius method of solving the problem but atleast it worked. THough I am having a new problem now, http://drupal.org/node/185019#comment-772680

 
 

Drupal is a registered trademark of Dries Buytaert.