blog documentation FAQ followers forum marketplace services youtube

solved problem with clone skin tool

The Jamroom Network » Forum » Using Jamroom » Page 21 » problem with clone skin tool
Strumelia
Strumelia
@strumelia
8 years ago
3,605 posts
This actually has occurred for months now- but when it happened before months ago I didnt realize it was the Clone skin tool that caused the site changes that I then went around fixing up.

When I go to Developer Tools-> clone skin, and try to clone my current active custom skin, I apply the correct prefix to the new skin name, and I at first get this error:
cloneskinError.jpg
cloneskinError.jpg  •  94KB




--
...just another satisfied Jamroom customer.
Migrated from Ning to Jamroom June 2015
updated by @strumelia: 08/02/17 01:10:38PM
Strumelia
Strumelia
@strumelia
8 years ago
3,605 posts
...but then when I try again with the same new skin name (May 2), it says that skin already exists...and sure enough it does- the tool had cloned the skin despite the error.

So then I set the new clone to be the active skin, I immediately see that various colors on my site have reverted to colors from long ago when I first created the new site- from a clone of my other site.

Here is what my (good) current active custom site skin looks like:
orig.jpg
orig.jpg  •  338KB




--
...just another satisfied Jamroom customer.
Migrated from Ning to Jamroom June 2015
Strumelia
Strumelia
@strumelia
8 years ago
3,605 posts
(...and that's what the new cloned skin 'should' look like, all with greys and brown)

But this is what I get now when I clone a new skin off of that..
notice the mustard and olive color fields which are a holdover of my original other site. Notice too the top links bar is all messed up and different. Notice also the "About" blog section has lost my custom name, as well as the "Join a Group!" title, etc... all kinds of things reverted back to a long ago non-customized state.
cloneskin.jpg
cloneskin.jpg  •  345KB




--
...just another satisfied Jamroom customer.
Migrated from Ning to Jamroom June 2015
Strumelia
Strumelia
@strumelia
8 years ago
3,605 posts
I've tried this cloning a bunch of times with the same result despite lots of integ checks etc. Tried deleting the faulty clone and starting over, no luck same thing happens, including the initial error message from the tool. The Clone skin Tool used to work perfectly for my until just I think around 6 or 8 weeks ago, when I started noticing color changes but didn't attribute it to the skin clone tool.

If you JR Team want to try it on my (low activity) site https://pennywhistleclub.com/ please feel free- the 'bad' new clone is the skin called May2. The 'good' (and currently active) skin is my Feb3 skin (don't delete that one please if you are testing stuff!)


--
...just another satisfied Jamroom customer.
Migrated from Ning to Jamroom June 2015
updated by @strumelia: 05/02/17 08:14:44PM
michael
@michael
8 years ago
7,805 posts
That "skin_cloned_from" error is a new feature that was added to the jrCore. Looks like it got added to 6.0.8, then instead of releasing 6.0.8 that version became the start point for the JR6.1 beta so the core change never got released. Once 6.1 gets out of beta it will stop showing the error.

On you penwhistle club site I have gone into the database:
ACP -> MODULES -> DEVELOPER -> DEVELOPER TOOLS -> DATABASE ADMIN

And run this 'SQL command'
ALTER TABLE jr_jrcore_skin ADD skin_cloned_from VARCHAR(128) NOT NULL DEFAULT ''
That has added the needed column.

You can do the same (or I can if you like) to your other site and your skins should be cloned correctly.

Sorry for the hassle.
Strumelia
Strumelia
@strumelia
8 years ago
3,605 posts
MIchael, would I paste in and then hit "execute" button, without limiting rows, as in this attached screenshot?

Also two questions before I do this-
-Are those two apostrophes hanging there at the end of the command text correct? (they seem odd to me)
-will the same number (128) be correct for running the same command on my other site, fotmd.com?
command.jpg
command.jpg  •  256KB




--
...just another satisfied Jamroom customer.
Migrated from Ning to Jamroom June 2015
Strumelia
Strumelia
@strumelia
8 years ago
3,605 posts
(I want to be able to clone my current skin before applying that tnymce image editing fix in Curtis' thread) :)


--
...just another satisfied Jamroom customer.
Migrated from Ning to Jamroom June 2015
michael
@michael
8 years ago
7,805 posts
Yes, just hit the "execute" button. You should see a line of green saying x rows effected.

It reads: "change the strucutre of the jr_jrcore_skin database. Add a new column with the title skin_cloned_from. Things added to that column can be any character, but only up to a limit of 128 characters. If no input comes in when a row is created, dont write NULL instead, just put the contents that you find within these two apostrophes. (which is an empty set)"

After that the cloning of a skin should work without error.
Strumelia
Strumelia
@strumelia
8 years ago
3,605 posts
Interesting and informative to get your 'plain english' translation of that code.

Ok, I just did all that on my other (main active) site fotmd.com
...and it works great- just cloned a nice new skin with no problems, looks good. :D
Thanks so much! Marking this thread solved.


--
...just another satisfied Jamroom customer.
Migrated from Ning to Jamroom June 2015
updated by @strumelia: 05/03/17 07:16:33PM