Re: Fatal error when clicking on member names
Reply #1 –
I'm trying to reproduce this error on a clean install of 1.0.3 and have not been able to.
I see you have SimplePortal installed and are using the Silence theme, do you have any other addons?
Re: Fatal error when clicking on member names
Reply #2 –
I have bridged it to Coppermine and have fancy box and ultimate menu.
Other than that I only have those that came with the board, where Integration Hooks Management, Karma and Paid Subscriptions is made inactive.
Btw, the virsion is 1.0.3
Re: Fatal error when clicking on member names
Reply #3 –
I totally forgot about that Coppermine bridge code I put together, did you use the code from this site?
Anyway thanks for the extra details, I'll see if I can set up a duplicate site and see if I can reproduce the error, since its triggering in the menu subs, I'm suspicions of one of the addons.
Re: Fatal error when clicking on member names
Reply #4 –
Sorry for the offtopic, but coppermine gallery can be bridged with elkarte? Is there a guide? I'd like to try it
Re: Fatal error when clicking on member names
Reply #7 –
I seems to have discovered what does it.
I have made a custom member group and it is members in that group that get the message.
When I removed my second account from that group, the error disappeared.
Re: Fatal error when clicking on member names
Reply #8 –
I have custom groups too and they work. I did not have this error.
Re: Fatal error when clicking on member names
Reply #9 –
Nefea could you post a screenshot of the details of that member group? Including permissions?
It may be some particular combination of things leading to a missing included file...
Re: Fatal error when clicking on member names
Reply #10 –
I swapped my special group member back to normal member and hadn't had much time to do anything else, until today.
Today I went into the setting of the special group (officers) to recheck the settings and the setting were the same as default members.
I then swapped my test account from default member back to officer group and it seems to work.
I have no idea what happened that caused to show that error, but it seems to be gone now.