bfarber

It's not needed. Language files need to be "(app)_(custom name).php" so we can already detect and remove language files by the application prefix. e.g. language files for the core application all start with "core_" - so when the application is removed we could just delete all language files starting with "core_". ;) This would not allow you to have more than one tab for the application, though it's arguable if that's a bad thing or not. For the record, the group tab integration stuff already supports methods to set the tab ID number properly, but the members tab integration does not presently. Errr, they already are. :unsure:

Yes, it's possible to have multiple languages. What makes you think it's only possible to have one?

This is a feedback forum. If you need support please use the appropriate peer to peer support forums. :)

Problem is, everyone has different requirements. Easy enough to add group support in I suppose (though it would take a bit of work to make it ACP-configurable), but then someone will ask for secondary groups. Then custom profile fields. Then profile settings. Never ends.

Has already been pointed out but... 1) It was always at the bottom of the page, however it was only previously at the bottom of the board index page. Now it is at the bottom of every page (which I find more convenient personally). What YOU are referring to was the link was duplicated on the view new content page (view new posts) at the top of the screen there. We have not put the link at the top of that page, because it is already at the bottom of EVERY page. Seems redundant to have the same link twice on the search results page (though, naturally, it would be easy for a skinner to add it back in if they disagreed). 2) There is no my assistant feature anymore. Quite frankly, the feature was relatively useless for the majority of users. 3) Things have been made slightly bigger to make them easier to read. There are a lot of people with less than perfect eyesight using the internet these days. I, too, prefer smaller sizes - but then again I'm 20-something and my eyesight is perfect. Easy enough to change this in your CSS. 4) Click your name at the top right, and it's in the list there. 1) Click your name at the top right, and choose My Gallery (instead of My Profile). 2) Click one of your albums 3) Click "New Image" It's the same as 2.3, with the exception that you have to click your name at the top right first.

This forum is for feature suggestions and feedback for IPB, not support. :) There will be no official upgrade path from betas to RC. Your ioncube error has been discussed many times in the appropriate customer support forum.

Exactly...

We have a perl script we'll be releasing that can help automate the basic structure of application creation (creating the directories and stuff).

Was someone sending spam through the system. Already dealt with.

This has gotten off topic. With the cussing and bickering, no need to keep this open.

Oh, I was looking at 3.0 when I posted that. Unfortunately 2.3 requires an additional modification. In 2.3.6 you'll see something like $this->create_local_member( $username, $password, $email ); Change to $this->create_local_member( $username, $password, $email, $this->ldap_config['ldap_group_map'][ $this->fields[$this->ldap_config['ldap_group_id']][0] ] ); Then you have to modify loginauth/login_core.php to accept the group id function create_local_member( $username, $password, $email_address='', $group_id=0 ) And to pass it to the internal method $member = $this->_create_local_member( $username, $md_5_password, $email_address, $group_id ); And then the internal method needs to accept it function _create_local_member( $username, $md5_password, $email_address='', $joined='', $ip_address='', $group_id=0 ) And then of course store it in the db 'mgroup' => $group_id ? $group_id : $this->ipsclass->vars['member_group'], Really we're starting to veer off course here. As you can see, it's much easier to do this in 3.x. ;)

http://resources.invisionpower.com/index.php?appcomponent=cms&module=articles&article=7510

Without IN_DEV on, you'd have to reimport the XML files from the various application directories one by one (admin and public both)

Not presently, no.

I'm afraid I'm not familiar with the workflow you speak of.

For the record, I've done modifications to map AD groups to IPB groups - it's relatively simple to be honest. In IPB 3, for instance... In the conf.php file add something like the following $LOGIN_CONF['ldap_group_map'] = array( 'group1' => 3, 'group2' => 3, // Extend as needed $LOGIN_CONF['ldap_group_id'] = 'ldapGroupCol'; The first config value will tell IPB which field in LDAP contains the "group id". The second is an array that maps the returned value to a group id in IPB. You will need to change these values accordingly. At the end of the file find $LOGIN_CONF['additional_fields'] = ''; and change to $LOGIN_CONF['additional_fields'] = 'ldapGroupCol'; This is, again, the field in your AD that has the group membership information. Then in auth.php where you see 'members_display_name' => $this->fields[$this->ldap_config['ldap_display_name']][0] ? $this->fields[$this->ldap_config['ldap_display_name']][0] : $username, 'password' => $password, 'email' => $this->fields[$this->ldap_config['ldap_email_field']][0] ? $this->fields[$this->ldap_config['ldap_email_field']][0] : $email_address, ) ) ); $this->member_data = $this->createLocalMember( array( 'members' => array( 'name' => $this->fields[$this->ldap_config['ldap_display_name']][0] ? $this->fields[$this->ldap_config['ldap_display_name']][0] : $username, could change it to something like 'members_display_name' => $this->fields[$this->ldap_config['ldap_display_name']][0] ? $this->fields[$this->ldap_config['ldap_display_name']][0] : $username, 'password' => $password, 'email' => $this->fields[$this->ldap_config['ldap_email_field']][0] ? $this->fields[$this->ldap_config['ldap_email_field']][0] : $email_address, // ADDED THIS 'member_group_id' => $this->ldap_config['ldap_group_map'][ $this->fields[$this->ldap_config['ldap_group_id']][0] ], ) ) ); $this->member_data = $this->createLocalMember( array( 'members' => array( 'name' => $this->fields[$this->ldap_config['ldap_display_name']][0] ? $this->fields[$this->ldap_config['ldap_display_name']][0] : $username, This is just an example and may need tweaking for your situation, but I've used something similar in the past without issue. You can use the additional_fields to pull other fields and then modify auth.php to do something with those as well (one example was, for a store using LDAP, I've modified it to check an "employment status" field to ensure that only active employees could access the forums). :)

Known (and fixed in RC1) bug Will be in RC1 PHP closing tags are never required in PHP files, and Zend actually recommends omitting them to reduce the possibility of sending whitespace before headers. Good find. Will be in RC1 (I'd consider this a bug really) Agreed. Will try to get this into RC1 as well. Thanks for the feedback. :)

You must have a license for IP.Board in order to download the software. We do not publicly release test copies of the software, however we do allow you to create an online demo. http://www.invisionpower.com/community/board/demo.html

If you have an IP.Board license, you can login to your client area to download the beta version of IP.Board 3.0.

Yes, it can be done.

Yup. My brother has a Helios last I knew. Anyways, we will most likely be configuring the lofi-mapping to capture more mobile user agents than we have presently. ;) It's only basically configured for testing, and as I said, the lofi skin is largely broken atm.

It's on the todo list

As you can see from our footer, we are testing it here and fixing the issues we can for it. Note the blog entry said "or so" - it was an estimate.

Perhaps where you are from the majority of users have those phones, but I can't think of a single person I know that does. :) This is why the user-agent mapping is configurable. ;) And the lofi is meant to be boring. :blink: It's meant to be ... well ... lofi - less (or no) images, no javascript, basic colors, so that on a mobile device it loads faster and can display data on a smaller screen. It is a skin, however, so feel free to tweak it on your site once it's released.

Yes, I changed it in the hook code. We'll have to reimport/export he hooks, and reimport here for it to be updated.