Closed BdM5959 closed 1 year ago
I have one question:
I will try to have a look at it later but no promise, I'm quite busy :(
Hi ildyria, of course I updated gulfile.js, now 'npm run compile' command runs with gulp release 4.0.2 I copied it into the first post, because I'm newbie here, what means PR ? BdM
PR usually refers to 2 things:
I guess this issue isn't relevant anymore and can be closed? @qwerty287 created and merged a lot of PR recently which updated and cleaned up the build system of the frontend (see https://github.com/LycheeOrg/Lychee-front/pull/292, https://github.com/LycheeOrg/Lychee-front/pull/337 and https://github.com/LycheeOrg/Lychee-front/pull/340). Now, the frontend uses Gulp 4.0.0, see
Hence, I assume the whole point of this issue is obsolete.
Moreover, I don't really understand why this has been an issue at all. If a user manipulates the build scripts (even though if this happens in good faith) and then things break, this can hardly be called an issue of the frontend.
Detailed description of the problem
Hi, when I tried to move a pic to a created album from searching result I got this error into the console. F() called from contextMenu.move looks good, the F() photo.setAlbum seems to be the error source. Issue occurs only from searching result otherwise f() runs well.
I compiled src on my desktop using
Please read after the Gulp compile report
I updated the gulpfile.js for running with gulp@4 as
Steps to reproduce the issue
Do a search from unsorted album, when related photos came up, select one for moving.
Output of the diagnostics (Settings => Diagnostics)
Browser and system
Your comments will be appreciated Thanks for your support BR