mld11

Just a simple question.

When you file a dispute against IPS for an issue like shawnking's, will IPS issue a refund?

To the best of my understanding, he paid for the products, but does not get to manage his own purchases. So, if he (since he already has) files a dispute with a reason such as, I paid for this product, and cannot use it on my own board, will you issue a refund and remove the product from that account?

In order to receive support, please make a topic in the Peer-to-Peer Technical Support -> IP.Board section, while signed in under your Active Customers account.

Is it possible to make use of reCAPTCHA as an available option in the Security section (System Settings) and select which Usergroups will use it, or just add a "Yes", "No" basis in every Usergroup?

I know it's built into Guests, if you allow them to send PMs.

I second both ideas. :o

+REP

I second both ideas. :o

+REP

Hello,

I searched in my admin panel, but couldn't find this feature; I was wondering if you can add the option to disallow potential members to signup using the same password as their username (username=password)? This is a big security issue with forums at the moment as you could just extract the member names and bruteforce the forum. The current "login security system" does not block this even if you dont use proxy servers, due to the fact that you are targeting seperate member accounts instead of the same member account.

I know that it is plain stupid to use the same username as your password, but there are just many people out there who still prefer to do that to remember their password easily.

Looking forward to your reply.

Thank you.

Cem

How about an addition to this, on the registration screen let the user, choose a RANDOM generated password (based on what they want) - than have it e-mailed to them (incase they ever forget).

Is it possible to make use of reCAPTCHA as an available option in the Security section (System Settings) and select which Usergroups will use it, or just add a "Yes", "No" basis in every Usergroup?

I know it's built into Guests, if you allow them to send PMs.

When useing "ACP Restrictions", if a group doesn't have access to something I would like it for them not to be able to see the tab.

add: Would be nice for the ACP search to only return results that group can use.

negative rep for posting my experience here?

there should be support tickets in that account from when i changed the email address and passwords and everything.

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

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.

Ideally, when users click on a link posted on a topic, the link should open in a new window and the following message would appear right before the redirect:

"We are taking you to the requested link... You are now leaving xxxx.com".

Perhaps it could be included as an optional setting in future IPB releases, just like in the Links System mod....

Would it be possible to add number of reputation points as a criterion for group promotion? I think this is a better way of determining quality of members than number of posts and days since joining.

IPS Staff manually screens all transactions to help prevent fraudulent transactions. This should have been noticed after you returned back to IPS after making your payment. Once they verify your payment is legitimate, they will send you another email saying "Welcome to <product_name>".

IPS Staff manually screens all transactions to help prevent fraudulent transactions. This should have been noticed after you returned back to IPS after making your payment. Once they verify your payment is legitimate, they will send you another email saying "Welcome to <product_name>".

Still, it was nice of him to let others know about possible errors they may experience in their upgrade, whether it was meant to be directed at one person or many.

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.