Amazon Honor System Payment Gateway

[d3bruts1d]

IPB already has a wide range of payment gateways available for subscriptions, here's a suggestion for another one... Amazon. :)

[skysober]

I too would like to see the Amazon Honor pay added, since it is more trusted and used more often than paypal for site donations.

[Brian Garcia]

I think it would be a good idea although I don't think it is as popular as paypal for it to become another payment gateway.

[Digi]

All gateways can be created outside of IPB development. All you need is to right up a new gateway API to handle it. Just like the login system, it is fully extensible.

[skysober]

All gateways can be created outside of IPB development.

True, but most modders have given up out of frustration that everytime a mod is made, that instead of a simple security patch or additional function patch, Invision changes the software with no backwards compatibility, and few of the mods work anymore.

Thus we are at the compassion of IPB to add what the customers request.

[Stewart]

True, but most modders have given up out of frustration that everytime a mod is made, that instead of a simple security patch or additional function patch, Invision changes the software with no backwards compatibility, and few of the mods work anymore.

Thus we are at the compassion of IPB to add what the customers request.

Not sure I agree with that, but regardless, that wouldn't apply to Subs Manager modules, they are seperate self-contained files :)

[Digi]

Amazing things, those API's.....just like commponents, it takes a lot of changes to actually "break" one. That and IPS is usually pretty damn good about making things backward compatible for a few versions should a huge change take place (ie 2.0 to 2.1). As to your other point, I've seen no lull in "new" modifications for each version of IPB on IZE or anywhere else for that matter. They come in just as regular as they did back in the 1.1.1 -> 1.3 days.....So no, there is no lull.

[mgalyen]

That and IPS is usually pretty damn good about making things backward compatible

hehe.. I just noticed this. I couldn't help but chuckle. If one does not have true multiple attachements -lost after version 2.1.7, an announcement mod, the report a post limitation, reading PM's, and the list goes on and on, not to count that as soon as a decent stable skin is made, everyone groans when a new version of IPB comes out, as we know one might as well throw money into the wind for having just paid for it, as of course it no longer works.

As to the Amazon Honor Pay, since this is now the most used method for sites to gain donations/subscriptions, we went with it and solved it by simply adding a donate link button at the top of the page. Amazon was kind enough to set up a linked page that allows member to use the pay system.

[Digi]

You are totally over exaggerating here. Any serious IPB developer/designer, or even someone that has used IPB for a little while and has a background in web development, knows what they are doing and can recover from version upgrades with very small down time. That is, of course, what a web administrator's job is. There hasn't been a skin "disaster" since 2.0 was introduced (and that was mainly due to all the new feature additions). There has never been a mod "disaster". The first time people groaned about modifications not working was 2.1, but that is simply because they didn't know of a good feature that IPS added in, "legacy mode", which allowed all 2.0 mods to work properly with 2.1 (which is what I was actually referring to in your half-quote). The main issue for 2.0 to 2.1 was finding where to put the edits but, sure, I'm sure we all still like to be using the non-OOP version of IPB pre-2.0 just to save some modification development. Most of the complaints about "mods not working" are from users that don't want to reinstall them when the new source is available and, given the fact that the source has obviously changed, people tend to assume that any new version means mod breakage.

Over all, anytime something changes, you will hear people groan. It is, after all, more work for them to do for, in many cases, a free mod/skin. Modding your forum and updating custom skins is a power user ordeal and not meant for the casual forum admin with limited experience in HTML or PHP. If you have "issues" with new version and modification re-installations, perhaps you should re-evaluate the mods and/or number of skins you have installed. Perhaps even consider having someone handle this stuff for you. Sure, it costs some green, but you don't want to worry about it right?

Instead of looking at "redevelopment time" (which is extremely limited in the right hands), perhaps you should look at all the things that IPS has added to help users transition properly through versions huh?

