Mark

Yes :)

:rolleyes: Brandon said "I'll simply say that our target release date is before June." - that is quite different to "Our target release date is in June." which is how it looks like some people read it. And people wonder why we don't like to mention dates.... That is the plan

We will continue providing tech support for 2.3.6 for the forseeable future, but there will be no more updates.

While obviously I haven't looked into this fully, nor do I have say over what features are added - I think it may be a little more complicated than you are thinking, this is just off the top of my head: 1) Searching - the search engine would probably need a bit of a rewrite to accommodate this 2) Permissions - what if they have permission for the alternate forum, but not the main one? Can they see the topic in the alternate forum? If no, it would be too resource intensive to work, if yes, well then, we have a bit of a permissions problem... 3) Moving - what if the thread is moved? Does it move from the forum it is moved from? Or both? What happens if you try to move the topic in the alternate forum to the main one? The move function would have to be rewritten a bit however that is decided. 4) Deleting - if you delete one, does the other delete? The delete function would have to be rewritten a bit. 5) What if someone wants to add an alternate forum after posting? We'd need something to accommodate that. 6) What if someone wants to remove the alternate forum after posting? Even worse, what if someone wants to remove the main forum and make the alternate forum the main forum? We'd need something to accommodate that. Personally, I think it would be a bit of hassle for a bit of strange feature - in what circumstance would you need this? There might be a better solution, such as allowing announcements to have replies, maybe?

Guys... relax. We're not going to get a team of lawyers to sue you and send repo men to your house to collect money for damages because you used "invisionpower" in your domain. If you want to use "invisionpower" in the domain, submit a ticket in the client area and we'll send it to the management who can discuss the situation further. Like Lindy said, creating resource sites is appreciated, and we're going to be working with you to defend our trademarks, not against you :)

We were actually talking something similar to this the other day. I'm not sure if it will actually happen - but I'll shift this over to the feedback forum so the right people see it.

Just because you would like it doesn't mean everyone does. In my opinion, AJAX is fantastic when it is done right. Not only is it good aesthetically, it has useful practical applications (such as the aforementioned video scenario). Unfortunately, it is rarely done right when there is a lot of information to process. There are so many different browsers which handle it slightly differently, it's a nightmare to code, confusing for the user when it doesn't work (but most likely submitted the content, just not returned it) and often done for little more than the sake of it. Even sometimes when I post a comment on YouTube, the submit button greys out and gets stuck on "Posting..." (or whatever it says) - then if I reload, sometimes its there, sometimes its not, maybe that's because the person posting the video has comment moderation enabled? Who knows? Not the user ;)

I really like this idea, but it is very hard to implement - I even tried making a mod at one point, but it just had too many drawbacks: The only way one could really do it would be to add a tag if the reply or multi-quote button was used with the quoted person's ID in - which isn't hard but, someone could always copy and paste another persons post (which isn't feasible to be filtering out) - and what if someone quotes several posts in their reply, but you are only ignoring one? It would be difficult to not show half of a persons post...

Let me rephrase that: upgrading would be a mess. Especially as it's so critical to get right (IT Crowd reference: "You don't want to end up in the middle of invalid memory!") and such a difficult thing to test - the only way to test it would be to create a test site filled with fake data, logging the way everything should be, running the upgrader and checking it all converted properly; and doing that is going to be very easy to make a mistake, or miss something. Unless there is some major compelling reason that they should never be used that I'm not aware of (if there is, please share: You didn't say why comma separated strings are so bad) I'd much rather know that the upgrader isn't going to be undertaking database structure changes for the sake of it.

What's so bad about comma separated strings? If they used linking tables for everything that is comma-separated or serialised, the database would be a mess.

How do you suggest it is done? And why not use regexes? They work fine...

Would be helpful if custom profile fields were passed to on_create_account. The only way to get that data now is to add $fields->out_fields to the function call in action_public/register.php and action_admin/member.php

Just thought I'd let you know all the Nexus modules have a license agreement when you go to download it except the hosting one.