I'll take this conversation up a notch, since I'm constantly creating my own menus, I understand what Joe means. If you were to remove the file from your custom theme, you would get a page load error on the main site.

This should not occur from a view file, if the file is not in the custom theme, it should load it from the main view folder. I've tried removing all contents from the file still keeping the file in the theme folder to see if the main view folder would override, it does not.

Bottom line if my MVC understanding is correct, if the file is not there, it should load from the main source, if the file is there it should override the main source.

Isn't this how custom.css works?

I guess I'm still used to Magento.

Edited by user Thursday, October 15, 2020 2:56:40 PM(UTC)  | Reason: Not specified

I'm pretty sure that's how it's working for me. So long as it's not a brand new view that has no 'original' version in /Views/.

Overall I'm happy so far with how the view overrides behave. It's just not obvious that an override is in play when working with admin pages/widgets.

Long term we really need to work on organizing customizations into a separate folder structure. It would be immensely helpful from a customization perspective to have something like:

/Custom/
/Custom/Views/
/Custom/Controllers/
/Custom/Models/
/Custom/Themes/
/Custom/Code/

The goal is to isolate out anything that is custom. So when a developer comes into the project a year later, he doesn't have customizations scattered all over the place like there is now.

Would the solution be as simple as adjusting MVC routes to include a /Custom/ folder?

In 7.x and Gold, the /ConLib/Custom/ folder was clunky but it worked well. You could easily organize customized user controls away from regular ones. This made merging future release updates soooo much easier because I could just pair the update /ConLib/ folder to the website /ConLib/Custom/ folder and BeyondCompare instantly does the magic.

Sounds like the override theme list is being cached perhaps?

What is supposed to happen in theory and what actually happens in reality are sometime contradictory. There many times especially when working with custom menus which happened to be a razor cshtml file where one has to reset IIS.

So I must respectfully come to the conclusion that how it's supposed to work and how it actually works at times could be in conflict. There are many times when I have rename a file in my theme which should have no effect on the system whatsoever, but yet the system crashes.

Normally fully clearing the cache from a browser does the trick, in the last situation that I had, only resetting IIS was able to resolve problem.

Coming from the school of hard knocks,
-Ray

Hello Naveed,

I appreciate your reply but I don't believe this is a major concern. There are certain glitches that occur in real life, which could be configuration, different hardware, or even gremlins in the computer.

I have learned so far that certain directories are extremely pickly and others are not. When working with multiple versions of a file, I like to rename a file using the date as the extension to the file name while keeping the file in that directory, try this under the bin directory and the system explodes constantly.

So one learns the glitches and moves forward.

If all else fails, reboot.

Many thanks

First of all for your custom views you do not need to create the custom views folder under the theme folder, you should better edit/update the view files under standard /Views folder. However it should have worked, as view engine should have first looked into the theme folder for a view file.




What you mean by reset everything back? do you mean that you removed the duplicated view file under theme folder?

I think browser cache have no effect in this scenario.

" First of all for your custom views you do not need to create the custom views folder under the theme folder, you should better edit/update the view files under standard /Views folder. However it should have worked, as view engine should have first looked into the theme folder for a view file."

I am not sure what you mean by this at all, if I do not mimic the directory structure from the main view folder, nothing works. This new view is under a directory under my theme called Custom. In other words Themes\[Name of Theme]\Views]\Custom\ [file is here].

In fact just to prove a point, I removed the file from under the proper directory and placed it in the root view folder of my theme. It did not work. I then placed the file back, and had no choice but to reset IIS once again for the file to load properly.

Just reporting my findings.

Extremely confusing statement, YOU DO HAVE TO MIMIC the directory structure under your theme folders or it doesn't work. Unless there's something different about my computer down here in Miami, directory structure under theme's is extremely important.

I'm not sure why anyone would suggest differently, or maybe I'm just misreading your statement.

Either way this topic has gone on long enough, everything works as long as proper directory structure is intact.

Thanks

Hi Judy,

I will tell you something, but you have to promise me you will not laugh. Still fairly new to GitHub, so I use a program called "Advanced Diary" to log all my code changes. I created a template within the program just for this. I even use color-code and have the the ability to sort things into changes that needed to be compiled and changes that did not. The beauty of the program is, besides the fact that it timestamps everything, it has the ability to hold attachments. So anytime someone sends me something, I'm able to zip it and attach it to the entry itself.

Yes I know it's old-fashioned, but I guess one tends to use what they know. Either way, I will check out your software, and hopefully later next month I'll be attending a three hour lecture on GitHub.

Either way I'm enclosing a picture for your review.

Many thanks

ChangeLog.jpg (893kb) downloaded 6 time(s).

Edited by user Wednesday, October 21, 2020 6:55:57 AM(UTC)  | Reason: Not specified

It actually works for us, because I try not to modify the code base too much. This new version, 9.0.3, actually fixed every single one of our issues, so I'm starting with a clean slate again, when it comes to the CodeBase. I was up all night trying to get GitHub up and running from within Visual Studio, not sure what happened, nothing work. Will need to try again this week after much needed coffee.

Since I will require the assistance of a developer down the road, I will need to embrace what everyone uses, hopefully to make life easier, but I will always maintain a diary.

Thanks