problems understanding how to override

[bradley.cormack]

First off - love UserSpice... even if its making my brain melt.

my host had an older version I tried first, and then I saw your site a newer version.
Im almost smart enough to know that where was a lot of changes in the code and more tables in the DB...
short story - I had to trash all the work from the older version. update wrote over all my code modifications.
BUMMER...
Now Im embracing the latest version... but DO NOT want to start over again when you update next time.

if I want to make my own maintenance.php that wont get over written, I stick it in usersc ? ? I get a error 500 on any pages I have stuck in there... Ive tried erasing the /users/maintenance.php and just use the file in /usersc but error 500...

without blasting through each file studying how you coded the intricate structure... do I have the right idea? do I have to write a handler that checks if there is a duplicate page file in the usersc directory and use that one instead ?

If I have to edit a bunch of base page code to deal with my custom pages, your next update will overwrite the base files changes I made.

How can I deal with my custom pages not breaking ?

Thank you for your help !
Bradley.

[bradley.cormack]

Or I've had too much coffee... *grin*
Checked out some youtube reference from Dan, and I think I may have misunderstood the concept of page override.

I guess it is inevitable that if I am going to "tailor" some of the core pages, I will have to expect re-coding after an update. 4.2.x to 4.3.14 was a big jump in my mind, just lining up my brain cells to bend bootstrap to my will...

If there is any advice or strategies out there, Im all ears!

Thanks for reading.
Bradley.

[Brandin]

You are correct to put items in Usersc...but the 500 error is some kind of error you need to figure out. There are one of two ways, check your error logs, or add this code to the top of the page (or head tags - you should probably only do this on a non-production install)

error_reporting(E_ALL);

That will hopefully give you some errors to fix.

[bradley.cormack]

Thanks for the nudge... it ended up being a trail of files not in scope/path...
The good thing is that I drilled through how the back end works and the splendor that is UserSpice. 8-) I'm looking over the last update release notes now, about to deploy.

Understanding the framework is always a good idea. I cant be too lazy, or my php kung-fu will degrade... and I hate to admit the next thing I did wrong...

I was looking at the WRONG err-log file, HAHA
(it was always 0bytes...I should have realized sooner)

Thanks again!
Bradley.