Yep, I alway try and avoid switching a page to php. While it’s as easy as flicking a switch, you sacrifice any SEO you have accumulated for the html page, and kiss bye bye to any inbound links from other sites. (without writing custom htaccess).
2 Likes
I think my original question may have got a bit “lost in translation” 
I was really looking for help regarding the multiple things I have to put on a site that has a public facing and a clinical/professional facing site. Copyright was one component but there are numerous others which are sometimes product related but to some not all products and they appear on multiple places throughout site. I’m fine with copyright but I do not want to have to do multiple globals and then put one or many on different products/pages. I was expecting one page where all globals could be put and a code put in places or pages to show them. Without having numerous globals on a page. E.g. a header and footer global pasted on 30/40 pages, when a globals page with one header and footer on and then a “code” on page to display it? I hope I’m explaining this well enough to understand? TIA
A global header and footer area, that can be enable / disabled on a page by page basis would be a nice feature.
This sounds a lot like having a “MASTER PAGE” where you can setup information that is common to all of your pages. Anyone used to using a modern desktop publishing piece of software is familiar with this concept. Most of these apps support master pages that can be used to provide information generic to the pages where they are used. They also support multiple master pages so you can have different ones for different pages.
Something like this in Elements would be a gamechanger in my eyes as you would only have to go to the master page to make changes that would be globally applied. Globals handle this very well but it can be tedious placing them on every page.
I already use a similar approach in Elements. When I start a new project I create a “master page” with all of my common global elements. I then duplicate it as needed to create all of the pages for the site. Saves me having to add the common stuff to each page.
UPDATE: I suppose it is possible once we see TEMPLATES that they might be a possible solution. If you could create a template of your page and then use it to create the necessary pages. If the template was then edited if it updated all of the pages derived from it, that would work,
3 Likes
That’s sounds more better to me a master page is what I need.
I’ll put this on voting page and see how many people like this.
THANKS for summarising my brain!
I like this thread and this topic. this one goes in the direction for which I already opened a thread some time ago. Elements and php-code as already written in this thread
I very often use PHP code in my content and meta tags (title and description) or header & paragraph to generate dates dynamically, for example like this:
<?php echo date(“Y”); ?>or
<?php echo date (“d.m.Y”, strtotime(“Monday this week”))?> the use and display of these codes in the meta title and meta description now works after an update. however, I still have problems using the codes within the content. here are some screenshots of how I use the php-code under rw-classic and how I would like to use it under rw-elements.
——————————————
is there a way how I can use the PHP code within the ‘Text-Component’ or ‘Typography-Component’ so that it is rendered and output correctly? in the same way as it works under rw-classic?
i know that i can also use an html component for the php code. i know that works too. but then i miss the styling tools like with the text component …
A custom component is the way to go here! You could even use an if statement so the PHP is hidden from the editor; you could then show some dummy text in its place. Much nicer way to do it, for example…
@if(edit)
We’re in edit mode, make it look pretty for the editor.
@else
Put your PHP in here so it renders on preview and export.
@endif
You could even take it further and add a text area control to the sidebar to paste your PHP into (to save having to edit the code). Maybe also add settings to control the size and font, whatever you need.
This is the beauty of custom components. Let me know if you need any help in throwing a solution together.
1 Like
thank you very much for your support.
if you have time for it, with all the busy stuff you have to do, a little help in the form of instructions what exactly to do or similar would be very nice.
thx
I’ve put togther a basic version for you… see the video for details, and Open Project here.
btw. It’ll be worth waiting for the new Elements build later today as it contains a fix for writing code in the Text Area controls.
Hope this helps.
Like that. I’ve been avoiding custom components but probably shouldn’t be.
Once you get into building them (especially with the help of ChatGPT), it can become very addictive, so watch out! 
Nice, really similar to a bric I built years ago for Blocs, it still sells well.
So I would say there is a valid use case for users. 
I also added a feature, if the start year was the same as current it just shows the one year. Handy, if only briefly
1 Like
Self updating copyright component - php free.
Download Link : http://www.garysimpson.co.uk/vault/temp-sharing/shared-components/Copyright.elementsdevpack.zip
5 Likes
That is great, nicely put together. 
Awesome. This is very cool.
Feature requests. The ability to opt to only use the current year. You can curretently do this by not providing a start year, but then you can’t get rid of the “-” between the years. I’d also like to be able to insert the word “copyright” after the copyright symbol.
Sorry if I’m being to demanding. So stoked to see Doobox on Elements. I have a lot of your stacks.
1 Like
Seconded Gary has been awesome helping me over the years and is a star!
1 Like
Gary this looks exactly what I asked for as always you’re a star! Great to see you on Elements page too!
2 Likes
If you enter the current year 2025 as the start year you will only get the current year without the “-”
The component assumes if your first published year is the current year, you only want to return the dynamic current year.
© 2025 Doobox. All rights reserved.
until next year when it will return…
© 2025-2026 Doobox. All rights reserved.
I’ll look at other additions.
3 Likes
Fantastic. Well thought out.
Hi Garry, thanks for all the work you’re doing and as I have used a lot of your stacks for RWC, I can’t wait to see what you will be coming up with for Elements. 
2 Likes