Jan Krohn

Thanks for the move AndyF. I presumed I've posted it in the wrong section. 

As an active Lifetime License holder.

If I want to add the IP.Blog,IP.Gallery,IP.Downloads systems I pay a yearly fee for them (I have active blog/gallery licenses).

If I want to remove the footer copyright I make a one-off payment (currently considering).

If I want to use the new spam service... my "Lifetime License" is effectively ruled null and void?

I would happily pay a small additional fee (as I do with the other add-ons), but essentially I'm being asked to pay for another full license. Hello, I have one.

Am I missing something or is this a financially motivated drive to force Lifetime License holders into regular payments.

I am in total agreement with everyone else here whom has a perpetual license or lifetime license here. I have both the perpetual and the standard just for the record.

If I really wanted this on my board, I can't get because I not willing to transfer my perpetual to a standard for the mere fact that I would lose out in the benefits of the perpetual license has to offer. More specifically, I am not willing to give up on the free upgrades regardless of if I renew support or not with that license.

In order to get the extra features, we should pay an extra $20 a year without having to change the structure of our license.

Make a new "service and support" plan available to lifetime and perpetual customers and charge $50/yr ($25 / 6 months) for it. Then those who want the additional services can simply renew the more expensive plan. Why force us to give up our licenses?

Yes, you are not 'stripping features' for legacy licensed customers. Instead, you are forcing the 'legacy' customers to give up their licenses in order to use a new service. Unacceptable.

I have been an IPB customer now for about 5 years, and for me they have been brilliant, cannot praise them enough. I have no technical knowledge, And I have probably sent some very basic support tickets, but this has never been a problem, they are always answerd promptly and the situation has always been sorted quickly.

Keep up the brilliant work and the top customer support.

Kind Regards
Jack

The final version is available in Client Area. Thank you very much to the team of IPB for the surprise!

Zef :)

Regarding the subscriptions manager. I'd like to point out that all of us at IPS take it very seriously and no one here wants to see it neglected. We realise that many of you monitize your forums using the SM so we have no plans to remove it or make it a poor cousin.

Our immediate plans are:

- Refactor the subscriptions manager from 2.3.6 to 3.0.0 [Done]
- Tidy up the ACP interface [Done]
- Fix reported issues with expiring subscriptions, upgrades and PayPal [Done]
- Write hooks and add settings [To Do]
- Release to QA [To Do]
- Release Beta / RC [To Do]

I spent most of last week and identified and fixed several issues. Most of which can be back-ported to 2.3.6. More details to follow.

I'm going to switch that debug bar off. People just obsess over it.

Refresh. ooh x.xx secods.
Refresh. ooh, faster.
Refresh. Oh, a bit slower.

Etc.

Guys, we are on a VPS with other sites. We routinely have 500+ users online. We are being spidered heavily. Expecting loads of under 1 and load times of under 500ms is unrealistic on this forum.

Just wait and see how it does on your own server. And if it's 100ms slower, don't worry about it there are worse things in the world.

The thing is, with this release being RC 1, more people are actually using it in a live environment. Therefore, with much more usage than any of the Betas went through, more bugs are sure to find their way out.

I will admit though, the staff is doing an excellent job of fixing what bugs are reported, and fixing them quickly.

You really surprised me with this update!!

Congratulations!

(long interesting journey but almost there :) )

Thanks guys, go nuts and test it out as much as you can. Please don't be alarmed if we seem to take a minor step back with some stuff, I've fiddled with a few things, mostly:


Topic Marking CSS Caching Memory Debugging So let me know if you see anything odd with any of that.