Mark

Possibly, if you submit a ticket I can have a look into it :)

It's been there since 3.0 was released ;)

I'd recommend expanding any help pane (click the icon next to close) as you're right, it's hard to see everything in that little window.


Our plan with documentation at the moment is to provide some guides for the areas that can't be covered inline (i.e. getting started, skinning) that take a more "examples" approach - the inline ACP documentation will continue however to be the main documentation source.

The problem with that massive pdf we had for 2.3 was not only was it difficult to update, while it seemed very thorough, the whole thing was pretty much "To add a forum, click 'Add Forum'" - which isn't really very helpful. We much prefer the inline help.

The habit one should be getting into is using the ACP search to find the page you need, and then use the inline help if you need it. Once you get used to it, I think you'll find this easier than opening the pdf, searching that, and then going back and forth from the pdf to your acp to do what you want to do.

Your server doesn't meet the requirements for IP.Board 3.0 - specifically, you don't have PHP5 installed.

Your host will normally install it for you if you ask them and you can download our requirements checker script here to check you have everything you need.

If you have any other questions or concerns, please submit a ticket or post in this forum. Thanks :)

I remember seeing your phone message, there was no number to call you back but I replied to your ticket as soon as I saw the message.

If you're still having problems, PM me the ticket ID number and I'll take a look for you :)


After one minute of being on hold, the phone system will automatically transfer you to an operator who will take a message, and then we'll call you back. Most customers find this preferable, particularly if they're calling from abroad and are paying for the call. Even if you're first in the queue - we can sometimes be on the phone to one person for a very long time.

Your tickets have been received by the system and will be addressed by a technician shortly.

We are currently experiencing a much larger than usual number of tickets and so it may take slightly longer than usual for a response. Our guaranteed response time is 48 hours, however, which all of your tickets seem to be under.

Thank you for your patience during this time. If you have any further questions or concerns, please let me know :)

Do you have a ticket ID number we could look up?

I have responded to your ticket.

Please let me know if you have any other questions or concerns.

Edit --> Use Full Editor on the first post in the topic :)

Please submit a ticket for support :)


invisionpower.com/customer

For the signature issue: that's a known bug. You need to run an SQL query on the posts table (I think it's the use_sig column needs to be set to 1).

For the login issue: you shouldn't have uninstalled the converter app. The converter application keeps a record of the conversion, so when you log in, the authentication logic sees you ran a conversion, and applies the correct login function for the software you converted from. But when you uninstall an application, all it's data is deleted.

I'm glad your overall impression of the converters is positive :)

For those couple of issues - could you send in a ticket? I've not heard of those happening before, but if I have access to the site I can work out what happened and touch up the converters if need be.
Just ask for it to be sent over to the conversions department and it will find it's way to me.

As for passwords, they definitely should be working, again, a ticket will allow me to fix that.

Technically, since 3.0, it is a separate application - when you install IPB for the first time, it asks you if you want to install it, which you can decline.

The reason it is shipped with IPB is because it's always been there. It would be unfair to start charging for something which was previously free :)


As for it 'taking a back seat' - I guess it's got to a point where there's not much more we can do with it. By all means, if you have suggestions for it, we'd love to hear them :)

[quote name='G

I think some people tend to forget that the bug tracker is for reporting bugs and nothing more. Some people read through the tracker regularly and turn the reports into discussions - that's really not what the bug tracker is for.

If you are experiencing an issue that is critical to the running of your board, then submit a ticket and we'll do the best we can to resolve the problem. It would be far too time consuming to expect the developers to post a fix for every issue.

It depends when you purchased your license.

Best thing to do is send the sales department a ticket.

[quote name='G

What you're suggesting is basically the browser signature technique. While it's not necessarily a bad idea, it by no means mitigates all possibilities of session hijacking.
While browser headers generally remain constant for the same user, and are relayed between proxies and gateways, it's not something that can be fundamentally relied upon.
Also, it is possible for two users to have an identical signature, and a proxy may normalise the header values, making the check pointless in some cases. Also, the attacker could just make the user's browser submit a request to their own server, at which point they could capture the header values and manipulate what their browser is sending (a feat which is much easier than it sounds with a bit of social engineering).

Like I say, it's not a bad idea, it just won't improve security as much as it sounds like it might when you first hear the idea. And there's certainly no immediate threat that needs to be patched anyway.

Sessions are used on pretty much any PHP-powered website and there is no fundamental security vulnerability in their use. That in the URL is just the session ID, and is IP matched. While things like browser signature checks could be added; they do not really add any security benefit.

Obviously, you would never give out a URL to a page in your ACP ;)

The message used to be truncated in 2.x, but the problem was, if the message is truncated, BBCode has to be disabled (otherwise you risk a closing tag being truncated and messing up the entire page) - people said they didn't like this behaviour as if a message was heavily formatted, you just got a notification of BBCode tags.

It's apples and oranges though, for example, the Standard license doesn't include telephone support while the Perpetual and Lifetime did and that is still honoured.

Yes, sorry, my point was it was something most people will never need to do, and if you ever do need to, it would only ever be once or twice.

If the option to do it was public, then it could possibly be abused by people trying to have multiple boards on one license or what have you.
It takes only a few clicks for someone to do it through a ticket, and allows us to make sure people are getting rid of the old installation before it's changed to the new location.

If you need to change your license URL you'll have to contact account assistance.

Really, you should never need to change it.

Check the 'IPB_THIS_SCRIPT' constant, it is set to either 'public' or 'admin' before anything else gets done.

But how would the system know if a user is in the ACP before it initiates the database connection? It has to check the admin_sessions table to verify if a user is in the ACP.

Well worth it for someone who needs a response at the drop of a hat! :thumbsup:

IPB is crazy to only double the charge, should at least triple it ... but also guaranty the respose to be within 3 hours.