ONLYOFFICE / onlyoffice-humhub

Plugin for integrating ONLYOFFICE online editors with HumHub
GNU Affero General Public License v3.0
12 stars 9 forks source link

Error 500 after Update #21

Open Fr13dr1ch99 opened 4 years ago

Fr13dr1ch99 commented 4 years ago

After Update to version 5.5.1.76 the space view shows the follow error message.

{
    "url": "/s/<spacename>/space/space/stream",
    "status": 500,
    "response": {
        "name": "Unknown Class",
        "message": "Unable to find 'humhub\\modules\\onlyoffice\\filehandler\\ViewFileHandler' in file: /var/www/localhost/htdocs/protected/modules/onlyoffice/filehandler/ViewFileHandler.php. Namespace missing?",
        "code": 0,
        "type": "yii\\base\\UnknownClassException",
        "file": "/var/www/localhost/htdocs/protected/vendor/yiisoft/yii2/BaseYii.php",
[...]
luke- commented 3 years ago

Has the problem been solved in the meantime?

Eloncase commented 3 years ago

which version of humhub and onlyoffice module are you running? everything seems to be working on 1.6.2 humhub and 2.1.3.2 connector

luke- commented 3 years ago

I also cannot reproduce the error.

nicovitt commented 3 years ago

I get the same error but cannot really tell what the cause might be. I also cannot disable and uninstall modules from the admin view. I think there might be an issue in my database as the update to version 1.5.1 resulted in an error when migrating the db. I kept then going and updated to the latest version of humhub. Will keep you updated when I have something new.

luke- commented 3 years ago

What error message do you get? Are the permissions of the folder /protected/modules set correctly in the file system?

nicovitt commented 3 years ago

Strange thing I did not get any error messages. Thanks to your reply I looked for the permissions and yes ... they were wrong... -.- What a shame. :D Long story short: Could not enable the module either so looked into the database and the module was listed in module_enabled. Deleted it from there, enabled over command line, works now. Don't know where this came from. Perhaps some artefacts from the update and some misconfiguration combined.

Thanks @luke-