Jump to content

Michael

Clients
  • Posts

    23,640
  • Joined

  • Last visited

  • Days Won

    114

 Content Type 

Downloads

Release Notes

IPS4 Guides

IPS4 Developer Documentation

Invision Community Blog

Development Blog

Deprecation Tracker

Providers Directory

Forums

Events

Store

Gallery

Posts posted by Michael

  1. Anyone else having issues getting the newest IP.Downloads from their client centers? I got everything else just fine, but the download for IP.Downloads will never start for me for some reason, the browser just keeps spinning.

  2. There doesn't appear to be any way anymore for third party applications to interface with the ACP help system: the section at the top of each ACP page that says "Get Help With This Page". It would appear that is now set to always just look and see if it can find content to grab from the http://acpdocs.invisionpower.com/ page. That does make the system cool in that you guys at IPS can update these docs and the help we get on our sites gets immediately updated on the fly, but it means that third party guys like myself have no ability to tie into that.

    Are there any plans to either let us add to this database or have some other way that we can hard-code in our own help text into our apps?


  3. The problem is we don't want to reveal too much about how the system works or spammers could just find a way to trick it...



    Yes, that's completely understandable, and I figured that this was a longshot anyway. It would just be nice to give folks that I think are being incorrectly caught by this at least some idea of why they got flagged.
  4. Is there any way now or planned where we can get more information on the hits our sites are getting on the spam service?

    The reason I ask is because I got a level 4 hit on a registration over the weekend from someone who was a customer of mine on another site, and I'm reasonably certain he is not a spammer. I checked his email address and IP address on another site that stores this sort of thing (not sure if I should post the link or not, but they've been mentioned in the general discussion of forum spam before) and while his email address came up with nothing there were a few hits on his IP address. But from what I can tell, in his physical location any number of folks could end up having that as their public IP address on any given day.

    I'm just wondering if there's some way where we can see what it was that flagged a particular registration, as I'm sure this is something likely to come up again with other folks too.

  5. In IP.Board 2.x, on the page where we manage our skin templates, you could easily tell which skin group had one or more modified skin templates in it as the little icon beside it would be red. This functionality was removed in 3.x. I found this to be helpful for a number of reasons, and would like to see it return.

    First, if an upgrade to the forum software modifies some skin templates, the upgrade script won't touch your modified skin template groups, and you'll have to patch those manually. When we look at a difference report, we used to be able to quickly see whether or not any of the templates changed in this new version needed this manual patching; if you could see that only 3 of your skin's template groups had been modified it made the job of patching a whole lot quicker. Secondly, it can be kind of an annoyance on a development board where you do things like test out code snippets. Again, when you upgrade that board, any modified templates you had won't get updated, so you may run into issues where you just fiddled with a bit of code, forgot to revert it, and now you have some code for the page that is out of whack.

  6. Since it often happens that a new version gets released, some bugs slip through the testing process and a new build of that version needs to be uploaded to our client centers, I think it would be very helpful if the Your Downloads page where we download our copies of the software showed the date (or some other such indicator) of when this particular version was last uploaded. Maybe a build number there would be a good idea instead?

    I'm just thinking of all of the topics we get where folks talk about bugs they have that have already been fixed, but they might not necessarily have known the version was rebuilt.

×
×
  • Create New...