bfarber

I'm not positive. All I know is that we are fully aware it's not likely to be included with 3.0.0 due to time constraints.

Please read the announcements in full. We publicly stated there *would* be bugs in the RC releases and you should only upgrade if you felt you could handle the bugs until they were fixed (by/in the final release). We release betas (and release candidates) for a reason. It's to find and fix issues that we did not come across ourselves. With so many people using the software in so many different configurations there are always bound to be issues we simply didn't encounter, and that's why pre-final releases are done.


Long story short, we're not going to rush RC2 because RC1 has some bugs. Nor will we rush final because RC2 WILL HAVE BUGS. We're going to continue working to make the software as stable as possible so that the final release is as bug free as we can get it.

Please read the announcements in full. We publicly stated there *would* be bugs in the RC releases and you should only upgrade if you felt you could handle the bugs until they were fixed (by/in the final release). We release betas (and release candidates) for a reason. It's to find and fix issues that we did not come across ourselves. With so many people using the software in so many different configurations there are always bound to be issues we simply didn't encounter, and that's why pre-final releases are done.


Long story short, we're not going to rush RC2 because RC1 has some bugs. Nor will we rush final because RC2 WILL HAVE BUGS. We're going to continue working to make the software as stable as possible so that the final release is as bug free as we can get it.

Why yes, you're welcome. I do take all the credit of course.

We turned it off because a few of our members felt the need to target certain other members and negative rep all their posts. In any event, you can turn it on and off and there are some controls for it in the ACP.

Yes, the release candidates are only available to customers who hold a license for the respective applications.

Please read the announcements in full. We publicly stated there *would* be bugs in the RC releases and you should only upgrade if you felt you could handle the bugs until they were fixed (by/in the final release). We release betas (and release candidates) for a reason. It's to find and fix issues that we did not come across ourselves. With so many people using the software in so many different configurations there are always bound to be issues we simply didn't encounter, and that's why pre-final releases are done.


Long story short, we're not going to rush RC2 because RC1 has some bugs. Nor will we rush final because RC2 WILL HAVE BUGS. We're going to continue working to make the software as stable as possible so that the final release is as bug free as we can get it.

We have an internal date we are targetting for RC2, but we're not going to announce it at this time. Suffice it to say, that date is not "1-2 months" away. But we'll see how things go in the tracker before making a final decision.

Why do these topics always come up right after a release? :rolleyes:

Please use the peer to peer forums for support.

We turned it off because a few of our members felt the need to target certain other members and negative rep all their posts. In any event, you can turn it on and off and there are some controls for it in the ACP.

We have an internal date we are targetting for RC2, but we're not going to announce it at this time. Suffice it to say, that date is not "1-2 months" away. But we'll see how things go in the tracker before making a final decision.

Why do these topics always come up right after a release? :rolleyes:

We turned it off because a few of our members felt the need to target certain other members and negative rep all their posts. In any event, you can turn it on and off and there are some controls for it in the ACP.

Ah, ok. To summarize...

You want to be able to use javascript in the editor.

Ah, ok. To summarize...

You want to be able to use javascript in the editor.

Ah, ok. To summarize...

You want to be able to use javascript in the editor.

We turned it off because a few of our members felt the need to target certain other members and negative rep all their posts. In any event, you can turn it on and off and there are some controls for it in the ACP.

It's simply new is all. Once you get used to it, it makes a lot of sense, and allows applications to be complete segregated and sectioned off from the rest of the code. Add a folder and you're done. Delete a folder and files for the app are gone. A lot cleaner than having to upload your files to 10 different folders (and then trying to remember what to remove).



userInfoPane is in skin_global. You can include one skin template directly from another skin template now, so you won't see this called in the source files pretty much at all. Instead you'll see this in skin templates


{parse include="userInfoPane" group="global" params="$params"}

Which means the skin template will output the results from skin_global -> userInfoPane (passing $params to it) wherever you see that tag.





A lot of this is covered in articles on the resource site.

Loading a member: http://resources.invisionpower.com/index.php?appcomponent=cms&module=articles&article=7533

Outputting content I don't think I've written an article on, though I'm sure we can do so.

Extending group configuration: http://resources.invisionpower.com/index.php?appcomponent=cms&module=articles&article=7529

TONS of various information: http://resources.invisionpower.com/index.php?appcomponent=cms&module=articles&article=7536
That article is primarily related to upgrading an application, yes. However, it goes into detail about the file structure, what files can do what, and so on. It's very useful so long as you are familiar with how to do things in 2.3.




We said we were shooting for a June release, and to my knowledge we still are. We expect an RC2 and at this time that is the only further RC release I am aware of in the works.



The thing was, we were shooting for December originally. But then we had so much great feedback with the preview site we were determined not to ignore it simply for the sake of rushing the release out. We wanted to incorporate as much as possible that made sense. The spam controls were greatly enhanced. Facebook Connect was added. The personal conversations changed a lot. Friendly URLs changed a lot and were made extensible. And we won't talk about the skin changes. A ton was changed due to feedback we received, and while it has delayed our original release plans, I think in the long run everyone will agree that IPB as a product is better because of the changes.



The subscription manager is nearing completion from my understanding. It will definitely be out for testing before IPB3 goes final.

As already stated your modifications will not work on 3.0. You can't reinstall them, reapply the edits, etc. They simply won't work. You will need to contact the modification authors to find out if they have written updates for 3.0, or if they plan to.

I assume you mean RC1. We do not provide support for RC1, however we believe you shouldn't have any issues upgrading now and then upgrading to final when it's released.

That said, there are always bugs and issues in pre-final software, so if you cannot address them or live with them until they're fixed, you may find it better to wait for final.

Yeah, you can only override source action files. So when class files take over and do the work (and especially when they redirect, etc. afterwards) it makes things a little challenging.

Some class files have built in hook functionality (like publicSessions.php) but not all.

I think you'll have to modify this for now, but we will look into building in specific hook functionality for the posting library in the next update, as that's very useful functionality.

Please submit a ticket as has already been requested. We do not simply delete user accounts on this forum.

Indeed, the huge influx of bug reports is not helpful in releasing the RC releases of our other applications. I'm not entirely sure the plans for their release, however, so can't say if the bug reports will have any major impact or not.

It does indicate it on the performance mode page, but I can see your point. I believe the status is stored in the caches somewhere, so it would be possible to load it on the front end easy enough and show an indicator (it would probably be a 10 second skin edit in all reality...)


$caches = $this->registry->getCache('performanceCache'); </php> <if test="count($caches)"> Performance mode is enabled! </if>
<php>







Something like that. :)

It does indicate it on the performance mode page, but I can see your point. I believe the status is stored in the caches somewhere, so it would be possible to load it on the front end easy enough and show an indicator (it would probably be a 10 second skin edit in all reality...)


$caches = $this->registry->getCache('performanceCache'); </php> <if test="count($caches)"> Performance mode is enabled! </if>
<php>







Something like that. :)

For the record, if you are insistent upon paying for 3.x separate from your license I can forward you my paypal email. I don't mind, really.




/jk