closed Forgot how to rename cloned skin...again

So sorry, but I could not find my old posts about this, and I have forgotten how to solve it the second time now. (ugh)

I customized my Ningja skin and then cloned it, filled in the new name in the name box with a unique name, and saved it. Made it the active skin, saved it again.
The directory shows the correct new cloned skin name, but the left skin column shows now two skins with the same original name- Ningja.
Sorry to have forgotten, but how do I change this again?

(and I envision this same thing coming up with various new people over and over- it seems like it should just put in the new name we've designated when naming the new cloned skin in the first place?)


--
...just another satisfied Jamroom customer.
Migrated from Ning to Jamroom June 2015
updated by @strumelia: 07/09/16 09:21:02AM

You can see all of your own old posts by clicking on the "244 posts" under your image in these forums.

It will take you here:
https://www.jamroom.net/forum/activity/1045/strumelia

The solution your trying to find is probably in mixed into a long thread titled "some problems" or similar with hundreds of posts.

anyhow, what you want to do is to open the include.php file in the skin you have created and locate the _skin_meta() function at the top of that file and change the title to what you want.

It will look similar to this:

The part to change is
Change the name to whatever you want.

Having it do it automatically is a good idea. I'll see if we cant get that added in.

Thanks.
updated by @michael: 12/29/14 09:23:54AM

This is fixed up in the next version of Developer Tools module Version 1.3.0

Thanks.
updated by @michael: 12/29/14 09:23:54AM

"You can see all of your own old posts by clicking on the "244 posts" under your image in these forums."

Ah! I was looking for my old posts via the ning-to-jamroom/forum/my_posts tab...which didn't even take me to any of my posts (?). Thanks, now I know to click on the post number link under my avatar! (d'oh....)

THANKS for fixing this in the next version- it'll save everyone from having to explain it for eternity. I could not find it using various search terms in the forums...I did try!

--------------------
Edit accomplished! Yay!!! :D




--
...just another satisfied Jamroom customer.
Migrated from Ning to Jamroom June 2015
updated by @strumelia: 12/29/14 09:23:54AM

Yeah I tried too. Couldn't find it. Too well hidden.
updated by @michael: 12/29/14 09:23:54AM

Hmmm....ok now I have a new question.

I made a bunch of customizations to my original Ningja skin. I cloned that skin, giving it a new name NingjaLisa1. I made the Lisa1 skin 'active skin'. Now I see that the new cloned skin does not have any of my customizations at all- it's now like the Original Ningja skin was before I customized it. And the regular Ningja skin still has all my customizations.

Is that the way things are supposed to work? Why wouldn't it work the other way around, with the new named cloned skin having my customizations so that I can apply any new jr skin updates to the original Ningja skin without overiding my customizations?

