Branches with Shadows V1 ReadyTheme

[mcrmedical]

Miva built our site using the Shadows ReadyTheme, and we don’t seem to be able to use the branches functionality that is now part of the core product. I’m wondering if there is an easy way to fix this. I think our site was created when Shadows was still on version 1.

When we create a branch, not all of the CSS files get copied into the branch, so the styling of the branch doesn’t work right. The branch does copy the CSS files from the “extensions” and “ui” subdirectories, but does not copy the CSS files from the “core” subdirectory.

Is there an easy way to fix this? It seems odd that a core feature wouldn’t work for us, since we're using a Miva authored ReadyTheme, so I thought I’d ask, before we started trying to figure it out for ourselves.

Any pointers? Thanks for the info, I appreciate it!

[lesliekirk]

Miva built our site using the Shadows ReadyTheme, and we don’t seem to be able to use the branches functionality that is now part of the core product. I’m wondering if there is an easy way to fix this. I think our site was created when Shadows was still on version 1.

When we create a branch, not all of the CSS files get copied into the branch, so the styling of the branch doesn’t work right. The branch does copy the CSS files from the “extensions” and “ui” subdirectories, but does not copy the CSS files from the “core” subdirectory.

Is there an easy way to fix this? It seems odd that a core feature wouldn’t work for us, since we're using a Miva authored ReadyTheme, so I thought I’d ask, before we started trying to figure it out for ourselves.

Any pointers? Thanks for the info, I appreciate it!

Hey Charlie,

That sounds like the bug I reported. The problem with the current configuration is that it will overwrite any versions of Shadows when you try to apply it to a branch. Look for the files in the main Shadows branch. Chances are the installation of Shadows 2.0 has overwritten all the files in the Shadows 1.0 branch.

Leslie

[mcrmedical]

Yes, sounds like it. Thanks for confirming that somebody other than us is having a problem. I appreciate it. Do you know if the bug you reported was confirmed as a bug that they'll work to resolve? What did you do to overcome the issue?

[RTHOMASDESIGN]

Are you referring to your "https://www.mcrmedical.com/" website? If so, that site was not built with Shadows. A lot of work would be required to upgrade.

You should be able to copy your existing branch to make edits. If the relevant resources do not automatically copy/transfer over, you can manually copy/upload them to the new directory (b02,b03,b04,b05 etc. typically located under /httpdocs/mm5/). Then make sure that the files are correctly being referenced under user interface > CSS/JavaScript resources.

If your intent is to upgrade to Shadows 2.0, you're better off creating a dedicated branch running the newest version of Shadows and starting from scratch. Again a lot of work would be required, and unless your a developer it's not an easy task.

Hope this helps a bit,
-Ryan

[mcrmedical]

Hi Ryan,
It's one of our other sites, "www.cprmanikins.com" which is live, but we're doing post launch fixes. We paid Miva to build it, then COVID hit, and it was the wrong time to launch. We put a lot of projects on hold during covid, and are trying to clean up the partially completed ones. It took us a while to get to this one. We've launched the site, and are trying to fix an array of things we missed in the QA process, before we push people to it.

We have developers, including the Miva design team, but Leslie mentioned above that it (or something similar) was submitted as a bug, and that begs the question of whether it's recognized as one. If so, okay, we'll muddle through until it's fixed. If not, we'll likely get Miva to "upgrade" it to V2.

In response about the files being copied, about half the CSS files are being copied into the branch, but it's missing one subdirectory with some the CSS files in that subdirectory. It seems odd that a core feature wouldn't work with a stock ReadyTheme (though we updated some of the content of the CSS files). If not making it backward compatible, it seems like there would be a migration guide for the old Miva ReadyTheme versions.

I'm gathering all the info I can so I choose the best course forward. I'm apprehensive about manually copying files, and entering them into the CSS/JS, because it seems like a dangerous thing if I miss something, and then do a merge.

I appreciate all the info. It's been helpful, thank you.
Charlie

[lesliekirk]

Hi Ryan,
It's one of our other sites, "www.cprmanikins.com" which is live, but we're doing post launch fixes. We paid Miva to build it, then COVID hit, and it was the wrong time to launch. We put a lot of projects on hold during covid, and are trying to clean up the partially completed ones. It took us a while to get to this one. We've launched the site, and are trying to fix an array of things we missed in the QA process, before we push people to it.

We have developers, including the Miva design team, but Leslie mentioned above that it (or something similar) was submitted as a bug, and that begs the question of whether it's recognized as one. If so, okay, we'll muddle through until it's fixed. If not, we'll likely get Miva to "upgrade" it to V2.

In response about the files being copied, about half the CSS files are being copied into the branch, but it's missing one subdirectory with some the CSS files in that subdirectory. It seems odd that a core feature wouldn't work with a stock ReadyTheme (though we updated some of the content of the CSS files). If not making it backward compatible, it seems like there would be a migration guide for the old Miva ReadyTheme versions.

I'm gathering all the info I can so I choose the best course forward. I'm apprehensive about manually copying files, and entering them into the CSS/JS, because it seems like a dangerous thing if I miss something, and then do a merge.

I appreciate all the info. It's been helpful, thank you.
Charlie

Hi Charlie,

Thanks for clarifying before I jumped back in. Yes, it is a confirmed bug (BUG ID: MM-11625). Here's a description of the bug report

With a branch made as a copy of production, branch file paths begin with a bXX where XX indicates the branch number. When a framework is applied only to a branch with the Overwrite CSS Resources, JavaScript Resources, and Other Resources checkbox checked, it causes the branch path to be overwritten with the live file paths. As a result, this also causes changes made to resources in the live file paths to be overwritten with the theme defaults.