I'm trying to log in to the Orchard Dashboard, but in the instance I'm working with, it has been configured so as to not show the log in link to the bottom, like the default theme does.
I've tried a bunch of URLs, including OrchardLocal/Admin and I get a 404. Is there a specific place to change the default URL for security purposes ?
I've tried looking in various XML files that have DetailsRouteOrchard nodes in them, but I have not found the URL for the dashboard.
Any ideas ?
Thanks.
Change the Project URL (like http://localhost:30321/OrchardLocal) in Web under Project properties and created new virtual directory.
Source : Orchard Dashboard is missing
Related
I have a simple azure web app and have set the default document in the portal to home.aspx. There is a home.aspx file published, it is browsable via http://my-domain.azurewebsites.net/home.aspx (not real domain) however the default document won't work when browsing to http://my-domain.azurewebsites.net it returns a 404. There is nothing special here. I even added it to the web.confg and it still returns a 404. It is a web forms project, set to integrated security with the correct default document added. Any ideas?
I setup the following web app (West): supportforlucuma There is only one other app in that plan which is the one that isn't working.
I can see the home.html page by visit “http://supportforlucuma.azurewebsites.net/”, Is your issue solved? If no, I will provide more information of how to debug this issue.
Except to set default document on portal and web.config, the default document also could be set in RouteConfig.cs file. For example, following code will set the index.aspx as the default page of current web application and it has the highest priority. If index.aspx file is not exist, a 404 error will response to client. Please check whether the similar code is exist in RouteConfig.cs file.
routes.MapPageRoute("default", "{page}", "~/{page}.aspx",false,new RouteValueDictionary( new { page = "index" }));
For further troubleshooting this issue, we can to get the detail information of 404 response. For example, which modules are executed on server side during the default page is accessed. To do it, we need to enable Failed request tracing. Then we could see the detail information by download the tracing log from LogFiles folder. For example, "ftp://xx.ftp.azurewebsites.windows.net/LogFiles/W3SVC355162095/".
I am trying to change my site uid(mangou-uk to mg-uk) in hybris. I changed in hmc but getting 400 error when I click on homepage category links and also in some other pages. What are the steps to follow to change site uid in hybris. Can anyone help me on this please.
Have you also changed the below properties in your local.properties file?
media.mangou-uk.http=http://localhost:9001/
media.mangou-uk.https=https://localhost:9002/
website.mangou-uk.http=http://localhost:9001/
website.mangou-uk.https=https://localhost:9002/
If you change your site uid from mangou-uk to mg-uk then you would also need to amend these properties accordingly, e.g.:
media.mg-uk.http=http://localhost:9001/
media.mg-uk.https=https://localhost:9002/
website.mg-uk.http=http://localhost:9001/
website.mg-uk.https=https://localhost:9002/
(the URL's might be different of course depending on your environment)
Have you restarted Hybris ? Usually this is cached in your session by the DefaultUrlEncoderFacade so most likely a restart would be enough.
Or try to delete and recreate the storeFront url Encoding Attribute from the HMC if you can't restart.
Did you also adjust the "URL Patterns" accordingly in the hmc?
It's under WCMS -> Websites in the hmc. For your website you will have to adjust the URL Patterns (in the Configuration section) . At least you have to do that in case you use the ?site=SITEID parameter approach.
Changed the site uid in hmc.
Changed the base store uid in hmc against the each website.
Changed the properties as suggested by #Alexey
Now its working fine.
I'm trying to get my subsites to inherit the look I configured (under site settings > look and feel > change the look) on the rootsite. How do I do this? Thanks in advance!
I'm using Office365 (Sharepoint online).
Generally, according to the article below, the subsites will inherit the theme from the parent site. Here is the article link:
look and feel inheritance
By the way, may I know whether your subsite is from another template? If so, please follow the instruction below:
1) Since the link of Master page setting is hidden, you can change the URL to the setting page by two steps.
Copy your site URL and remove the target of URL after the default URL. See the example below:
Root URL : https://XXX.sharepoint.com/SitePages/Home.aspx
Change to : https://XXX.sharepoint.com/
Add the ‘_layouts/15/ChangeSiteMasterPage.aspx’ behind the URL from step a. See the example below:
Root URL: https://XXX.sharepoint.com/
Change to : https://XXX.sharepoint.com/_layouts/15/ChangeSiteMasterPage.aspx
Note: if you get the error message, please go to check the publishing featureon Team Site.
Per my test, you need to enable SharePoint Server Publishing feature if the subsite is not a publishing site.
Then when changing the look of rootsite, the look of subsite will get changed too.
I have set up a small XPage and have until now used the full path to the Xpage for testing, i.e.
http://devsrv1.magerman.ch/Development/Schulungen/Schulungen1_0/Schulungen_(1_0)_Dev.nsf/HomeWithDataView.xsp
I then tried to apply a Web Site Document
But the links are no longer currently functioning. I have the feeling that I'm missing something pretty basic, and am unsure as to what the best practice is. I'm quite happy with having the original request to the hostname resolve to a full path, i.e.
input
schulungen.magerman.com
and have it resolve to
schulungen.magerman.com//Development/Schulungen/Schulungen1_0/Schulungen_(1_0)_Dev.nsf
but haven't found a way to do this elegantly.
At the moment, my relative links '/OtherXpage.xsp' fail as they try to get to schulungen.magerman.com/OtherXpage.xsp
Any pointers?
Create a Web Site Rule. You can create it from your Web Site document in edit mode with action button " Web Site ... / Create Rule".
You can find a description how to fill the fields here.
The problem is usually that you need to add a trailing slash to the hostname
http://www.xpagedeveloper.com/2013/quicktip-get-right-path-when-autolaunching-an-xpage
my xPages app (with oneUI theme set) works perfect when I use e.g. this URL:
https://testserver.xxxx.xxxx.com/app_folder/Home.xsp
and then our Domino admin mapped it to a new URL
https://myApp.xxxx.xxxx.com
that by default opens Home.xsp page
but now I see several UI issues - some icons/images are not shown, some controls displayed incorrectly.
What could cause this problem? It's the same Domino server but just two different ways to log in. Is it something related to "XPages Resource Servlet" configuration? Where can I check it?
For example. I have an image on xPage that has following resource:
"../../oneuiv2/images/sortDescending.png"
then when I log in through https://myApp.xxxx.xxxx.com - it doesn't show the image...
OK, then I replaced it with:
"/.ibmxspres/domino/oneuiv2/images/sortDescending.png"
same result.
but this works:
"/.ibmxspres/global/theme/oneui/images/sortDescending.gif"
I can replace all images/icons with new resource URLs but anyway other standard controls are not shown correctly..
Based on our short discussion your problem is in wrong URLs.
So why one URL works and the other one doesn't? Concatenation, in my opinion. Browser, JS frameworks (DOJO) and JS programmers in general tend to use either relative URLs or cut/concatenate URL string. This my result into URL that is not understandable by server.
In your case check URL mapping made by your admin - does it apply to all URL formats used by XPages? Are those transformed URLs accessible on server (enter them in URL bar of browser)? That is the key to get your XPage working.
OK.. it's fixed. The problem was in Virtual Server Mapping document.
Names.nsf -> Web -> Web Configuration -> Virtual Server -> Mapping tab...
we had to set
HTML directory: domino\html
which was
HTML directory: /myappdbname.nsf
instead