grahack - 16 May 2007 01:40 PM
I didn’t mean ‘did you fix the code’, but ‘did you rename the CI index.php file’. Your problem may come from this.
My “problem” is fixed by replacing the hardcoded index.php as previously mentioned. I came across this ‘bug’ because on my server I actually have to change the config to:
|--------------------------------------------------------------------------
| Index File
|--------------------------------------------------------------------------
|
| Typically this will be your index.php file, unless you've renamed it to
| something else. If you are using mod_rewrite to remove the page set this
| variable so that it is blank.
|
*/
$config['index_page'] = "index.php?"; //Note I need the ?
//$config['index_page'] = ""; //hardcoded would be a problem who have this also maybe?
In any event, I needed “index.php?” so what was previously hardcoded “index.php” caused problems.
I’d like to centralize things. Dan wants to keep his 4webby stuff, but I think that things should reside in one unique place.
Ok, so it’s a suggestion for Dan as his site is nice, to also include the FAQ. I looked more at his site than I did at the wiki, even though the wiki may have more content. Again, I’m just getting to know FAL so I’m looking a bit all over right now. Another thing to do might be to distribute the userguide & FAQ with the package (assuming it’s not there already and I missed it). Maybe put a link in the footer of the distribution that links to the userguide, etc.
You can reformat the FAQ if you want. When we have time, we’ll work on the docs/tutos/wiki/ciforge…
I’m new to CI, I’m not a professional programmer, but have been following FAL with interest from a distance. I was a bit afraid of the so much action and being a newbie and didn’t understand stuff. Even when I shopped around for PHP frameworks what got me to CI was the userguide. I would not have tried CI if not for the userguide. So to that end, I suspect there’d be even more usage of FAL with better documentation. But truthfully, with the distributed examples, there’s a lot already there for “documentation”.
Crimp - 16 May 2007 02:08 PM
I don’t understand the ‘kick users off’...
Edit: I guess he means getting the boot Live. It would be hard to top that for rudeness… 
As it turns out I’m American, not French. I did do some backpacking overseas for 6 months and commonly heard “you are not your typical rude american”, which I didn’t appreciate until I returned back to the USA, and I remember thinking 2 steps past customs how rude americans are.
Blacklisting would be a similar feature that I’m talking about. But I was really inquiring about getting the boot (sounds like an English/Irish saying) live. I personally don’t see the need to get the boot live, but I do see a use for the option to limit users from logging in only once at any given time. I’m not sure but maybe this entails having another table where all logged in users are kept. Then if someone logs in again, check if that person is already logged in, if they are logged in check if that user is allowed multiple instances, and then add to the logged in users table. If they are not allowed multiple instances, remove the original instance and add the new instance. Again, I’m not a pro, so my logic may be somewhere around Uranus 
(between the Sun and Pluto?).
Donations
Actually before you even mentioned it I was trying to look for where to make a donation. I think I saw where one time but can’t find it again. In the distribution package homepage it mentions the donation, but there is no active link or directions? Suggest you make an active link at the various sites, especially in the distribution’s homepage.
It’s only a big orange star with a big donate next to it. It’s almost too big. Putting a link in the download package’s homepage where it says “donate” would be another good spot.
