I am trying to: use toolset without losing my mind
Link to a page where the issue can be seen: admin
I expected to see: my toolset plugins activated
Instead, I got: views won't activate since installing blocks. when i reinstall/acativate views, access, blocks and forms deactivate themselves. I can reactivate them but views will not activate. i think this is the cause of my issue in not seeing the option to 'create content template' in dashboard.
I'm not sure why you are seeing a problem with Forms, but you can't activate both Views and Blocks at the same time because they are essentially the same plugin, just with different default settings relating to which UI you see when creating templates and Views.
Install and activate one of them—it doesn't really matter which one.
Then go to Toolset > Settings and choose which UI you'd like to see.
As an experienced Toolset user it would probably be a good idea to choose showing both the new Blocks editor and the classic Views editing experience, that way you can create Views with the block editor but also use the editor you are used to in specific situations. (There are some features of Views that haven't made it into the block editor yet.)
Try that and then if you still have problems let me know.
oh, ok. i did choose both - so that part is ok - everything is functioning as it should. didn't realize they were the same since both are still in the plugin list. the site admin is really slow after installing blocks anytime i'm doing anything with toolset. it maxes out I/O really easily. taking hours just to make a few udpates. is there anything i need to do after installing blocks - should i delete views or anything?
is there something wrong with the way i installed blocks? or configuration? i've followed all the steps in the tutorials. screenshot - 'create content template' button missing from some types. 2nd screenshot, new page AFTER pressing switch to block editor.
I cloned the site and after removing all the plugins and theme but leaving fusion still had issues. i removed fusion plugins. now when i click new page, i do get the block editor with blocks. but if i click from a view to content template, it brings up block editor without blocks. memory issues seem to be gone, but things are operating slowing and if i'm in blocks on one screen and view in another, things lock up.
how do i use avada and blocks together?
still cannot install any module - goes to a 404 page when i click install from the library.
I had a site with some existing content and templates designed with fusion builder, and installed Blocks on that site and edited the templates, stopped editing with fusion builder, edited with blocks instead, and I didn't run into any obvious problems.
Do you have some specific steps I can try to recreate a problem?
I don't know what "if i click from a view to content template" means.
I think the content template for the view was created in fusion or blocks. so from the view you click to edit the content template in fusion/blocks. that's what i meant. honestly though - i really don't know what is going wrong since everything i try seems to not work or max out the server. maybe i should wait for the next toolset updates? is there any eta?
I'm not sure that an update will help, as there aren't any known performance issues being worked on, and I'm not seeing them on my own site with the current versions.
If you want me to take a look at your site I can, although a staging server would be better, as I'd want to check how the site performed with Avada and just Types and Blocks (and the fusion plugins).
I'll set a private reply in case you have credentials to share.
no, i don't know anything for sure! but just intuition - i think maybe i installed or updated or used something in the wrong order and it's causing issues for the whole site. do you want me to disable the plugins?
Maybe we could try with the Toolset plugins disabled and see how the backend behaves, and if it is working normally I can try activating Blocks and other Toolset plugins one at a time, checking the logs and using Query Monitor to see if something in particular provokes the problem.
