{SOLVED} Can't respnd to reviews

Beautiful Tammy, that worked like a charm with the 3.2.1 install, thanks sooo much

😀

EDIT::

sorry everyone, false alarm.. oopps I forgot to revoke my admin priviledges when i tried it. Still cant respond to reveiw as regular member.

*blushing in embarrassment*

Maybe it's the bridge or maybe I screwed up the settings trying to get it work before the update to 3.2.1 but this still isn't working for me. In fact it's doing the exact same thing. I've only upgraded my test archive for now, if you decide to look at it.

Probably I've done something terribly wrong during the 3.2 update, because now I have this problem, too. The thing is: with the user/revres.php file of 3.1.1 users can respond to reviews; with the 3.2.1 they can't. So, I imagine that something went wrong with the update of the database 🙁

Actually guys, it was me, not you, it was me

I gave my test account some admin privilidges the other day, forgot to revoke them and just got a wee bit excited when the update came and.,... well

ummm sorry  😳

LOL, I'm just happy I didn't screw something up! 😀 Don't worry about it.  😆

Please, tell me if I'm wrong: apparently the problem is on line 32 of user/revres.php, where it says:

		if($adminloggedin || $uid == $useruid) {	

In fact, that means that you can respond to the review only if: a. you're an admin; b. you're the author of the _review_ (not the author of the story).
($useruid should be the id of the logged user, the author of the story that wants to respond to reviews. $uid is defined on line 31 and comes from the fanfiction_reviews table, where 'uid' is the author of the review.)

For this, I think an extra line of code should be added, where - I don't know, really - you get the user ID of the author of the story (let's call it $authorid), and only after that should come the code:

		if($adminloggedin || $authorid == $useruid) {	

I'll try to do this on my site; in the meantime, the problem can be temporarily 'solved' commenting line 32 and line 44 (the closing }), though this way - I suppose - any user can respond to the reviews of a story, knowing the right url.

Same here, I installed 3.2.1. and it seems to have taken care of the messed up statistics (the reviews are off by 1 now, but I can live with that *g*), but I'm still getting the same error when I try to respond to reviews. I tried with my test account and had one of my users try as well. With no success. URL is still http://www.naiceanilme.com

I'll try to do this on my site; in the meantime, the problem can be temporarily 'solved' commenting line 32 and line 44 (the closing }), though this way - I suppose - any user can respond to the reviews of a story, knowing the right url.

Thank you so much! It's not a complete fix, but it'll get my authors to stop emailing me about this.

Ok, I tested the fix on my site and then again on local with a brand new installation of 3.2.1, and it works.
I'm posting it here, so you can use it if you have the same problem as me, at least until Tammy fixes it officially.

Open user/revres.php
Find line 32:

Code:

if($adminloggedin || $uid == $useruid) {

Delete it, and add these lines instead:

$resultch = dbquery("SELECT uid FROM ".$tableprefix."fanfiction_chapters WHERE chapid = '$chapid' LIMIT 1");
list($authoruid) = dbrow($resultch);
if($adminloggedin || $authoruid == $useruid) {	

Wonderful, I could hug you, you know?!

it works like a charm. Thanks so much.

Thanks you so much! Even a mentally challenged coder like me was able to do this! It works!

T.

will this also fix the problem I get...

if anyone (admin or member) clicks on Review Response  they get the message You are not authorized to access that function.

this is a clean install of the latest efiction that im using with no mods done to it

as its a new install let me know if you have to specifically install something for the reviews (like the challenges module)

thanx in advance of the help!

My authors also can not respond to reviews.

http://asherida.net/kakasaku/eFiction32/index.php

Using 3.2.1... new install.

Did you add the temp fix found on this thread?