I have been trying out lm_paypal and I can across a problem: I associate a content type with lm_paypal advert so that a user has to pay thru paypal before his advert is published. So, he composes his advert using the content type so that it get saved in his personal account. Now, to publish it globally, he hits Paypal subscribe so that he goes to the paypal page. But then he changes his mind and hits the 'back' button. In his account page, the status of the composedadvert still shows as unpublished. But, unfortunately, if you go to the front page (my published option is "promote to the front page"), the advert is published!!!! So, without paying, the advert got published.
Thanks,
Arindam
Comments
Comment #1
LeeMcL commentedApologies for the long delay but I've been pretty swamped.
I've tried to duplicate this locally but have been unable to. The code is such that the node only becomes published when it gets an incoming subscription for the node. I can't see how pressing back at any stage would get around this.
Can you tell me the versions of Drupal and LM_PayPal you are using, please?
Lee
Comment #2
arindamghatak794 commentedSorry about the late response. When I used this module, I was using this with a new content type I made called Request wherein people could submit classified ads to the site for a price. In Admin - Settings - Content type, it was set to be published and promoted to the frontpage. Now, when I tried using this module, when I went to the paypal page, but obviously didn't want to go any further since I was just testing it, I hit the 'Back' button. So, in this scenario, I was expecting the ad to not be published but it was indeed published. I am using Drupal 4.7.6 and LM_Paypal 4.7.
Comment #3
arindamghatak794 commentedAnother suggestion, just my 2 cents worth: I think it would be nice if the subscriptions were listed not on the profile page but on the edit section of the profile page. That way, it would seem a little less intrusive/annoying I think.
Thanks!
Comment #4
john franklin commentedClosing all 5.x and earlier issues. If this is still an issue, please reopen and update with 6.x or 7.x details.