[Gelöst] Split: Home Page View – Featured Product Display – Full width screen display
This support ticket is created vor 5 Jahren, 9 Monaten. There's a good chance that you are reading advice that it now obsolete.
This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.
Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.
Heute stehen keine Supporter zur Arbeit im Werkzeugsatz-Forum zur Verfügung. Sie können gern Tickets erstellen, die wir bearbeiten werden, sobald wir online sind. Vielen Dank für Ihr Verständnis.
Thank you for the great effort. I'm not happy with Divi over this but I obviously have to look in a different direction. This ticket is going to splinter in subject now and I will understand if you have to switch it to a new one.
There is still a problem with this. The client now insists on being able to add the top header image at will themselves. The problem with that is that currently, the client has to log into the Toolset view to change the image but there are three problems:
1. My clients do not have full admin privileges to their wp-admin, I provide them the user level of either Shop Manager or Editor.
2. If the client were able to access the View, it would be a confusing and problematic experience for them on the backend.
3. The Divi frontend Visual Builder does not work with Toolset Views.
I think a frontend form with Toolset might be the next logical direction to go but I have never created one. Do you think that could be a solution and if so can you direct me?
"The client now insists on being able to add the top header image at will themselves"
This that you are referring to is the main banner at the top of the site here versteckter Link?
"1. My clients do not have full admin privileges to their wp-admin, I provide them the user level of either Shop Manager or Editor."
You can provide them with an editor account, this way they can edit the page on the backend and change the image should they feel like.
"2. If the client were able to access the View, it would be a confusing and problematic experience for them on the backend."
I agree that this might be a bit problematic as if the client isn't very familiar with the setup then they can change something that might end up breaking the page. However if you provide a proper tutorial and walk them through the steps then this should be possible.
"2. The Divi frontend Visual Builder does not work with Toolset Views."
You are correct that it doesn't work.
"I think a frontend form with Toolset might be the next logical direction to go but I have never created one. Do you think that could be a solution and if so can you direct me?"
The problem here with Toolset forms is that it can work to customize the homepage, however this image section was added using Divi, so this will need to be edited on the backend. Because with the frontend forms you can only edit the fields that are directly on the Post itself.
There are some unresolvable issues between Divi and Toolset as they apply to this particular project case. I have to ask, what components, page builder etc., in your opinion would have been a more efficient way in constructing this particular project, in case I should want to recreate it?
Each page builder have their own advantages and disadvantages and it just unfortunate that working with Divi and Toolset caused so much.
It actually boils down to personal preference. I cannot give a recommendation at this point because each builder's special cells are made specifically to how their developers would want it. This in turn means that our views plugin won't be able to provide contents for these sections.
Personally If divi didn't have issue with Bootstrap then it would've worked well. However Elementor is a viable option that doesn't have issues with bootstrap.
I believe the conflicts with Divi may increase over time as they announced that they are developing their own dynamic content functionality. It was suggested by one support agent that I replace Toolset with their beta dynamic content feature but since they do not have a way to link such to an automated template system, I would have to install the template from the template library each time I wanted to add a page, post, project or product.
Although I still struggle with Toolset apps, aside from frontend page builder issues, essentially I'm satisfied.
I have looked at Beaver Builder, Elementor and others. Is there a logical workflow for switching to Elementor or would it require a ground-up rebuild?
Sorry to hear about this and that I cannot provide better assistance on this.
However switching to a new builder for future projects would require a build from the ground up.
Though since the toolset items are already built you wouldn't need to do anything to those, you would just need to setup the pages with the builder in a way you like.
It should be noted that with Elementor you are not able to use their builder in views to design the loop output like with Beaver Builder and the Divi builder.
Thank you for this information. Allow me to clarify, I was referring to a redevelopment of the site by replacing Divi Builder entirely and rebuild it with Beaver Builder and the previously created Toolset Modules alone.
This particular site is very important because it is intended to be the base theme for other similar sites. With the current situation, I would be duplicating a problematic website.
In your opinion, would it be logically possible to save the current Toolset Modules for the site > migrate them to a new Beaver Builder - Toolset installation > reconstruct the site (without Divi)?
For the most part that is correct but whatever that was built in DIVI would need to be reconstructed in Beaver Builder.
So some of your views use content templates from Divi so those would need to be redone to use Beaver Builder. Migrating over the views themselves and anything that is toolset related would be completely fine.
However you know i'm here to assist if there are any issues arising with this.
Divi has worked out well for me in other websites but this is an important project and the incompatibilities are going to bear a lot of weight. Before I get in any deeper, I'm going to redevelop it in either Beaver Builder or Visual Builder.
Can this ticket be slit that this point to stay on topic?
