IPB 2.1.2 & ICB 1.2.1 Released

[UBERHOST.NET]

I'm thinking we'll see IPB 2.1.3 next week, tons of bugs were fixed this week and not many more have been coming in (great job Brandon!).

Right, I believe so too. I just can't wait for all the whiners to start boo-hooing about reinstalling their 117+ mods and yada yada yada.

Well I say boo-f#$&ing-hoo!

[princetontiger]

That's a smart idea, though...

Hopefully we'll see something next week.

[Mr Incr3dible]

how do I upgrade to this current version?

[bfarber]

You can upgrade to the current version at any time (assuming you have a license) by downloading it from the client center and uploading all of the files to your server. Afterwards visit http://yourdomain.com/upgrade/ (replacing yourdomain.com with your domain name of course).

We provide upgrade services at no cost if you have a current license. Just submit a ticket through the client center if you would prefer for us to upgrade your board. :)

[VaBeachGuy]

I've just upgraded to 2.1.2 and installed ICB, the only problem that I'm having is with some of the ICB skins not matching my board's skin and I have no idea how to adjust it. Here's what it looks like:



What do I have to edit to make the background black?

[TestingSomething]

And please understand. I realize everyone likes to mod their boards (heck, I should know ;) ), but the thing is, we don't want to NOT release an update package when we could help users resolve various issues, just because it is difficult for modders to readd their code changes.

We are looking into a method of sorting this out for future upgrades, hopefully so that those users who like to mod their boards will have an easier upgrade experience. It's difficult and time consuming to document each and every code change we make as we are working on an upgrade, and relatively unnecessary for the majority of users. Thus we have to find some sort of common ground. The exact methods we use to do this have not been finalized however.

As much as I have edited and how slow I am where I can make sure all of the edits are right, it would be sucha pain. I think when 2.1.3 comes out I am going to take a chance on not uploading certain files. one I wouldnt have switched out would have been func_boardstats, but since you mentioned that, I would obviusly need that one. But I am doubting very much that such source files as topics.php, forums.php, profile.php, etc... would NEED to be reuploaded and also the queries file which is usually updated on a lot of the modifications. I bet if I dont overwrite files I have modiied, I would have far less issues than if I do th whole thing and have to re-edit everything.



Also, the 1 thing that is more annoying than anything is that they switched the way the cache files are named. That almost makes me think they purposely were trying to give a headache to modifiers. i doubt that is the case, but it made me wonder at first. And I rememebr when i bought this software, one of the selling points on the site was how it is modifiable. So you cant really say that and then not have to consider that group as well as the normal ones.

Or maybe another thing which could be done is document which files are used to change which fixes or new features. example: calendars.php for calendar fixes (and func-boardstats in this case), etc.

I dont know what the answer is really, other than it being more obvious which files MUST be changed for things to go smoothely, vs. which can be left alone.

Also, it would be good to have an idea of how soon new versions will be released. i realize that isn't always known, but I just doubt many customers assumed in this amount of time there would be a 2.1.0, 2.1.1, 2.1.2, and 2.1.3!

[Stuart Elliott]

I think when 2.1.3 comes out I am going to take a chance on not uploading certain files.

Just to jump on that one point...

And you'll complain when it all goes titsup.com afterwards won't you ? :rolleyes:

[Boult]

I upgraded from 2.0.3 to 2.1.1 to 2.1.2, and except for the calendar issues, and the link issue, most everything seems to be OK. I haven't added any new skins yet; I'm just using all the old skins that I was using in 2.0.3. And from what I can see, most everyone in my forums are using the default 2.1.2 skin, anyway.

Most of the buttons in the editor don't work the way I expect them to, however.

Like when you highlight a word, and click the boldface, italic, underline or strikethrough buttons: rather than inserting and wrapping the bb code aroung the highlighted text, you get the popup. This also happens with the alignment buttons, quote and code buttons in the new editor. However, the url, email and img buttons wrap the bb code when you highlight text and click those buttons.

Also, the users of my board were wondering what happened to the "BBCode Help" link next to the link for the smilie popup. Not everyone is terribly computer savvy, and I think it's odd that when adding BB Code, it asks for a hint, but there's nowhere for board users to see those hints.

Regarding "BB Code Help" link if you take your time to compare the ipb_templates.xml for both 2.0.x and 2.1.x find this line "<!--SMILIE TABLE-->" and you will notice the line below that line is missing.

here in this board running 2.1.2, it is missing that link.

that missing BBCdoe Help link has been reported in bug tracker as "unfiled" as of Oct 30 by other member.

[TestingSomething]

Just to jump on that one point...

And you'll complain when it all goes titsup.com afterwards won't you ? :rolleyes:

well they are supposed to fix problems no matter what version I have. There is no rule saying I must upgrade to a new version to fix issues with their sooftware.

[bfarber]

Hello,

