[Closed] Edited archive page is not the one appears on front-end

[Author]

Posts

[jakubN]

Hello,

I recently migrated test site to production with Toolset.

I made an archive page showing custom post "EVENT" before migration

After migration i faced few issues, especially with editing archive page template.

Those problem pushed me to make a new archive page template which should replace the first one.

Now i have a problem that when i look on front end i see post id "30569" (new one) as archive page, but when i go to edit tamplate on backend it redirects me to template as post id "30570" (older one).

[Jamal]

Hello and thank you for contacting the Toolset support.

Actually, both IDs are part of the same archive template. ID 30570 is equal to (30569 + 1). Toolset archive templates, built with the blocks editor, use two posts per archive on the database. The first one is the archive template wrapper(30569) and the second one(30570) is the archive template content. That's why the first one appears on the list of the archive templates, and the second one on the address bar while editing it. It is, therefor, expected that you will be edited from the 30569 URL to the 30570 one.

This being said, I wonder if you are having any issues with this template? Are you able to edit it and see your updates on the frontend?

[jakubN]

"This being said, I wonder if you are having any issues with this template? Are you able to edit it and see your updates on the frontend?"

Yes, exactly. On front-end and back-end i have like two diffrent templates. Changes made on backend doesnt show on frontend.

[Jamal]

Maybe you have some kind of cache that is still holding the rendered archive for the frontend. Please purge any caching plugin, and if your hosting provider has some kind of caching, purge it too.

If that does not help, allow me temporary access to your website to check this further. Your next reply will be private to let you share credentials safely. ** Make a database backup before sharing credentials. **