Jump to content


Photo
- - - - -

Intended Glitch? Importing 3.2 Forum Skins for 3.3


  • Please log in to reply
16 replies to this topic

#1 keiichi morisato

keiichi morisato

    Not Applicable

  • +Clients
  • 2,222 posts

Posted 22 March 2012 - 04:01 PM

For anyone who can answer this: I remember that when IPB 3.3 was being developed that we were informed that forum skins for 3.2 would work with 3.3. However, I've recently discovered that you cannot import an IPB 3.2 forum skin into 3.3. Was this intended?

The Anti-Spam Guide to IPS. This is an updated guide designed to help fight against spammers. While there is no fool-proof method, all you can do is put up roadblocks to slow them down.

Group Badges, Display Name Customization. This is a guide that helps customize forum display names on your message forums.


#2 Amy T

Amy T

    Needs Serious Help

  • +Clients
  • 2,994 posts

Posted 22 March 2012 - 04:18 PM

I hope it is not intentional.
otakuplayground.com is my site.

#3 beberobu

beberobu

    IPB Newbie

  • Members
  • Pip
  • 19 posts

Posted 22 March 2012 - 05:31 PM

Mda... unfortunately i confirm that the skins dont work on 3.3 !

#4 Sandi_

Sandi_

    Code Addict

  • Members
  • PipPipPipPipPipPip
  • 1,096 posts

Posted 22 March 2012 - 05:39 PM

The only skin I have imported so far is Deviant III, but baring the waring that I was importing a 3.2 skin it installed and works just fine.

Edit: I also just now imported IBR ( from the market place here ) and it also installs and works as intended.

Twenty years ago we had Johnny Cash, Bob Hope and Steve Jobs.

 

Now we have no Cash, no Hope and no Jobs. PLEASE! Don't let Kevin Bacon die.


#5 Ryan Ashbrook

Ryan Ashbrook

    \IPS\Convert::i()->run();

  • IPS Staff
  • 1,089 posts

Posted 22 March 2012 - 09:22 PM

The warning displayed when attempting to import a skin from a lower version of IPB has been in place since IPB 3.1, if not earlier.
  • Rhett likes this

Ryan Ashbrook - @ryanashbrook
Invision Power Services, Inc.
Saving the world. One IP.Board at a time.

Please do not PM for support, but feel free to use our Client Area for questions.


#6 .time

.time

    Spam Happy

  • Members
  • PipPipPipPipPip
  • 768 posts

Posted 22 March 2012 - 09:30 PM

For anyone who can answer this: I remember that when IPB 3.3 was being developed that we were informed that forum skins for 3.2 would work with 3.3. However, I've recently discovered that you cannot import an IPB 3.2 forum skin into 3.3. Was this intended?


They didn't say 3.2 skins would work with 3.3, they said the default skin would not be redone. 3.2 skins still need to be upgraded, just minimally.
  • Rhett likes this

#7 keiichi morisato

keiichi morisato

    Not Applicable

  • +Clients
  • 2,222 posts

Posted 23 March 2012 - 05:41 AM

I just know that when I import a 3.2 skin, the skin crashes when you try to load it. If 3.2 skins work with 3.3, should it be doing that? I don't think so because the skins are supposed to be compatible.

The Anti-Spam Guide to IPS. This is an updated guide designed to help fight against spammers. While there is no fool-proof method, all you can do is put up roadblocks to slow them down.

Group Badges, Display Name Customization. This is a guide that helps customize forum display names on your message forums.


#8 bfarber

bfarber

    RBT-KS

  • IPS Management
  • 28,575 posts

Posted 23 March 2012 - 07:35 AM

The statements being made here are pretty general and global. Most 3.2 skins will not need to be recoded from scratch to work on 3.3. They need but a few specific updates, many of which we've posted in our KB for upgrading users who are facing specific issues.

