Jump to content

congratulations on v3!


Guest Mesmer

Recommended Posts

  • Replies 167
  • Created
  • Last Reply
Posted

Part of the speed issue seems to be the member seo name caching. We cache it in the members table. When we first upgraded, those weren't "built" of course, so as people clicked around and they were building, mysql wasn't too happy.

We're going to have a tool to build those upon release. ;) This is why we upgrade our forums early...to catch this sort of thing. There are other things we're looking at improving, but will probably take a little bit to investigate.

Posted

Speed isn't a problem for me.. running good as can be at the moment..

If anyone wants sprites for the buttons, just implement it on your own skin when making your skins :)

Posted

'Customerating' sounds judgemental. As in 'Customer Rating'. 'Memberating' has the feel of 'pontificating' or 'ruminating'.

In that way that it was used, maybe 'customerating' is more appropriate.

  • Management
Posted

Right at the bottom, Brandon. The IPB 3 tracking system is not compatible with the 2.3.6 system, so all tracked data is wiped.

  • Management
Posted

Where the hell is the mark all as read link =x



Every post is marked as unread for me




Topic markers do not carry over in the upgrade. The link is at the top of each forum. Look for "(Mark this forum as read)"
Posted

I'm looking for the 'Mark all posts as read' link - I have to go through and mark each forum as unread? Oo




Right at the bottom of the forum. In the footer. ;)
Posted

Just FYI, Brandon, I did more surfing on the site. Every single page has the same error, but a different line number and character.


This error is already in the Bug Tracker several times, so I won't clutter it up by reporting it there again.



They all follow the form:



Line: (26 or 35)


Character: (3 or 4)


Error: Object Expected


Code: 0


URL:

http://forums.invisionpower.com/index.php?app=forum&



I saw the same thing. Then I saw that the upgrade change my Pro Skin choice to the new Lo-Fi one. Once I updated that field to the new default, the errors disapperared.



Posted

I saw the same thing. Then I saw that the upgrade change my Pro Skin choice to the new Lo-Fi one. Once I updated that field to the new default, the errors disapperared.




Well I'll be damned! Same here. And now that I'm on the plain Board skin instead of Lo-Fi, you're right. No more errors. Veeeery Eenteresstink!
Posted

Yeah. I will have to say I was about to raise hell that they pushed a IPB 3 with broken javascript onto the board here. But little did I realize that it was the skin choice...

Good thing I clicked around a bit.

Posted


Well I'll be damned! Same here. And now that I'm on the plain Board skin instead of Lo-Fi, you're right. No more errors. Veeeery Eenteresstink!




Now added to my upgrade TODO list, switch all members who are using the Pro skin to the default before starting the upgrade.
Posted

Now added to my upgrade TODO list, switch all members who are using the Pro skin to the default before starting the upgrade.




I just reported this as a bug, so you might not have to switch everyone's skin.
Posted

I usually have switched all non-default skin selections to the default for every major change. (ie when the skins undergo a major change). It is safer.



Ditto.
Posted

So far I am unimpressed with IPB 3.
We were told to expect a great looking skin design that would blow us away... where is it?

If the current skin is it... some people have low standards. This current skin is comparable to the pro version of the IPB 2.3.X series.

Now the features of IPB 3 is awesome! But to me the looks are most important, features are secondary.

Archived

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

  • Recently Browsing   0 members

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