Have some issues with courier - After Installing Courier inside the back office it asks you to enter a location, so I enter the location of the second instance of Umbraco.
After logging out and logging back in I do get the extra menu item in content - Good
Also In the back office when I go to Courier section > Locations it shows the URL user id ect - Good
If I open the courier.config and change anything (eg the user id) save the file, then touch the web-config file to force a recompile of the site.
If I go to Courier section > Locations I see this message
Location could not be loaded, this could be a configuration error, or because Courier is running in trial mode, and cannot not load locations not on the local machine
Even if I go back to the courier.config and change it back to exactly what it was before, it still shows the same error. The only way I have found to fix this is to uninstall and reinstall courier.
Can one one tell me why this happens how I can fix it?
Not sure as to the direction of the question, but this is how you configure the locations within courier.config. User 0 will be the admin user so I'm not sure it is a good idea to change that.
<!-- Repository connection settings -->
<!-- For each site, a custom repository must be configured, so Courier knows how to connect and authenticate -->
<repositories>
<repository name="http://example.co.uk/" alias="http://examplecouk/" type="CourierWebserviceRepositoryProvider" visible="true">
<url>http://example.co.uk/</url>
<user>0</user>
<!--
Alternative, you can specify the specific login / password / encryption values
<login>admin</login>
<password>1234</password>
<passwordEncoding>Clean|Hashed</passwordEncoding>
-->
</repository>
</repositories>
Related
We get this error a lot on our Umbraco site, also we've noticed that when we publish content, it doesn't actually publish it, then I check the log and I see this error message.
Is this because there maybe more than one admin user logged in at one time?
Pete
Having more than one admin user logged in at the same time is not a problem at all. There's plenty of running sites with many backoffice users logged in and editing at the same time. The only case where this could give an issue is the fact that if you have two users load up the same item in the backoffice and one makes changes and saves.. and the other one then saves without reloading first, the changes from user1 will be overwritten by whatever was loaded when user2 loaded up the page.
One thing that could lock up your indexes however is having multiple sites run off the same index files (which is NOT supported) - so make sure you're not doing this. I've seen some people forgetting having an old IIS test site configured in the same folder after going in production which could bring up this issue.
Another thing that I usually do is exclude the index folders from both anti-virus scanning and the windows indexing service, as I've seen both of these take temporary file locks which sometimes interfere with umbraco's access to the index files. The indexing can be turned off by right-clicking the specific folder in explorer, selecting properties > advanced > uncheck the 'allow files to be indexed'.
(To make this simpler - I've re-posted the first part of this question as a separate question, which has now been answered:)
Umbraco - Incorrect alternative link to document
Here's the full, original question:
On our website, we have the following structure:
sitename
-Global
-English
-UK
-English
for the Global > English page, the links to the page are showing as:
Link to document
/global/en/
Alternative Links
http://english
so the 'Link to document' is correct, but the alternative link isn't. On the UK > English page, I just get the correct 'Link to document'
On our development version, I've just turned on the useDomainPrefixes = true option in the umbracoSettings.config of of the site, and I've added a hostname for the top level 'sitename' node. Now I get the following as page links for the Global > English page:
Link to document
http://english/
Alternative Links
http://hostname/http://english/
http://english
I get the correct links for the UK > English page, showing the correct hostname in the URL like this:
Link to document
http://hostname/global/en/
I've tried re-publishing the entire root node (sitename), however I get an unusual timeout error. I've increased the timeout for the app pool, and for the session and the umbraco timeout in the web.config, however this is a different error probably related to the proxy server contacting the web server.
Is republishing the entire site the only fix? I've tried only publishing the sitename > Global node, which completes successfully, but doesn't fix the issue.
This is sometimes caused by setting the domains for the content nodes incorrectly. If you've right clicked and selected "Manage Hostnames" then you can get issues like this.
Remove all hostnames and see if everything works with UseDomainPrefixes=true.
I would reinstall from scratch and rebuild the site if the worst happens and you really cannot fix.
I have just put up an Umbraco 6.0.3 site on eHosting and set all the directory permissions iaw our.umbraco.org/.../permissions. And this(http://our.umbraco.org/wiki/reference/files-and-folders/permissions/perform-permissions-check) reports the permissions as "perfect". .NET framework set to 4.0 and App pool has been set and recycled. Site shows up but no macros load and in the Umbraco UI there is only a Content node and a Media node, both the Content and Media trees are empty.
I can't think of anything else it can be. This is the first V6 site I've put live.
Is there anything else I can check?
Cheers
Check that your user login has permissions to view those nodes. The fact that you are not seeing any other sections (Settings, Developer, etc) suggests this.
Also - are you using any hostnames in Umbraco for the site (where you right click and click manage hostnames on the content node)? If so then check that the root node has a wildcard hostname added.
This is a case of retracing your steps over what you've done. If the other options don't work then you can do a database refresh too (copy the dev database to live). The fact you can login to the admin UI, says that you have the database working. However, is it possible that you've tweaked anything manually in the database?
Are you using MVC or ASP.NET rendering engine?
Check your log files and paste them here if all else fails and we'll try and help you out as best we can. You'll find them in App_Data/Logs/UmbracoLogs.txt
When the content and media nodes failed to load for us in Umbraco 6.0.3 it was due to a bug in Courier which causes the back-office to malfunction if you are connected to a MySQL database (throws an exception complaining "Keyword not supported: 'charset'").
Courier interferes with many back office functions and in this case it is incorrectly assuming that you must be connecting to an MSSQL server.
The only solution was to uninstall Courier (which was OK for us because we'd already determined that there are too many show-stopping bugs for it to function as advertised).
I developed a site for a client before a domain name was chosen. As a result, the URLs for the site pages look like:
http://host.mynost.net/~tempname/index.php?id=8
A domain name has now been purchased but if I click on any Wayfinder links it still uses the old path as above instead of, say:
http://domainname.com/index.php?id=8
I assume this is configured in the config.inc.php file, but I am unsure of what to change.
Can anyone point me in the right direction? Thanks!
You need to change $modx_base_url= '/' in /core/config/config.inc.php and if that is not enough - manually clean /core/cache/ folder.
Four years later, I've dealt with the same thing for a few months, and was incredibly frustrated.
An updated answer to this issue would be navigating to Settings (icon) > Context, then choosing Key > web (right click) > Update Context > Context Settings.
Change http_host (ex. localhost) and site_url (ex. http://localhost/).
Now, from the top menu Manage > Clear Cache as well as Manage > Clear Cache > Refresh URIs.
It was like finding a pot of gold.
I have a web on some super-old Modx version which I needed to temporarily set up for viewing, and I ran into this issue.
The way I changed the base URL is in the database:
table: modx_context_setting
key: site_url
This outlines how to move modx to a new location ~ which is essentially what you have done.
http://rtfm.modx.com/display/revolution20/Moving+Your+Site+to+a+New+Server
genereally you can get away with updating the config.inc.php & clearing the cache, but it's a good idea to go through the system setting table in the db looking for old paths, some packages do store path info in there.
I've found a dilly of a pickle with a new web server. We have a new web server that is displaying dates differently than our old web servers.
We are running asp classic web pages on IIS 6.0 with windows server 2003.
We have logged in as an administrator and set the regional settings as appropriate and then applied the settings to current user and default user profile.
We then went into registry and update the appropriate formats under HKEY_USERS/.default/control panel/international.
Update the asp.net configuration for our websites to the correct code-page and locale.
Does anyone have other places that the application could be getting date formats from?
I know this isn't the 'proper' way to fix the issue. However, the application was written many years ago, getting something through planning/change control would be a pain, and is the only application running on the server. Thus it is okay to configure the server to cater to this single application. Besides it was driving me crazy that a new server that should be configured identically to an old server was not working.
It turns out that in addition to HKEY_USERS/*/Control Panel/international, there is a setting for non-unicode programs. It can be found under HKLM/system/currentcontrolset/control/nls/language/Default. Set that to the correct code page and it is golden.
On the other hand, if you prefer to not modify the registry directly, you can update all these values through the Regional settings from the control panel.
You can adjust the formats through the 'customize' button.
You can change the 'language for non-unicode programs' under advanced tab.
Just make sure that you check the 'apply to the default profile' at the bottom of the advanced tab.
I don't think the highest vote answer is right, though it's close.
I had to use regedit to change all the internationalization settings of HKU\S-1-5-19\Control Panel\International (NT Authority) and HKU\S-1-5-20\Control Panel\International (Network Service) to match the settings that were already in HKU\S-1-5-18\Control Panel\International (Local System).
This worked perfectly.
I modified all the settings I could see which were different, by hand.
I should think I only really needed to change the settings for S-1-5-20 (Network Service).
Go to Control Panel -> Regional And Language Options, set all options you need, then under 'Advanced' tab select settings for non-Unicode programs and check 'Apply all settings to the current account and to the default user profile.'. Press OK and restart server.
On Windows Server 2008 administrators have additional 'Administrative' tab. There press 'Copy to reserved accounts'.
Classic ASP Defaults to the Locale ID that was configured when the server was Setup. If you have access to the original server run the following code to get Locale ID it's operating under and verify that the new server is using the same.
<%=Session.LCID%>
If the Locale IDs are different and you cannot change it on the new server then you can add a line to the Session_OnStart sub in the global.asa for the application that assigns the correct Locale ID to Session.LCID.
Using an ASP page with the content:-
Response.Write GetLocale
Might be informative, it'll show you what locale VBScript thinks its using.
I've seen issues like this in the dim and distant past when using integrated security. The ASP caches the regional details from a user hive when it first needs to use them then continues to use those settings until the process dies. ASP gets these settings from the user hive associated with the user identity the code is currently running under. Most of the time that would be DEFAULT because the user doesn't have a profile on the system.
However if the user happens to have logged on interactively to the server they will have a profile and so their settings are used. Hence I've seen situations where the server appears to have intermitten problems with regional settings.
I can't recall if I've seen this on IIS6, I've definitely seen it on IIS5.
If you run your ASP application under a different account (not IUSR_Guest)
Login as that account, set date/time format to what you want and restart IIS.