Skip Navigation

[Resolved] I somehow lost an archive template when moving a site to new URL

This support ticket is created 2 years, 3 months ago. 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.

Sun Mon Tue Wed Thu Fri Sat
- 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 -
- 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 -

Supporter timezone: Asia/Karachi (GMT+05:00)

This topic contains 18 replies, has 2 voices.

Last updated by Waqar 2 years, 2 months ago.

Assisted by: Waqar.

Author
Posts
#2465527

I moved our site from development.floridastateforests.org to floridastateforests.org . I deleted our old key and set up a new one. But there was a lot of content that was broken in weird ways on the new site. I have fixed many of them already. But I'm currently stumped on figuring out what happened to an archive template that I had set up previously.

The archive page is here:

hidden link

The page to edit the template for this page is here:

hidden link

On this page, it says:

----------------------------------------------

There is an autosave of this post that is more recent than the version below.
View the autosave

View not found

----------------------------------------------

Note that my custom post types on this site are created using a plugin called Custom Post Type UI. I created our custom post types using this plugin BEFORE we purchased your plugin. Everything still worked using this, so I didn't bother with changing things to use Toolset to create these custom post types. I don't think this is what is causing the problem we're experiencing now because everything was working fine this way on the development site.

One other thing that might provide a clue is I had to redefine the post type in all our Views after moving the site. Our views were showing posts of all types and what I had previously checked to only show content of a specific post type was unchecked. That was an easy fix to just recheck everything. But this might have something to do with why this Meeting Minutes archive isn't working now.

Strangely, another archive page we have on a custom post type called Benefactors is working fine. I don't know what's different about the Meeting Minutes post type that would cause this problem.

Any assistance you can provide would be appreciated.

#2465603

Hi,

Thank you for contacting us and I'd be happy to assist.

Can you please share some information about what migration method did you use? We officially use and recommend these two plugins for migrations:
https://wordpress.org/plugins/duplicator/
https://wordpress.org/plugins/all-in-one-wp-migration/

In case, the issue persists using one of these plugins or if re-migration is not possible, you're welcome to share temporary admin login details of both these websites, so that I can compare the difference and troubleshoot this accordingly.

Note: Your next reply will be private and making a complete backup copy is recommended before sharing the access details.

regards,
Waqar

#2466705

Thank you for sharing the access details.

I was able to log in successfully, but I'm not able to access the website's admin area. It keeps redirecting back to the "My Account" page on the front end.

Can you please make sure that this user has the "administrator" role and share the steps to access the admin area if the website is using some different path or restriction?

I'm setting your next reply as private again.

Note: When using a manual migration method, the serialized data can become a challenge. To avoid that, you'll find some useful information in this official guide:
https://wordpress.org/support/article/moving-wordpress/#changing-your-domain-name-and-urls

#2469989

Oops. Sorry about that. I didn't realize I had changed that user account to Subscriber. It's set back to Admin now.

#2469991

The previous reply didn't take me to a private response. I did change the password, so please reset my next response to private so I can send that to you.

Also, sorry about taking awhile before responding, but we had to deal with the huge hurricane coming through here. I'm back to working on things now, so my next response should come quickly.

#2469995

Also, thanks for the info about not doing a global search and replace on the database. I didn't know that was an issue.

I just have bad luck with getting Duplicator to work on large sites, so I've always done it manually in those cases. I didn't realize that my method could cause problems too. I have two more enormous sites I'm currently working on (that also have Toolset installed) so I'll be moving them out of subdomains and into the root soon. So I'll follow what this page you've steered me to says on those. I think this site is working fine other than this one View no longer being present. It's in the system in some way, so I'm hopeful you'll know how to resurrect it. Otherwise I have to rebuild it from fuzzy memories of how I had it before. It's not a complicated layout at all, so rebuilding it wouldn't be a huge problem. Just remembering how I had it set up for styling will be the hard part to remember everything.

#2470547

Thank you for sharing this update and hope that the hurricane passed over safely, for everyone.

I've set your next reply as private again so that you can share the updated username and password.

#2472037

Yikes, it sounds very scary, but, glad it remained under control.

