Content
You are here:
jquery.atwho not found
Added by Milton Stanley over 10 years ago
I’m running a fresh install from origin/dev. When running in development, I get an Action Controller Sass:SyntaxError of
File to import not found or unreadable: css/jquery.atwho
on load.
It’s referenced from app/assets/stylesheets/external.css.sass, which has an @import for that file.
I’ve bundle installed, and done everything EXCEPT precompile assets (because there’s no need for that in development, right?)
I can’t find any jquery gems in the Gemfiles. Is this a bug, or am I fundamentally misunderstanding jquery, rails and Sass?
There is a forum post a while back about this, but it also seems to indicate that jquery was at one time gem installed.
Thanks,
Replies (10)
I have the same problem while updating beta version of 3.0
Any hints ?
No luck adding to Gemfile, but it looks like it’s referenced in bower.json. Are there now new requirements not mentioned in the installation instructions?
EDIT: Latest install included in the repo (but not on the wiki here), in doc/INSTALL.md, adds Node.js, npm/bower prerequisites.
EDIT #2 (sorry, I should just take the time to research fully before replying): BUT the release and stable branches refer back to the wiki here for installation [[Installation_OpenProject_3_0]] which makes no reference to those prerequisites. Is this an oversight?
That is to say, release and stable seem to require those extras
jquery, node.js, bowerbut the install instructions don’t include them.How can i correct it? I don’t know ruby,gems and rails very good. It is important for me because i must make presentation OpenProject to my team and boss for few days. It isn’t possible without right installation.
Ralf: Here’s what to do (worked for me). Issue seems to be not following install directions closely (I admit it!) - I had issues with the official installation instructions.
Piotr: it’s pretty easy as long as you follow the directions. If you do get lost, feel free to comment here on the forum.
Link: [[https://www.openproject.org/projects/openproject/wiki/Installation_OpenProject_3_0]]
The VERY FIRST STEP will give you links to your specific flavor of *nix. If you follow them, it will work. I would recommend going to one of the links, rather than following the actual page.
I have a good install running now, plugins included. My only issue now is that Passenger can’t find fonts, so I’m just using the Rails command line:
RAILS_ENV="production" rails start
Hi Milton,
thanks for the hints. My Setup is on openSuse/MySQL and beta worked perfect for me.
But allthough I tested the other installation instructions (Debian etc.), no success.
Actually I have no time to solve such time consuming installation issues, because we are evaluating OpenProject for our purposes (we aim tight intgegration of eclipse to OpenProject). I have thought, that a simple update to stable release would be as easy as making a coffee (;-)
I’m looking forward to changes of installation docs.
Regards
Ralf
On my Debian 7.4 (64bit) installation was failed, too. I try five times, dot by dot, exactly as instruction says.
Hello everyone,
please excuse the late reply! Regarding the problems you seem to have: Bower (a package manager for JavaScript dependencies) was just added to the
dev
branch. If you like to run thedev
(which we don’t recommend for production because a stable is available now) please follow the instructions in the installation manual.The bower dependency will be mentioned in the HOWTOs as soon as bower becomes part of the stable branch.
I hope these hints help you to continue?
Kind regards,
Hagen
Actually our installation guides were misleading (I fixed them now).
They made you use our development branch, which can break from time to time (but always uses the latest features).
The downloading openproject step is now:
I’d recommend to use the stable branch if you want a production system.
However, if you want to test the latest (and greatest) new features of OpenProject, you may use our development branch with Hagens’ instructions.
yours,
tessi
I’ve just validated my old opinion about Bower on this year Brazilian RubyConf, that have happened last week, which is: Don’t use it with Rails. Simple as that. There are many philosophical reasons not to do so, and the most important one is that you now have 2 different package control system that don’t talk to each other.
A most simplistic solution that works “most of time” (on the edge cases we can just make our own RubyGem or use the existing ones), is to use Rails Assets project.
If you don’t know it yet please take a look: https://rails-assets.org/
It solves the problem by converting bower packages to rubygems and exposing a “rubygems source” address.
You can save everybody from the burden of installing node, then stalling bower, than updating the assets etc…
I know this is not unanimous yet, but I believe that this is the right direction.
(I’ve made this statement with the best of intentions, not trying to bash anyone).