Development Discussion Board

Add this to your CSS, and problem solved:
Should it be the default in phpBB? Don't know, don't care. I always use the above rule to stop the user from manually resizing textarea elements.

I probably should mention that image resizing requires a LOT of memory. While it's probably not an issue with avatars, it most likely will be with attached images. Adding the following line to the start of posting.php and ucp.php should eliminate most of those issues: ini_set('memory_limit','128M');...

Open /includes/functions_user.php and locate the following line (~ line 2078): $prefix = $config['avatar_salt'] . '_'; Insert BEFORE the above line: $file->resize($config['avatar_max_width'], $config['avatar_max_height']); Add this function to includes/functions_upload.php (I put it just before the ...

http://www.dion-designs.com/noscript.php - yeah. And then you have a js-animated something-or-other in the header. Nice. I could not find the registration link at all. Maybe it's hidden by my width adjustments? The appearing animation of topic list on the index page is a perfect example of throwing...

I apologize if this has been mentioned before (I tried looking, but couldn't find it). Does this include "mark topics/forums read"? I ask because if I click that and then click the link to return to where I was, the topics get marked as read. However, if I let it sit there and let it go a...

Here are replacement files/functions that "untangle" the "spaghetti code". Javascript functions: function set_ajaxbox() { var elem = document.getElementById('msg-ajax'); elem.style.backgroundImage='none'; center_box(elem); } $(function() { if (goodbrowser) { $('[data-ajax]').each...

Thank you for your input...that is all I asked. 1. By "core" I mean the .php files, and to a lesser extent the support javascript files. 2. I can see why you would call what I did "spaghetti code", though it's really no more than a difference in philosophy. I don't believe in clu...

Yes, in a large-scale production environment, the code should be using data-* attributes. However, the attributes I'm using work just fine, and should continue to work fine into the forseeable future. Just because it works, doesn't mean its correct. Please do read spec: http://www.whatwg.org/specs/...

Yes, in a large-scale production environment, the code should be using data-* attributes. However, the attributes I'm using work just fine, and should continue to work fine into the forseeable future. I suppose the big difference in my method is it adding "ajaxify" support to specific temp...

In any template, if you want to have a tag "ajaxified", you must add a data-ajax attribute to the tag. For links, you would add data-ajax="" . For <input type="submit" tags, you would add the following: data-ajax="(formid)" data-action="(formaction)"...