-
Notifications
You must be signed in to change notification settings - Fork 817
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
fix: Nautilus integration conflicts with ownCloud #6418
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mgallien Did you see my comment? |
52a2c19
to
f9fd183
Compare
Hello @mgallien, |
-> fixes conflicts with the ownCloud extension Signed-off-by: mammo0 <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sorry for the big delay
approved and we will take care of merging and release
thanks for the contribution
Hello,
today I stumbled across issue #3803.
After some testing I found out that the culprit are the two Python classes
MenuExtension_ownCloud
andSyncStateExtension_ownCloud
. They are defined by the Nextcloud and the ownCloud integration.If the names are changed to something else, like
MenuExtension_Nextcloud
, then both integrations are working again.Since you are using the code from the ownCloud integration (https://github.com/owncloud/client-desktop-shell-integration-nautilus), the names of the classes should normally be changed by the
setappname.sh
script. But this name is branded to "Nextcloud" in this repository. This means the "ownCloud" strings in the integration (syncstate.py
) won't get replaced. So I changed the branding back to "ownCloud" and now the strings are correctly replaced during the Cmake build process.