[phpBB Support] Komischer Effekt

[flumsi]

Hello everyone

phpbb3 3.3.1.4 & PHP v8.3.x

I discovered a small issue and don't know where it's coming from, let alone where I can fix it.

Maybe it has something to do with the style, I have no idea.
I've barely done anything in the last two days except for guild events.

Am I seeing something wrong, or has the distance from the reply button to the bottom of the first post changed?

Has it gotten bigger?

Also the display on the right side of the pages. Shouldn't Total Posts be placed horizontally in the middle of the page buttons?

Screenshot 2025-05-21 144115.png

Screenshot 2025-05-21 144130.png

[Stoker]

The best thing to do is check with another style, and/or disable extensions one by one until you find the problem

[pxdetroit]

.
I'm not seeing anything wrong, but it's hard to compare when the images can't be viewed side-by-side. Do you have access to both versions now or is one an older screenshot?

If you can load both pages separately try to line them up so you can switch back and forth in your browser. Your eye will notice tiny changes. Or take screenshots that are exactly lined up the same way. It sounds obvious but it helps when all else fails.

Can you "inspect" the pages in your browser? I use that trick constantly. It shows me the margin, padding, font details THAT THE BROWSER is actually pulling. (You know how phpbb has code split up into lots of different classes.) So "inspect" that area on both pages and see if anything is different.

I thought I had another idea but I guess I've forgotten it. Anyway, those are the two things I'd try first.

[flumsi]

Hello everyone

Sorry, I was a little involved in life

Right-clicked on that spot in the browser and clicked on Inspect.

Screenshot 2025-05-23 105926.png

Screenshot 2025-05-23 110051.png

Screenshot 2025-05-23 110105.png

[flumsi]

Screenshot 2025-05-23 105926.png

Screenshot 2025-05-23 110123.png

Screenshot 2025-05-23 112351.png

With the extension org. active and the

Code: Select all

.pagination {
    margin-top: 20px;
    justify-content: center;
    display: flex;
    flex-wrap: wrap;
}

With the extension org. active and the

Code: Select all

.pagination {
    margin-top: 0px;
    justify-content: center;
    display: flex;
    flex-wrap: wrap;
}

Changing to 0 and clearing the cache does not make any changes

So I deactivated the dmzx download system extension, and everything is working as it should.
This extension has been running for a long time and has never caused any problems.
It did receive an update in the last few days, but I didn't think that would cause a problem.

[Stoker]

You need to make sure you have updated all the files from that extension.
Double check and then ask the ext author what could cause it

[flumsi]

Hello everyone

@pxdetroit

Can you "check" the pages in your browser? I use this trick all the time. It shows me the margins, padding, and font details that the browser actually retrieves.

I had to get to grips with this feature in the browser at first, but it helped narrow down the error and find it more easily.
Thank you for that

@Stoker

It's best to try a different style and/or disable extensions one by one until you find the problem.

It wasn't the style, but an extension that you wouldn't have guessed.
Thank you for that

I'll collect all the data and contact dmzx in his support forum

[Stoker]

Juist to make sure, you have tried Control + F5 in your browser when vieving to page?

[flumsi]

Cache & ctrl+f5 are my best friends

[pxdetroit]

Cache & ctrl+f5 are my best friends

Wow! I never knew about ctrl-f5! I googled it and wow. All this time I've been clearing the cache from the ACP. I guess we're even now for the "browser inspect" tip.


Do you know more about the cache (or just that if it's not cleared your changes don't go into effect)?

I have a couple more for you to keep in mind. It's okay if you don't use these but just know stuff like this exists so when you get stuck again (it's a never ending cycle of bugs/fixes) you will not feel so hopeless.

Swapping out your "php.ini" file is an invaluable tool. Sure it takes a minute to set up the first time, and every time you want to swap them you have to get into your hosting account (unless someone knows a shortcut). But this will show you exactly what the error is, why it's an error, where it is, in which file, on what line. It's just about the most helpful debugging method I've seen.

Just know that if you get really, really stuck, you can fiddle with the "phi.ini" to rig it so your site will temporarily show (detailed) error messages on the screen. You have to change it right back obviously but it works like a charm.

The other thing is in the browser inspection there's a menu for "console" that is inside / next to the defaut "elements" window. That "console" will tell you in bright red letters if it finds any errors. "Console" will find different errors than (the modified file) php.ini. And make sure to refresh the cache "console" will get buggy. But it's also a good debugging tool.

Thanks again for "ctrl-f5" !!!!!

Don't forget: When all else fails temporarily change your php.ini to display errors.