It's just an equivalent of (?!\w)
Re: Fixed SMF bugs
« Reply #30, on March 1st, 2012, 05:58 PM »
It's just an equivalent of (?!\w)
To a degree, this is why SMF always suggests use of repair_settings.php to fix everything.
As far as the attachment pruning, I seem to recall 0 being ignored as it falls foul of empty(), though it is a little unlikely to want to prune everything. I'm not sure it is a bug as a result. But I can look into it.
I've never really used that one. Don't even know if it works with Wedge actually...
Also, max width and max height for attachment thumbnails are set to 400 in your code... Any reason for that? Even here, the max width is much higher than that. I changed it locally to 1280x1024 which is probably good enough for maximum thumbnail dimensions...
Speaking of which, how about setting 'int' to have a 'min' of 0 by default? You've already set it to 0 pretty much everywhere, really...
Well, setting a max is good because it prevents the textboxes being huge (otherwise they're long enough to easily fit a 32 bit int), and I just figured 400 was a sane size for a *thumbnail*.
I actually didn't want to set a blanket default but it's probably for the best.Quote Speaking of which, how about setting 'int' to have a 'min' of 0 by default? You've already set it to 0 pretty much everywhere, really...
I thought thumbnails were what Wedge would show below posts -- i.e. what is capped to 640x480 on Wedge.org right now. I thought there was nothing else..?
Generally speaking, SMF never asked an admin to set a value of -1 to disable something or whatever -- always zero.
"Unable to verify referring url. Please go back and try again."
Always says that...
They are - to a point. If the image size is smaller than the thumbnail size, it will display the image unresized. Now, if no thumbnail size is set, it will just show the image full size... (that's what's happening here)
Makes sense, I guess...Quote Generally speaking, SMF never asked an admin to set a value of -1 to disable something or whatever -- always zero.
Lemme guess, there's a broken image somewhere on the page?
(I've noticed this before: where even 404s are pushed to Wedge for handling, it screws up the referer, 404s need to not be logged in writeLog())
It's not full size here, it's at 640x480... Which is precisely the setting I'd like to modify. Having to use the media gallery when you just want to post a quick attachment isn't so cool.
I don't think so?
Well, they need to be if you want the admin to be able to fix the 404 in the first place...?
Nope. http://wedge.org/pub/plugins/7122/a-project-i-started-a-while-back/ disagrees with you: the original image was larger than 640 wide, so it was rescaled to cap at 640px, but there's no thumbnail for it - that image shown under the post is 640x501, and downloading it also gives you a 640x501 image.Quote It's not full size here, it's at 640x480... Which is precisely the setting I'd like to modify. Having to use the media gallery when you just want to post a quick attachment isn't so cool.
Well, I know that Weaving reports 3 missing images on the page for me, which fouls it up.
I have no issue with the htaccess pushing 404s to index.php, but they must not be logged in writeLog(), because that pushes it into the online log, which is where the referrer is tracked as far as checkSession('post', 'admin') is concerned (which is what's causing the problem)
But the thumbnail settings in Wedge.org are 1280x1024. Where does the 640 value come from, then..?
logging 404's and not logging them for checkSession use.