Code Monkey home page Code Monkey logo

Comments (9)

feinom avatar feinom commented on May 17, 2024

The same is true when trying to rename an existing file. It works on your own personal files, but fails when trying to rename a shared file/folder.

from core.

Jasperado avatar Jasperado commented on May 17, 2024

The same problem occurs when using the sync client (as described in #80).

This is an absolute blocker for our environment. Is it possible to get any estimation on when this issue might be addressed?

from core.

MaximilianA avatar MaximilianA commented on May 17, 2024

+1 - this completely blocks the usage for us. So a ETA for the fix would be highly appreciated!

from core.

directhex avatar directhex commented on May 17, 2024

I can confirm that 3d13c9d appears to fix the problem

from core.

MTGap avatar MTGap commented on May 17, 2024

Cherry picking the commit into a new branch doesn't seem to work... Is there an easy way to do this backporting. This QA process requires too much time on my side if I need to do two different branches and pull requests. Any tips?

from core.

Jasperado avatar Jasperado commented on May 17, 2024

Manually adjusting the files.php in our production environment (clone of branch stable45) fixed it.It also fixed issue #80.
Thx btw.

from core.

anamba avatar anamba commented on May 17, 2024

Same result as Jasperado, manually adding the $info = array() and the if block fixes these two issues for me.

With that resolved, I've now run into a different issue, but it appears to be unrelated (an OmniOutliner .oo3 file/bundle refuses to sync, although other bundles, and even other .oo3 files are fine).

from core.

anamba avatar anamba commented on May 17, 2024

Never mind... it probably was related, as it was among the files I was trying to sync before resolving this issue. If I simply rename the file it syncs properly.

from core.

DeepDiver1975 avatar DeepDiver1975 commented on May 17, 2024

@MTGap It's not the CodeReview process itself which requires too much time but maintaining multiple releases is time consuming - but most of us will agree with me that that's a pure fact.
Sometimes it requires totally different patches to fix the same issue in different releases. But that's the way it is.
Yes - it's time consuming!

Enough on general talking:
I think you need to branch stable45, apply the patch manually (copy'n'paste) and push the merge request.

Take care!

from core.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.