envonge

When you view a member in the ACP you can view all rep they have given and all rep they have received.

Someone should move this to the feedback forum ;)

Everytime IPS upgrades my forum software, I have to re-install every one of these hooks because the hooks aren't being updated with the forum upgrades.

With IPB 3.0.3 Upgrade, IPS Staff identified the following Hooks:

(T30) Bump Up Topics
(DP30) Top Reputation
(T30) Show Reputation in Topic View
(IM) Users Awaiting Validation
(IM) Global Forum Message
(IM) Sliding Quick Login

I just think it's a sorry excuse to say you only support the IPB 3 upgrade errors associated with IPS Created Hooks. The fact is that IPB is supported by third party mods. One would think that this problem would have been dealt with by now. This makes the third time I have had to uninstall these hooks and reinstall them. IPB UPgrades are supposed to be trouble free and work with Skins and Hooks that are already installed.

I hate to say this, as I have enjoyed the forum software, but these excuses are vein and the lack of support in trying to fix this problem has yet to be corrected. You would think that these problems would have been fixed by now.

IPS Staff: I hate to say this but the IPS Upgrades are becoming a real inconvenient Annoyance.

What am I talking about? Everytime there is a service update to IPB (2.0.1, 3.0.2, etc) the upgrade creates havok with the hooks that I have installed. Not only do I have to disable the hooks, but, they have to be un-installed and then re-installed. The upgrades are not anticipating already installed hooks and adjusting for them and it's becoming an annoyance.

Does IPS plan on fixing this problem or is this going to be a regular 'romp and stomp' action with every upgrade/update? For one, I would love to see this corrected.

Ok, so I purchased a license off of ize nearly 2 years ago, and all was well and good, until 2 days ago i try to login to my other account, display name, .Shawn, and find out it wont let me log in, so i try to recover my password, and it tells me there's no account in the system using that email address, so i find this a little fishy, so i contact support, and they tell me that the original owner has control of the account and that there,s no way to prove the account is mine, altho i have renewed it 2 times with my credit card, i gave them that info, gave them my email address that it used to be tied to, and pointed out the face that this guys name is scott i believe and the display name is .Shawn, i find this absolutely absurd that customer service, nor debbie will do anything for me. but really, what would they care, losing one customer wont hurt their pockets any..just my rant on the customer service here.

I am not sure what you expect us to do. By your own statement the account is not in your name it's in the name of the Scott you mentioned. Scott is the client of record. He could certainly login and change that information but that is up to him - we will certainly not go changing client login information just because someone claims to have purchased the license from a third-party site. Can you imagine the chaos that would cause?

alright, ill give up on it, filed a dispute on paypal, hopefully ill get my money back at least the money i paid for the license, just slightly frustrating when something like this happens. :(

this is like trying to talk to a friggin wall...

Hey guys,
So I'm not an expert (in anything), but I've been running a few pretty active forums for almost 8 years now (most of these years were IP.Board!). I've had to endure several server moves. I wanted to write a brief outline of my experience, since moving an active forum to a new server isn't the easiest thing in the world.

The dilemma with moving an active forum is that:
a) because it's active, you don't want your many users to tolerate any downtime.
b) because it's active, chances are your DB is huge and so this increases the time required to move over, and the potential downtime.

Moving a forum entails a few things:
1) Getting the code up and running on your new server
2) Getting the database moved over to your new server
3) Pointing your users at the new server. I'll assume you're sticking with the same domain so this will be just a DNS flick.

Solution #1: You could blindly do these three steps, but you'll be faced with a bunch of issues. The main one is that you will have two servers running off of different DB's, and there's no way to guarantee that the DNS change propagates at the same time for all your users. You'll have people posting and browsing the old forum, and people posting and browsing the new forum. Any changes to the "old" forum will disappear once everyone has propagated over to the new forum. Unacceptable.
Downtime: None.
Discrepancy: Yes.

Solution #2: To prevent the discrepancy between having and old and new forums running, you could just turn your board "offline" during the propagation period. The procedure would be:
a) turn the board offline on the old server
b) move the code/DB over
c) wait for propagation period
d) turn the board online again on the new server.
This will prevent your users from wondering where their posts went, but you have to remain offline for the DNS propagation period (which is on the order of hours, and reportedly can be even more). Again, unacceptable, because you don't want to be down for hours.
Downtime: Several hours, but you can post a nice message.
Discrepancy: None

Solution #3: Point both servers at one DB (DB-copy). The procedure is:
a) Setup/copy all code to the new server
b) Turn your forum offline.
c) Copy your DB over to the new forum
d) Point both servers code to the DB on the new server
e) Turn your forum online.
f) Flip the DNS switch and wait for propagation.
By pointing both servers at one database, you guarantee no discrepancy. That way, whether users are accessing the old or new server when DNS propagates, they will see the same things. You only need turn your forum off for the duration of DB copy, which you can probably pull-off in less than an hour, depending on the size of the DB.
Downtime: Probably on the order of minutes, and you get to post a nice message.
Discrepancy: None

Solution #4: Point both servers at one DB (DB-replication). The procedure is:
a) Setup/copy all code to the new server
b) Setup master->slave replication between the old and new DB's
c) Point both servers' code to the DB on the new server (which is the slave)
d) Cancel the master/slave replication on both servers
e) Flip the DNS switch and wait for propagation.
Essentially, this is the same as solution #3 but instead of having to turn the board off, you rely on MySQL's replication functionality, which lets your new DB mirror your old one. The one issue is that replication requires a bit of technical know-how. There's a good guide here. Also, that you will have a bit of cross-server traffic (for the DB replication, and from the old server's code to the new server's DB during propagation).
I just tried this on a site with several GB's worth of MySQL DB (forum, etc) with zero downtime as far as my users are concerned. A completely transparent move.
Downtime: None
Discrepancy: None


The devil is always in the details, and I didn't go into any of the technical ones. There's some good guides around about how to carry-out any of these steps, and they'd probably do a better job than I can. I just wanted to point out that there is a process whereby you can move a large, active forum in a way that's transparent to your users.