If you only upload half of the files for a version, and your site doesn't work, unfortunately we are going to have to upload the other half. ;) Often times there are changes in one file that affects multiple files (just as an example, with 2.1.2 there is an issue with the moderator forum drop down menus if you enable the Short Forum Jump list which is corrected in 2.1.3...you have to upload class_forums.php, forums.php, moderator.php...)

Like I said, we're discussing a way to work around this for future versions, because we do understand people mod their boards. Additionally, like Matt did last time it is quite possible we can get a list of all the changed files as well. :)

[smallblockfuelie]

Thanks for the info. Any projected release date for the latest update?

[Adam Kinder]

well they are supposed to fix problems no matter what version I have. There is no rule saying I must upgrade to a new version to fix issues with their sooftware.

So you're saying that when a security problem is found with Windows or whatever OS you're running, you don't apply the patch and expect Microsoft to personally fix your copy of XP SP1 by hand? The patch and upgrade IS the fix for the issues in the current version.

Usually the best way to handle modifications is to keep an exhaustive list of edits and such so that you can reapply them after an upgrade.

[ckoebke]

@Adam

Who is looking at the bug tracker ? seems no one :( new security updates but some bugs that are easy to fix still in the new version. My company would kill me if i let bug reports untoched for days.

[bfarber]

If you are referring to the IPB bug tracker I have been going through it. Some bugs aren't quite as easy to fix as one might think, and as we are actively working on 2.1.3, QA has been testing what is completed.

Any items in there presently will probably not be included with 2.1.3, however most of the bugs in there are ones reported AFTER the latest patches were handed to our internal testing group. There was no way to have them ready as a result.

Any that were in there prior to the latest patches being developed were likely difficult to resolve (i.e. a javascript free skin/site for WebTV/Mac IE5/Pocket PC), or we are still determining the best way to resolve the report (i.e. the issue reported with queries using LOWER() in them). :)

[TestingSomething]

Additionally, like Matt did last time it is quite possible we can get a list of all the changed files as well. :)

The problem witht hat is almost all of the files generally modded for modifications were some of the changed files.



I think the best thing I can think of is maybe mod the files slowly when ti coems out and just keep 2.1.1 up until I finish modding the 2.1.3 files. That is about my only option if I want to upgrade, I would say. It is going to be tough becuase some modifications took huge amounts of edits. I may just make a list of files affected with each modification then for each file do all of the different edits for the various mods. That would at least be quicker than doing each modificatin separately and then reopening the same files over and over.........



Either way I hate the thought of having to do this again. Who knows how many hours it will take.

[.John.]

All I'm going to say, is this is why the Components System was introduced. If you complain to anyone, complain to modification authors for not being compliant - IPS has already done their part.

[TestingSomething]

true. Alhough I am sure it is tough for them to figure out how to switch their way of setting them up. But who knows..., quite a few did manage to do them as components VERY early on such as arcade.

edit: well actually I dont think many of them are true components. They still involved a little file editing.

[ikki83]

Hi! i'm an Italian newbie for invision 2.13.
I've got this error:
Fatal error: Cannot instantiate non-existent class: skin_global_94 in /var/www/html/sources/ipsclass.php on line 1407
I read in this forum how i can resolve that but... I haven't a cacheid_94 in my cache folder, so i can't edit the skin_global... How can i do? This problem born after a skin installation.
I've made he rebuildskins.php yet.
I think (but i'm not sure) that the missing skin is the default skin (in fact i NEVER change that after skin installation).
I can't enter in the acp because i've get the same error.
I hope someone can help me...
Thanks a lot!

[.John.]

#1 - This topic is regarding 2.1.2 and ICB 1.2.1 - not 2.13

#2 - There is no IPB 2.13

#3 - This topic is for the exclusive purpose of discussion of the release

#4 - If you need help, you can get help from other customers in Customer-to-Customer Assistance or at IPSBeyond.

#5 - If you want IPS to help, you can submit a ticket.

[Invisionary]

#1 - This topic apparently exists to allow customers to talk down to other customers or behave like unofficial moderators :P

[rct2·com]

Why is it impossible to find out what ICB costs?

What is the cost of a perpetual license please?

[Gaia]

Cost of the blog is 50USD and it is only yearly as far as i know.

[Invisionary]

Why is it impossible to find out what ICB costs?

What is the cost of a perpetual license please?

I can't see why you thought it was impossible :blink:

Got to your customer area then click Products -> Invision Blog -> Buy Now

As Gaia rightly says, it's $50 and it's a yearly license (like the gallery).

[rct2·com]

It's impossible if you are not a registered customer.

Which is a weird sales & marketing approach.

[Josh]

It's impossible if you are not a registered customer.

You have to purchase IPB before those modules will work for you, so the price is really only useful to registered customers anyway. You can order them at the same time as IPB, in that case the prices are displayed on the order form for non customers: Order Form.

That being said, we will likley add the price to the main blog page :)