I use the Mac app more, and coming from Spotify (I tried Apple Music once, but the UI was so bad it made me go back), I like how a number of other things can be accomplished with other apps. Music.app is required for Marvis to function.ĭoppler, meanwhile, is its own app, and expects you to bring your own files (it supports importing from Apple Music, but I don't know how far it goes, given I've not used that feature), which reflects in its design, since it's more minimal on the features it supports. The project page instructions need updating though.I've never used Marvis Pro, but just from looking at it on the App Store, it seems more to be a companion to Apple Music: It can be a pain in the B*** wrangling where exactly to locate what files for modules that depend on libraries, so I hope this rock solidly clarifies it. So, for example you should now have web/libraries/dropzone/dist/dropzone.js and web/libraries/dropzone/dist/min/ So go into web and find the libraries folder and put the unzipped folder renamed to dropzonejs in there. Where, as a reference point / orientation as to what "web" - it's the folder when index.php is located - the initial Drupal bootstrap code that is loaded when your site is visited. In fact all I did was rename that unzipped folder as dropzonejs and just copy it into web/libraries When you unzip that zip, you'll see dist folder in that unzip folder - you can then copy this into a folder called dropjonejs in the libraries folder. Instead the solution to get the library with the correct name and path position is to download the zip from which can be found on Because giving gives the user of this module insufficient clue as to how to get dropzone/dist/dropzone.js into your Drupal site's source tree - that folder path doesn't exist in the github source, or at least it is not obvious. I should add that the link given on the project page, Download DropzoneJS - is not the link you want to use. Remaining tasksįor assignee of this issue to determine. via a local composer or the js stored with the module as its own local libraryĪnd then update all documentation as required. to actually show the full path and filename in the message.Ī) users of this module need to manually install the dropzone.js () libraryī) this is managed automatically by the module, i.e. Where web is the folder directory that core, modules, sites etc also reside in at same level as described above.Ĭonfirming this is correct, because when I now run drush updb with this, I don't get the error.Ģ) make error message in web/modules/contrib/dropzonejs/dropzonejs.install at lines 43-50 for version 2.3 more user friendly, i.e. The correct path is: web/libraries/dropzone/dist/min/ Proposed resolutionġ) Correct the /project/dropzonejs instructions to use this path, as mentioned in modules/contrib/dropzonejs/dropzonejs.install at line 21 and 24 (for version 2.3) īut on the basis that the /project/dropzonejs page hasn't been updated yet, I'm assuming the outcome of raising these issues is still ongoing or hasn't addressed that, so I wanted to raise this issue. I'm also aware of what appear to be related or similar issues, having done a quick search. That error refers to a different file name - which is not the same name as dropzone.js on the /project/dropzone project page. Where libraries is in web folder, on the same level as core. I've done as above: my file and path is: web/libraries/dropzone/dist/dropzone.js You need the full library which is easily available from the Github repo (the full path to the required js file should be: /libraries/dropzone/dist/dropzone.js). The instructions are incorrect - on /project/dropzonejs they say:ĭownload DropzoneJS library and place it in the libraries folder (/libraries).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |