pouet 2.0 bugs me beautifull
category: general [glöplog]
Hey,
i have a strange problem/glitch since 2 days or so, I'm getting this every time I'm logging in. I already tried to clear the cache/cookies but it does not help. It's on Firefox (26) and Chrome 29 (Windows).
And a little feature request:
Is it possible to become a pm system here on pouet? It would be much easier to contact some buddys if i could pm them.
i have a strange problem/glitch since 2 days or so, I'm getting this every time I'm logging in. I already tried to clear the cache/cookies but it does not help. It's on Firefox (26) and Chrome 29 (Windows).
And a little feature request:
Is it possible to become a pm system here on pouet? It would be much easier to contact some buddys if i could pm them.
@CHEF-KOCH - I thought that was only my problem...
Google Chrome Version 28.0.1500.95 m & Windows 7 (64)
Google Chrome Version 28.0.1500.95 m & Windows 7 (64)
I reckon' it's all T_S' fault...
site keeps logging me out. I occasionally get "Who are you and where did you come from ?" error message. i'm not modifying cookies. I did notice extra stuff in it since yesterday.
__utma=A.B.C.D.E.F;__utmz=A.B.C.D.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none);
__utma=A.B.C.D.E.F;__utmz=A.B.C.D.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none);
Quote:
i have a strange problem/glitch since 2 days or so, I'm getting this every time I'm logging in. I already tried to clear the cache/cookies but it does not help. It's on Firefox (26) and Chrome 29 (Windows).
That is called zalgo, an annoying feature rather than a bug.
Anyway, for those who hate the spacing on the prod pages, this brings the old behavior back:
Code:
div#prodpagecontainer
{
max-width: 644px !important;
}
td#screenshot
{
width: 400px !important;
}
(next bug: the preview is adding an empty line for each line in code tags)
I think this wasn't mentioned yet, the search box is too big on a small screen (1024x768)
neop: then I suggest you use your browser's built-in zoom function, since you unfortunately belong to the 9% of users who still are on such an insanely low resolution. Pleasing everyone isn't possible, but pleasing 90% is, and that is enough in my book.
Or try changing the browser. Chrome at least seems to handle the search box correctly even if the windows width is in the range of 600 pixels.
tomaes/neop: fixed
gloom: i use 1024x600 too (netbook) and it's a oneline fix anyway.
gloom: i use 1024x600 too (netbook) and it's a oneline fix anyway.
Also: the "getting logged out" problem is because of the default session-garbage-collector of PHP which is by default set to kill every unused session after 24 minutes(!)
gloom: I usually use a bigger screen, but that one is packed for evoke ;) And when I use two browser windows side by side (1920/2 = 960), each window will be even smaller.
gloom, BS, this bug is easily reproducible in iphone 4 (chrome). so yes, some of us read pouet on insanely low res.
one question, since one can see who is online and who is not, how about a message system (like a "mail" with inbox etc) in pouet? would that be too much work to implement?
I created this thread for reporting bugs, new features will come later.
Since gargaj mentioned the PHP session GC... i'll consider that a bug!
Bug XXX: login for one year not working! :P
Bug XXX: login for one year not working! :P
Increasing the session.maxlifetime is probably not the best idea. I guess setting an autologin cookie would be the better solution.
whizzter: a missing feature is not a bug. be kind to the people working their asses of for your pleasure.
+f
Quote:
Increasing the session.maxlifetime is probably not the best idea. I guess setting an autologin cookie would be the better solution.
That's basically reimplementing the same session system though - why do it twice? Increasing the session lifetime to more than 24 minutes is the same effect systemwise. Wouldn't even need to be too much, I'd say a week is okay since expiry resets when you revisit a page, and let's face it - we all visit Pouet once a week.
Also, that limit is 24 minutes because the INI takes seconds, but the GC takes minutes, and they probably wanted 24 hours so they set it to 60 * 24 :D
An option to remove the Zalgo "feature" would be nice. But the workaround provided by tomaes works.
Not a bug, but more of a feature: http://www.marlborotech.com/Zalgo.html and http://stackoverflow.com/questions/6579844/how-does-zalgo-text-work
Limiting this abuse of 'Zalgo text' might be a good thing.
Limiting this abuse of 'Zalgo text' might be a good thing.
Maybe I should read back before I post soemthing.
*something
Lots of people in this thread should do that, numtek :)