I didn't see a topic for this one, so posting.
When you get an alert "Profile Comment" and click on the link provided (Ie: Brinneal commented on your profile!), I get the following error at the top of the Comment page:
Warning: mysqli_fetch_row() expects parameter 1 to be mysqli_result, string given in /www/subeta.net/include/class/database.new.php on line 277
Oddly enough, if I click on Comments from the Personal Drop Down box, I do not get this error.
I am using Chrome.
Love may not always be destiny, But a Gift.

Is this still happening? Feel free to comment and I can see if it happens for me :D
Dexter by ❤
not the exact same problem but is to do with comments.... when I read a comment on p2p (in my own comments) , and hit reply (like I normally do) It says comment is posted. however, I have now been told users never got comments. I tried it again today with the same result...It says it's posting it to the person but it doesnt get it nor does it show up as it used to It only works if I go directly to their profile and comment. If I need to create a different board please let me know
This error happens with me too. I'm not sure if you figured it out with Brinny through comments or not but I thought I'd let you know about it
Warning: mysqli_fetch_row() expects parameter 1 to be mysqli_result, string given in /www/subeta.net/include/class/database.new.php on line 277
I see this error also if I click on the profile comment in the event tab on my dashboard when someone leaves a comment for me to see.
Same problem as original post.
Thank you kindly ^_^.
A friend is someone who knows all about you and loves you just the same ❤.
I know that Destiny did raise this with the programmers..I guess maybe they are a bit busy :)
It is still happening for me too.
Love may not always be destiny, But a Gift.

It will be looked into but as the error is not causing major problems, they are looking at other things first. I will post when it is taken care of!
Dexter by ❤
Hey guys, I know this was a while ago, was this ever resolved for you? Are any of you still getting this error?
🐝 ☕ bug (he/him) | your friendly neighborhood code wrangler. stay in the loop! join and check out the latest admin post highlights
Write a comment on my page please! :D
🐝 ☕ bug (he/him) | your friendly neighborhood code wrangler. stay in the loop! join and check out the latest admin post highlights
Commented! Let me know if that didn't go through, I'm on my phone atm
I actually think I may have inadvertently fixed this when I added pagination to these pages this Thursday, because I didn't see the error for your comment just now. But I recognize the error message as something I encountered and fixed when I was adding pagination xD
Gonna comment you back so you can see if it's still happening for you. If you can't check it on your phone, no rush, just keep the event and let me know when you get to a computer :)
🐝 ☕ bug (he/him) | your friendly neighborhood code wrangler. stay in the loop! join and check out the latest admin post highlights
Still getting it. You think if I delete all my comments the error may go away?
Can you paste for me the exact URL the event takes you to?
And no, I don't think deleting comments has to do with it. I know exactly what the error message means though, I just gotta figure out where in the code it's coming from and it should be a quick fix.
🐝 ☕ bug (he/him) | your friendly neighborhood code wrangler. stay in the loop! join and check out the latest admin post highlights
Can you comment me again? I deleted the event already :x
Edit: nvm just a sec!
Edit2:
gonna comment you again, and you let me know if it's better now ^^
🐝 ☕ bug (he/him) | your friendly neighborhood code wrangler. stay in the loop! join and check out the latest admin post highlights
Yaaay! I think it's good now, I'll leave it up to you to decide if we should lock, or wait for others to double-check us. Thanks for the debuggin help
🐝 ☕ bug (he/him) | your friendly neighborhood code wrangler. stay in the loop! join and check out the latest admin post highlights
That's probably up to / but I'd probably give it a day or two to see if anyone else can confirm it's fixed for them and if so, call it completely fixed :)
No problem! Always happy to help. Thank you for fixing it!
Oh wait you're not a minimod in this forum d'oh
my bad I got confused SORRY.
🐝 ☕ bug (he/him) | your friendly neighborhood code wrangler. stay in the loop! join and check out the latest admin post highlights