[Dspace-tech] Javascript disabled on DSpace?

28 views
Skip to first unread message

Borda, Susan

unread,
Aug 26, 2015, 2:22:18 PM8/26/15
to dspac...@lists.sourceforge.net
Hi-
I just installed Space 5.1 with Mirage 2 on a Centos 6.6 VirtualBox. When I go to my new DSpace page (localhost:8080/xmlui) I’m getting a message that says “Javascript has been disabled for your browser. Some features of this site may not work without it.”

Javascript is working on other sites just not this one.

Where do I enable javascript for Dspace, is it in one of the Mirage 2 or xmlui files?

Thanks,
susan

Andrea Schweer

unread,
Aug 26, 2015, 2:22:19 PM8/26/15
to Borda, Susan, dspac...@lists.sourceforge.net
Hi Susan,
This is not a DSpace setting, it's something in your browser. It's a little bit odd for this to happen in what is presumably pretty much a fresh Centos install. Can you try with a different browser? Your VM has access to the Internet, yes?

Did the maven step of the build process complain about anything? Mirage 2 will sometimes tell you that the build was successful even when it wasn't, so you'll need to keep an eye on the output while maven is running.

If none of these things help, could you try to switch on the developer tools for your browser, then force-reload the page to see whether you get any error messages to pinpoint the problem? In Firefox, you'll want to open the Web Console (try Ctrl-Shift-K). In Chrome, it appears to be called JavaScript console (try Ctrl-Shift-J).

cheers,
Andrea

-- 
Dr Andrea Schweer
IRR Technical Specialist, ITS Information Systems
The University of Waikato, Hamilton, New Zealand

Andrea Schweer

unread,
Aug 26, 2015, 2:22:31 PM8/26/15
to Borda, Susan, dspace-tech
Hi Susan,

