bfarber
-
Posts
163,911 -
Joined
-
Days Won
346
Content Type
Downloads
Release Notes
IPS4 Guides
IPS4 Developer Documentation
Invision Community Blog
Development Blog
Deprecation Tracker
Providers Directory
Projects
Release Notes v5
Invision Community 5 Bug Tracker
Forums
Events
Store
Gallery
Everything posted by bfarber
-
We import a name, a proxied email, the profile image, and the status. I think that's about it (maybe some other small details like birthday, can't remember). Facebook already cleans this, so there should be no injection possible.
-
IPB already supports native fulltext searching with MySQL. It's an improvement over the older method (post LIKE '%something%') naturally, but it's still not that efficient on a huge board, and unfortunately there's really little that can be done for us to make it more efficient. ;) That is why we've introduced Sphinx support built into IPB.
-
For what it's worth, I'd be interested looking into other alternative search solutions in the future (such as Lucene). The search engine in IPB is abstracted to the point where we can accomplish this in the future should there be a good enough reason. I think, though, that anyone interested in replacing their search engine would be happy enough with Sphinx anyways, so it's probably better to spend our resources on improving Sphinx than providing alternatives. Unfortunately, as Charles said, there's only so much that can be done about MySQL...
-
There's only so much one can do. You'll have to understand the technicalities of search before understanding why it's such a resource hog. ;) We do support Sphinx in IPB3, with improvements coming to it over the next few versions. If using sphinx, search is no longer usually an issue.
-
Indeed, wouldn't be much of a performance mode if search was still on. ;) That said, you're free to go re-enable it yourself after enabling performance mode. Performance mode is simply a shortcut that disables some unnecessary features that you can use during peak traffic times. You can enable/disable all of those features manually if you wanted, and you can mix and match at will (enable performance mode, and then go turn search back on for instance).
-
I said something along the lines of "our intentions at this point in time is to have final out before the end of June". That was back in April or so, I think. People, as they have a habit of doing, took that as "it will be here before June", naturally. Or as some sort of promise, which it clearly wasn't.
-
There are no plans to charge for subscription manager separately at this time. We are intending to release it as a community project once we've got it updated and running with IPB3 properly.
-
It will at least be another hour. Think that covers all the bases? Edit: This is an attempt at humor, and not an actual release timeframe/idea. ;)
-
It should be both a matter of days and weeks. I mean, if it was 8 weeks, that's 56 days. So either way you'd be right. :)
-
Ways to compensate for IPB 3.x not fully supporting IE6
bfarber replied to Fast Lane!'s topic in Feedback
In the skin just add Stop using IE6! (or whatever you want displayed here) </if> <if test="$this->memberData['userAgentKey'] == 'explorer' AND $this->memberData['userAgentVersion'] == 6"> -
Ultimately, the issue comes down to word-wrapping. The only way to "fix" it is to remove word-wrapping. This is high on my "wants" list because I think word-wrapping when programming is horrible. It's just an opinion though. Ideally in a future release there will be some options so people can set it how they want.
-
Ok ok. There is no way in IPB to turn off IP address tracking, nor will there ever likely be an option to do so. Hopefully that addresses your original post. As this topic has kind of taken a life of it's own, I'm going to close it now.
-
Ways to compensate for IPB 3.x not fully supporting IE6
bfarber replied to Fast Lane!'s topic in Feedback
IPB should function in IE6 (primarily because almost all javascript functions have proper fallbacks in IPB3), however it won't look pretty. We have stated we would like to work on IE6 display a little bit over time, but it is not a priority. The display can be worked on without breaking other things based on conditional style sheets. -
I like the idea of auto-expiring moved links. Would save from having to install a task to do this (which I know a lot of people did with 2.3)
-
We don't store the page number presently, so the data is not available to show you.
-
If we released an RC3, we'd just repeat the process. Everyone would find and report bugs in RC3, which we'd spend time fixing, then we'd get to the point where it's like "ok, we fixed over a hundred bugs in RC3, we should do RC4 just to make sure it's stable enough to be final". As someone else said, you take the plunge eventually. There WILL be a 3.0.1. ;)
-
That would probably about double the amount of time we take marking bug reports, and unfortunately that's not really in our best interests. When there's a visible bug, there are often 30 or more bug reports on the same issue (for instance, the parse error in the bulk mailer in RC2). I'd rather be fixing bugs, than showing members who didn't do a proper search why their bug was marked as a duplicate.
-
Generally when Charles notifies me he has found a bug, I go hunt it down (because he's usually reported it by that time) and mark it working as intended or not a bug. Then I go back and try to fix it later.
-
I didn't say I didn't respect the feedback. ;) Heck, it's all irrelevant to me (I don't do the skinning, nor do I use the buttons). Just saying, as a developer sometimes you implement something and you get some feedback that you just don't expect.
-
This is just one of those things you'd never imagine people would get up in arms over. :rolleyes: You'll be happy to know the buttons are defined in a skin template, so you should be able to move them where-ever you like. :)
-
You might be able to do it via a hook, though it could be challenging since so much of the moderator functionality is handled through a separate class file. I haven't looked into it.
-
There's no technical reason it couldn't be done. We simply used the first format. I can't think of any specific underlying cause.
-
It's not a bad idea, if there was an on/off setting. That's my personal opinion on this. ;) Would allow me to move some topics without having to leave the "Moved to:" link.
-
You must have missed the beginning of this second page Arctic :P
-
There are upsides and downsides to different methods. With having view new content use a different template, everyone that is unhappy with how the view new content page appears (and there are some vocal members unhappy with it) can skin that page to look closer to ipb2, while leaving search results themselves more modern (for example). We tried to follow a pattern of one template per page. (Note, active posts and view user posts/topics have their own separate templates as well ;) )