If a 3.2 skin "crashes" (I'm not sure what you mean by this specifically), it likely was very customized and may need further updates. If it calls a function that no longer exists on the backend, for instance, the skin would need to be updated to stop calling that function. A lot can be done in a skin, and there is no way, ever, to guarantee *every* skin will work after an upgrade. It's likely just something specific the skin or skins you attempted are doing.
  • Rhett likes this

Brandon Farber
Development Manager / Senior Support

If it sounds like fun, it's not allowed on the bus!

php5_zce_logo_new.gif     

Invision Power Services, Inc.


#9 keiichi morisato

keiichi morisato

    Not Applicable

  • +Clients
  • 2,222 posts

Posted 23 March 2012 - 11:38 AM

Brandon, when I've tried to re-import a skin, it had no customizations to result in that crash. It was from a fresh skin install prior to the modifications. While it's no major concern for me, I'm just wondering why IPB 3.3 would flag a fresh/new skin install as it does, with the 3.2 warning. What happened in my case was that I had tried to inistall a forum skin for 3.2, one of the free skins distributed in the marketplace, and when I tried to "change forum skin" I get a warning that the skin has crashed and that I need to talk to the designer of the skin.

I'm just wondering that if the 3.2 are compatible that I'm wondering why the skin would crash if it really is compatible with 3.3. I was trying to ascertain some manual edits and ended up deleting a skin from my forums. When I went to reinstall it, this "crash" is what happened. Now, I'm just waiting for specific IPB 3.3 forum skins to be released.

I wouldn't think that the skins were modified prior to their distribution in the IPS Marketplace.

The Anti-Spam Guide to IPS. This is an updated guide designed to help fight against spammers. While there is no fool-proof method, all you can do is put up roadblocks to slow them down.

Group Badges, Display Name Customization. This is a guide that helps customize forum display names on your message forums.


#10 Marcher Technologies

Marcher Technologies

    $life=FALSE;$code=TRUE;$time--;

  • +Clients
  • 11,717 posts

Posted 23 March 2012 - 10:29 PM

Brandon, when I've tried to re-import a skin, it had no customizations to result in that crash. It was from a fresh skin install prior to the modifications. While it's no major concern for me, I'm just wondering why IPB 3.3 would flag a fresh/new skin install as it does, with the 3.2 warning. What happened in my case was that I had tried to inistall a forum skin for 3.2, one of the free skins distributed in the marketplace, and when I tried to "change forum skin" I get a warning that the skin has crashed and that I need to talk to the designer of the skin.

I'm just wondering that if the 3.2 are compatible that I'm wondering why the skin would crash if it really is compatible with 3.3. I was trying to ascertain some manual edits and ended up deleting a skin from my forums. When I went to reinstall it, this "crash" is what happened. Now, I'm just waiting for specific IPB 3.3 forum skins to be released.

I wouldn't think that the skins were modified prior to their distribution in the IPS Marketplace.

Every skin is modified prior to marketplace release, or it would not see a marketplace release... that's what skins are, customized templates/css of the IPB stock.

#11 Rhett

Rhett

    R1Lover

  • IPS Staff
  • 4,124 posts

Posted 23 March 2012 - 10:36 PM

For further clarification...
3.2.3 skins are for 3.2.3
3.3.0 skins are for 3.3.0

Each version change "can" bring skin changes... some versions are minor... some are more critical, it's always "best" to use a skin designed and updated for your current version. You can do this manually as Brandon suggested with the KB articles information (if they are light changes), or purchase a skin created or updated for the proper version. Keep in mind some skin errors are not always seen on the front end either, so ensuring you have the properly updated skin/changes is important.
  • Marcher Technologies likes this

"If you're spinning your wheels or sliding backwards... you better look for some traction, before you fall off the road!"

 

 

Rhett
Hosting & Support Manager
Invision Power Services Inc


#12 .time

.time

    Spam Happy

  • Members
  • PipPipPipPipPip
  • 768 posts

Posted 23 March 2012 - 10:45 PM

They didn't say 3.2 skins would work with 3.3

because the skins are supposed to be compatible.


I can only be so clear. :ermm:

If you tell us the exact error you're getting, we can help you fix it, but it isn't going to work out of the box, and I don't think anyone ever said it would.
  • Marcher Technologies likes this

#13 Rimi

Rimi

    Strip Me

  • +Clients
  • 6,121 posts

Posted 24 March 2012 - 01:06 AM

I imported my 3.2 skin with no problems.

#14 Lord Nowe

Lord Nowe

    Advanced Member

  • +Clients
  • 458 posts

Posted 24 March 2012 - 01:11 AM

All I did was use the CSS off of my 3.2 skins and made entirely new skin sets on 3.3, and just transferred over the CSS. Sure I did loose a few template modifications, but those can be redone later.

nowesig2.png


#15 Bethanyrayne

Bethanyrayne

    IPB Full Member

  • +Clients
  • 145 posts

Posted 24 March 2012 - 05:40 AM

I have had my custom skin upgraded to 3.3 but when I run a merge report it says I have "unresolvable conflicts" in Global Template, IPB Styles and one in IP Content. The skin appears to work perfectly.

The person who upgraded my skin said:

"I think it still produces a merge conflict message because the merge center isn't what made the edits so it still thinks there are things still left to be merged. It also likely is looking for specific lines for specific code, which in a custom skin, are very different from the default skin. Different things are in different places, and the program doesn't know they are still there, just in a different spot. It also notices some colors and styles are different from default, so it thinks there's a conflict. I think you're good to go. All skins that are custom will likely come up as having a conflict, but they are only because the content has been moved around, so I don't think you have anything to worry about. "

is that true?

#16 Rimi

Rimi

    Strip Me

  • +Clients
  • 6,121 posts

Posted 24 March 2012 - 10:23 AM

Yes that's true.

#17 Bethanyrayne

Bethanyrayne

    IPB Full Member

  • +Clients
  • 145 posts

Posted 24 March 2012 - 11:34 AM

Thank you Rimi




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users