(I'll add dspace-tech back in -- perhaps others with the same problem can benefit from the discussion)

With the same message coming up in Chrome, to me it sounds like you've probably run into one of the Mirage 2 build problems. Have a look at the official DSpace documentation for a few hints: https://wiki.duraspace.org/display/DSDOC5x/Mirage+2+Configuration+and+Customization#Mirage2ConfigurationandCustomization-ThebuildprocessandenablingMirage2

cheers,
Andrea

On 01/04/15 03:53, Borda, Susan wrote:
Hi Andrea-
Thanks for the info, I knew it was a long shot that that the setting was in Dspace. I get the same message in Chrome. I will re-run Maven to see if I can spot the error.

Thanks again,
susan

Borda, Susan

unread,
Aug 26, 2015, 2:23:00 PM8/26/15
to Andrea Schweer, dspace-tech
I’m having this same issue:
-susan

Andrea Schweer

unread,
Aug 26, 2015, 2:23:03 PM8/26/15
to Borda, Susan, dspace-tech
Hi Susan,

what maven version are you using (mvn --version)? I just discovered that Mirage 2 doesn't appear to work with Maven 3.3.1; Maven 3.2.5 is fine. https://jira.duraspace.org/browse/DS-2533

cheers,
Andrea


On 02/04/15 12:28, Borda, Susan wrote:
I’m having this same issue:
-susan


Hilton Gibson

unread,
Aug 26, 2015, 2:23:09 PM8/26/15
to Andrea Schweer, dspace-tech
Hi All

Just tested on a clean Ubuntu 14.04 LTS desktop and found the following:

Regards

hg

Hilton Gibson
Ubuntu Linux Systems Administrator
JS Gericke Library
Room 1025C
Stellenbosch University
Private Bag X5036
Stellenbosch
7599
South Africa


------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
DSpace-tech mailing list
DSpac...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette

Borda, Susan

unread,
Aug 26, 2015, 2:23:17 PM8/26/15
to Andrea Schweer, dspace-tech
Yes I am indeed using Maven 3.3.1. I’ll remove it and install 3.2.5 and try it again…

Thanks!

From: Andrea Schweer <sch...@waikato.ac.nz>
Date: Wednesday, April 1, 2015 at 9:58 PM
To: Susan Borda <susan...@montana.edu>, dspace-tech <DSpac...@lists.sourceforge.net>
Subject: Re: [Dspace-tech] Javascript disabled on DSpace?

Keith Jones

unread,
Aug 26, 2015, 2:23:18 PM8/26/15
to Borda, Susan, dspace-tech
I just finish trying it with maven 3.2.5, previously I had 3.2.3 but I'm still getting the same compile error. 

[INFO] /export/home/putnam/dspace/SOFTWARE/dspace-5.1-src-release/dspace/modules/xmlui-mirage2/target/themes/Mirage2/
node/with_new_path.sh: PATH=$(dirname $(readlink -f /export/home/putnam/dspace/SOFTWARE/dspace-5.1-src-release/dspace
/modules/xmlui-mirage2/target/themes/Mirage2/node/with_new_path.sh)):.:/usr/local/bin:/usr/local/sbin:/usr/local/samb
a/bin:/usr/local/ant/bin:/usr/local/maven/bin:/usr/sfw/bin:/usr/sbin:/usr/bin:/etc:/usr/etc:/usr/openwin/bin:/usr/ccs
/bin:/usr/local/local:/opt/csw/bin:/export/home/putnam/mark/bin:/export/home/putnam/dspace/lib/postgresql-9.1-901-1.j
dbc4.jar:/export/home/putnam/dspace/.nvm/nvm.sh: is not an identifier
[ERROR] MojoFailureException:
org.apache.maven.plugin.MojoFailureException: Failed to run task
        at com.github.eirslett.maven.plugins.frontend.mojo.NpmMojo.execute(NpmMojo.java:45)
        at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
        at com.soebes.maven.plugins.iterator.ExecutorMojo.executeMojo(ExecutorMojo.java:302)
        at com.soebes.maven.plugins.iterator.ExecutorMojo.execute(ExecutorMojo.java:235)
        at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
        at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
        at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
        at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuild
er.java:51)
        at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
        at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
        at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:160)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:601)
        at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
        at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
        at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
        at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: com.github.eirslett.maven.plugins.frontend.lib.TaskRunnerException: 'npm install --color=false' failed. (e
rror code 1)
        at com.github.eirslett.maven.plugins.frontend.lib.NodeTaskExecutor.execute(NodeTaskExecutor.java:38)
        at com.github.eirslett.maven.plugins.frontend.mojo.NpmMojo.execute(NpmMojo.java:43)
        ... 24 more
[INFO] ------ (Mirage2) com.github.eirslett:frontend-maven-plugin:0.0.16:grunt
[INFO] Running 'grunt classic_mirage_color_scheme no-compass-prod --no-color' in /export/home/putnam/dspace/SOFTWARE/
dspace-5.1-src-release/dspace/modules/xmlui-mirage2/target/themes/Mirage2
[INFO] /export/home/putnam/dspace/SOFTWARE/dspace-5.1-src-release/dspace/modules/xmlui-mirage2/target/themes/Mirage2/
node/with_new_path.sh: PATH=$(dirname $(readlink -f /export/home/putnam/dspace/SOFTWARE/dspace-5.1-src-release/dspace
/modules/xmlui-mirage2/target/themes/Mirage2/node/with_new_path.sh)):.:/usr/local/bin:/usr/local/sbin:/usr/local/samb
a/bin:/usr/local/ant/bin:/usr/local/maven/bin:/usr/sfw/bin:/usr/sbin:/usr/bin:/etc:/usr/etc:/usr/openwin/bin:/usr/ccs
/bin:/usr/local/local:/opt/csw/bin:/export/home/putnam/mark/bin:/export/home/putnam/dspace/lib/postgresql-9.1-901-1.j
dbc4.jar:/export/home/putnam/dspace/.nvm/nvm.sh: is not an identifier
[ERROR] MojoFailureException:
org.apache.maven.plugin.MojoFailureException: Failed to run task
        at com.github.eirslett.maven.plugins.frontend.mojo.GruntMojo.execute(GruntMojo.java:36)
        at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
        at com.soebes.maven.plugins.iterator.ExecutorMojo.executeMojo(ExecutorMojo.java:302)
        at com.soebes.maven.plugins.iterator.ExecutorMojo.execute(ExecutorMojo.java:235)
        at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
        at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
        at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
        at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuild
