I have prepared an Orchard based website locally, using WebMatrix. I then published to my hosting provider.
However the deployed version isn't picking up the styles or scripts, either my theme or for the dashboard, and it's giving me 404 errors.
I guess I have to change the path somewhere to get it to pick up the files, can anyone tell me where? or is there a different solution?
I thought that this would be a setting on the website, but as it turns out it was an IIS setting.
I switched the pipeline mode from Classic to Integrated, and everything worked.
Related
I have been given a Drupal project and I am trying to set it up to run locally.
I'm using XAMPP to host the project.
I had several pitfalls while trying to set it up. Now I've reached a point where I can see a drupal project, although not the one I've been given.
So now I'm asking for help on how I can run the project drupal code instead of some default that is being shown. I've added setting files as required by the installer. But now it's not running the drupal project that I want.
How can I get the project code to run?
How does drupal find the code that is shown?
Displayed
Thanks in advance!
A friend has asked me to do some work on his existing site which was built in Rapidweaver. I'm on Windows, so is there another way I can access and edit his site?
The Rapidweaver project file is meant to be edited only in Rapidweaver, really. As far as I know, the only way around would be to use an HTML editor to modify the pages that are already in the server. However, I would not reccomend you to do it unless you are not going back to Rapidweaver anymore. Because changing the files in the server does not update your local Rapidweaver files. So, you could end up editing something in the server, then getting back to Rapidweaver and upload a "new" version that would not be completely up to date (the previous changes in the server version would be overriden by the older rapidweaver project).
For that kind of work, a CMS (Content Management System) is a more flexible way to work. Nowadays, one of the most common is Wordpress. It will require an inicial setup but after it is working it can be updated from anywhere via web browser, or even from an app in your iPhone. But it is not a Rapidweaver based sollution.
There are a couple CMS related plugins or stacks (Dropkick CMS, Armadillo, Easy CMS, Total CMS...) for Rapidweaver that could also be useful in this context. Once again, first you would need to buy a licence and to setup the website using one of those plugins or stacks. Only then you would be able to edit on the go.
Our production Liferay instance absolutely refuses to deploy my latest theme. Something is preventing it from displaying my latest CSS changes. Unfortunately, there are NO log errors and no Firebug Console errors, so it's been a real headache to diagnose. I just get a really ugly plain page with links and no styles applied.
I have tried everything I can think of to fix this.
Undeploy/redeploy theme
restart the Glassfish container
use Liferay Server Administration page to "Clear content cached across this JVM", "Clear database cache", "Verify Database plugins", etc.
undeploy, restart, redeploy
undeploy, delete leftover files/folders pertaining to the theme in 'applications' folder, restart container, redeploy
clear my browser cache
try a different browser
many more combinations of the above. You get the idea.
Last night I reached the boiling point because my theme deployed and displayed in our test environments without issue, but didn't work in production. The only thing that was different is that I wasn't using
include-and-override=portal-developer.properties
in my portal-ext.properties file.
I took a gamble and added this line to my production portal-ext.properties and restarted the production server. My theme now displays without a problem.
The file portal-developer.properties only appears to contain the following properties:
theme.css.fast.load=false
theme.images.fast.load=false
javascript.fast.load=true
javascript.log.enabled=false
layout.template.cache.enabled=false
browser.launcher.url=
combo.check.timestamp=true
freemarker.engine.cache.storage=soft:1
freemarker.engine.modification.check.interval=0
openoffice.cache.enabled=false
velocity.engine.resource.manager.cache.enabled=false
com.liferay.portal.servlet.filters.cache.CacheFilter=false
com.liferay.portal.servlet.filters.etag.ETagFilter=false
com.liferay.portal.servlet.filters.header.HeaderFilter=false
com.liferay.portal.servlet.filters.themepreview.ThemePreviewFilter=true
So, finally, my question is, am I merely trading a slight performance boost for a massively easier deployment experience?
Or are there more serious concerns to loading this file in a production environment?
Thanks in advance for the input!
Ben
You'll get a really bad performance with that portal-ext.properties. That configuration is only intended to be used in development environments.
If you delete the css/.sass_cache directory on your deployed theme you'll see your css changes and you'll be able to use a different portal-ext.properties on production environment.
http://issues.liferay.com/browse/LPS-26939
Regards
I'm new to MVC3 and have the feeling this may be an obvious problem but nevertheless I can't find a related question on the issue.
I'm developing a web site in MVC3. My production environment has several web sites positioned as follows, eg:
www.companywebsite.com/app1/
www.companywebsite.com/app2/
...to
www.companywebsite.com/mynewapp/
I'm using IIS on Windows server2008 and have created the "mynewapp" folder. But when I deploy my application into this folder all my relative links and files break.
I've converted my scripts and images to T4-MVC references which seems to handle the relative paths but any bog-standard hyperlinks that I have as relative links will not work (and I don't want to convert them to Razor links due to use of images).
All my mapped routes are working fine without change.
Is there a global setting I can use for deployment to the production environment which will tell my project that the base folder is /mynewapp ??
Thanks in advance.
I have an installer I am modifying where we are modifying a web site in IIS. The requirements state that the end user must create the site first in IIS. We read the site information they choose from a dropdown in the installer for their site, and store the information in properties in WiX.
I have a WebSite element under a component, and have the ConfigureIfExists set to yes. A lot of this seems to be working great, it resets the directory of the site to where the website is on the drive.
The problem is that when I check the set up in IIS, the web site is not started, even when I have AutoStart = yes and StartOnInstall = yes. The problem I am seeing is that, since it is an existing web site, it creates a duplicate binding for the site, same port and everything, which is causing the site not to run.
Does anyone know why this is happening, or how to resolve it? I need it to not duplicate the binding so that the web site can be restarted when installation is complete.
I advise you to try this scenario with WiX v3.6 (take the latest available build). There were lots of fixes in IIS7 extension, and it's very likely your problem will just go away.
EDIT: now WiX 3.6 is in official beta. It is quite stable and contains lots of fixes to IIS extension.
I had a similar problem. I was able to work around it with the following method, but be advised, it is kind of a hack.
For my existing website, I match it on SiteId and set whatever configuration properties I want to change with the WebDirProperties attribute. Then, in the iis:WebAddress element, I set the Port number to some unused port (I used 8081). This will add an extra http binding in IIS7 (as you saw in your question). Then, I create a custom action that I run before InstallFinalize. The custom action basically loops through the site Bindings, looks for the one that matches the bogus port that I entered in wix and deletes it. Then the custom action starts the website and everything is good.
This was the only way I could find to get it to work in Wix 3.5. It is not the best method, but it worked for me.