To make the image display full width, first select the parent Group or Row block, then set that container to Full Width alignment.
After that, the Image or Cover block inside it will be able to expand properly.
Try:
- Select the outer Group block
- Set Alignment → Full Width
- Then select the Image/Cover block and also choose Full Width if available
This might resolve the problem. Refer below image for visual guidance:
https://drive.google.com/file/d/1MK9b1HxWx25kza0TOiId4XGDPFbgBoee/view?usp=sharing
I learned that if you put a image that you want to be full width do not put it into a row, change the row to a group and it works
How ever I still have my problem
I created a custom template that uses a custom header template part.
If I use the Twenty-Twenty-Five “Pages” template I have no problem getting Full Width on my images however if I change to my custom template I do not get full width
Can the content part of a page ininherit settings from the Header
Just figured it out. In the template after header there is a Group in the “Pages Template” there is no option to make this Group a wide width. However after this Group there is a child Group which you can make a wide width and this solves the problem
The issue is usually caused by the parent container limiting the image width. Full width images only work if the theme and parent blocks allow wide/full alignment, so when an Image block is placed inside a Group or Row block, the “Full Width” option can disappear because those containers restrict the layout. Try checking the parent Group or Row settings and disable content width restrictions or set the container to full width.
Also make sure your theme supports wide alignment. For the Cover block, it behaves differently from a normal Image block because it crops images to fit its container which is why the image may appear narrow instead of showing the full media size. Check the Cover block alignment, focal point, and minimum height settings, and test placing an Image block outside the Group or Row to confirm whether the container settings are causing the problem.
-
This reply was modified 1 week, 1 day ago by
danialtaqi6.
-
This reply was modified 1 week, 1 day ago by
danialtaqi6.