2.3 question

[Luke]

I am in a bit of shock that IPB will be jumping to "2.3" all of a sudden. I understand that this is mostly bug fixes and more connect-ability with converge, but there is one thing in the announcement that confuses me.

"New URL skin mapping - ability to apply a skin based on the URL a visitor is viewing"

With 2.2 and before you could apply skins to specific forums. From the sounds of it you can apply a skin to a url rather than a specific forum... Is that right? If so... couldn't the modder already do this by overwriting the skin id before the cache is loaded? I'm just wondering what the purpose of this is... This is not something I would benefit personally, let alone thing about it. Does it have more to do with IPS Beyond?

[bfarber]

Say the admin wants all help file pages to use a different skin (maybe make it look more like a faq) they can apply all urls containing "act=help" to use a set skin. Or all profiles (using showuser=). Or just THEIR profile (showuser=1). The possibilities are endless.

This doesn't have much to do with IPS Beyond at all, no. This doesn't require any modifications to use either, so I'm not sure what you were getting at with the modder overwriting the skin id cache. This is a feature in the base product.

[zigs]

What have I missed :blink:

[Luke]

Well I'm fairly sure that the modder can set the skin id in the component_init file. But you wouldn't be able to do it in a help file that way... So that makes sense. For me the biggest advantage is I have a couple old modules that don't have skin bits in new skins I got... So I guess this could be used to force that module to use a skin that does until I'm able to add the bits to those skins.

My question is: Is the feature that set the forum skin being replaced by this? Or is it two separate options?

[Charles]

It's a new thing it doesn't replace anything :)

[TestingSomething]

Other than that the only actual feature I see is the "files" tab in profile. Ir is that from downloads system already?

[UBERHOST.NET]

Other than that the only actual feature I see is the "files" tab in profile. Ir is that from downloads system already?

Yes, when you have IDM installed, it adds the "files" tab in the personal portal.

[Mert]

kewlceo, I think he asks the one on this site :)

There's a download manager section in User CP and Files tab in profiles now. Maybe there are some preparations about Download Manager here :unsure:

[Keith J. Kacin]

Well I'm fairly sure that the modder can set the skin id in the component_init file. But you wouldn't be able to do it in a help file that way... So that makes sense.

This tool really wasn't made for modders, as it is a simple tool in the ACP that any admin can use.

It just makes the board completely customizable. For example, if you look at the URL to this reply screen:
http://forums.invisionpower.com/index.php?...mp;qpid=1478864

You can add a new skin remapping entry for: act=Post&CODE=02&f=298

So anyone replying directly to a topic in this forum will have a different skin. Or you can do "showtopic" and have every topic have a seperate skin.

As Brandon said, the possibilities are limitless.

[Dll]

It sounds good (if perhaps one of those things that sounds great in theory but never really has much use to the majority of people), but still lacking imo is a feature which allows you to assign access to different skins to different usergroups. I'm guessing that won't be available with this release?

[Alex]

To everyone about file tabs and files in ucp, they have been there for ages.

[Charles]

It sounds good (if perhaps one of those things that sounds great in theory but never really has much use to the majority of people), but still lacking imo is a feature which allows you to assign access to different skins to different usergroups. I'm guessing that won't be available with this release?

2.3 is about bug fixes, performance, and Converge integration - we're not really out to add a lot of features at this stage :)

[bfarber]

Yeah, some releases we concentrate on adding a lot of great new toys, while others have different core approaches - this particular release wasn't a lot about new features, but more about backend strengthening. :)

[Alex]

So is .4 or 3.0 next ;P

[Cybertimber2009]

Say the admin wants all help file pages to use a different skin (maybe make it look more like a faq) they can apply all urls containing "act=help" to use a set skin. Or all profiles (using showuser=). Or just THEIR profile (showuser=1). The possibilities are endless.

This doesn't have much to do with IPS Beyond at all, no. This doesn't require any modifications to use either, so I'm not sure what you were getting at with the modder overwriting the skin id cache. This is a feature in the base product.

Does this also mean that IP.Blog now has the framework to allow custom skins for a user's blog? It sounds like it could be used by applying that technique.

[Charles]

