Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Last release 6.8 SourceGuardian mandatory #1216

Open
lonesomewalker opened this issue Jan 15, 2025 · 6 comments
Open

Last release 6.8 SourceGuardian mandatory #1216

lonesomewalker opened this issue Jan 15, 2025 · 6 comments
Assignees

Comments

@lonesomewalker
Copy link

Uncaught exception: Uncaught ErrorException: SourceGuardian Incompatible loader version. This protected script was encoded with a newer version of SourceGuardian. Please download and install the <A HREF="https://www.sourceguardian.com/loaders/">latest loaders</A>. Error code [19] in /var/www/office/go/modules/business/privacy/model/Settings.php:2

I thought this is optional?

@derjoachim
Copy link
Contributor

Just double checking: do you happen to have the privacy options module installed and possibly enabled?

@mschering
Copy link
Member

I've tried to install afresh copy of Group-Office and this works without any issues.

The error complains about your installed loader being too old. I guess you just have to install the latest one.

You could do so by running this command:

curl -s https://raw.githubusercontent.com/Intermesh/groupoffice/master/scripts/sg_install.sh | bash

@lonesomewalker
Copy link
Author

I know how to update :-)
But it is NOT okay, since this is optional.
What to do if somebody can't upgrade?
Since SourceGuardian is only needed for the encrypted stuff, is there no better solution than to fail?

@mschering
Copy link
Member

It fails because it’s too old. If you don’t need it just uninstall it.

@lonesomewalker
Copy link
Author

Hi :-)
It is not that I would do that, unfortunately under some conditions you can not do so, because you don't have control over the server... therefore i opened this issue.
I can run my stuff pretty good on our own servers, but as you can see we had a customer who wanted to try the community edition and we failed to install because the server owner seems to not care about updates...
So, since the SourceGuardian stuff only affects the pro stuff, it might should be done as a check like the typical GO check...?

Or is this a limitation from SourceGuardian?

@mschering
Copy link
Member

Hmm, I'm not sure. If you don't install any pro module it should never require sourceguardian. It checks if it's available first but maybe it fails when there's an old version installed. Maybe I can check the version number.

mschering added a commit that referenced this issue Feb 3, 2025
@mschering mschering self-assigned this Feb 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants