Sorry for my English...
I have a problem with BundleCOnfig...
I added new script bundle:
bundles.Add(new ScriptBundle("~/bundles/js").Include(
"~/assets/js/progress-bar/src/jquery.velocity.min.js",
"~/assets/js/progress-bar/number-pb.js",
"~/assets/js/progress-bar/progress-app.js",
"~/assets/js/preloader.js",
"~/assets/js/bootstrap.js",
"~/assets/js/app.js",
"~/assets/js/load.js",
"~/assets/js/main.js"));
And add this code to _Layout.cshtml:
#Scripts.Render("~/bundles/js")
When I load page at localhost:21612/ no errors occur. Page displayed correctly:
Normal load
But if I load page at localhost:21612/Home/Index I get errors. And in path is added controller names:
Errors
I do not understand what the problem is, because the relative path to the script, why is inserted controller name?
UPDATE: Problem solved. The fact is that in the file main.js, all the way to the other scripts were installed as src="assets/, and should be src="/assets/
The tilde has changed in MVC5 to do clever things with URL rewriting. I don't understand why it's doing this to you but if you're doing any URL rewriting, you can turn off overly clever fixing of on-page URLS, see this answer:
https://stackoverflow.com/a/12105210/7353829
Related
I have created my custom component.
Every thing is working fine.
but when I am appending format=pdf in URL Joomla shows error
"0 - Invalid controller: name='xxxxxxxx', format='pdf'"
If I am adding format=html then its working fine.
I have followed this article for pdf generating.
joomla pdf
Thanks
Have you included your controller.php file in your custom component's XML manifest file? If you don't have it there, then this is most likely the cause of your problem.
Hi I convert the web app to web site. I follow this link to do it. However I have an error for a few pages which are .ascx and the Global.asax. The error is “Context is not a member of …”. I also exclude the .vbroj file.
I searched the web for fixing the above error and found that link http://forums.asp.net/t/1148374.aspx?Context+is+not+a+member+of+Page+name+
. Although I did what it said, but the error didn’t go away. Would someone tell me what I can solve the issue.
Summary what I did:
1. Delete the .desginer file
2. Changed Codebehind to CodeFile
3. Change the path of the code file with full path within the root directory.
For example:
Form CodeFile=" Footer.ascx.vb" Inherits="Testing.Footer"
To CodeFile="~/Templates/Footer.ascx.vb" Inherits="Testing.Footer"
I solved the problem by deleted the namespace of inherits and change the full path of CodeFile. Also change the full path of #Reference
I recently took on a project built on XUL (standalone, using xulrunner) - However I can't get it to properly run.
I'm getting this error when I attempt to start it using the command line (xulrunner.exe ../application.ini -jsconsole):
No chrome package registered for chrome://case_scenario_builder/content/case_scenario_builder.xul
The chrome.manifest file looks like this:
content case_scenario_builder file:chrome/case_scenario_builder/content/ contentaccessible=yes
content jslib jar:chrome/jslib.jar!/
skin case_scenario_builder skin file:chrome/case_scenario_builder/skin/
locale case_scenario_builder en-US chrome/case_scenario_builder/locale/en-US/
Any ideas on where I could start debugging?
I figured it out!
In case anyone else runs into this as well:
It was due to the caching system in place by default and the use of .jar containers instead of folders.
The XUL environment had cached both JS and XUL files - and even after disabling those, I had to extract everything that was in the .jar file to the content folder and update the chrome.manifest file.
Thanks for your suggestions on debugging! - they helped the process.
I guess your manifest just isn't getting loaded. To test that I'd introduce an intentional syntax error and check the error console. E.g. if you put
asdfasd
on its own line, you should get a Warning: Ignoring unrecognized chrome manifest directive 'asdfasd'. in the Error console.
(Note to other experts: initially I wanted to suggest dropping 'file:' prefix and avoiding underscores in the package name, but I tested it on a Firefox nightly, and it works fine.)
Your chrome package clearly didn't get registered. From what I can tell, the reason is the bogus file: prefix, you should drop it when specifying relative paths:
content case_scenario_builder chrome/case_scenario_builder/content/ contentaccessible=yes
Btw, I suspect that you copied contentaccessible=yes from somewhere - you should drop it as well unless you know what it does.
I am having issues with Heroku and Haml, I am able to run my app on localhost no problems, all test pass to, however when I go to run it on Heroku I get the following error:
We're sorry, but something went wrong.
We've been notified about this issue and we'll take a look at it shortly.
I read another post on Stackoeverflow that basically said to add a .gems file and add:
haml --version '>= 2.2.0'
I did that and I'm still having the same problem, so I'm wondering what I am doing wrong.
Update: I fixed that problem had to do with cache - and Heroku being read-only however now the theme I've selected via web-app does not load up on the Heroku page it shows up on local host however correctly. I looked at the log file for Heroku and it doesn't show any errors, so is it another permission issue?
Here is the log file - https://gist.github.com/1173667
Thanks,
Looks like your stylesheets are not included as part of the layout.
Assuming your stylesheet is available as public/stylesheets/styles.css, try adding the following line inside the head tag in application.html.haml
= stylesheet_link_tag 'styles.css'
That should resolve the theming issue. If not, post the code in application.html.haml
UPDATE:
From the logs, looks like you have two layouts: layouts/sign and layout/application. If they are there for a reason, you need to address that.
Else, change your home controller to render the new layout:
class HomeController < ApplicationController
layout "sign"
end
I have a rails application I would like to use for multiple sites, each with different designs.
I would like to change the rails installation /public directory to something else (dynamically eventually). However, I have run into a problem (bug?) changing directories...
In my application.rb file I change the paths.public path to something other than "public" (let's say "site_one"). Here is the code:
puts paths.public.paths
paths.public = "site_one"
puts paths.public.paths
The two "puts" commands are for debugging. Now run "rails s" and you will see:
/home/macklin/app/public
/home/macklin/app/site_one
This verifies the path is changed correctly. However, shortly afterward, rails throws the following error (let me know if you need the full trace):
Exiting
/usr/lib/ruby/gems/1.8/gems/railties-3.0.3/lib/rails/paths.rb:16:in `method_missing': undefined method `javascripts' for #<Rails::Paths::Path:0x7f422bd76f58> (NoMethodError) from /usr/lib/ruby/gems/1.8/gems/actionpack-3.0.3/lib/action_controller/railtie.rb:47
My guess is it cannot find the javascripts directory even though it is clearly sitting in the "site_one" folder.
Does anyone know why I am getting this?
I know this question is pretty old, but I think I found an answer for this in Rails 4.2.
You just simply have to put this line in your config/application.rb:
middleware.use ::ActionDispatch::Static, "#{Rails.root}/another_public_folder_name", index: 'index', headers: config.static_cache_control
This makes all files in /another_public_folder_name to be served by Rails.
This is the way Rails use to setup the standard /public folder. I found it checking the sources:
https://github.com/rails/rails/blob/52ce6ece8c8f74064bb64e0a0b1ddd83092718e1/railties/lib/rails/application/default_middleware_stack.rb#L24
Duh. Just add 2 more rules for stylesheets and javascripts (I guess they get wiped when you change the parent path)
paths.public.stylesheets = "site_one/stylesheets"
paths.public.javascripts = "site_one/javascripts"