Discord-logo.jpg Join our Discord!
If you have been locked out of your account you can request a password reset here.

User talk:Bunni

From Internet Movie Firearms Database - Guns in Movies, TV and Video Games
Jump to navigation Jump to search


Archive 1 Archive 2

Upgrade Issues

If you notice any upgrade issues, or hit any errors on the site, you can let us know here or email manager at imfdb.org

Known Issues

Issue: MediaWiki no longer allows accented characters in page titles. 1,606 pages that had accented characters in their page titles have been moved to new pages with the Broken\ prefix. Plan: We are working on a script to automatically move these pages to new pages with valid titles.

Issue: Some images are missing. Plan: We are working on a script to automatically pull these images from the backups.

Issue: Full SSL encryption is now enabled. If you were logged in via http your cookie may no longer be valid. Fix: If you see errors related to 'session hijacking' clear all imfdb.org cookies and log in again.

Panzerbüchse 39

The Panzerbüchse 39.

PzB 39 Anti-tank rifle - 7.92x94 mm (Patrone 318)
File:Sniper5 Panzerbüchse 39 hold.jpg
Holding a Panzerbüchse 39.
File:Sniper5 Panzerbüchse 39 aim.jpg
Aiming a Panzerbüchse 39.

There is a problem with this weapon. The link is not working. The German letter (ü) does not work in the link. --Emto_PL (talk) 08:47, 4 September 2022 (UTC)

Thanks, this is the same issue as the page titles. There is a script to 'fix' the image titles but I'm not 100% sure of its consequences so I'll try it on the development server first and report back. --bunni (talk) 16:19, 4 September 2022 (UTC)
When will the bug be fixed? Lots of websites are down all the time.--Emto_PL (talk) 11:37, 14 September 2022 (UTC)

"Keep me logged in" doesn't work

Every time I visit IMFDB after previous closing of the browser, and even after I closed the tab with the browser still active, I have to log in again, despite I check the "Keep me logged in" box every time. This happens regardless of whether I performed any actions, or just visited the site. I changed the previously used eight-digit password to a ten-digit one, as recommended, but nothing has changed. I use Firefox, hadn't a chance to test in on Chrome or Edge. Sorry to disturb you with this issue, it's not a fatal problem, but it would be good to solve somehow in the future, it if possible. Thanks. --Greg-Z (talk) 15:38, 4 September 2022 (UTC)

Can you try specifically going to the https://www.imfdb.org version of the site? You have to type it in manually in the search bar, you'll know you have it because the you'll see a lock in url bar. For me that keeps me logged in on Firefox, Safari, and Chrome. If you have restrictive cookie settings or a cookie blocker that might also be logging you out. We'll move to a 100% https site for everyone next week. --bunni (talk) 16:25, 4 September 2022 (UTC)
Following your instructions, I typed the address and was redirected to http://www.imfdb.org/wiki/Main_Page with crossed out lock in the url bar. Then I logged in, checking the box, then closed the tab, opened again the HTTPS address - and was not logged. Sorry, maybe I did something wrong?
If you click the Random page link does it take you to a https version with a lock in the url bar or a http version with a broken lock? For me I don't get a redirect if I manually type https in the url bar and Random page sends me to https with a lock in the url bar. If Random page doesn't send you to https then you may have a 'preferHTTP' cookie that keeps redirecting you to http, you could try clearing cookies in your browser for imfdb. In Firefox if I click the lock there's a dropdown for 'Clear cookies and site data...' --bunni (talk) 17:06, 4 September 2022 (UTC)
As far as I know, I don't use any restrictive cookie settings or a cookie blocker. At least I had no problems with keeping logged in the old version. I'll try to inspect my browser for any possible cookie problems, and also I will try to install Chrome and test it. If the problem will still exist, and nobody else suffer it... OK, it's not fatal, I will just log in each time. :) Thanks! --Greg-Z (talk) 16:51, 4 September 2022 (UTC)
When clicking Random page, I get into HTTPS page with lock. I installed Chrome, and everything works perfect, so the problem was only in Firefox only. After cleaning Firefox cookies, I'm logged in correctly, so looks like the problem was on my side and now it is solved. Thanks for advices, and again I apologize for disturbing you. --Greg-Z (talk) 17:24, 4 September 2022 (UTC)

Thank ya

Ey, Bunni. Thanks for upgrading the website for us, I finally now have access to this account (after checking my spam folder on my email). I've seen the reports of it that was going on the Talk:Main Page and the development on it, glad to see it finally worked out there. Also, I'd give thanks to User:Ultimate94ninja too since I asked them about the problem I was having earlier. --XSlayer300 (talk) 01:32, 6 September 2022 (UTC)

Another Issue

Hello, Bunni. I don't know if this has been addressed elsewhere, but I also have a problem: I updated the Verdun page with new images a week before the website upgrade. These were processed and shown correctly. But now the older images are back on the page.--HighPhigh (talk) 09:51, 10 September 2022 (UTC)

I've had the same issue on other pages. The replaced images (after waiting the usual little while) had successfully updated themselves, but after the site upgrade a couple days later they reverted to their older versions, and are still stuck that way. Alex T Snow (talk) 22:44, 11 September 2022 (UTC)
I think the issue here is that there's a window of a few days before the site upgrade where updated images didn't get their new versions copied to the new server, I'm currently working to verify this. The updated images should still exist on the old server and in the backups. --bunni (talk) 22:53, 11 September 2022 (UTC)
That would make sense to me. For clarity, the actual updated image files themselves didn't revert and are still here on the site, it's just the pages that use them are still displaying the old version. As if the "page" didn't "ask the server" for an update, for a rather layman's way of putting it. Alex T Snow (talk) 23:04, 11 September 2022 (UTC)
Oh interesting. Can you link me to one of these pages? There may be a maintenance script that I need to run to update these pages. --bunni (talk) 23:08, 11 September 2022 (UTC)
One is on Strike Witches: OVA, second image in the Bofors section. The image file page also still shows the old preview (in both places) but also lists that I did in fact update it, and if you click on the image and open it fully it does actually display the new version (stitched image with more visible on the left side). In my experience this is all totally normal after updating an image, but only for a few hours-ish until the server realizes something has changed (or similar), the difference here being that I updated these almost two weeks ago. Alex T Snow (talk) 01:37, 12 September 2022 (UTC)
Possibly the problem is somehow connected with the fact that the last update of the cache was more than a week ago - 3 September 2022?--Greg-Z (talk) 06:52, 12 September 2022 (UTC)

Page titles with special characters

Hi, I don't want to sound like I'm rushing you guys as I'm sure it's a headache trying to fix all this, but when it comes to page titles that now have "invalid" characters should we keep waiting for that fix script/etc you mention, or is it okay to rename them to something that works manually? I just don't want to step on any toes or screw up a larger-picture fix by fixing something individually. Alex T Snow (talk) 05:02, 17 September 2022 (UTC)

We're working with someone now to build a script for both the Broken pages and the broken image names that have accents, but that process will probably take 2-3 weeks, in the meantime it's okay to rename them manually, it won't harm anything. --bunni (talk) 16:23, 17 September 2022 (UTC)
Thank you! :) Alex T Snow (talk) 18:53, 17 September 2022 (UTC)

Do Not Sell My Personal Information