I noticed that out of the 2 WordPress Archives, the affected archive (Meeting Minutes archive) doesn't look like it was created using the blocks editor.
( screenshot: hidden link )

Yet, when its edit screen is opened, it uses the blocks editor and not the classic/legacy editor. Can you recall if it was originally created using the classic editor or the blocks one?

From this archive's block editor screen, the option to "Use the Classic Editor" can be used to switch the environments, but I'm reluctant to use that option because it will reset the archive.
( screenshot: hidden link )

Is it possible to make the old development website accessible again? It will allow you to see how this archive was originally set up and recover it from the database or recreate it, if not too complicated.

#2473565

Yeah, I'll get that set up again. Give me a bit to get this done. I should have thought about that before removing the development site.

#2473739

OK, I have set up the development site again. I tried to do this myself, but I'm hitting a snag. I deleted the Meeting Minutes archive that was present on the now live site. I then went to the Toolset Dashboard and tried to create a new Meeting Minutes archive. I copied the block that I had present on the development site version of the archive and was ready to paste that into the new one on the live site. But now I can't get past the initial formatting screen on the live site.

I'm on the initial design page that says:

WordPress Archive - Design
Use WordPress Archive Elements

Pagination

Front-end sorting

Search
Select WordPress Archive Loop Style

I'm clicking on Unformatted and have Pagination selected, but then nothing happens. I thought it would open up the block editor after I chose the archive loop style, but it won't do anything letting me past that page.

If you can get me past this snag, I should be able to paste in the code that I want to execute on this archive page. The credentials for the live site are the same as before.

#2474045

Thank you for sharing this update.

The website has the "Classic Editor" plugin active that limits/restrict the features of the new blocks/Gutenberg editor.

This is why, when you try to work with a WordPress Archive created through the blocks editor, it is not getting created successfully.

You can set the default editor for the archives to "Classic Editor" from WP Admin -> Toolset -> Settings -> General.

After when you'll start creating a new WordPress Archive, the classic editor and not the blocks editor will be used.

#2474163

I have Classic Editor installed on all the other sites I'm working on with Toolset and I don't think I've gotten stuck on this spot when setting up an archive within blocks before. I prefer to use the Block editor for building these archive pages. Should I try temporarily deactivating the Classic Editor plugin and then reactivate it if I'm able to successfully create the archive in the block editor?

#2474685

Yes, you're thinking on the right lines for troubleshooting this.

You can temporarily deactivate the Classic Editor plugin and then try creating an archive again.

If that doesn't work, you can temporarily disable all non-Toolset plugins and switch to a default theme like Twenty Twenty-One. If it's fixed, you can start adding the disabled items, one by one, to narrow down to a possible conflicting one.

Let me know how it goes and in case the issue with the creation of the archives persists, I'll need your permission to download a clone/snapshot of your website, to investigate this on a different server.

#2476387

Deactivating Classic Editor did nothing.

Disabling all other non-Toolset plugins did nothing.

Changing the theme to Twenty Twenty-One revealed that my theme was obscurring seeing a Next button on the layout screen. I then tried selecting the layout and hitting Next. That took me to a screen about choosing the loop. It was set to the Meeting Minutes content type correctly, but beneath that there was only a Back button. That took me back to the layout screen. I still couldn't get out of that. So I put the theme back and reenabled all plugins and am still stuck.

I've asked the client for permission for you to clone the site. It shouldn't be a problem, but I have to ask first. More later.

#2477329

It's OK to clone the site. Let me know what you need to do that.

I have more issues to report with this same problem. I now saw that all our custom code within the Search and Pagination sections of our Views reverted back to default on the site move. I've re-added all of those now. Another thing I'm seeing is that two of our archive pages have somehow moved into the Views section. So some seriously strange stuff has happened as a result of moving the site from development.floridastateforests.org to floridastateforests.org.

I'll let you know if I notice any other issues as a result of this move, but for now I cannot rebuild the archive page that we need working -- Meeting Minutes archive. Everything else with our site seems to be working as before. It's only these strange issues with Toolset that I'm seeing so far.