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
-
Searching for speed test will perform a search to find posts with either "speed" or "test" in it. I just did the search and all entries seemed to have one of the two words (at least) in them. A search for "speed test" (with the quotes) will find posts with those two words together. This didn't seem quite as reliable as it should be, but then again we are limited by MySQL as well. +speed +test should find posts that have both words, but not necessarily consecutively as in the last example. Admittedly #2 and #3 did not work as they should have. I'll have to talk with the other developers about that tomorrow, as I know some special character stripping occurs that might have affected this. We would love to install Sphinx (it's much more reliable, much more efficient, and allows for 2-3 letter searches) however we try to keep our installation as close to a base installation as possible so that we can easily catch major issues that will impact the majority of our customers, i.e. issues with the search system.
-
I'm afraid this won't be in 3.0.3.
-
[suggestion] Help topic for using the reputation system.
bfarber replied to Andy Millne's topic in Feedback
There's an open bug report about that. -
Hello, Please note that Invision Power Board is a commercial product and as such, you must purchase a license to use the software permanently and/or obtain technical assistance. You may find more benefits to purchasing a license here. If you are an existing customer, please log into your client center and follow the instructions for upgrading your IPS forums account, found at the bottom of the first page you see. We look forward to helping you!
-
TWOP = televisionwithoutpity.com As for the suggestions, yes, that's one of the things we did with the warn system on their site. As I recall there were also neutral warns, and the interface was overhauled. When you banned someone from warn panel they could see the reason (instead of a generic ban message). When they went to post, if they had an unacknowledged warn they had to acknowledge it (but weren't bugged with acknowledging it in the mean time). I liked the changes overall once they were done.
-
You can manually add an ipb_rtl.css to your skin and it will override the generic one. As for your other request, no, it's not possible. That is EXACTLY what CSS is designed for: Cascading Style Sheets. The main CSS is set in ipb_styles.css (for example), but when using RTL the RTL CSS file is loaded afterwards and modifies some of the main styles to swap positioning and direction.
-
I can understand where you are coming from, but in my eyes that's a "cost of doing business". That's like running a hair salon and asking the city for free water - you don't use it or drink it, but you need it to do your work. I don't think the city would give you free water, myself. Realistically, though, you should be submitting a ticket addressed to management, I think, as they're likely the only ones that can really give you a yes or no in the end.
-
I don't really see any advantage to this myself. Further, it would probably annoy the majority of users, or they would set the password the same.
-
In reality, it would slow us down significantly attempting to maintain multiple versions of the board with minor operating system and webserver specific tweaks. It would not speed anything up at all, development wise, and there are very few server-specific functions that we would ever possibly make use of.
-
It's not necessary and I see no benefit to this option. You can already install IPB on Apache or nginx, for example (as well as most other webserver software packages).
-
You simply change your board url in conf_global.php to use https in this case. There's no need for a setting to do this. We have a bug report open on this and are likely going to add https support to the ACP when the login over HTTPS bug is fixed. I'm not sure yet if it will cover the entire ACP or just logging into the ACP.
-
Nice enough idea. I'd use it, but not sure how many others would.
-
It's something we will think about in the future, but not something on the horizon just yet.
-
Because only so many people would be able to benefit from such a feature, we've not bothered. As you said, ffmpeg would need to be installed, and the majority of our users don't have the ability to do this. Given the abundance of other suggestions that most users CAN make use of, this remains low on a prioritized feature list.
-
There's no magic "make faster" button, or "make faster" line of code we can add. If you are having specific issues it might be best to submit a ticket so we can take a look at your site. Perhaps you are missing an index on a database table. Perhaps there's a slow query that we've not seen to date that is running on your site. Perhaps you have customizations that cause this (for instance, I've seen the unreal portal cause massive slowdowns because it does a group by against topics/posts table on the homepage....bad idea). I mean, "make it faster" is a noble goal, and of course we work to improve performance with every release, but it's not black and white, and if there was something magical that could be done to instantly boost speed we certainly would.
-
You can download Converge in your client area, and then use the Converge Wordpress module for account sharing.
-
I'm relatively sure it was intentional. Just hard to remember specifics.
-
Yes, for larger sites the statistical difference will be nearly nothing. Care to take a guess how many sites use IPB that have about 100 posts though, that would instantly see the "bug" if we used the incorrect cached number? :P
-
Honestly, we don't recommend anyone to use InnoDB. The theory behind "row level vs table level" locking is sound, but in practice I've never seen any IPB perform better on InnoDB myself. At the end of the day, we cache this data where it's used on the front end for the purpose it's used. In the ACP on that one particular page, a correct/accurate count is desired, so we run a query. We can't simply NOT run count() queries in a PHP script like a bulletin board. I'm not sure what kind of resource offset you'd end up seeing if we tried to maintain an accurate count for posts on the front end - it's possible (perhaps probable) the overhead in recounting every time a delete occurs (which happens on the front end) could offset any gain you'd get from the once in a blue moon you might visit the specific page we're referring to here in the ACP.
-
Well then, I stand corrected. I suppose the new skin should likely be available with 3.0.3. (Keep in mind, I don't do any of the skinning stuff, nor do I coordinate with external skinners in any way, so Charles naturally knows a lot more about the status of the new skin than I do). Let's worry about 3.0.3 first.
-
A select count(*) query with no where clause is generally a very fast query, because database engines store the total number of records in internal tables/indexes. These queries should not cause any problems whatsoever. Further to that, how often do you load up the cache management page in the ACP? The queries are done to be sure you have the correct most up to date number. The caches on the front end do not take into account deleted posts, for instance. So if 3 posts are made, all 3 are deleted, then 3 more are made and all 3 are cached - it would reflect only 50% posts being cached, instead of 100%.
-
If you can point me to that, it would be appreciated. Like everyone, I miss posts and topics from time to time. :) Last I knew, the author was still fixing up issues and finishing application support in the skin.
-
It was an oversight I imagine.
-
The oldest tickets would have been submitted ~Friday, so they likely simply weren't gotten to before the weekend. Support is staffed shorter on the weekend. Your tickets should be addressed today I'd imagine.
-
There are alternate hooks available on the resources site for posts instead of topics.
