Uffff ... well, this is a serious limitation.
You should incorporate some mechanism to do this.
If you want Toolset Block to be your system to make pages and posts you will have to implement this mechanism.
Regards,
Jose
This will go directly to the team responsible for handling the feature requests.
It will greatly help if the developers extended our container block so that it is able to break out of the theme's container div.
However one work around is possible, if your theme supports a full width layout, then what you can do is set the page to full width and then add a container block and set a fixed width for this container for your other content.
So what ends up happening is that your image block will be full width but your actual content would be in a fixed width container.
Hi Shane,
I have already sent the suggestions.
No. My theme is DIVI.
DIVI allows different page widths for pages built with DIVI, but not for pages built with Gutenberg.
Thanks for your help.
Regards,
Jose
Given that the them you are using is Divi, I would recommend using the Divi builder to build your page and then add the view to that page using our Views Shortcode.
The only disadvantage to this is that you will need to use the classic builder for you Blocks plugin, which can be enabled by going to Toolset -> Settings , Scroll to "Editing experience" and enable "Show both the legacy and Blocks interface and let me choose which to use for each item I build".
Secondly what you can do is to create a content template for the page and set it to full width in the divi settings for that content template.
Then you can use the block editor on this content template to achieve something similar because of the container block that we have, you can set a fixed width for that container and anything within that container will be a boxed layout and anything outside will be full width.
Please let me know what you think of this idea.
Thanks,
Shane
Hi Shane,
For this particular case it might be possible, however, for other things it would not be possible, for example archive pages and other similar pages.
Thanks,
Jose
In the other cases then you would need to use the Divi builder to build out the archive and just load the elements you want from toolset using our Toolset shortcode for views.
This should also produce your desired results as well.
So there are some limitations here that we can try to workaround.
Are these other issues related to this exact thread?
If so you can let me know what these issues are.
Whenever the issue is different from the original issue of the thread we always recommend that a new thread be opened so that it can be tracked separately.
Yes, I have other unsolved threads created.
Regarding the solution that you have given me, it would surely not work to use DIVI for the archive pages, since Toolset has problems with the editing buttons of new types to call forms of Toolset Forms, I was with Waqar a long time with all kinds of problems In this style and in the end to make it work we had to use Toolset pages and not use DIVI.
Thanks Shane.
Where you have the edit form in content template, could you try removing the divi builder from it and just add the shortcode itself to the content template?
Also I know that with the divi theme builder customers have been having issues and this is because divi made changes to the post variable that is currently breaking alot of shortcodes.
So try doing this and let me know. Secondly if you create a content template for your post without divi and add the edit link for the form does it work?
From the video i see that it doesn't work when it is in the divi theme builder.
Thanks,
Shane
This ticket is now closed. If you're a WPML client and need related help, please open a new support ticket.
