Matt
-
Posts
69,390 -
Joined
-
Last visited
-
Days Won
551
Content Type
Downloads
Release Notes
IPS4 Guides
IPS4 Developer Documentation
Invision Community Blog
Development Blog
Deprecation Tracker
Providers Directory
Forums
Events
Store
Gallery
Everything posted by Matt
-
Thank you! We appreciate you taking the time to post this.
-
As Brandon noted, we will remove anyone's avatar if we feel they are trying to mimic staff. That's not because we're incredibly mean and selfish it's just that it gets confusing for others if at first glance you look like staff. If Brian doesn't have the time to create and release a generic logo free version then that should be respected.
-
I will be around, don't wory. :) I can assist the techs if they need it and can deal with any critical issues if they arise.
-
This is just a one off. sphinx.pdf
-
Yeah, we have considered this. It wouldn't take too much effort to do although arguably each user will have access to the same data so I'm not entirely sure what the point would be. Both need access to members, posts, topics, forums, logs, etc. I can't think offhand of one table that isn't required by both systems.
-
The two biggest obstacles are legacy issues and size issues. No one with more than 500k posts is going to want to run queries to update or move the posts to a new system. It could potentially take hours to complete. Another consideration is size. Some operating systems impose a 4gb limit on a single file. We've had some customers who've hit this problem with the datafile for their posts table. Lumping all 'post' type data into one table will only exacerbate the issue further. You'll also have locking issues if a lot of applications are constantly reading writing to a single large table as well as maintaining indexes required for full text searching. It's one of those normalization theories that is sound but limited by the back-end software.
-
We are aware of the tracker category and have scheduled in some time to fix them. The pressing priorities are 3.0.2 (and all apps) along with MSSQL and the subscriptions manager. None of the bugs are critical and affect the ability to view information or make purchases. On a personal level, there's nothing more annoying than being criticized with an exaggeration. :)
-
This occasionally happens in IE7. A refresh should fix it. We've never been able to reproduce this reliably enough to look into it any further.
-
This is almost solely bug fixes and efficiency improvements. And better Sphinx support.
-
In all fairness, there is nothing stopping you from downloading all the resource articles while you have access and make your own offline archive. If you want access to the customer forums, resources articles and support then you just need to pay the $30 renewal for another year's access. :)
-
Thanks so much, that means a great deal to me personally. I'm going to print it out and hang it on my wall.
-
The resources site is for those with active support on their license. It's only $30 for 12 months for perpetual license holders.
-
Alexa rely heavily on users having the plug-in for their browser so I would be incredibly wary of any statistics that it generates. In any case I have no idea why it would consider IP.Board profiles separate from the rest of IP.Board. They quite clearly use the same mark-up, design and URL as the rest of the board.
-
Updated: IP.Subscriptions 1.0.0 Beta 3 is available now! We're pleased to announce that IP.Subscriptions 1.0.0 Beta is available for download from your client center. This is the second beta release of the subscriptions manager that is compatible with IP.Board 3.0. Many long standing bugs and issues have been fixed in this release including: Recurring subscription cancelation immediately ending subscription and demotes member Multiple currency issues Inaccurate reporting of totals Incorrect end date calculation after upgrading ...and many more As always, please do be aware that this is a beta product and should not be used in a live environment without testing first. Please also be aware that currently only the PayPal and Postal Method gateways work correctly. Other gateways will be converted over the next few weeks once the framework has been finalized. A fairly big change is how multiple currencies are handled. From 1.0.0 Beta 2 onwards you will need to specify a currency for each subscription package. This is to ensure that the correct value is calculated for payment regardless of the current exchange rate. If you are upgrading from a previous release and have non USD subscription packages set up, please go via the ACP and edit these to select the correct currency code to use. The following items are to follow in the next release: Pre-installed hook to display current subscription settings (You are subscribed to package X which runs out in X days) Force the user to cancel a current recurring subscription before upgrading to another Ability to renew a subscription before it expires (ACP configurable). Due to a bug since fixed in IP.Board 3.0.2, you'll need to ensure that the guest member group can view the board and that you do not enforce all guests to log in if you are testing with PayPal. Please report any issues in the bug tracker as normal.
-
I will be releasing beta 2 of the subscriptions manager later today. It was set for a release last week but I got a list from a heavy subscriptions manager user with some bugs and issues which I've been going through and the product is much improved because of it.
-
The main back-up runs at about 6:15am-6:20am my time and can last up to 10 minutes.
-
Again, we're discussing options for legacy customers. Anything right now is pure speculation for the sake of it. :) Just give us a day or so. We don't want to make anyone feel second class. That was never our intention.
-
It wouldn't be difficult for us to do that. It could join in the email address quite simply.
-
This has now been resolved. :)
-
Thanks for the update ;) As mentioned above, our turn-around is within 48 hours. Our techs are working flat out and we'll get to your issue ASAP. Thanks.
-
It does get quite complex, doesn't it? It was precisely this situation that we wanted to avoid as it is a bit of a nightmare keeping track of it all in the customer center. Paying the difference would only really work on the renewal anniversary so the first question we'll get asked is "My support is up in 5 months, can I pay 40% of the $20 to access the spam service now or do I have to wait until my support is up or do I have to bring my renewal forward to today in which case can I get a partial refund or credit on my last renewal?" etc. It's an ongoing issue trying to apply legacy licenses to new frameworks and models.
-
Ah yes, I did mean year! I appreciate that you would be OK with it, but we can't assume everyone will. In any case, we will review the feedback offered and take it from there.
-
Well, if we did we'd have to make it optional. I don't think that a current perpetual license holder who is used to paying $30 a year for support is going to appreciate a price hike.
-
It's very unusual to have those two missing from a standard PHP install, but there you go. We've seen odder things. In any case, I'm dealing with this issue now and have just updated you again. I'll close this topic as it's run its course and thank you for bringing this matter to my attention.
-
Honestly, it was never our intention to make anyone feel 'second-class'. We just introduced a new service to help combat spam. If there's enough demand for a separate pay-for service then we'll be foolish to not consider it. Please understand that we value all our customers and will always take on any feedback that's given.
