I just downloaded the latest source codes of orchard. I run the solution using vs 2012. I am getting this URL in my browser.
http://localhost:30321/OrchardLocal/
Is there a way I can remove "OrchardLocal" from the URL. when I push the app to the production server. I dont want to see http://test.com/OrchardLocal/
Right click Orchard.Web and select properties then go to Web. Should be able to edit it there. However when pushing to server you shouldn't see OrchardLocal... I think ^_^
Related
I am new to contentful. I have set up a content type in the content model of the example project as Blogpost. As a second step, I added the content entry of type Blogpost. I noticed that there was no preview configured in the web app. I looked into the guide in order to understand how to set up the preview URL and I am quite stuck at it. Please find in the image below, how i setup my web preview URL,
After configuring, when I go back to the entry, and try to preview it, it gives the following error
Can someone please help, what am i doing wrong here.
Thanks,
Bee
I'm pretty new to web developing and very new to VS code. I'm trying to use live-server to be able to get the html in the browser to update without having to refresh the browser. I can't get it to work and I have been googling and trying stuff out for 2 days. Can somebody help me while I still have some hairs left on my head?
Thank you!
/Joel
It's necessary to firsly save the file in which you are working(htmlfile).
In my case i go to file and select autosave. it starts to work as wish.
If I have a website that runs in online, how do i update my website? I do not want any client to see the progress. Only the output. Using c panel to edit my website.
Make a note on your website saying website is down for upgrading/maintenance. Take it off internet. Work on your code duly, update and host it back.
Configure the. htaccess to display maintenance mode then change to normal mode after making the changes
I'm currently developing a module in DotNetNuke 8.0.3.
I have a weird problem. I'm pretty sure I was able to make changes on my ascx and pressed F5 to see the changes on my browser.
Now I have to rebuild everytime.
I have no clue how to resolve the problem.
I think this is IIS problem (something about cache) but I'm not sure.
The files in the desktopmodule update when I save them in visual studio.
Edit
I didn't find a fix. I tried several things about caching in IIS or messing up with web.config but it didn't do anything.
Sometimes I can update my page directly and it looks like it happens when IIS change my module into an application
Login as Host
Navigate Host -> Host Settings
At the bottom, under Advanced settings, there is a setting titled Performance Settings
Expand Performance Settings
Change Cache Setting to None
Click Update
Click Clear Cache
I have a HTML file, which I've uploaded as a web resource and linked to via an activity's form designer in an IFRAME. So far, so good.
Then, when I edited the source file locally and uploaded it (browse-save-publish, of course), I got no difference in the appearance on the screen. Here's the weird part. When I open the uploaded file in the editor, I can see the changes to my source code. On the RTF tab I can also see the change in colors of the background.
However, reloading the "create new"-form doesn't bring those changes to the client! I've tried restarting the window, restarting IE, clearing the cache. Nothing helps.
When I entered the very same page from a different client, I got to see the updated version. But after that, the subsequent changes are not updated either. It's like if IE thinks "oh, matey, ya wanna cache that for life, I see". Well, I don't. I'd like to see my edition in action pretty much directly and without creating a new account with a new client. :)
After a while, the update seems to go through and I get to see a new version but not in all browsers.
What is causing it?! How do I kill it?
(Win8/IE10/CRM11OL)
I have seen CRM do some weird IIS Caching. I'd assume this is a server side issue, but your using crm online, they won't let you run an IIS reset now will they? :) Have you tried running it on a new client in private browsing mode, deploying your change, and opening a new private browser to test if it is a client caching issue or a server caching issue?