The blog archive template in the backend is displayed incorrectly.
Yesterday, I created a new blog archicve template for a new post category. Today, I wanted to make some adjustments to the template, but I noticed that it looks completely different from how I originally designed it. It seems like the archive template is displaying content/layout from the single post template of the same post category.
However, on the frontend https://www.uxsense.eu/category/ux-beitraege/, the post archive template is still displayed correctly.
Single Post Template (Backend, is loading correctly)
Archive Post Template (Backend, doesn't load correctly)
Archive Post Template in Frontend (Is loading correctly, but not in Backend)
Comments
Hi,
Please see the following article:
https://support.muffingroup.com/faq/bebuilder-content-different-from-frontend-missing-styles/
Ensure that your WP URL settings are correct.
Thanks
Thanks, but the article describes a different issue. In the article, the template is displayed correctly in the backend (WP-Admin), but not on the website frontend. In my case, the template is loaded incorrectly in the backend (WP-Admin), but the frontend is displayed correctly.
My settings in WP-Admin, as described in the article, are correct.
Please send us the WordPress dashboard and FTP access privately through the contact form, which is on the right side at https://themeforest.net/user/muffingroup#contact and we will check what might be the reason.
Notice!
Please attach a link to this forum discussion.
Sending incorrect or incomplete data will result in a longer response time.
Therefore, please ensure that the data you send are complete and correct.
Thanks
I could not enter your website:
Can you whitelist Poland, please?
Thanks
done
You had the same slug for the single post template and archive template, which caused this issue.
After we changed the slug, the template works properly.
Please check it out now.
Best regards
Thank you for the quick fix.
Will this issue be addressed in a future update?
If the system has problems with identical slugs, there should be a validation preventing the use of already existing slugs.
Will you consider improving this in upcoming releases?
Best regards
The theme does not generate slugs, WordPress does.
So it is not a theme-related issue, and we do not have influence on that.
Best regards