Ryan H.

I still utterly fail to see why they did this. It doesn't aid understanding, it doesn't make things clearer; I don't imagine it makes things any faster either.

I would definitely like to see some way of doing this as well, but I can assure you that it was removed for its CSRF potential.

I imagine this has already been stated, but the report center is quite lacking in finesse compared to what it was in 2.3... Two changes in particular that I would like to see made to it: - The ability to view the report and comments directly from the topic via an AJAX popup, a la warn logs. - Moving or hiding [spoiler-like] the post in post reports, so that it's not necessary to scroll past the [sometimes multiple-page-long] post in order to see the actual report. In general, it seems to me that the system as a whole should be more streamlined and conducive to handling reports en masse. The 2.3 application had that; 3.0's doesn't.

Yup.

You effectively want post revisions. I could see that becoming a huge sap of resources, especially on larger or more active boards.

http://community.invisionpower.com/index.php?app=downloads&showfile=2264 Install, enable, enjoy.

As in, one person can only give so much reputation within 24 hours [the existing setting], but they can also only give so many reputation points to one individual user consecutively [what he's proposing]. Not that you can control the limits for each user individually. [Although being able to disable it for specific users would also be useful.]

But you can't limit it by user. I fully support both additions.

What is breaking about your skins? There shouldn't be anything that causes them to stop working properly outright.

Chances are he never fixed his account when the changes were made. I'm fairly certain he has an active license [but who am I]. Concerning your account, see here:

If you think ahead, you can do that part yourself by creating a new skin set before upgrading, changing some small thing in the stylesheet [adding a space] to mark it as modified, then upgrading and comparing for differences.

3.0.4 is almost entirely bug fixes. If you want to know exactly what bugs were fixed, have a look in the tracker.

Any security checks would be server-side and in the source files; them being in the templates would only mean that it could be removed by the client making it utterly useless [that is, the security hole would be there regardless of the state of the skin]. I realize that there are conditionals which are not public-facing, but again, those would not be the final layer of security. The worst that could happen in that regard, that I can see, is that a form key would be mistyped [which there are a couple cases of in prior versions] causing a particular action to not work. Not quite board-compromising caliber. There is definitely the potential for bad things to happen through custom skins, particularly if the creator includes their own special PHP for whatever purpose, but for a general skin and especially one of Sherri's, I'm pretty sure that would not be the case.

Things don't work that way.

I can't see such a thing adding anything to a community but animosity and competition.

http://community.invisionpower.com/forum/420-modification-requests/ It's not the most frequented, but that's probably the closest you'll find outside of finding and asking individual modders. You're free to request modifications there, as well as offer a cash reward if you feel so inclined.

If the Yahoo spider goes to the search page, it's going to be displayed as searching the board. Similarly, if the Googlebot goes to the "add reply" page [you have posting enabled somewhere for guests], it's going to be displayed as replying to a topic.

I think you're right; unfortunately, I don't see the problem being remedied without the resources site being opened to more general access [for developers AND users]. And apparently that's out of the question.

You can probably connect with your FTP credentials, but would you really know what you're doing in the shell?

You could read and listen to what he says, instead of just insulting him...

CSS Expansion: I would suggest learning about advanced selector methods or alternate ways of identifying a particular part of the page. It can get messy, but I think you'll find that you can single out practically any element with the proper selector. That said, there are indeed a couple areas [none I can think of at the moment though] which would be much facilitated by an added ID. Board logs: Absolutely yes. I made this for our board myself back in April when we were trying to track down a compromised staff account, and the logs have proved absolutely invaluable in numerous instances since then. IPs not being logged in the system at all if the person never posts, messages or votes is an extreme disadvantage of the system, and login logs solve that perfectly. It may be trivial when integrated with IPB, but I would also suggest logging their current member group and whether they logged in "anonymous" or not, along with the rest of the info.

I imagine that would kind of screw with the license system.

Overall top posters is a particular filter on the actual member list [in this case, post count, descending]. Today's top posters is not and cannot be made as such a filter; the information involved is generated on the fly based on actual posts made in the past day. Could they make it follow the "hide from member list" setting? Probably, yeah. But the current behavior is technically correct.

I don't know if they've been released yet, but both of the classic skins have been upgraded as community projects. You can see and use them on this forum.

Personally, that seems rather excessive, especially with the existence of dynamic IPs. If someone manages to get through the htaccess protection, you've got bigger problems to deal with. Is it still possible to rename the directory in 3.0?