er.java:51)
        at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
        at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
        at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:160)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:601)
        at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
        at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
        at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
        at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: com.github.eirslett.maven.plugins.frontend.lib.TaskRunnerException: 'grunt classic_mirage_color_scheme no-
compass-prod --no-color' failed. (error code 1)
        at com.github.eirslett.maven.plugins.frontend.lib.NodeTaskExecutor.execute(NodeTaskExecutor.java:38)
        at com.github.eirslett.maven.plugins.frontend.mojo.GruntMojo.execute(GruntMojo.java:34)
        ... 24 more
[INFO] ------ (Mirage2) de.saumya.mojo:gem-maven-plugin:1.0.6:exec
[WARNING] Compass can't find any Sass files to compile.
[WARNING] Is your compass configuration correct?.
[WARNING] If you're trying to start a new project, you have left off the directory argument.
[WARNING] Run "compass -h" to get help.
[ERROR] PluginManagerException:
org.apache.maven.plugin.PluginExecutionException: Execution null of goal de.saumya.mojo:gem-maven-plugin:1.0.6:exec f
ailed: Java returned: 1
        at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:143)
        at com.soebes.maven.plugins.iterator.ExecutorMojo.executeMojo(ExecutorMojo.java:302)
        at com.soebes.maven.plugins.iterator.ExecutorMojo.execute(ExecutorMojo.java:235)
        at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
        at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
        at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
        at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuild
er.java:51)
        at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
        at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
        at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:160)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:601)
        at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
        at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
        at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
        at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: Java returned: 1
        at org.apache.tools.ant.taskdefs.Java.execute(Java.java:87)
        at de.saumya.mojo.ruby.script.AntLauncher.doExecute(AntLauncher.java:107)
        at de.saumya.mojo.ruby.script.AntLauncher.executeIn(AntLauncher.java:141)
        at de.saumya.mojo.ruby.script.Script.executeIn(Script.java:108)
        at de.saumya.mojo.gem.ExecMojo.executeWithGems(ExecMojo.java:106)
        at de.saumya.mojo.gem.AbstractGemMojo.executeJRuby(AbstractGemMojo.java:469)
        at de.saumya.mojo.jruby.AbstractJRubyMojo.execute(AbstractJRubyMojo.java:298)
        at de.saumya.mojo.gem.AbstractGemMojo.execute(AbstractGemMojo.java:222)
        at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
        ... 23 more

The compile will complete and report build success but the Mirage2 will not display properly.

Borda, Susan

unread,
Aug 26, 2015, 2:23:19 PM8/26/15
to Andrea Schweer, dspace-tech
Just added a paste of my output.log to: https://jira.duraspace.org/browse/DS-2368

Thanks,
susan
From: Andrea Schweer <sch...@waikato.ac.nz>
Date: Wednesday, April 1, 2015 at 9:58 PM

To: Susan Borda <susan...@montana.edu>, dspace-tech <DSpac...@lists.sourceforge.net>
Subject: Re: [Dspace-tech] Javascript disabled on DSpace?

Borda, Susan

unread,
Aug 26, 2015, 2:24:32 PM8/26/15
to Andrea Schweer, dspace-tech
Hi-
I finally got this working this morning thanks to Alex in the Jira post. It is odd that the Mirage 2 build doesn’t seem to work unless you download the dependencies. 

Thanks,
susan
Reply all
Reply to author
Forward
0 new messages