No.454
No idea if bug or feature, but at least on my machine I don't get the countryballs displayed when showing a post from a crossthread reference.
No.459
EC has been loading quite slowly the past days, and I don't seem to be the only one affected by this (everywhere else the pages load as quickly as expected).
No.461
>>460not the one mentioning it, and didn't check for actual data (network tab).
i've noticed that connecting wasn't a problem, but the data (thumb pics) were loading slow.
No.462
>>460Yes, it took ages to load the comic thread, for example.
No.525
s.png (49.45 KB, 1012x348)
>>524It's a png in disguise, that's why the image handling functions complain.
No.526
>>525Thanks! Now I feel retarded for not having seen through it.
No.535
I think I just found a weird bug: I was searching the Dokumentationen-thread on /b/ and couldn't find it while schrolling through the pages. I almost got mad because I thought it got deleted, but then I saw it is in the catalog on 1st position of page two. Strangely it wouldn't show up when I tried to navigate to page two, the next thread was shown on position 1 (Sauffaden). The behaviour was the same whether I used Dollchan or not.
I bumped the Dokumentation-thread and then it showed normally on page one. I deleted the bump, then it correctly fell back to first spot on page two, form that point on it was fixed, likely because one of my actions caused a thread list to rebuild. I can only assume that some event on the board (maybe thread creation/deletion) caused the internal thread table to fuck up and simply miss out on one thread, while the catalogue still worked correctly. While I doubt this can be fixed easily, because it's specific as fuck, people should be aware that this bug exists, even if it took a year for someone to notice.
See screenshots for details, the documentation thread does not show on the board on page transition, while still existing in the catalogue on page 2 pos 1. It does not matter if pages are switched manually or via dollchan infinite scrolling, so the scrolling function works, it's probably some internal thread list that is delivered to those scroll functions that's already flawed.
No.561
>>560Is that the "Dark"-css, and on which browser does that happen?
No.562
>>561Yes, Dark, on Chrome
No.563
>>562Applied a fix that should work on most instances of the problem, the element in question now has a min-width-property, so no matter how slim the thumbnail is, the element will retain a minimum-width of 150px, which is enough for the filename in the example. Might still look shit with longer non-wrappable filenames though.
No.580
>>579Seems to be back, but right now the whole site is slow as fuck.
No.581
>>579No idea what happened there :DD Those graphs are sensitive to missing values, so if something didn't load properly, it won't show at all.
>>580It's usually a provider issue. You can easily check this by opening the radio page: If it's also slower than usual: Provider issue. Sadly it happens almost daily these days, which is especially bad for the radio. Temporarily slow loading times on a slow board aren't a big deal, but streams, which rely on real-time communication, will cut off, which sucks.
No.584
Code blocks should not have overflow enabled, but instead a scrollbar
No.594
>>584Added followwing directive to the general css:
code {
white-space: pre;
overflow: scroll;
}
That did something, but not sure if it is what you wanted. Also still no scrollbars for some reason, maybe conflicting directives elsewhere.
No.598
>>597It is intended, I think we started to allow it when someone wanted to make an image dump, and had to type in random shit to get his posts through, which of course is annoying. Best option would be to deny posts which contain neither text nor images, but there's no config option for that, we'd have to implement this by ourselves. I just checked the corrensponding part in the code, and it should be possible, maybe I'll give it a try next weekend or so.
No.599
>>597>>598A change has been implemented, now an error message should display when there are neither text in the post body nor attached files present. Any combination of files or text should suffice that the post goes through. Please report if you encounter problems, like rejected posts which weren't empty.
No.645 KONTRA
>>644was a dollchan compatibility problem; deactivating it redirected me to banned! page.
first ban in several years of posting on EC - not sure if i should be proud or ashamed :D
No.647
>>645You got caught up in the process when (a small minority of) our recent guests started creating several low effort threads in succession, and we felt the need to clean up. The ban has been lifted.
No.648
>>646actually went over all my posts and can't find anything with red text or a deleted post. ban doesn't specify any post as well :/
i would assume it is either because of this one >>>/b/24787 - sure... a 3rd thread suxx, but we reopen threda all the time, if it got systemkontra'd.
or this one >>>/b/24756
it would have been funny, but semi-encouraging might have been a little over the top :DDthis might also be a possibility >>>/b/24770 - yes, stupid link shortener cancer, but it redirects to my own ">_"-thread
>>>/b/12308 No.651 KONTRA
>>648> or a deleted post>>647> clean upoh, yeah. one of my posts actually was in a deleted thread. but that one actually read
> [...] Warum schubst ihr unsere tollen Fäden vom Brett? :(if a mod just banned all IPs involved in that thread... might have been it. :3
sry for giving you additional work ^.^
but der Ausnahmezustand seems to be over, at least for a while.
No.704
>>703>gepetzt Wo/wie geht das?
No.707
>>703Es war nur ein Report da.
>>704Pfosten anhaken, rechts unten auf der Seite ist ein Report-Knopf.
No.708
>>707Das ist mir komplett entgangen. Was wohl noch? Dieses Brett ist die reinste Wundertüte.
No.709
>>708Anstelle des Banners hast du eine geringe Chance den Link zum Mitgliederbereich und Login zu erhalten.
No.710
>>709Sie wollen mich wohl verhohnepipeln, werter Herr?
No.712
>>710Ne. Kannst ja aktualisieren bis es kommt wenn du mir nicht glaubst.
No.713
>>712Glücksspiel-Mechanik in meinem Ernstchan?
No.715
>>714Dann halt Pechspiel.
No.724
>>723Meistens ist das Bild dann nicht die Erweiterung, die es vorgibt zu sein. Wenn du es mit IrfanView aufmachst, wird er sich wahrscheinlich beschweren und sagen, dass es ein jpg ist oder so, siehe
>>524 >>525 No.729
>>724Ernst hatte sich ja auch gedacht, dass etwas mit den Metadaten nicht in Ordnung ist und ein Bild nach dem anderen deswegen konvertiert. Es war aber eins von vier Bildern und der Hinweis, welches Bild davon, hätte bei der Fehlereliminierung helfen können.
No.746
>>729Stimmt, ich habe es mir gerade angesehen, ich habe auf die Schnelle keine Lösung dafür. Das Problem ist, dass an der Stelle, wo dieser Fehler geworfen wird, keine sinnvollen Informationen über das Bild verfügbar sind, außer Erweiterung, Dateigröße und Abmessungen, aber kein Name oder Pfad. Ich könnte die Fehlermeldung zwar erweitern, aber es würde nicht viel bringen. Falls mir noch was einfällt, passe ich es an.
No.773
Arabic text isn't displayed in posts
Other alphabets seem to work fine, see >>/int/20584
No.780
>>773>>774I had a look at it, everything that has been delivered to the browser is also displayed, that means whatever was lost, didn't make it into the database in first place. It seems unreasonable to mess around with charsets, just to enable a language only few can read, so sorry, can't do, preasu understandu.
No.822
Bug oder Feature:
Folgende Situation auf /b/:
- Heute-Faden geht in Autosäge
- Ernst macht neuen auf, verweist in altem Faden darauf
- Anderer Ernst macht andern Heute-Faden auf, verweist auch im alten Faden darauf
- Erster Ernst löscht seinen Faden und Pfosten
- Neuer Heute-Faden ist jetzt in der Fadenreihenfolge HINTER dem alten Heute-Faden
Kann es sein, dass da beim Löschen des Pfostens und Neuberechnung der Stoßreihenfolge die Autosäge nicht mehr berücksichtigt wurde?
Denn rein von der Pfostierzeit her stimmt die Reihenfolge ja, da der letzte Pfosten im alten Heute-Faden neuer ist als der neue Heute-Faden, nur sollte das ja bei der Autosäge eigentlich nicht mehr berücksichtigt werden.
No.830
>>822Yes, I have seen that, too, it's very likely a bug, exactly as you described it. However, it seems to be a rare occurence and not a big problem, so I'd rather sit that one out.