I also noticed that the “Post” template page did not upload to my server after re-publishing all files. It’s not there.
Just a quick short update. It’s already quite late here in Switzerland.
I’ve taken a look at it — which wasn’t exactly easy — and I do have a suspicion.
It is most likely related to the complete page structure, meaning the overall setup of your website. It’s really quite messy. Please don’t take this the wrong way, but the way your site is structured, with the paths and the .html pages, is probably causing conflicts that lead to the issue.
I’ll take a closer look again tomorrow.
Thanks, Got it.
In my own defense the website has evolved over a few decades. My first site went up in 1997. I think I started using Rapid Weaver around 2007. Search results from more than 20 years ago still point to the extra pages I have there. That’s why I have not deleted them. Some of them I keep in case I want to reactivate them.
Still, why should that interfere with Elements cms? If it does, that seems like a problem that Elements should correct.
In my view, if the cms is setup correctly, it should just work.
Thanks @Pegasus for looking at it. 
@jazzvibe I had time to really dig into the project file tonight, and there are multiple issues.
The primary one though seems to be an issue with the Lander project you are using (pinging @MultiThemes because I don’t know if this is coming from the project side of things, or our side @dan..)
The page filename is showing up on every single one of your pages, not just the blog/cms pages, and that seems to be coming from the Lander project based on cruftlessLinks being set to false in the project’s data.json file per the below.
We don’t have a Cruftless Links setting in Elements (not that I’m aware of anyway) like we do in Classic (Tidy Website Links), so I’m not sure why/where this gets set (I guess it’s set manually in the project file?)
For example take a look at our Microblog project file, Cruftless Links is set to true.
If I visit Lander for Elements I don’t see a bunch of pages with index.html and index.php in the URL so I’m assuming something got borked somewhere for @jazzvibe’s project file specifically.
Anyway, I changed cruftlessLinks to true in your Lander project’s data.json file, saved it, and that resolved the issue of index.php and index.html showing up in the URL on all your pages (including the blog/cms pages).
That didn’t solve the problem though. Your blog page loaded fine:
But your individual posts pages weren’t showing any content:
So, I again compared your project file with our Microblog project file, and noticed the following:
So, I just made yours look the same:
Then I republished your project file, and the individual posts are showing up normally now:
Anyway I’ll send the corrected project file to you via DM because we shouldn’t be sharing project files on the public forum when they were built with third-party developer’s paid project files (the new Elements Store solves this problem )
I’m also removing the links to your project file in your previous posts so nobody else can download it.
Hope that helps resolve the Blog Saga. Let me know if you have any troubles with anything else.
Thanks Dan, I’m guessing Lander shows up because this Elements site was imported from my Classic site which was using Lander at the time I imported. I rebuilt the pages manually in Elements from the basic import layout Elements provided. I’m not using Lander since moving to Elements.
Did this happen because of importing my Classic site into Elements, is that what’s going on?
Oh ok, that makes sense then. Never mind @MultiThemes..
Probably, perhaps you had Tidy Website Links disabled in Classic for the project, and that setting got imported over when running the Beta Importer into Elements which would explain why that was set to false in the data.json file. (I’m just guessing here).
Anyway the Importer feature was just a Beta feature. Glad to have spotted this though, def something we’ll need to look out for for anybody else who has ran that Beta Importer from Classic to Elements..
Will ask @dan and @tpbradley about it as well.
Do I need to somehow manually strip out the Lander stuff (if so where)?
Or will I just get in deeper trouble?
Honestly don’t know, the importer was always a Beta feature..
I think for now you are good. If you encounter any other troubles let us know though.
It’s good to read that @differentdan was already able to help you. So it seems my first impression and suspicion weren’t that far off after all.
Wishing you continued success and enjoyment.
Nice catch! Thanks @differentdan and @Pegasus for digging into it!
I’ll remove importing that setting from the converter so it doesn’t carry over incorrectly. That should prevent this kind of issue going forward 
Thanks for your help as well, it did get everything moving in the right direction!
By starting with the importer from Classic to Elements (six months ago) I thought I was saving time while learning how to use Elements. I didn’t fully understand the ramification of that decision. Looking back at the time spent trying to figure this out and the current state of my site’s underlying code, I now see I would have been better off starting fresh in Elements.
For those of use who have utilised the importer … is there anything in particular we should check for Tom ?
Sorry for the delay, the project was made with Elements standards, the only extra thing is a custom component for breadcrumbs.