pouet 2.0 bugs me beautifull
category: general [glöplog]
btw. awesome work. thank you :)
### 09042013: Bug Report: illegal call to member function on this page. ###
@AMcBain
How about a lookup table to shave of precious microseconds from "page created time"
Code:
return s+["th", "st", "nd", "rd"][s%10>3?0:(s%100-s%10! = 10)*s%10];
How about a lookup table to shave of precious microseconds from "page created time"
Code:
ordinalLUT = [1,2,3,4,4,4,4,4..etc up to 200 places];
return inputNumber + ["th", "st", "nd", "rd"][ordinalLUT[inputNumber]];
simpler
Code:
return ["1st","2nd","3rd","4th"..etc up to 200 places][inputNumber];The URLs on the previous/next page links on various pages (userlist, prodlist etc... at least) don't take into account the possible "&reverse=1" parameter and just omit it.
That's a known one yeah, I just never got around fixing it yet.
Yeah, it's already on our bug list
Okay, user script updated to be more reliable in Chrome and other user-script running browsers. The link button stuff now detects and tries to fix links missing "http://". The "link with edits" button just prepends it as the URL is used for the argument. The regular link button turns it into a link-with-edits where the original URL is the text, so it still appears as you wrote it, and uses the fixed URL as the argument. Updated the pull request too with the URL-fixing stuff.*
* The reliability was due to browsers disagreeing on when the user script should be loaded so sometimes the event it listened for to start up had already been fired before it was even loaded. Now if everything is good to go, it starts. If not, it waits for the event.
* The reliability was due to browsers disagreeing on when the user script should be loaded so sometimes the event it listened for to start up had already been fired before it was even loaded. Now if everything is good to go, it starts. If not, it waits for the event.
Aw crap! I totally posted that in the wrong thread! Well, I won't cross post it ... but while I'm here, can you check out the pull request? Pretty please with a cherry on top? ;)
### 09072013: Bug Report: illegal spelling errors on the faq page. too many for exemple: cutsom, mantain, persistance, occurence, carreers, immediatly. grammar police on standby. ###
gramar police used "exemple", it was supper effactif.
Seems there's still a bug(?) where prod titles on the front page are in all-lowercase...
that's not a bug, that's design
But that's a problem with the screenshot, not Pouet 2. Or am I missing something?
It used to be widescreen and not cropped like this, iirc. But now that you mentioned it, I'm not sure. I'll take a new one in any case.
sure, just post it in the 'fix me beautifull' thread
### 09082013: Bug Report: illegal self closing select tags on account and submit prod pages. standards violated. rendering engines confused. ###
What the heck? They self-closed the opening tag of a select with nested option tags! The web dev in me is aghast. :P
When i add this prod to my watchlist, it changes its state (icon changes, green box appears), but it doesn't show up on the watchlist.
There is one other prod already in the watchlist. I tried shift-reloading and removing/re-adding the prod multiple times. Adding other prods to the list works fine in most cases, but not for prods whose last comment is quite old. Maybe only prods with comments newer than the watchlist feature show up or something?
There is one other prod already in the watchlist. I tried shift-reloading and removing/re-adding the prod multiple times. Adding other prods to the list works fine in most cases, but not for prods whose last comment is quite old. Maybe only prods with comments newer than the watchlist feature show up or something?
Well, at the moment it's the only item on my watchlist and the last comment from cce shows up on it.
That's a known problem and I'm unsure how to solve it.
### 09142013: Bug Report: illegal response time for certain single letter prod searches. brought to you by the letter E ###
Quote:
by ggn:
oopsie
Wouldn't it be useful to know what on that page is different in Pouet 2.0, either by bug or change in workings, that you would like to see corrected? As a developer myself, links to thinks and "doesn't work" are really unhelpful. If this is something that's just wrong information, you should have used the new correction submission system or the Fix Me Beautifull thread if it kicks you out there.