If you deactivate Meow gallery the view is correct again? Then I would recommend you to contact their support forum: https://wordpress.org/support/plugin/meow-gallery/
as I wrote, I did that (was my first thought too ;)) This is what they said:
This might be an issue with your theme. The way the archives are displayed depends on the theme. Would it be possible that it displays the shortcode, and because of its size, it doesn’t render the rest? If you can try out some default or other themes to see if the issue persists, that would be helpful. Thanks!
I then did a preview with some other default theme, and there it worked, so it seems to really relate to the theme. No idea what the part with the shortcode means 😉
Unfortunately, that’s exactly what makes it difficult for me to understand. I have just tried to recreate what you have:
- a page in which blog posts are listed. The template contained in TwentySeventeen is used for this.
- a post to which a feature image is assigned and which contains a meow gallery in the post content. I have compiled the latter in the block editor using the Meow block.
In the output, I now see the feature image first in the list of blog posts for this post, then the content of the post. The problem is therefore incomprehensible to me.
Have I overlooked something in what you have done?
By the way, there is also a support forum just for TwentySeventeen: https://wordpress.org/support/theme/twentyseventeen/
And there is also a general German-language support forum: https://de.wordpress.org/support/
maybe some images will help 😉
https://www.dropbox.com/scl/fi/2zm6ttgd734f2digjzoo6/Screenshot2024-09-01163723.png?rlkey=6za1dn0sucavmqf6sctrim1sk&dl=0
this is the list view of the post (hope the dropbox link works)
and this is the resulting view https://www.concertshots.de/blog/ (note the posts below work correctly, done with Nextgen Gallery), the first Meow Gallery is displayed
In your screenshot you can see that you are using the gallery block of the block editor – not a plugin. Given your new description with Nextgen Gallery, I’m wondering what exactly it’s about. I can’t reproduce the problem with either the normal gallery block or Meow Gallery (which you apparently no longer use?).
Can you write a very simple post on your site? Just consisting of the title, a short introductory text, a post image and a gallery. Then see how it is displayed in the list of posts. It works fine for me. If it doesn’t work for you, a plugin you are using is to blame. You would have to deactivate all of these to exclude them.
However, if this compilation works as expected for you, then the strange display is due to the other posts being displayed incorrectly. This could also be a difference in content, possibly caused by a plugin.
that was a good find, you’re absolutely right, it was a standard gallery… switched the first one to Meow, behaviour is still the same tough. I made a test post (first one here https://www.concertshots.de/blog/), and it works as it should, however I get a “forbidden” when I try to enter it (completely different problem I guess). In the log I have this
[Sun Sep 01 20:29:45.239385 2024] [autoindex:error] [pid 807447] [client 77.9.46.89:50187] AH01276: Cannot serve directory /var/www/vhosts/concertshots.de/httpdocs/test/: No matching DirectoryIndex (index.html,index.cgi,index.pl,index.php,index.xhtml,index.htm,index.shtml) found, and server-generated directory index forbidden by Options directive, referer: https://www.concertshots.de/blog/
I have permalinks set to postname, so theoretically it would be correct, but it seems to try to access a physical directory with that name, which obviously doesn’t exist… Other than that, in blog view it looks correct so far
-
This reply was modified 8 months, 2 weeks ago by
TauTau_de.
Yes, /test/ is used as a test directory for some hostings.
If it works with this one in the list, then it must be due to something else in the other entries.
good to know… deleted that one and created a different one, and it works… really confusing 😉 So it must have something to do with the post itself
To find out, you could edit the post in the code editor. See: https://www.pair.com/support/kb/gutenberg-editor-how-to-access-the-code-editor/
There you will see the code of the blocks. Save the complete code in a text program next to the browser. Then you can remove some of the blocks as a test and then check the list after saving to see if the view changes. This way you might be able to find the offending block.
Of course, you can also do this in the visual editor. You just won’t be able to save all the content so quickly there.
just to finally solve this: I recreated the post (since text was just copy&paste and the Meow galleries were already there), this was easy and fast. And it now looks like it should. I received the initial text as Word document, maybe there was something weird in when copy&pasting from there. In the future I will only use text-only to prevent this… again something learned 😉
Nice if you were able to solve it. You are welcome to set the topic to solved.
cannot be empty for resolve 😉