I'm not getting it- what is the procedure for my applying any future Ningja skin updates, without losing my customized stuff? What am I supposed to do with the new cloned Lisa1 skin if it has none of my customizations?
Sorry if I sound dense, but it seems backwards or something?
(hope it's ok that i un-marked the "solved" on this thread until I understand the answer to my last question here)


--
...just another satisfied Jamroom customer.
Migrated from Ning to Jamroom June 2015
updated by @strumelia: 12/29/14 09:23:54AM

If you had have made the customizations to the skin files in the file system, then they would have been copied over.

The template edits via the ACP don't get copied over. They are over-rides to the skin.

I'll look into what we can do to sort that out.
updated by @michael: 12/29/14 09:23:54AM

Hmm, are you saying that any edits to the skin within the JR ACP need to be also done from my server end, or INSTEAD be done on my server end, where the skin templates are? Are you saying that skin edits within JR acp are sort of temporary and not sticky? Not quite understanding, but I had better understand it darn well before the next Ningja skin update, fer shur! =8-*


--
...just another satisfied Jamroom customer.
Migrated from Ning to Jamroom June 2015
updated by @strumelia: 12/29/14 09:23:54AM

Got this added in to the next version of Developer Tools. From version 1.3.0 when you clone a skin, the ACP changes also get cloned.
updated by @michael: 12/29/14 09:23:54AM

Michael - wondering if that needs to be an option? Some users might want to clone a 'clean' skin to start afresh with.


--
Paul Asher - JR Developer and System Import Specialist
updated by @paul: 12/29/14 09:23:54AM

I figure "clone" means clone. If they want a fresh skin to start with after, they can easily go into the TEMPLATES tab and hit the 'Reset' button.

Or they could do that before they cloned the skin. Seams like the right way to do it. Take a look and see what you think. I'll push it in a couple of hours.

--edit--
I'm not writing the ACP changes out to the file system, just copying them over as template alteration. So the file system changes will still be of the base skin.
updated by @michael: 12/29/14 09:23:54AM

OK - Presumably they can also just uncheck all the active buttons as well prior to cloning to get a clean skin?


--
Paul Asher - JR Developer and System Import Specialist
updated by @paul: 12/29/14 09:23:54AM

Yeah, it just makes an exact copy of whatever is there at the time of cloning. So what they end up with is what they have at the time of cloning.

If a button is active at cloning time it will be active after cloning, they can then turn it off. Or deactivate it before cloning.
updated by @michael: 12/29/14 09:23:54AM

No - they are "sticky" but are specific to a skin. So let's say you have a custom skin called "CustomSkin" - that would be in this directory:

skins/CustomSkin

Then you customize the templates via the ACP -> Skins -> CustomSkin -> Template tab. Those changes are going to be stored in the database for the "CustomSkin" skin.

If you then CLONE the CustomSkin to say 'CustomSkin2', the database changes (at least right now) that you made to CustomSkin are NOT copied over to CustomSkin2 - only the actual files in skins/CustomSkin are copied.

I believe Michael is fixing this up.

However - if you plan on making a number of changes to your custom skin, I would highly recommend that you do your modifications directly to the templates in skins/CustomSkin. While it works both ways (changing the actual template OR customizing it via the ACP -> template section), you'll get a little bit higher performance by modifying the templates directly.

Hope this helps!


--
Brian Johnson
Founder and Lead Developer - Jamroom
https://www.jamroom.net
updated by @brian: 12/29/14 09:23:54AM

Brian, you mean I'll do better in future by making changes to my custom skin templates while in my SERVER cpanel, rather than through the JR ACP?

Michael- I agree, "clone" should mean clone, and if cloning doesn't actually result in an identical skin (with its modifications) then that's going to cause a whole lot of problems and confusion for people like me.

My goal here was to clone my customized ningja skin and name it Lisa1, then when the new Ningja update came out I would update my original Ningja skin, not worrying about it overwriting my customizations because I had my Lisa1 set aside. After the Ningja skin updated, then I would 'compare' the new Ningja to my cloned custom skin and:

Add my own customizations to the new updated Ningja? and then 'clone' that to a new Lisa2 and activate Lisa2. Then after Lisa2 seemed good I could delete Lisa1 which lacked the Ningja update... is this the sequence how I should go about it?
-of course this assumes that a cloned skin will keep the customizations I created on it in JR ACP...which you say you are going to make it function that way?

Should I attempt to go into my server cpanel and search out all the tweaks I've done in my Ningja skin and apply them in the custom skin folder templates now, or should I just wait until you change how the cloner functions? I know you guys are working on a new ningja skin update soon, so I'll need to know how to save my custiomizations properly before I update Ningja.

Thanks!


--
...just another satisfied Jamroom customer.
Migrated from Ning to Jamroom June 2015
updated by @strumelia: 12/29/14 09:23:54AM

Yeah, its done.

The way to work with the files on the file system is more aligned with traditional development methods.

Traditionally in order to change the way a website looked, you would have a copy of it on your local pc, then make some changes to the file then upload it.

Jamroom (and other CMS systems) allow the admin user to get around the need for this by providing other methods to update what is displayed.

The method you should use is whichever you feel most comfortable with.

Anybody coming in from a web development background is going to feel more comfortable working with the tools they already use. Tools that allow the server files and the local files to stay in sync and provide features to allow for easy customization.

Just as an example some of those tools are:
* PhpStorm
* Dreamweaver
* Eclipse
* text editor + FTP program

If you are unfamiliar with these tools and are trying to customize the files by using the features of cpanel, I reckon sticking with the template editor is a better way to go.

If you want to learn more about the development side of things, the team uses PhpStorm.

Your probably more interested in running the community than becoming a Jamroom developer at a guess.
updated by @michael: 12/29/14 09:23:54AM

Micheal, I hear what you are saying, thanks.

When you say "Yeah, its done."- what do you mean?

I just tried cloning my customized Ningja skin again and (again) the new clone did not exhibit all the header template changes, links, logo, colors, etc that I had customized over the past couple of weeks.
Am I not understanding something, did you change something?


--
...just another satisfied Jamroom customer.
Migrated from Ning to Jamroom June 2015
updated by @strumelia: 12/29/14 09:23:54AM

That was the context it was mean in. version 1.3.0 is not in the marketplace yet. Once its been checked it will be released. Should be soon.
updated by @michael: 12/29/14 09:23:54AM

Ah ok, wonderful!

So if I am understanding it right... I will have to wait until my Developer Tools is updated before I can clone a real customized clone of my currently customized Ningja skin then. In other words, i can't update my Ningja skin until I can make a clone of it that retains all the customizations i have made over the past several weeks.
I don't trust my current knowledge and abilities to copy over all my various changes into templates on my server end in the meantime- I think i'm liable to screw it up and then lose everything I've done.


--
...just another satisfied Jamroom customer.
Migrated from Ning to Jamroom June 2015
updated by @strumelia: 12/29/14 09:23:54AM

Can't see any reason to delay releasing it. Its in the marketplace now. Run your system update and you should be good to go. If you find any issues, let me know. (in a new thread. )
updated by @michael: 12/29/14 09:23:54AM

I'm confused, sorry Michael.
I've already had Developer Tools for a while, it says it's installed and says it's 1.3.0. Yet my cloned skin loses any modifications anyway. ?


--
...just another satisfied Jamroom customer.
Migrated from Ning to Jamroom June 2015
updated by @strumelia: 12/29/14 09:23:54AM

you've had 1.3.0 for a while? mmmm, strange. Thought it wasn't released.

Give Reloading it a try for me, see if that fixes it.

ACP -> MARKETPLACE -> TOOLS -> "Reload Modules or Skins" -> Developer Tools -> RELOAD

Thanks.
updated by @michael: 12/29/14 09:23:54AM

Ackkk!!! Did this, Reloaded DT successfully, then created a new named NingjaLisa1 skin from my (customized) Ningja.... set it as active...
and now my whole site is completely SCREWED, everything I did for the past few weeks is completely gone,and I don't even have the checkbox available to reset it back to my customized Ningja skin.

HELP !

My new site home page:



--
...just another satisfied Jamroom customer.
Migrated from Ning to Jamroom June 2015
updated by @strumelia: 12/29/14 09:23:54AM

Ok, I finally was able to set it back to my customized Ningja skin (not the new cloned skin). Whew.
Seems I have a problem with the new cloned skin...
Michael, should I delete my Lisa1 cloned skin and try again?


--
...just another satisfied Jamroom customer.
Migrated from Ning to Jamroom June 2015
updated by @strumelia: 12/29/14 09:23:54AM

not nesacarily attimes cached datas screwed u can go intio the databasse reset to the defauolt skin (elastic) then go back and reactivate your skin and its perfectly fine


--
soaringeagle
head dreadhead at dreadlocks site
glider pilot student and member/volunteer coordinator with freedoms wings international soaring for people with disabilities
updated by @soaringeagle: 12/29/14 09:23:54AM

what your seeing there is a site with no css formatting at all so its the cached css thats not loading
simply switching skuins loads that skins css then switching back reloads your skins css and unless u have a huge screw up it should work fine


--
soaringeagle
head dreadhead at dreadlocks site
glider pilot student and member/volunteer coordinator with freedoms wings international soaring for people with disabilities
updated by @soaringeagle: 12/29/14 09:23:54AM

@Michael --> the Developer Tools update is not working for me. I can't clone any skin now and have it be functional. Something's not right- thanks for looking into this. I'm ok for the moment as I was able to get my customized Ningja skin back activated again, but the cloned skin is not functional, though I left it there ("Lisa1" skin) for you to look at if you need to.

(note- the new cloned skin does not show up in the left side column of skin names, but it does show up inthe little drop drown menu. That's new too since the update. The good news is that the new clone did retain its name I gave it...lol)


--
...just another satisfied Jamroom customer.
Migrated from Ning to Jamroom June 2015
updated by @strumelia: 12/29/14 09:23:54AM

i havent tested it yet i will now


--
soaringeagle
head dreadhead at dreadlocks site
glider pilot student and member/volunteer coordinator with freedoms wings international soaring for people with disabilities
updated by @soaringeagle: 12/29/14 09:23:54AM

srry thought u posted that in y post about the tool
reposting my responce here

works perfectly for me 'i cloned clunkyjunk (my cloned junkbeta) to junkyclunk
it shows inthe left it activates just fine it appeared to copy the css even


but @micheal
only 1 minor oversight
it doesnt copy the custom images
thats the only glitch isee otherwise awesome

though junkyclunk showed up as nkyclunk cause the name was too long and chopped it off the left side

can next updatre also copy the custom images/


--
soaringeagle
head dreadhead at dreadlocks site
glider pilot student and member/volunteer coordinator with freedoms wings international soaring for people with disabilities
updated by @soaringeagle: 12/29/14 09:23:54AM

u dont have to copy on the server end
open 3 tabs
2 with the cloned updated skin 1 with the previusly customized skin
in 1 you look at what templateds have checkmarks then in the other click compare compare your edited template to the new version (unedited) click modify in each andcopy paste your edits into the new clone

there will be other code changes but you should be able to recognize the code u changed and only copy paste that


--
soaringeagle
head dreadhead at dreadlocks site
glider pilot student and member/volunteer coordinator with freedoms wings international soaring for people with disabilities
updated by @soaringeagle: 12/29/14 09:23:54AM

Doesn't work


Doesn't work

@Michael --> the Developer Tools update is not working for me. I can't clone any skin now and have it be functional. Something's not right- thanks for looking into this. I'm ok for the moment as I was able to get my customized Ningja skin back activated again, but the cloned skin is not functional, though I left it there ("Lisa1" skin) for you to look at if you need to. Thanks!

--> Michael, I've started a new thread on my problem, please reply there instead. thanks!


--
...just another satisfied Jamroom customer.
Migrated from Ning to Jamroom June 2015
updated by @strumelia: 12/29/14 09:23:54AM

clarify..doe4snt work u mean u cant reset to elastic or when u reset then reactivate somethings still wrong
have u run the integrity check then looked in error logs

cause the dev tools are working just fine it seems u have something somewhere thats screwed up and most likely the integrity check will find it


--
soaringeagle
head dreadhead at dreadlocks site
glider pilot student and member/volunteer coordinator with freedoms wings international soaring for people with disabilities
updated by @soaringeagle: 12/29/14 09:23:54AM

The image shows that the site is missing its style sheet. That's all. Don't panic.

Run the integrity check and clear the caches.
updated by @michael: 12/29/14 09:23:54AM

Right. I didn't think about those. I'll get that sorted,.
updated by @michael: 12/29/14 09:23:54AM

Thanks Michael- I did that as a matter of course and it didn't help. De-activated, reactivated, cleared cache, integrity check. Still wasn't working right. i could try it again a third time if you think i should.

But I'll now be posting about this in my new thread on my cloned skin issue instead of in this thread. Thanks...


--
...just another satisfied Jamroom customer.
Migrated from Ning to Jamroom June 2015
updated by @strumelia: 12/29/14 09:23:54AM