Page 1 of 1

Where to post problems

PostPosted: Sun Jan 21, 2007 5:41 am
Author: krillmeed
Your phpBB Version: 2.0.
phpBB Type: phpBB / IMPortal
MODs: Yes
Your knowledge: Basic Knowledge
Board URL: http://www.krillmeed.com/forum/index.php

PHP Version:
MySQL Version:


What was done before the problem appeared?
1.41 update


What was done to try to solve the problem?
Nothing



De.scription and Message

I have problems with a couple of mods which i added myself, i.e. Blog mod, RPG mod, and the FAQ mod. The question is, i started in the 1.40 topics about this, do i start new ones here or carry on with the ones in the 1.40 version ?

PostPosted: Sun Jan 21, 2007 6:23 am
Author: Fubie
If you are now using 1.41 then yes. This is the place to be.

PostPosted: Sun Jan 21, 2007 6:29 am
Author: krillmeed
Thanks i will start the list <img>

PostPosted: Sun Jan 21, 2007 6:40 am
Author: krillmeed
i would like to add, that all problems are due to mods i have added myself. The update went in perfectly and i am only a novice. One observation, might also be usefull to add to the update from previous version readme, that the php security values will have to be edited again if you put in your own values. i.e. admins allowed and moderators allowed.

Re: Where to post problems

PostPosted: Mon Jan 22, 2007 6:37 pm
Author: Teelk
"krillmeed";p="20006" wrote:i would like to add, that all problems are due to mods i have added myself. The update went in perfectly and i am only a novice. One observation, might also be usefull to add to the update from previous version readme, that the php security values will have to be edited again if you put in your own values. i.e. admins allowed and moderators allowed.
The phpBB Security values shouldn't need to be added again. The update should have randomly generated and updated the DB and includes/phpbb_security.php file. I think the problem is that on some servers, when a file is overwritten, the CHMODs for that file are reset. Therefore, a file with CHMOD permission 666 would again be 644 and unwritable, which is what I think is happening with phpbb_security.php. A solution for this would be to add all CHMOD instructions to the update instructions, instead of just the new CHMOD instructions.