When i try to PM another user, i get a strange array fault:
Quote:
Fatal error: [] operator not supported for strings in /mounted-storage/home45c/sub002/sc33250-FSII/testcase/members/modules/private.mod on line 143
This is a section between line 142 till 144 from the private.mod file:
Code:
foreach($sendtox as $d){
$sendto[] = strtolower(trim($d)); }
Can anyone tell me what's going on here? And am i the only one with this Private messaging problem? If so, could somebody please send me a working private.mod or maybe paste the code here?
Access: Admin
Total Posts: 1395
Joined: 2006-05-19
Hi Southdistrict,
I apologize for not replying sooner, I've had quite a lot going on and have in all honestly been ignoring the site up until now.
The private message error you're having I've been unable to replicate. From what I can tell it could possible be due to aA PHP problem, perhaps you're using an older version?
Access: Admin
Total Posts: 1395
Joined: 2006-05-19
This was a tricky one as the code was working on both the machines I tested and developed it on. I've made a slight change to the private message module (modules/private.mod)
Edit it, around line 144~ you'll see this code
Code:
foreach($sendtox as $d){
$sendto[] = strtolower(trim($d));
}
If it helps, figuring out the problem: sometimes there occurs this message when trying to access the private messages:
Warning: mysql_result() [function.mysql-result]: Unable to jump to row 0 on MySQL result index 10 in /x/x/x/test/news/config.php on line 80
Warning: mysql_result() [function.mysql-result]: Unable to jump to row 0 on MySQL result index 11 in /x/x/x/test/news/config.php on line 83
Warning: mysql_result() [function.mysql-result]: Unable to jump to row 0 on MySQL result index 12 in /x/x/x/test/news/config.php on line 88
Private Messages
You can't edit this section. Contact the administrator.
Sometimes only the last term "You can't edit ..." pops up. Even if the special section is not deactivated. That takes place even for some sections in admin-accounts, where everything should be accessible.
I have not found out how to reproduce that - takes place almost randomly ...
Could have something to do with logging between two different accounts and not updating the relevant user-rights accordingly/just in time by the script?
Maybe it is of some help for you, to get into that.
then try send a private message to see if it works.
As for the error randomly appearing I can't see any reason for this happening, can you create a new file on your server called phpinfo.php and inside it put this code
Code:
<?php phpinfo(); ?>
upload it to your server and link me to it, I want to take a look at the configuration to see if there is anything I can find that could possibly be causing this.