No.31
>>30Is it possible, it cant upload .mp4 ?
Oh please no.
Of course it can be fixed somehow.
But why setting up a new board with a software from the dark ages?
That needs to be completely rewitten to have even the basic features?
Please consider using a current software instead of fixing something that is horribly out of date.
Thanx.
No.33
>>31i was able to upload mp4 and webm without a problem, maybe because i use dollchan? idk
the 10mb data cap could cause problems aswell, but i didn't get any notification about it, just couldn't post
No.35
>>32After I converted the mp4 to webm this came up
>>34Dont waste your time with the dead vichan.
No.36
>>32>maybe there have to be extra codecs installedThe server shouldnt care about the codec inside a video file because the server doesnt decode it anyway. The browser is doing that.
No.59
>>34>Please change software to sth. current asap. You wont get even started with this. Dont waste your time and your money and your effort for a dead unmaintained software. Unless you want a dead unmaintainable chan.The fact that Phutaba was forked from Wakaba, one of the oldest western chan softwares, and hasn't been maintained for years, yet has none of these bröplems, goes to show how janky vichan really is.
Well, Perl > PHP and Phutaba was made by Germans, rather than a coalition of Poles, Brazilians and USians, so there's that. :3
No.66
Reomved the useless mail link from the poster name when sage is set. Will maybe try to add a visible Kontra next, don't be shocked if I break some stuff in the process.
>>61mp3 should be possible, I already uploaded some here. I assume the file (or the sum of all file sizes in the given post) was under 10MB? And do you use Dollchan?
>>36Yes, that sounds reasonable, still I have no idea what else it could be that for most people mp4 just work fine, but a few people have major problems with this. From what I know now it sounds like an issue on client side, but what could such an issue even be? a file upload should be fairly standard, and I couldn't even think of a possible client issue here.
>>34>>35Can you post the refused file as zip? I'd like to try uploading it from here, I wanna know if it's an issue with the file or if it is client dependent.
No.67 KONTRA
>>66didn't this remove the visibility for dollchan users aswell?
No.68
>>67yeah, i kontrad the post and atleast i can't see it anymore, even with dollchan
No.69
>>67>>68Really? Good to know, now I know how dollchan recognized the sage. I will try implementing it the old style, and if this somehow doesn't resonate with dollchan I'll either revert the change or just leave it the way it is as long as it's decently visible. In any case: Thanks for the important information!
No.70
Henlo from Moldawia. Is this a englisch Imagebord?
No.72
>>70most users are german, but there is an >>/int/ board aswell
No.74
>>73will the KONTRA text eventually become red again? maybe with the boomerbeige update?
No.75 KONTRA
>>74Yes, that's the plan. I'll inform css man right away so that we can coordinate our efforts.
No.76
>>72But why the perplex write in englisch?
No.79
>>66Yes, it was a 9MB file and I was using Dollchan.
No.80
>>79Can you post it as zip? Maybe I can get some extra info on this if I can recreate the issue on my machine.
>>78Yes, there seems to be some issue with catalog updates. Most pages you see are pre-generated by vichan in the background, so by the time you visit them, you get a pre-generated static html page. Very good for performance and database load reduction, especially good for cheapskates like us. But bad if those updates aren't triggered when a change in content happens, and my theory is that this is the problem: The catalog isn't updated when a thread is deleted. I just rebuild the pages manually, and the entry disappeared right away. Maybe it would also disappear if a new thread is created or something else, don't know yet. Anyway, thanks for the report, I doubt I can fix it at the moment, but I'll add it to the bugs list for tracking.
No.81
Is there/will there be any spam protection? I just tried on /test/ to post two threads in a row and no problem. Is that only on /test/ or do we actually not have any protection?
No.82
>>81There's a pretty sharp spam protection availabe in the config, in fact it was so sharp that I had to disable it for now. I plan to re-enable it, though, and only remove the parts that caused problems. That will likely happen in the next week. I'll make sure to post a sticky in advance so people won't be confused when all their posts suddenly are rejected because spam protection is too greedy.
No.84
>>82Cant yo configurate it to where its useful but not annoying?
No.85
The spam protection is shit but annoying.
No.89
>>84The thing is: There are a few parameters you can nudge. And no matter how I nudged those: It wouldn't let me post, because all my posts "looked like a bot". So I think at least one of the several implemented checks is broken at the moment.
>>85I think we can at least use some components. We'll see what we can do.
>>88Indeed.
No.93
>>89Can't you put a timer on post frequency? Like 60 seconds for replies and 15 minutes for threads?
t. no clue haver of how such a feature would be implemented
No.97
>>93Not more than 30 secs for replies and maybe 5 mins for threads seems better. Even if the timer is short it already should pretty much stop every spam attempt, because the time adds up, if you really wanna spam in amounts, that matter/are important.
In general i support the idea, better than getting clarified as bot for posting wrong.
No.98
>>97And maybe just starting after the third post in 30-60 seconds, so most users don't even notice the spam protection, when theyre making a fast second post in a short time period.
No.99
>>97Ernstchan is a rather slow board. Hence the long suggested periods. Though they were suggestions and up for Ernst tire serious discussion. Tweaking the amount of seconds seems like the least important part on admin side. I'm guessing you can change it rather easily once implemented.
No.125
>>124Seems the css is not compatible with dollchan.
I don't use dollchan myself, so not exactly sure what's wrong.
Or maybe it's your dollchan settings?
No.126
>>125may very well be and nothing extremely concerning, but still should get fixed in the long term
i would assume it's good if nu ec is compatible with dollchan ;3
No.127 KONTRA
>>126changed a bit around in my settings, at least turning off obviously visually impacting stuff doesn't fix anything, might be caused by less obvious settings or dollchan entirely
No.132
>>126>>127Found the issue(s).
Just some small margin / display settings that dollchan assumes are set as vichan default.
https://pastebin.com/WCEe4KTG^ new version.
There's still some weird stuff with dollchan, like some of the icons being misaligned.
I'll try to tweak it later
fuck I hate css
No.141
The Radio stream banner does not always appear when first loading EC, but if I visit the radio page and then return to EC it is there.
#mysteries
No.142
>>132Updated.
>>93>>98>>99Today's security changes re-enabled the structure that will allow us to do such things. Some things are possible just by configuration, but we can also add our own checks, which of course is more work. But I think it's worth it.
>>138Hmm strange, normally this should wrap. No matter how small I make by browser, it wraps properly, and I cant find any fixed size or positioning directives for that element either. And it's missing quite a lot on the left side.
>>141Dang, I hoped I had fixed this, but it seems that the issue is still there. Basically, the radio banner isn't generated when the page is generated by the server, it is only pulled by the client via javascript when the page has already loaded in the browser of the user. Can you tell me which browser you use, and if you have javascript enabled for ernstchan.top?
No.143
>>142browser = Edge
javascript is on, but privacy set to strict
No.145
>>144Note to self, don't make right before going to bed without testing
https://pastebin.com/3RX0M5RVpls replace asap
No.151
>>150I am, thanks, and I can confirm the error, so it's obviously a problem with the file itself. I'll try to find out what the problem exactly is, but this could be a tough one.
No.152
I can't seem to be able to post webms or mp4s.
It says there was a problem processing them.
No.153
>>152Sorry, my bad, should work again.
No.156
Since today while lurking by phone loading a page has become extremely slow. All elements and thumbnails seem to be done,but the loading progress bar is not moving for seconds.
No idea if it's my mobile provider, just wanted to document the issue somewhere.
No.157
>>155>It's not possible to post an image if the image was already posted somewhere else on the brett.It should be fixed now, can you try again?
>>156For me it seems fine. If more people notice issues please report.
No.158
>>157>It should be fixed now, can you try again?Thanks, now it's wörking.
No.159
>>156Don't have the same issue, it even loads pretty fast on mobile internet at work.
No.173
>>171webp geht leider noch nicht, nicht sicher warum. PHP sagt, dass webp-Unterstützung prinzipiell da ist, und vichan sollte es auch können. Aktuell funktioniert es aber maximal als Datei, nicht als Bild. Ich müsste dazu mal in Ruhe die ganzen Werkzeuge zur Bildverarbeitung und Daumennagel-Generierung durchgehen. Leider kracht es bei manchen Optionen, das muss ich mal in einer ruhigen Minute mit vorheriger Ankündigung ausprobieren.
No.175
Hi Where are the formatting tags? I need more than spoilers.
No.177
>>175Try ##, ~~ and __ before and after your text. The tag for bold might change to something less retarded when I finally buy that regex for dummies-book.
No.179
>>177why bother looking up regex docs when you can just ask chatgpt
No.180
>>177I know a bit of regexp if you need help
No.181
>>177Great, thanks! Also requesting italics. I
love italics.
No.184
>>179Not sure if ChatGPT is familier with vichan, so I wouldnt know if I was able to ask a sensible question.
>>180Thanks, check out the zip I attached, I hope everything you need to know is included in that text file, if you're experienced with regex maybe the problem is obvious, to me this looks like moonspeak. In case you need more information just ask.
>>181In
that case I recommend
two percent signs on each side No.185
2x ToDo at the front page
No.192
>>184Can you try these:
$config['markup'][] = array("/\[b\](.+?)\[/b\]/", "<span style=\"font-weight: bold\">\$1</span>");
$config['markup'][] = array("/\[i\](.+?)\[/i\]/", "<span style=\"font-style: italic\">\$1</span>");
$config['markup'][] = array("/\[s\](.+?)\[/s\]/", "<span style=\"text-decoration: line-through\">\$1</span>");
$config['markup'][] = array("/\[u\](.+?)\[/u\]/", "<span style=\"text-decoration: underline\">\$1</span>");
$config['markup'][] = array("/\[spoiler\](.+?)\[/spoiler\]/", "dunno what to put here");
$config['markup'][] = array("/\[code\](.+?)\[/code\]/", "etc");
Although, not sure how this would work when you have multiple bbcodes for the same string, like [i][b]asd[/b][/i]
Maybe it's better to do this through tags than inline html? Your call though.
' is not a special character in regexp, but might be a special character in php or whatever else the string gets passed to. so you might need to escape it multiple times, or some other weird shit, I dunno. I have to deal with crap like that all the time when writing regexp inside an SQL query.
I'd recommend instead using ` . easy to reach, looks similar, and is not a special character.
I like ``asd`` for code line, and ```asd``` for code block, but your choice.
No.194
>>192Oh, and if that doesn't work, try these:
$config['markup'][] = array("/\\[b\\](.+?)\\[/b\\]/", "<span style=\"font-weight: bold\">\$1</span>");
$config['markup'][] = array("/\\[i\\](.+?)\\[/i\\]/", "<span style=\"font-style: italic\">\$1</span>");
$config['markup'][] = array("/\\[s\](.+?)\\[/s\\]/", "<span style=\"text-decoration: line-through\">\$1</span>");
$config['markup'][] = array("/\\[u\\](.+?)\\[/u\\]/", "<span style=\"text-decoration: underline\">\$1</span>");
$config['markup'][] = array("/\\[spoiler\\](.+?)\\[/spoiler\\]/", "dunno what to put here");
$config['markup'][] = array("/\\[code\\](.+?)\\[/code\\]/", "etc");
Explanation. The following are special characters in regexp, and need to be escaped:
. , + , * , ? , ^ , $ , ( , ) , [ , ] , { , } , | , \
BUT. since you're calling from inside php, "\" itself is a special character, and you need to escape "\" with another "\". the "\\" gets converted to "\" and sent to regexp, and then [ and ] get escaped there.
No.195
>>192>>194Tried the first of those each, both had input "[b]boldenings[/b]" and yield no output as a result, something that I also had several times already without understanding why. I checked, it's really an empty post body in the HTML source. It's as whatever function processes this: It really hates those brackets.
>>190<3
>>193I have no strong opinion on that, on my keyboard those are both on the same key anyways. If no one has a reason to do otherwise, I'd implement ´, because that's the one without shift key.
No.196
>>195$config['markup'][] = array("/\[b\](.+?)\[\/b\]/", "<span style=\"font-weight: bold\">\$1</span>");
$config['markup'][] = array("/\[b\](.+?)\[\/b\]/", "<span style=\"font-weight: bold\">\\1</span>");
Maybe one of these?
Yeah, I know regexp but I don't exactly know how php interacts with regexp.
No.198
>>197>>196Okay, I think b, i, s, u and spoiler work. For some reason code refuses to work, even if I try it with some symbol instead. Probably a mistake of mine, I have to check. Anyways, thanks again for your help!
No.199
B A L D
No.200
>>198Try this.
$config['markup'][] = array("/\[code\](.+?)\[\/code\]/s", "<code>\$1</code>");
According to some random page I got from google:
>/s is for "dot matches line breaks"I'm even gonna take a gamble:
I bet this will work as long as there's no newline. No.201
I think the Today thread didn't get bumped. I made a post today at 17:33 and it's still below the thread with the last post from yesterday.
No.208
>>201For some reason this was set to bumplock, it was probably me fooling around with Systemkontra tests a few days ago and forgetting to clean up again, sorry about that.
No.211
>>200or even this:
$config['markup'][] = array("/\[code\]((.|\r|\n)+?)\[\/code\]/", "<code>\$1</code>");
You can also play around with having separate bbcodes that work only on the same line, or on multiple lines.
No.212
>>211Tried this one, it works well, it's implemented. Thanks a lot!
No.214
Often when I recently replied to a thread and try to post again, the whole text of my previous reply is still in the text box. No idea if that has to do with my (outdated) dollchan, the board software, or both.
No.219
>>214Not sure if that can be fixed server-side. Does anyone else have this problem?
No.233
I just got the error message "Invalid image BP1" repeatedly with different files, I think they were all .jpg
No.234
>>233Thanks for the report, can you upload said images as zip in this thread?
No.235
>>234Sadly, no. I mostly paste pictures directly from image search into the box.
No.242
>>241Thanks, I just tried it on /test/ and could open a new thread with these pictures. Do you remember the exact error message? It was probably one of these:
>You look like a bot>Your request looks automated; Post discarded.>Flood detected; Post discarded.Even if I can't recreate it, I could try changing those messages a little, so that I could see where exactly the thread creation fails.
No.243
>>242It was the flood discarded message. Had the same problem with the "Stoss wenn hoch" thread photos on b a day before, but then it obviously worked.
No.244
>>243>It was the flood discarded messageOkay, that was the one I least expected, but I found the issue: I am retarded, and it should not happen again. It was actually a mistake in a piece of code I added. If it still happens please notify again, sorry for the inconvenience.
No.245
Having trouble loading EC intermittently, something going on? Other sites seem to work normally for me.
No.246
>>245>something going on?Daily backup to AAS/Antifa servers. Ok, for real: Can confirm, checked the server, looked good for me. Seems to be gone now as well, maybe general hiccup at our host, like VM switching to another physical host.
No.247
>>244Okay, cool. Thanks for your bother.
No.251
>"You look like a bot".
All I did was using dollchan to reply to a thread from the main page.
No.252
>>251Thanks for the report, I will investigate. Can you give me some extra information? 1. did you have the thread page open for a long time before you replied? 2. did it work (immediatly) afterwards, or were there more errors? Did you reload the page before it worked?
By the way this is still standard vichan bot detection, of which large parts were already deactivated, because of frequent false positives. Seems there's still some more wörk to do.
No.253
>>252>did you have the thread page open for a long time before you replied?No idea, but I don't think so.
>did it work (immediatly) afterwards, or were there more errors?I might have gotten the same error multiple times.
>Did you reload the page before it worked?I openened the thread and posted from there.
No.254
Sometimes, latest replies don't show up, both on board pages, and even if you open the thread where the new post was made.
CTRL+F5 seems to fix the issue. Maybe there's a way to prevent pages from being cached?
Here's something I found after 10 seconds of googling:
https://stackoverflow.com/questions/49547/how-do-we-control-web-page-caching-across-all-browsersMaybe it'll help.
No.255
>>253Okay thanks. I checked the parts of the code which can trigger that error, unfortunately there a quite a few of them. I can't say which part was responsible for that behaviour, but I made some changes so that if it happens again, the error message will be more telling, so please report again it that happens with the exact error message, text or screenshot will do.
>>254Thanks for the link, this is known, the article you referenced is the first one I came across when trying to fix this. If you want to check: This stuff has already been included in the source. I haven't found a way to prevent this, but I have at least a rough idea what the problem should be.
1. it's not a vichan issue: The index pages for each board are always up to date after a post is made (that's why F5 works)
2. I don't think it can be fixed in the HTML either, because the no-cache directives are already there
I know that vichan uses a built-in cache, which was recommended during install to "drastically enhance performance". I can only assume for now that this built-in cache only updates the freshly rebuilt contents after a given timespan, this timespan varies greatly, and it is heavily influenced by board activity. For example the first post on any day can take up to 40 minutes until it shows up when just clicking the board links and not pressing F5, while in the evening when it's more busy everything shows up instantly. I hope I will find it soon, and then I'll probably disable it completely and check out the performance hit, or at least drastically reduce the maximum time the delivery of cached content is allowed.
It's a mystery for me while this cache seems to respect F5, but not the meta-tags. Until now I thought those have the same effect and would even be indistinguishable for the server.
No.260
>>259Thanks.
For your service I offer this rare Ernstwurf. To prevent unauthorized distribution, I put copy protection on so the spoiler will only open for the poster linked above.
No.261
>>260Copy protection on MY Ernstchan?
No.262
>>260You're welcome, and thanks for the OC. That reminds me that there's only a single spoiler image so far, I'll have a look if we can pick a randomized one out of a given pool again. Obviously this one here would be included.
No.264
>>261Copy protection, Archive Immunity™, reply blocking...there are no limits for a master spell-caster like myself :D
>>263I didn't realize we only had one spoiler image before your hackenings. Nice work. Also fast.
No.265
Is there actually any reason why we have the anglo date system?
Of all date formats it makes the least sense.
No.266
>>265No particular reason, this was the default. I thought I hade changed that for /b/, but either I never did that or I lost that change somewhere. I'll try changing it for /b/ and then ask the guys on /int/ what they'd like to have.
No.267
>>265>>266It's done, but despite it normally being configurable on board level, it seems I can only set it for all boards at once. The reason is as far as I understand that we use a vichan standard javascript library called local-time.js, which makes it possible to have local date and time instead of UTC everywhere, and this reads its date and time-config from the central config file instead of the individual board config. So unless I change it in the central config, it's ignored. That's also the reason why I thought it was already changed on /b/: It was, until the inclusion of local-time.js reverted the change.
No.269
>>267Cool, thanks.
I wouldn't even mind a yyyyMMdd date format or not having localized time or anything, just not the silly MMddyyyy.
No.280
>>279>The caching issue when you made a post but didn't see it on the main page unless you pressed the reload button or F5 is likely fixed Jah be praised, mon
No.297
Faden wird nicht gestoßen wenn man pfostiert.
>https://ernstchan.top/b/res/4275.htmlAndere Fäden schon.
Warum ist das so? Ernst verlangt eine Erklärung!
Danke
No.300
>>299Und wieso wurde das verhängt?
Ich war es nicht.
No.302
>>300Bumplock wurde ursprünglich gesetzt, weil der Faden aussah wie eine Mischung aus kopierten Nachrichtenmeldungen und Scheißewerferei. Dann wurde ein weiterer Kriegsfaden eröffnet, der geschlossen wurde mit Verweis auf den bestehenden Kriegsfaden, der aber zu diesem Zeitpunkt schon auf Bumplock stand. Das wirkt natürlich so, als solle das Thema als Ganzes wegmoderiert werden, das ist allerdings nicht der Fall.
Wir haben das im Moderationsteam besprochen: Kriegsfäden sollen erlaubt sein, auch wenn die nicht Jedem gefallen. Das gilt schließlich auch für Drachenlord-Fäden. Außerdem gibt es auf /int/ auch einen Kriegsfaden, und dort funktioniert er ohne Probleme.
Wir nehmen den Bumplock daher wieder raus, und werden im Faden gegebenenfalls aufräumen, falls uns dort im weiteren Verlauf einseitiges Geschille des Typs Shitmany/Urine oder sonstiges Gestänkere auffällt. Kriegsfäden haben leider einen Ruf, besonders "meinungsstarke" Pfostierer anzuziehen, allerdings möchten wir explizit nicht, dass deshalb das ganze Themengebiet verboten wird. Sonst könnten Störer sich so einen Mechanismus in Zukunft zu Nutze machen, indem sie unliebsame Fäden zukrebsen, bis sie verboten werden. Das soll bei uns nicht möglich sein.
No.303
>>302Ok, vielen Dank.
Als OP werde ich dort natürlich auf einen saubebren Faden achten und etwaige Scheißepfosten melden.
Meine Devise lautet weiterhin: Informationsfaden mit Informationen von beiden Seiten.
Vielen Dank für die ausführliche Antwort. Bin ich so gar nicht mehr gewöhnt.
No.316
>>315I always am two hours behind (until refreshing the page)
t. travels even harder
No.317
>>315>>316Problem is known, the reason for this is that both the auto updater and the time adjuster are javascripts, and the time adjuster only runs on initial page load, so the newly fetched posts are base time zone, which is UTC. It's possible to fix this, not sure if I can do it though, might be a little messy. but thanks for the reports. In any case, just like
>>316 already mentioned, a reload will fix the existing posts.
No.342
>>279>In theory it might still happen the other way round, when a thread is opened in a separate window and misses a post that is already shown on the main page, though I've never seen it.I have seen posts who complained about this exact thing actually happening, so I now implemented a server-side directive that all html pages always must be revalidated upon load. I don't think the performance hit is relevant here, and it should fix the issue that you ever get to see content that's not equal to the latest content on the server, no matter if overview or thread page.
No.361
No idea if it's a bug or my laptop trackpad mousebuttons, but today I had a doublepost going off twice and getting a "flood detected" message.
What I mean is I pressed "Reply" and I got the message "flood detected" because apparently the post got sent correctly first and then immediately it tried to send it again.
No.363
>>361Might be related to
>>273 No.364
>>360Yes, this is true. I think Dollchan overrides the normal file selector script, and while the normal file selector script won't add any new input elements when there are already four of them present, Dollchan does not recoginze the limit. I am not sure why this is the case, it could be that the presence of the button for another file selector (which does not do anything when the maximum number is reached) is confusing Dollchan, and it replaces the not working button with a working element of it's own, and if the user tries to add a fifth file, it is rejected by the post processing routine. This is just speculation on my part, though. In any case, uploading more than four files isn't possible, no matter if Dollchan is used or not.
>>361>>363Yes, this scenario will result in a flood detected message. If multiple identical messages are posted in a short time, this is regarded as a flood attempt. Don't worry though, the first post should go through, and there is no autoban or whatsoever. Worst thing that could happen is an increased cooldown for posting, but even that will disappear after a short time.
No.365
>>364>uploading more than four files isn't possible, no matter if Dollchan is used or not.I found that out, yeah. I didn't really want to add more, just did it to see what would happen.
No.368
>>367I can see in our logs that a rather low post number was deleted by the user who posted it, it's likely that this was the joke thread. Unfortunately we have no realistic way to bring it back, I recommend opening a new one. To be suer (If anyone was wondering): It wasn't removed by a mod.
No.369
>>368Great, so one misclick is enough to delete entire thread and all replies in it? Could we alter this behavior? Like that user can't delete threads which are >1 day old.
No.370
>>369Probably possible, I'll have a look in the code. I'd try to design it in a way that only threads are affected, and not regular posts.
No.371
>>369>one misclick How did you even do it? No idea if that is different when NOT using dollchan but I have to check a box on the post (or thread if first post) I want to delete, then scroll down to the end of the page and click delete. No way I could do such a thing by accident.
No.372
>>369>>370It is implemented, threads that are older than one day can't be deleted by the user (mods still can of course) from now on, it will yield an error message that the thread is too old. I don't recommend trying it out on your favourite 200 reply thread! I also noticed a weird behaviour that sometimes I have the error message that the password would be wrong when trying to delete a thread. That is not related to the change in code, in fact that is an existing similar routine that prevents deletion under given circumstances, I don't know why this seems to have false positives on occasions. If you encounter any of this, please leave a report.
No.373
>>372>If you encounter any of this, please leave a report.I found out that I can't delete my own posts from inside the thread if I made them on the main page. Haven't tried the other way around yet.
t. dollchan user
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.