Possible Issues

This document aims to capture a concise and confirmed version of the known GitHub issues as well as other issues that can occur.

As with all projects there are some possible issues that you may encounter while using it. Some may depend directly on this project, while others may exist due to components it relies on. Please check this document and the GitHub issues if you believe there is an issue within the project or being affected by a dependency. If you can add to the existing issue or one does not exist, please do not hesitate to create one.

Known Issues/User Constraints

• Must use unique MarkLogic ports per app

• Cause: Port Reuse - please check [README.mdown](https://github.com/marklogic/slush-marklogic-node/blob/master/README.mdown) on how to change the ports locally

• Detection:

  • ml local bootstrap failure
  • Error: listen EADDRINUSE
  • The exact same content found in different applications

• Effect: Unable to run the application or data may not be what's expected

• Solution: Check the README.mdown on how to alter your ports locally

• Loading docs via MarkLogic Content Pump (MLCP) requires Roxy configuration & MLCP install

  • Cause: mlcp-home doesn't exist in deploy/local.properties. MLCP may not exist
  • Detection:
    • ERROR: MLCP not found or mis-configured...
    • Unable to use MLCP
    • Unable to use MLCP from Roxy
  • Effect: May be difficult to insert sample set or large amounts of data into MarkLogic
  • Solution:
    1. Ensure MLCP has been installed. Check README.mdown for more about MLCP
    2. Add mlcp-home to deploy/local.properties. Check README.mdown for more about Roxy

• BrowserSync Install Issues on Windows

  • Cause: BrowserSync has dependencies in Windows
  • Detection:
    • npm install errors during initial slush generation
    • npm install browser-sync throws errors
    • gulp serve-local has errors regarding BrowserSync
    • Editing app resources does not modify them after gulp serve-local has started
  • Effects:
    • npm install issues
    • unable to properly use the app locally
  • Solutions:
    • http://www.browsersync.io/docs/#windows-users suggested
    • Possibly install this https://support.microsoft.com/en-us/kb/2977003 or installing Python 2.7+, then run npm install browser-sync

Known Issues (v0.2.0) (List)

• [#207] NPM/Bower Component Issues After Initial Slush Generation

  • Cause: Internet connectivity issues during npm install and bower install during initial slush generation
  • Detection:
    • npm ERR! during initial slush generation
    • Various JavaScript module missing errors on node or browser console during app running after initial slush generation
  • Effect: The app or parts of it may not successfully run correctly after initial slush generation
  • Solution:
    1. Delete the bower_components and/or node_modules folder(s) within your project (It will not hurt anything to delete both, everything will come back assuming you have an internet connection)
    2. Rerun npm install followed by bower install. Watch for errors in either, warnings are generally fine.

• [#211] Port In Use Error When Running Multiple Instances of Slush Generated Sites (The slush template supports running only one browser-sync demo out of the box. For running multiple ones, either use --nosync or change the browser-sync port as follows.)

  • Cause: Browser Sync have bug dealing with UI port selection (link)
  • Detection: Error: listen EADDRINUSE - when attempting to run gulp serve-local multiple times
  • Effect: Unable to run another instance of a different generated application
  • Solutions
    • Recommended: Change the BrowserSync port from 3000 to 3045 in your generated gulpfile.js. Any open port will work.
    • Recommended: Use the --nosync option at the command-line.
    • NOT Recommended: Turn off BrowserSync by adding ui:false, to ~line 593 of one of your generated gulpfile.js.