Config settings disabled

[omniscientdeveloper]

Are these fields suppose to be disabled?


-omni

[Joachim Müller]

What browser do you use - apparently Mozilla? I noticed something strange was going on, probably improperly nested tables (that's why the table cells don't use the full width), but I didn't notice config fields being disabled. The config fields are not disabled for me using IE6 or Firefox 0.9.3

GauGau

[Casper]

Edit, just also tested on IE and Firefox 0.8 (I must upgrade), after doing full cvs check, and all working OK for me.

[omniscientdeveloper]

I have FF 0.9.2. I thought that it was the actual config or english file, since the html for the fields have disable properties. I replaced all my files and ran update, however, I can do it again.

HTML Snipet:

Code Select Expand


                <td width="40%" class="tableb" valign="top">
                    <input type="text" class="textinput" style="width: 100%" name="user_profile2_name" value="Interests" disabled="disabled"/>
                        </td>
                        <td class="tableb" width="10%">



As you can see below, there are actually more fields, but on first thought, I thought that these were suppose to look this way. I'm thinking that there is some global variable (maybe) being passed or some funky english.php settings.


-omni

[Nibbler]

I added this 2 weeks ago ('Added facility to disable config settings that are irrelevent with bridged installs.') I thought it would avoid confusion to disable settings that didn't have any effect. They are defined in an array at the top of config.php.

[Tarique Sani]

@Nibbler - good one!
@omni - read the stickies and FAQs

[omniscientdeveloper]

LOL

You know what...now that you say that I do remember hearing this. I just forgot about it. I did, however, do a search before I posted. I didn't come up with anything. I didn't think to search the FAQs though. I had an odd feeling that this was a "feature" though, that's why I asked a question in the beginning instead of saying it was broken.

Anyway, is it possible to change it so the fields are gone altogether and replace it with text that says something like "not used on bridged installs"?


-omni

[Casper]

Well in support of Chris, I cannot remember this, although I have been away for most of the last 2.5 weeks.  I read every post on the dev board when I got back, and still cannot find where this is mentioned.  I'm sure nibbler did tell us somewhere, but I can't find it.

[omniscientdeveloper]

It's ok. It's not that serious. I searched the changelog afterwards and saw that it was in there also. I'll just have to make a note to check those things, if I'm gone for an extended time period.


-omni

[Nibbler]

Very well, message 'Function disabled when using bb integration' added to config page. My apologies for not posting the change on the board.

[Tarique Sani]

In Nibbler's defense CVS comments are important for precisely this reason

[Joachim Müller]

k, I guess this is sorted out now. Actually there's no policy that every new feature needs to be posted about on the dev board, as long as it's in the changelog. This thread is gettiing a mild "flame" thread, so I' suggest we'll just close this case.
After all, Tommy's addition is a great improvement imo - cheers to that.

Joachim

P.S. Don't forget that this sub-board will become semi-public (once we let the testers in) and fully public once we release - I suggest we keep discussions about dev team internals to the dev general board

[Tarique Sani]

I can honestly assure that no offense/reprimand/flame was intended by me - just a bit of black humor
Case closed

[Casper]

It was also never my intent to start a blame/defence fight.  So if my post was taken that way, I apologise.

Perhaps this is a case for a dev thread ending in the crap bin   

[omniscientdeveloper]

LOL

Black humor isn't taken too well in the USA, at least not where i come from.  Hence, no reply from me. LOL


-omni

Crap bin indeed.