Return to Project-GC

Welcome to Project-GC Q&A. Ask questions and get answers from other Project-GC users.

If you get a good answer, click the checkbox on the left to select it as the best answer.

Upvote answers or questions that have helped you.

If you don't get clear answers, edit your question to make it clearer.

+2 votes

When I click in my profile on private messages I get this error code:

Question2Answer fatal error:

User accounts are handled by external code

Stack trace:

require() in index.php:28
require() in qa-index.php:183
qa_get_request_content() in qa-page.php:824
qa_call_override() in qa-page.php:194
qa_call() in qa-base.php:671
qa_get_request_content_override_1_in_qa_poll_overrides_php() in qa-base.php:619
qa_get_request_content_base() in qa-base.php(595) : eval()'d code:12
qa_call() in qa-base.php(669) : eval()'d code:1
qa_get_request_content() in qa-base.php:619
require() in qa-page.php:207

in Bug reports by pingurus (2.2k points)
good catch. I didn't even notice that there is such link from User profile. It might be even bug in Q2A itself.
Saw the dame thing today :)

1 Answer

+1 vote
Best answer
Private messaging should be disabled, but the item to disable it seems to have disappeared in the settings. Could potentially be a bug with the Q2A software.

Our authentication code (single signon with Project-GC) doesn't support the functions needed for the private messaging, which has been an active decision in itself.

In a perfect world we would hide the sub menu that isn't working. But it's hardly worth the priority, hopefully it will get fixed with a Q2A upgrade.
by magma1447 (Admin) (225k points)
selected by pingurus
Thanks for this answer. I have the same problem and was wondering why.
It looks like the fix is in 1.8.0 version:
The link should not be shown there either in the next version, when the messaging will be disabled:
Thanks Jakuje. I just wanted to say that I have saved this QA article. I will update at some point. But since we have a few patches I have been holding off. Right now I am trying to not do too many changes since we will have a major update on Thursday. I want to make sure _why_ something broke after that, if it does.
Any update on this? It is fixed in Q2A for almost 4 years and from time to time, somebody stumbles upon this. If not updating to newer version, backporting this simple patch might make sense.