jbob
(jol yates)
26 March 2026 10:30
1
Fishing here for a little more info : )
The discussion is about getting an old client over to Elements
Could the new CMS capabilities allow said client to remotely inject text into any page ?
I could imagine having the body (or a section of) each product page set up such that he can edit / add.
It could be direct ..
or somehow indirect (ie product x.md could somehow echo in the right spot on the product x page)
ben
(Ben)
26 March 2026 10:42
2
yes, you can already add a CMS item to any part of any page from within Elements.
The online editor will allow your client to edit any CMS content directly in any browser
jbob
(jol yates)
26 March 2026 10:44
3
Fab answer Ben, thank you !!
jbob
(jol yates)
26 March 2026 10:57
4
Ben - please clarify …
… so I can just add an item from my CMS blog (for example) … onto my homepage ?
dan
(Dan)
26 March 2026 11:07
5
Absolutely, here’s how to do it…
jbob
(jol yates)
26 March 2026 11:37
6
I don’t get that to work (when previewed)
What would I be doing wrong ?
dan
(Dan)
26 March 2026 11:54
7
Quick first check… is your page set to php?
Failing that, I’m wondering if there’s an error in your Markdown file
jbob
(jol yates)
26 March 2026 11:58
8
No - the page I’m pulling into is not .php
Guess that would be the issue
: )
If I change a page to .php from .html … do I need to .htaccess 301 redirect it ?
… or does it just default to .php if the html version is absent ?
jbob
(jol yates)
26 March 2026 11:59
9
It’s bloody magic what you guys are doing
1 Like
dan
(Dan)
26 March 2026 12:02
10
Locally you don’t need to do anything, but you’ll want to remove the old index.html file from the server. Different servers have difference preferences on what they’ll pick first, some pick index.html first, other index.php.
Anyway, if the page is named “index.html” in a folder, the server will just choose “index.php” instead, so no need to do redirects or anything like that.
Hope that makes sense.