We were forced to revert our development website to a previous backup version from a few months ago. Before removing the more current version, we used your Toolset Module Manager to export all our Views, Post Forms and Access settings. We then deleted that version of the site from the server. We reverted back to the version of the site we needed and then installed the Toolset Module Manager plugin on that version. I started to import the Types .zip file, but the Review page seems to only include Field Groups, Fields, Post Types, Relationships, and Custom Taxonomies. I'm not seeing where it will import our Views. Did I misread what I exported from the old site. I hope not because getting that site back to do it again will mean having to set it up on another development subdomain, which will take a lot of time/effort.
Is there any way to import the Views from the site MySQL database? I have that easily accessible and can import tables from that pretty easily if I know what to import. I don't know the structure of how you store Views in the site database though so it may be more difficult than I'm hoping.
if you see closely you will have to drag/drop the views to the module you want to export.
But please note that module manager can be used to import/export classic views not the block views.
At least you have good news that you have took backup of your database.
Can you setup a staging site using the database backup you have and then send me admin access details and let me know what views you would like to export?
*** Please make a FULL BACKUP of your database and website.***
I would also eventually need to request temporary access (WP-Admin and FTP) to your site. Preferably to a test site where the problem has been replicated if possible in order to be of better help and check if some configurations might need to be changed.
I have set the next reply to private which means only you and I have access to it.
The problem is every time I migrate a site to a different domain, all my views break and I have to rebuild quite a bit of the functionality in them. I can usually easily do that by bouncing back and forth between development and production site and copying pasting anything lost, or redoing anything lost, but I won't be able to do that here. The development site with the views is off the server and the domain for it is being used by the version we reverted to. To set it up again, it would have to be on a different domain which will break the views. I never did get it figured out how to avoid this Views breakage on a site migration and I just decided it was easier to just rebuild them every time it was necessary rather than trying to get plugins like Duplicator to work properly. I always have problems with it as well, especially on the larger, complex sites like these that I'm building using Toolset, and I'm reluctant to force my clients to get Duplicator Pro because they've often already spent A LOT on recommended plugins through the development process. I hate having to hit them with one more at the end.
I thought I did drag all the Views over. That was the primary reason for me to use that tool. I was trying to preserve all the Views that were added after the point we were reverting to. Something may have gotten messed up in the process though. I can't rule out that possibility. But that would be highly bad luck for that to be the only thing that didn't work given that was the most important thing.
Is there any way to just pull the Views directly from the MySQL database? I can easily export any tables from the more recent database and import those tables into the database that's on the site now that was from a few months ago. I think that's the only way these views will be intact, unless I go to the trouble of deleting everything again, restoring the more recent site, exporting the views again, then deleting everything one more time and reverting the site one more time. I REALLY hope I don't have to do that here.
I haven't sent credentials here because I wanted to see what you'd say to this info before I try to set up another staging site. I just don't know how to do that on a different domain without having all the Views break.
But if you want to just export the view's then you should try to use the module manager but you will have to export required views as I shared information with my previous reply.
It's quite cumbersome to extract all view's information and as views are stored to posts table and postmeta table itself.
I would suggest the best way is not to interreact with database but setup a test site using the database you have and then try to export your required view's using module manager.
I've followed that FAQ page before and haven't had any luck with getting the third party plugins to work on large sites. I know I need to get Duplicator Pro, but I end up just getting frustrated, then biting the bullet and migrating manually and dealing with all the headaches that come with that. Previously, I only had to copy and paste some missing code and redo some of the top half of the views to get them working again. But now I'm seeing that other things are breaking using that approach with another client's site. One of our post forms started doing something weird and now I'm seeing that a date filter that was working before is no longer working. So I'll have to learn to get one of those plugins to work somehow or just tell clients that they have to buy Duplicator Pro.
I wouldn't mind setting up another version of the site on a different domain if I knew that wouldn't break the views. But when the Views break, that defeats the purpose of doing it as I still won't be able to get what I'm trying to get. So exporting with module manager at this point won't work on another domain. I have to set it up on this domain again, which means I have to go through that whole process of deleting the site, setting up the most recent one again, getting the views, then deleting that site and setting up the one I'm reverting to again. That's what I was hoping to avoid by asking about the MySQL database approach.
So views are located in posts and postmeta? It would probably still be easier for me to import those tables into this database than to go through all the deleting and re-uploading yet again. I really don't want to have to do that again as I spent hours getting everything working right again on the reverted site.
However, I'm thinking I may be able to just empty the current database after backing it up, then import the one with the views in it, export the views using Module Manager AND copying and pasting everything from the Views into a Notepad file or something like that just in case, then empty that database out again, then import the database from right now that I just backed up. I don't think I need to do anything with all the files on the server, because everything on the current site (that was the reverted site) has now been updated again. So this site is actually more current now.
However, I'm thinking I may be able to just empty the current database after backing it up, then import the one with the views in it, export the views using Module Manager AND copying and pasting everything from the Views into a Notepad file or something like that just in case, then empty that database out again, then import the database from right now that I just backed up. I don't think I need to do anything with all the files on the server, because everything on the current site (that was the reverted site) has now been updated again. So this site is actually more current now.
==>
I suggest that you should create another test site where you should use the existing database you have and once that site is setup you should export the view using module manager
Then try to import those exported view to the site where you want to import.
