Theme migration is off-topic, and a BIG complicated topic.
Having clean copies of the current version before any changes can help.
Using version control for all changes can make it easier.
But if there’s no version control, or way to build history of changes, then using a diff tool like meldmerge can help in other ways.
Easiest way to lower migration headaches is to hire an expert.
Reach out if you need services , please always provide context in all new communications.
( click profile pic for options to connect)
Thanks for keeping the discussion on track, the door to version discuss was opened via “The code has changed slightly in the newer update of canopy. The one we are using is:“
This added that the version we are on may explain why it may not work with either of the fixes mentioned and caused me to mention what we were on, this is also due to what was discussed did not mentioned versions and the response to my initial question got me thinking we may need a later version!
In cross checking where we stood it became very clear the changes higher versions are not slight changes! In fact, they are extreme as of v6!
So further trying to figure out how to get this issue addresses where we are IE 4.2.1 what I need to figure out is:
Is there recollection what the original version worked on version used?
And what would that current version being references be ie “one we are using”
This would help us understand the investigation direct to go.
The insanity of upgrades will be discussed elsewhere when needed.
click profile pic for options to connect)