[Dazed]

Do you guys happen to have the skin change files only for the new release?

Thanks

[Michael]

We've got a lot to do. Sorry for the inconvienence. I've been working on documentation today and will be on that task for quite a while to come I think.

Change sets for upgrades to stuff will come, but they're not a feature yet.

to get them what I would do is use GIT, the version control system built into PhpStorm. Do you use that or GIT with anything else? That would help you merge.

Keep the original skin on one branch, your skin on another branch, update the new skin, then compare it with your changed branch to give you the changes.

Or if you dont use GIT some sort of compare program. I think 'beyond compare' was what I used to use when I used windows years ago. Dont know about a similar program for Mac. On linux there is Meld, maybe others.


_________________
Michael Ussher
Jamroom Network Team Member: http://www.jamroom.net
Priority Support: http://www.jamroom.net/Support_Center

[Brian]

I know this isn't the answer you want, but I don't think we will be doing change files for JR5 - instead we're working on an "upgrade" system to allow system upgrades for skins/modules to happen right on the system (i.e. press an "upgrade" button and it is done).

One thing that will do is show you a list of the files that were updated - so to help you out, you would just "upgrade" the skin your custom skin is based off of, and you would then see a list of the files that were updated - those are the ones that changed.

Let me know if that sounds good.

Thanks!

- Brian


_________________
Make sure and check out:
* The Jamroom FAQ
* The Jamroom Documentation

[Dazed]

Anything to narrow it down is good. Not many will have the out of the box version after a month. Everyone is going to tweak a file or two or three or four .

I posted in the suggestion forum about using a variable for the skin name so that it would require less work on our part since the skin name is hard coded. When the upgrades come out, it would override all cloned skin names leading to headaches. All img paths would also be wrong.

So when upgrading a cloned version, the current process almost needs to be:

Upgrade core system
Upgrade core skin
rename cloned copy
clone the core to the same name as the clone you had before
run a diff on the new clone version vs old clone version
update individual files

It seems like this should be an easier process so anything you can do to alleviate it would be appreciative!

[Brian]

Yep - that makes 100% sense - I'll get a ticket open on that to check it out.

Thanks!

- Brian


_________________
Make sure and check out:
* The Jamroom FAQ
* The Jamroom Documentation