2.0.x (not sure exactly when) - Skin difference tool to compare older customer skins with the new version's Master Template
2.1 - "Legacy mode" to allow for backward compatibility with 2.0.x modules and components
2.0.x - started releasing partial "upgrade" packs in order to limit the number of files replaced during the upgrade process. Used to help people whom modify their forums limit downtime and time spent re-installing those mods.

These are pretty big deals IMO. Things IPS never needed to include, but did because they wanted to make transitions easier for you. Additional things that can help you limit downtime include:
-Creating difference files against your current files and the new. Most likely, unless you are super-modified, very few manual "updates" will be required per version and a good file difference tool can apply the new changes quickly.
-Make use of "child" skins in the ACP and only edit those. This way, when your skin author comes up with an update to a skin you might have further modified, you can quickly re-apply your changes to the new version using the skin difference tool.
-Don't use modification or skins with limited "free" support. Limited by time available, not necessarily anything bad. Any company that was erected to do custom services to IPS software, and releases things free, typically updates their work quickly in the event of a release.
-Creating a Development forum for you to work on setting up a "new release" can greatly reduce downtime. This allow you to basically copy the changed files over to the main site once you've got everything in order and simply run the upgrade scripts for database changes.
-Lastly, and most importantly, you don't need to upgrade the second a new version is available, excluding a security release (but these typically don't hurt skins or many mods). Give the mod/skin developers the time to upgrade and set up your own upgrade plan for your forum. Having a plan can make a huge difference. Besides, if you take a month to complete your plan and get ready, many 0-day issues will likely be fixed in later bug fixes.

I'm glad you found a solution for your pay system :thumbsup:

[bfarber]

At the end of the day, while we ATTEMPT to accommodate users who modify or skin their boards, our primary focus must be, and will remain, the default software - unfortunately it's simply not possible to take into account all the modifications and skins available. We have to fix problems and add requested features in the software - you have to determine if it's worth applying our fixes. Nobody requires you to. :)

[mgalyen]

We have to fix problems and add requested features in the software

So true, and well understood. Yet when features are removed it is extremely frustrating. As all know, community forums are used for 3 main things. Text communication, photographs, and video.

In the text area, IPB is most definately 100% of the time the leader and best.

In the photos attached or linked withing the posts, with Deans mods, such as true multiple attachments, (pre 2.0 of course,) again 100%

In the Videos sharing, with the mediabox mod, again well ahead of all other forum software.

As to the skins finally being where they needn't be replaced with every minor upgrade, that sounds like it is quite an accomplishment and thanks to IPB for listening to the customers in this need.

Now that amazon can work with 2.0+ and the mediabox also works with 2.0+, the only major item that prevents upgrading is waiting for IPB to add true multiple attachments. Once they return this feature, then I, along with thousands of members whom actually use the software, will most definately be excited and thrilled.

I don't mind the work as a 'webmaster' to do upgrades, even if that takes days, and sometimes hiring help, if it gives faster software and more security. I do mind when the members get upset or frustrated because a feature is missing or lacking in compare to other forum types they also visit. IPB is the easiest for admin to use, but in the end, it isn't what admin want... it is what members see and use. They are the reason for the community in the first place. That is why I as an IPB customer, voice out what the actual forum members say, in hopes that IPB listens and takes their needs into account...

[Digi]

do mind when the members get upset or frustrated because a feature is missing or lacking in compare to other forum types they also visit.

I understand your sentiments here :)

Have you, by chance, had your members try out the new attachments system? Many would say that it is far better and easier to use than Dean's "multi upload" mod. Not sure if attachments are enable in the test forum here but, if they are, you should send your members here to test it out and see if they like it or set up a temp test site available to the public though a single test account (ie demo/demo). My guess is that they will be quite happy to upgrade, at least the bulk of them. :) If you are holding back, based on the assumption that your members will revolt, then it seems a bit silly :P

[bfarber]

We support multiple attachments - there's really no need (and it causes MANY more problems in the grand scheme of things) to have multiple upload boxes rather than the system we have now.