I'd love to see some way to tie into the checkout process without having to create a listing. For example, say somebody wants to add an extra service like charging for stores or whatever, you would have to currently make them buy a listing package and do it like that, but what if you don't want it tied to the listing package expiration?
What I think could be done would be to add hooks or branches inside the payment provider code to create the amount and owner info, then specify a function to run when the provider returns information about the payment. I think this would open a whole new section of module ideas.
Discussion
What functionalities are affected by the move to jQuery?
It is really to early to say. The plan is to remove the cpaint ajax library with jquery and use it for javascript validation.
jQuery has a compatibility mode so it should be too much of a problem. I think it is the right choice.
I don't think any functionality of the standard script should be an issue, maybe conflicts with 3rd party javascript site owners add themselves.
I'd love to see some way to tie into the checkout process without having to create a listing. For example, say somebody wants to add an extra service like charging for stores or whatever, you would have to currently make them buy a listing package and do it like that, but what if you don't want it tied to the listing package expiration?
What I think could be done would be to add hooks or branches inside the payment provider code to create the amount and owner info, then specify a function to run when the provider returns information about the payment. I think this would open a whole new section of module ideas.
Maybe 4.2 or 5? :)
Hi guys. I added a feature request forum here: http://www.68classifieds.com/forums/feature-requests/
I don't get email notifications of comments here so I may miss part of the discussion.