Unhooking the Payments API in Vantage?
To hook or to unhook? That's the question!
I've spent a few days now doing due diligence on Vantage as a potential platform for a site we're planning as we're drawn to the Payments API, i.e.
the pay to post feature with user dashboard.
For our planned site we are in a position to start charging to list from day one.
Having looked through as many working examples of Vantage I haven't yet seen one that is making use of the payments feature.
It just seems a waste that no-one seems to be taking advantage of this feature, yet we find ourselves in the position of needing the payment feature
but not the rest of Vantage as we have a clear idea on how to build our own directory with exactly all the custom post types, taxonomies and
custom fields using the Advanced Custom Fields plugin <- A total game changer of a plugin for WordPress!
During our research we keep seeing the same line, not just with AppThemes but the crowd over at Gravity too, and that line is: use the hooks available etc.
So, if we can 'hook' things up, can we by the same token 'unhook' things?
We're talking about unhooking and isolating the new Payments API so that we can use it on our own themes.
Another solution would be to 'unhook' the bits in the Vantage theme that tell the Payments API to connect with the custom post type 'Listings' and
then create our own custom post type and 'hook' up the new Payments API to it.
After all, if you look at the following screen you will see that AppThemes have used a Custom Post Type to generate the Payment Plans, and that object is then placed in a separate meta box on listing post admin:
http://cdn.appthemes.com/wp-content/...lan.png?4c9b33
This is a clever idea!
Judging from the way in which the new Payments API is constructed, it seems possible that the payment feature in Vantage can be isolated and with some custom coding be implemented on any theme, not just AppThemes.
Anyone here know of the possibilities with this idea?
Reply With Quote
You must be an AppThemes customer and logged in to view this response.