Jump to content

IPB 2.1.3 Released


Guest IPS News

Recommended Posts

Posted

Who really cares, with the exception of you, about WebTV support. Most other customers would prefer more important and less obscure bugs were corrected first.

You shouldn't proclaim such things to be straightforward.

  • Replies 546
  • Created
  • Last Reply
  • Management
Posted

We are looking at the possibility of adding WebTV support back into IPB, but be aware of the following problems:

1) WebTV is almost obsolete.
2) It's built on NS 4 / IE 4 technology which is almost five years old now.
3) An increasing number of websites will simply fail to work on WebTV

I understand your problem, but put simply, we're not going to rewrite large sections of the IPB code to accommodate a single user who refuses to upgrade their gateway to the internet.

We will make it so that a future version of IPB reverts to a simple textarea without javascript for non-javascript equipped browsers, but that's about as much as we're going to do.

It's just not viable to base the code of IPB on five year old technology - not without sacrificing all the good advancements the internet has made over the past few years.

This may make it into IPB 2.1.4 but it's not guaranteed.

Posted

That'd be a great idea, having IPB revert to a simple text area without javascript for browsers that don't support it. That should have been included in the beginning, IMO.

  • Management
Posted

That'd be a great idea, having IPB revert to a simple text area without javascript for browsers that don't support it. That should have been included in the beginning, IMO.



It kind of does, just not very well.

John: Not a bad idea, although an Amiga should be the minimum.
  • Management
Posted

It was removed because it didn't work particularly well. It was back in an early beta long before the "Loading..." box, so when it timed out, the user didn't know about it and/or didn't wait for the ajax to complete.

It was also before the improved marking was added, so cookies weren't being set right, etc, etc.

We'll bring it back for IPB 3.0.

Posted

It's truly amazing how many complaints people have over this release. In fact, a few pages back I called one fellow, dflorin, a smartass? Well, he sends me this nice pm :lol:





Now, at 28 years old and almost 30 in 2 years!, I am very likely older then him, to which I suspect he's probably 15 or younger, so it's the other way around.



At any rate, I'm sure I'm not the only one sick of all the complaints of this upgrade when so many people botch up what I see as an easy upgrade process. As for confirmed bugs, yes they are confirmed but it looks likes some of them have been fixed by Fusoya, and the others just can't be reproduced, or are being fixed.



*Happy with 2.1.3!* :D





You really are a smartarse Quark, you are also rude and condescending. You had no right to call him a names in the first place.

People come on here because they have problems, genuine problems, this upgrade has not worked the same on every forum. You may well be happy with 2.1.3, others aren't, as they're entitled to be.

Posting PMs is pretty off too, only someone like you would do something like that.

Before you go into another of your puerile rants, l'm 58, 60 in two years, so l guess by your criteria l'm much smarter than you, so have some respect for your elders.



:)
Posted

That'd be a great idea, having IPB revert to a simple text area without javascript for browsers that don't support it. That should have been included in the beginning, IMO.



while doing it how about making it so can also use it as a low bandwidth skin for search engines
while on a roll ..pda skin as well ?
Posted

I don't think Matt was referring to reverting the entire skin, just the posting area (my guess is using browser-sniffing to determine if the js will work or not).

Guess it could be *possible* to add the posting abilities to the lo-fi skin, which would then be a full low-bandwidth "skin" in theory.

@New Display Name and quark...please stop. ;) This thread really isn't for support either, though I try to help everyone out here as best as possible. If you guys need to argue or call names, do it in pm, or off site. Thanks!

Posted

All my events I just noticed are one day behind after the upgrade to 2.1.3.

I have tons of calendar events and the same thing happened when I upgraded from version 1.3.

Is there anything I can do on a large scale to change this?

I've already had to manually edit them once.

Anyone else run into this?

Posted

The calendar events are managed slightly differently/better in 2.1.3 compared to 2.1.2. You can now set an event start time which will utilize the time zone setting, or make it an all day event, in which case time zone settings have no bearing. I don't think there would be an easy way to rectify the events without some testing first (don't want to give you test queries without knowing if they will correct the issue ;) ).

Posted

The calendar events are managed slightly differently/better in 2.1.3 compared to 2.1.2. You can now set an event start time which will utilize the time zone setting, or make it an all day event, in which case time zone settings have no bearing. I don't think there would be an easy way to rectify the events without some testing first (don't want to give you test queries without knowing if they will correct the issue ;) ).



This same thing happened when I initially upgraded from 1.3 to 2.1.2 as well.

Not sure what or why but I've already had one of my staff members manually fix the calendar dates and now they are all off a day again (I'm just assuming it was due to the 2.1.3 upgrade).

This is a major pain for a site like mine, I have a full NFL calendar with hundreds of events, manual edits like this can take hours.

Is there anything at all I can do and will this happen everytime I upgrade?
Posted

This won't happen again in the future...many changes were made in the 2.1 series regarding the calendar events, and they should be fine henceforth.

The idea I was thinking you could try was to set the event's specific start time, but I'd have to take a look at the database columns (would involve setting a time zone, and a flag to say it's a specific time event). Or remove the start time setting if there is one. Then the event should show properly. But I would have to take a look and run some tests, which I wouldn't want to do on your live site. Feel free to submit a ticket and I'll see if I can give you a hand Monday with it. :)

Posted

This won't happen again in the future...many changes were made in the 2.1 series regarding the calendar events, and they should be fine henceforth.



The idea I was thinking you could try was to set the event's specific start time, but I'd have to take a look at the database columns (would involve setting a time zone, and a flag to say it's a specific time event). Or remove the start time setting if there is one. Then the event should show properly. But I would have to take a look and run some tests, which I wouldn't want to do on your live site. Feel free to submit a ticket and I'll see if I can give you a hand Monday with it. :)



Its already submitted, thanks a bunch. :thumbsup:
Posted

There already is a low bandwidth skin for search engines...



Which can also be used for PDA's, etc...




Yes, you are technically correct.

However, the downside of using the LO-FI feature is a duplicate content penalty that some search engine's apply.

It would be great to have a stripped board with the barest graphics, CSS, and JavaScript without having to rely on LO-FI.

Flashy graphic-intensive themes slow down board access for the bandwidth deprived as well.
Posted

Well, I think one of the other purposes of the lowfi version is to have topics and such as definite links, like t197995.html instead of the ?showtopic=197995 or other GET command.

Not exactly sure why those are needed, but I'm sure they serve some purpose, something to do with search engines and ancient browsers I think...

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...