This is an update to IP.Board not IP.Blog.

[bfarber]

I think if I'm understanding him correctly though, fundamentally you could do what he suggested. The only thing is the admin would need to set the custom skins per-blog presently.

IP.Blog may incorporate an update at a later point that makes use of the feature potentially to apply custom skins to a blog. It's possible, but you'd need to check with Remco about that.

[Petrescu]

There are no changes to ibf_posts in the upgrade is there? Can you create a 2.2.2 > 2.3.0 upgrade for us as I find these most useful.

[Millar]

I still do not understand why the sudden jump to 2.3, I would have expected 2.2.3, look at the difference from 2.0 to 2.1 and 2.1 to 2.2, when compared to 2.3 there is a lot more.

So why the sudden jump?

[Luke]

I think if I'm understanding him correctly though, fundamentally you could do what he suggested. The only thing is the admin would need to set the custom skins per-blog presently.

IP.Blog may incorporate an update at a later point that makes use of the feature potentially to apply custom skins to a blog. It's possible, but you'd need to check with Remco about that.

The blog already has a feature to set a custom skin for a blog page customizable by user.

[stobbo]

I still do not understand why the sudden jump to 2.3, I would have expected 2.2.3, look at the difference from 2.0 to 2.1 and 2.1 to 2.2, when compared to 2.3 there is a lot more.

So why the sudden jump?

Thats what I was thinking, the 2.2 series was only fully released in December. But hey its only a number.

[Lewis P]

And is it me, or is the post view missing something......

Like a icon next to the member name?

[Mert]

Yes, online indicator is missing there. There's already a report about it in Bug Tracker :)

[Lewis P]

I wasn't looking to be honest. :D

[Labonte18]

A Guide To Software Version Numbers

Once you start playing with software you quickly become aware that each software package has a revision code attached to it. It is obvious that this revision code gives the sequence of changes to the product, but in reality there's substantially more information available through the code than that. Here's a guide for interpreting the meaning of the revision codes and what they actually signify.

v1.0:
Also known as "one point uh-oh", or "barely out of beta". We had to release because the lab guys had reached a point of exhaustion and the marketing guys were in a cold sweat of terror. We're praying that you'll find it more functional than, say, a computer virus and that its operation has some resemblance to that specified in the marketing copy.

v1.1:
We fixed all the killer bugs ...

v1.2:
Uh, we introduced a few new bugs fixing the killer bugs and so we had to fix them, too.

v1.3:
Hey, it could be worse!

v2.0:
We did the product we really wanted to do to begin with. Mind you, it's really not what the customer needs yet, but we're working on it.

v2.1:
Well, not surprisingly, we broke some things in making major changes so we had to fix them. But we did a really good job of testing this time, so we don't think we introduced any new bugs while we were fixing these bugs.

v2.2:
Uh, sorry, one slipped through. One lousy typo error and you won't believe how much trouble it caused!

v2.3:
Some jerk found a deep-seated bug that's been there since 1.0 and wouldn't stop nagging until we fixed it!!

v3.0:
Hey, we finally think we've got it right! Most of the customers are really happy with this.

v3.1:
Of course, we did break a few little things.

v4.0:
More features. It's doubled in size now, by the way, and you'll need to get more memory and a faster processor ...

v4.1:
Just one or two bugs this time... Honest!

v5.0:
We really need to go on to a new product, but we have an installed base out there to protect. We're cutting the staffing after this.

v6.0:
We had to fix a few things we broke in 5.0. Not very many, but it's been so long since we looked at this thing we might as well call it a major upgrade. Oh, yeah, we added a few flashy cosmetic features so we could justify the major upgrade number.

v6.1:
Since I'm leaving the company and I'm the last guy left in the lab who works on the product, I wanted to make sure that all the changes I've made are incorporated before I go. I added some cute demos, too, since I was getting pretty bored back here in my dark little corner (I kept complaining about the lighting but they wouldn't do anything). They're talking about obsolescence planning but they'll try to keep selling it for as long as there's a buck or two to be made. I'm leaving the bits in as good a shape as I can in case somebody has to tweak them, but it'll be sheer luck if no one loses them.