Jump to content

KT Walrus

Clients
  • Posts

    1,331
  • Joined

  • Last visited

  • Days Won

    1

 Content Type 

Downloads

Release Notes

IPS4 Guides

IPS4 Developer Documentation

Invision Community Blog

Development Blog

Deprecation Tracker

Providers Directory

Forums

Events

Store

Gallery

Everything posted by KT Walrus

  1. Yes. The PHP memory limit is a "soft" limit in that PHP only checks when requesting more memory at runtime if it has reached the limit. It is the same as for the other limits like post max size, upload max size, or cpu limit. Setting these limits high have no effect on execution unless the script actually needs the extra memory. For a well written script like IPB, you are only going to be affected by a high limit if the script really needs the memory for some operation and then it only hurts if lots of people simultaneously use lots of memory. If it was a real "hard" limit that upping it would really cripple a system, they wouldn't allow you to change it locally or in your PHP script. It takes no privileges to up a memory limit.
  2. Maybe this is old information. I got this idea by reading this article: http://carsonified.com/blog/features/webapps/serving-javascript-fast/
  3. I think the current approach to having lots of individual JS and CSS files on a page with some loaded by the minify script isn't quite as efficient as it should be. I suggest that you spend a little development time to implement a better solution. Since browsers are required to never cache a file that uses a query string, make all JS and CSS files use FURLs (e.g., /javascript/ips.attach.js) as an option to loading the files through index.php.Don't combine any individual files into one URL. Load them in the script individually with maximum "forever" caching headers.Include a version number/last modified timestamp for a JS or CSS file in the FURL (e.g., ips.attach.v93802339.js). Don't change the underlying file name on disk. Since index.php (or another script that doesn't log in) is used to serve the files, the script will simply return the file with the version timestamp stripped out. The timestamps can be cached but recached on demand or whenever changed through the ACP.Keep a minified cache on disk of all files so the file is minified once (unless its timestamp changes and then the minified cache should be invalidated).Since all JS and CSS would be served as FURLs with forever caching headers and the filenames are timestamped, this should result in most all browsers caching the files and only requesting a file to load only once. The key is the FURLs need to look static and not dynamic to the browser. By using the timestamps, the browser will download any changed files when the timestamp it sees in the FURL is changed, but otherwise will use the browser cache. Minifying isn't very important with this approach except for the first time the files are downloaded to the browser, but since you already use a dynamic script to minify some of the files (but not all), you may as well have this as an option when you minify. And, minifying provides a little obfuscation. I believe that one of the reasons that IPB3 feels slower than IPB2 for some is that the pages have lots of JS and CSS files that are loaded individually and some by using a query string (which some browser implement the standard of never caching files that use query strings - some browsers ignore the standard and cache anyway).
  4. I implemented a quick bbcode for showing pretty fractions, using this php code: { return preg_replace( "/\s*(\d+)\s*\/\s*(\d+)\s*/i", "<span style='font-size:80%'><sup>\\1</sup>& #8260;<sub>\\2</sub></span>", $content ); } private function _buildOutput( $content ) For [fraction]3/11[/fraction] it shows as: 3⁄11 (only the fraction height is reduced by 80% so that it looks normal) This works, but I haven't been able to figure out how to get the RTE to show the formatted fraction instead of the BBCode. What I really want is to implement a drop down menu that allows the user to just pick a formatted fraction from the drop down. Maybe all fraction up to 16th such as: 1⁄2 1⁄3 2⁄3 1⁄4 2⁄4 3⁄4 1⁄5 2⁄5 3⁄5 4⁄5 So, I've gotten half of what I want, but it occurred to me that IPS could implement this much better. I'd like to see a new dropdown in the editor to allow you to insert a fraction (from the list) and have this fraction appear formatted in the RTE editor.
  5. I would think you could get someone to mod your board to revert this behavior back to the IPB 2 implementation. Apparently, all that is needed is to exclude some forums when computing that information. I haven't looked at it, but it might be just some extra bits in a where clause somewhere.
  6. I hope Invision purchases the skin and includes it in the standard IPB distribution. Mobile access is increasingly important for many community boards and using the Lo Fi skin for mobile computers just isn't good enough. Count me in as one who will buy this skin on the first day it is available...
  7. Not really. I just want my Admin CP password to be different than my board password. That's all. I already protect my admin cp using the webserver. I suppose I could add HTTP authentication for the webserver, but it would be simpler to just store the admin cp passwords separately and let me change this password independently of my board password.
  8. Maybe I missed it, but I'd like to have a separate password for the Admin CP from the forum password for the admin account. I know I could probably just create a separate account for accessing the Admin CP, but it is more convenient to admin both the board and the Admin CP from the same account. Since you have to log into the Admin CP from a special login page, it makes sense to me that the Admin CP password be completely separate from the board password.
  9. Probably just about as many as use the media link dropdown! :thumbsup: Actually, I'd trade the media link dropdown for a special characters dropdown any day.
  10. I'd still like to see a user preference to enable HTTPS just for that user. HTTPS is slower and many users won't care to use this if it makes the board run slower. I also don't really want to enable it for everyone as it will just eat up more server resources for people who don't care about eavesdroppers. As for the ACP, I would think you would want the whole ACP covered by HTTPS since a lot (or some) of what you see and do in the ACP is sensitive. Of course, it is hard to see a hacker really going to the trouble to monitor all your traffic to and from the ACP. All they really would want is the ACP password. I restrict ACP to my IP (by configuring my webserver) so this is less of an issue for me, but I still wouldn't want my ACP password to be sent as plain text and subject to someone watching packets sent to and from my webserver.
  11. In addition to the option to use HTTPS for password pages, I'd like to see an Admin CP setting to allow the user to access the board using HTTPS all the time (a per member preference). Also, I'd like to have a setting to force all users to use HTTPS. Also, the Admin CP should be accessible only over HTTPS (by a setting). This is the way my GMail company email works and some users would like to have the added security of accessing a board over HTTPS. I know HTTPS slows things down a bit and puts more of a load on the server, but I think it should be a supported option (especially for corporate forums or forums where content access is only by login and some content is only accessible to some members).
  12. That set is pretty good. Maybe don't even need the Show All menu like the emoticons. That small dropdown would do for me. I want people to use symbols like
  13. I'd like to suggest that you add a special HTML characters menu to the editor, like the smileys menu. For example, I'd like to see commonly used characters in the dropdown and all characters in a side menu. The editor currently doesn't allow these codes to be entered using their friendly name (you must use the numeric version) to get such symbols:
  14. I'd like to have the ability to add a caption to each attached file (after the upload, but part of the post form) that would be shown instead of the "filename, size, downloads" default caption. If you are uploading a set of photos, it would be nice to be able to describe each photo individually (so the caption shows when viewing in the lightbox). The caption input box could appear between the filename and "Add to post" link when the uploaded attachment appears in the Attachments list. If the poster doesn't enter anything for a caption, then the default "filename, size, downloads" would be used.
  15. I'm surprised that no one has commented that this would be a good enhancement. My members are older and often don't have the skill to crop their own photos and it is important to me that all photos shown be cropped correctly to just show the head and shoulders of the member. Adding in JCrop to assist in getting properly squared and cropped personal photos would help a lot.
  16. I'd like to see some sort of support for uploaded video streaming added in IPB. That is, if the user attaches a video file to the post, the video could be processed into flv or H.264 video (using FFmpeg - which would have to be installed by the server admin) and played in a free third-party Flash player (like the JW Player). FFmpeg could be used to generate a thumbnail for the uploaded video to show as the attachment (like photo thumbnails do now for photos). Video streaming is becoming a standard feature of many sites and I see no reason that it shouldn't be supported by IPB like photos are supported. Of course, the feature should be optional since this could eat up a lot of bandwidth and disk space.
  17. This is only true for MyISAM tables. For InnoDB tables, count(*) with no where clause does a full index scan which can be quite time consuming for very large tables. You really should cache these values when their only purpose is for displaying stats (or cache them if the table is not MyISAM). MySQL has to do the full scan for InnoDB because InnoDB supports transactions.
  18. I'd like to see the RTE supported for Safari and other webkit browsers. I don't know what the technical hurdles are in providing such support, but I have seen WYSIWYG editors for forums that have no problem with Safari. so maybe it is now possible.
  19. I too have a need to add some filters to the topic view queries. I haven't looked into it yet since this is on my to-do list, but I would vote for some sort of query replacement/edit capability without modifying IPB source. Specifically, I'd like to see all queries labeled/numbered somehow and then an SQL hook that would feed the constructed query and the query label to the hook where it could be modified to add my extra where stuff or extra select columns just before executing it.
  20. I can't seem to figure out how to set up an RSS feed that is specific to the member. On my board, the members are restricted to viewing different content (some members can view some content while others might be restricted but could view other content. So, my suggestion is to implement an authenticated RSS feed that is restricted to topic posts that the member has permission to view. I'm not sure if there is a standard way to implement this, but I could see the RSS feed having a key that is specific to the member and that IPB remembers the last IP Address that the member used to access the board. Then, the RSS feed could check that the IP Address of the RSS feed match the last logged in IP Address for the member and serve up only the topic posts that are visible to that member for the feed. If the IP Address match fails, then a message with a link back to the board could be shown instead so that they can reset their IP Address so the feed works again. Anyway, however this is implemented, I would like to see it since my board is restricted for guests and I really don't want to be responsible for some members only information escaping through a wide-open RSS feed.
  21. I'll just hope that the skinning community comes up with a decent iPhone skin. It can't be that hard to do. Make some buttons that look like the iPhone theme and then put out very simple html for the various pages. Maybe I'm over estimating the job, but the iPhone is the majority of mobile browsing and deserves a decent experience.
  22. I'm revising my suggestion. I just visited webhostingtalk.com in Safari (spoofing my user agent to pretend to be an iPhone) and the skin they use is fantastic. Lo Fi just won't cut it in comparison. Everything is laid out very nicely. So, I'm upgrading my feedback to request that IP.Board come with a default skin designed just for iPhone/mobile users. Maybe Lo Fi is it, but it should have buttons and even the colors that iPhone users expect and can have Javascript. The iPhone just has a small screen so the skin should be written with that in mind.
  23. Just tried adding the viewport code shown above into the Lo Fi skin on my board and it works much better! There will also need to be some header changes so the Signed In line doesn't overwrite itself with the left and right links all smashed on top of themselves and the App Menu wraps badly (because I have installed a lot of apps), but these things are probably easy to fix in the skin for mobile users. So, my suggestion stands. I'd like to see a better Lo Fi skin for mobile users.
  24. I'd like to see the LoFi skin work better on the iPhone or maybe a new skin derived from the LoFi skin for iPhone use. The main problem, at least when using Safari on my iPhone, is that the fonts are so small and the page so wide that I have to keep zooming in on each page to see the text and choose links. I haven't researched it, but there must be some way to make this work. When I browse to m.google.com with my browser user agent set to pretend to be an iPhone, I see that the page is formatted specifically for the iPhone so that the page fits the phone's screen exactly and the fonts are large enough to be seen. Just a quick look at the source for the page as seen by an iPhone, shows: meta name="viewport" content="width=device-width,initial-scale=1.0,maximum-scale=1.0,user-scalable=0" There is some other header html that might be making this work better. Anyway, that is my suggestion... make Lo Fi work better on the iPhone.
×
×
  • Create New...