misterfu

Thank you so much, @gerygreen – that fixed it!

Also thanks to @threadi again, this was the right direction… just two additional lines missing.

I’m really happy now… ??

Hi @threadi – yes, I removed the CSS again as it did not work. Just added it again, purged all caches. Disable minify JS/CSS/HTML as well.

But now all images below the big featured image are completely gone.

Hi @threadi – thanks for the idea and pointing me into this direction.

Website is now back (we experienced a bigger HDD issue and the whole RAID had to be restored, of course things like this always happen on the weekend…), but unfortunately the proposed interim solution does not work for me.

Thank you, @clorith!

I have now deactivated multiple plugins (incl. combination of CSS) and cleared all caches.

Unfortunately, the issue still exists: https://www.jawattdenn.de/jawattdenn/hopping/sgs-essen-tsg-hoffenheim.html

My frontend debugging skills are unfortunately not good enough to see what’s wrong here… Any idea what else I could try?

@ninjateamwp Thank you – just reached out to them!

Hi @boppar – what always worked for me is to deactivate the plugin, clear the page cache completely, remove the plugin and then upload the ZIP file which I have downloaded from the Envato Market. In my installation it takes some time until all folder are shown again (due to the number of folders & files, I assume), but this worked multiple times. I did not lose any data so far.

@ninjateamwp

I am using “Sort Files – By Name – Name Ascending” and this is the order order the first 15 images:

20210116_RWL_22_SCW_RWE0001.jpg
20210116_RWL_22_SCW_RWE0010.jpg
20210116_RWL_22_SCW_RWE0011.jpg
20210116_RWL_22_SCW_RWE0012.jpg
20210116_RWL_22_SCW_RWE0013.jpg
20210116_RWL_22_SCW_RWE0014.jpg
20210116_RWL_22_SCW_RWE0015.jpg
20210116_RWL_22_SCW_RWE0016.jpg
20210116_RWL_22_SCW_RWE0017.jpg
20210116_RWL_22_SCW_RWE0018.jpg
20210116_RWL_22_SCW_RWE0019.jpg
20210116_RWL_22_SCW_RWE0002.jpg
20210116_RWL_22_SCW_RWE0020.jpg
20210116_RWL_22_SCW_RWE0021.jpg
20210116_RWL_22_SCW_RWE0022.jpg
etc.

Can you see the issue now?

0002 is listed between 0019 and 0020. This is not correct, it should of course be listed directly after 0001 (which e.g. the ‘ls’ command in the shell does).

Thanks in advance.

Hi @ninjateamwp!

Thanks for the quick response. Maybe it did not become very clear in my initial post why I’m sure that this is related to a sorting-bug in Filebird. Let me try to explain in more detail:

To avoid any confusion, let’s not talk about galleries and how something is displayed in the frontend. It’s also happening in the backend.

If I select the Filebird Media Library and navigate to one of the folders I have created, I can sort files by name ASC or DESC.

First image I can see in the main grid view has filename

20210116_RWL_22_SCW_RWE0001.jpg (OK)

By already the second image in the grid view is:

20210116_RWL_22_SCW_RWE0010.jpg (NOK)

It goes on with:

20210116_RWL_22_SCW_RWE001[1-9].jpg

Before then this image is listed:

20210116_RWL_22_SCW_RWE0002.jpg
etc.

That’s why I think there is a small bug in the filename ordering. Maybe the zeros are stripped from the filename, just a guess?

Awesome – thank you so much, upgraded to 2.5.2, can confirm the fix.

Sure, see for example here:

https://www.jawattdenn.de/jawattdenn/hopping/sgs-essen-vfl-wolfsburg.html

Hi @htmgarcia,

Values are:

“Link to”: “None”
“Image Size”: “Thumbnail”

• This reply was modified 4 years, 2 months ago by misterfu.

btw: This is how it looked in the fronted:

https://share.rwe-network.de/prive_torsten/failed_to_load.png

Hi @rafinkhan – sorry, error appears again. Very strange, it’s now happening every time when I’m editing a post and then try to save it.

But hey… at least it’s now reproducible and I can confirm that manually applying this change fixed it:

- if (\method_exists($current_screen, 'is_block_editor')) {
+ if ((\is_string($current_screen) || \is_object($current_screen)) && \method_exists($current_screen, 'is_block_editor')) {

• This reply was modified 4 years, 2 months ago by misterfu.

Thanks @rafinkhan – I discovered this when I upgraded the plugin from an old version to the most recent one. After I have re-installed it from scratch I could not longer see the error.

Thank you for the fast feedback, @twentig!

Even if WordPress is still only ‘beta compatible’ to PHP8, it’s already running really smooth. Thanks for considering the fix in the next version of the plugin, as well!