This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
2356
Archived fixes / Re: Undefined index: display_quick_reply
« on November 26th, 2012, 01:11 AM »
As per http://wedge.org/pub/bugs/7714/error-log-entry-when-viewing-image-in-linked-topic-album/ fixed locally, will commit shortly.
2357
Archived fixes / Re: Error log entry when viewing image in linked topic-album
« on November 26th, 2012, 01:10 AM »
Fixed locally.
2358
Archived fixes / Re: Editor method add_button does not set button class
« on November 26th, 2012, 01:08 AM »
Added it locally. I'm still running on a fan with partial power, waiting for another to be in store >_<
2359
Archived fixes / Re: News in header not properly deleted
« on November 26th, 2012, 01:03 AM »
We added the ability to cache news items (to save bbc parsing multiple items every single page), but it wasn't clearing the cache on delete.
I've fixed it locally, will commit shortly.
I've fixed it locally, will commit shortly.
2360
Archived fixes / Re: Moderation filters "function" param wroong
« on November 26th, 2012, 01:00 AM »
Any chance you can provide your plugin so I can test this, please?
Thing is, surely the if would have to be updated as well?
Thing is, surely the if would have to be updated as well?
2361
Archived fixes / Re: Moderation filters "function" param wroong
« on November 25th, 2012, 01:47 AM »
Awesome, so in that case we can fix that readily enough. :)
2362
Archived fixes / Re: Moderation filters "function" param wroong
« on November 25th, 2012, 01:25 AM »
And that doesn't affect any existing rules? (It's been months since I looked at that code)
2363
Plugins / Re: Maximum Images Per Post
« on November 24th, 2012, 03:52 PM »
Also looks like you missed a language string...
2364
Plugins / Re: Maximum Images Per Post
« on November 24th, 2012, 12:52 PM »
Sweet, the moderation filters can be extended through the hooks! (Not tested, you see)
I still haven't figured out how to cope with making a nicer error message to users, though. I might just give them a space to add an explanation for the users rather than trying to write something that makes a sensible explanation out of the rules given how complex rules can actually be.
I still haven't figured out how to cope with making a nicer error message to users, though. I might just give them a space to add an explanation for the users rather than trying to write something that makes a sensible explanation out of the rules given how complex rules can actually be.
2365
The Pub / Re: Getting ready for an alpha release: WeCSS/Wess improvements
« on November 23rd, 2012, 08:12 PM »
And Firefox is trying to be like Chrome...
As a thought, couldn't we add a scheduled task to houseclean periodically? Perhaps once a week, clear the CSS cache?
As a thought, couldn't we add a scheduled task to houseclean periodically? Perhaps once a week, clear the CSS cache?
2366
The Pub / Re: Getting ready for an alpha release: WeCSS/Wess improvements
« on November 23rd, 2012, 05:38 PM »
Ah, I forgot about that (and that you can't set sizes for fallback fonts)
2367
The Pub / Re: Getting ready for an alpha release: WeCSS/Wess improvements
« on November 23rd, 2012, 02:23 PM »
Windows version should be irrelevant to the browser just as it is with Linux. The only rules around Windows are that certain versions don't support certain browsers, e.g. XP won't have IE9 or 10.
2368
Archived fixes / Re: Session writing
« on November 21st, 2012, 03:08 PM »
You can't really use mysql_ functions directly, because the connection won't be available to them anyway, as that resource is held inside wesql. That still doesn't explain how come half the classes that are loaded are not registered.
2369
The Pub / Re: Looking for volunteers to test the Wedge private alpha!
« on November 21st, 2012, 06:03 AM »
It's totally unsuitable for us, we don't use gettext style language files (for multiple reasons)
2370
Archived fixes / Re: Editor method add_button does not set button class
« on November 21st, 2012, 05:22 AM »
Well, it's not an enormous problem, the late 2011 MacBook Pros (at least the 15" and 17" as far as I can tell) all use the same pair of fans, one for the CPU, one for the GPU. I'm covered by AppleCare, so it is a case of checking them have them in store then taking it in for them to replace it... in theory.