We have an issue relating to “Unpublished Content” on our Umbraco (7.154) site:
Our setup
We have one Umbraco installation (7.154) which hosts multiple sites: each site appears as a "level 1" node, with its content/pages as "child nodes" appearing underneath.
Each site has a “Domain” set under “Culture and Hostnames” (New account here, can't display images directly):
Site A - Node Hierarchy
Site B - Node Hierarchy
Under each Site, there is a “Forgotten Password” node with a similar Path (relative to its site root):
• Site A: “Home/Forgotten Password” (unpublished node).
• Site B: “Home-****/Forgotten Password” (published node).
The Issue
On site A, when any hyperlink pointing to the “Forgotten Password” (relative path) is followed it resolves instead to the SiteB “Forgotten Password” node.
My understanding is that Umbraco URLs are resolved by a NodeID reference in the Umbraco DB: so these nodes should be unique despite having the "same" name.
Could this behaviour be Umbraco searching (by Node Name) for a "fallback" that is published?
Any advice is appreciated. Thanks for your time.
They should as you mention be unique. THings I suggest you try:
You could try clearing the cache. This could be corrupted somehow. In the backend, settings, examine, clear the indexes for external
Check your code, maybe it's a typo or something.
Are you using route-hijacking in our controller. If so if you hit a break point, what ID is being passed into it from Umbraco.
Related
I'm using umbraco 6.2.6 and try to package some of the umbraco cms content in my PC to the another umbraco cms in different machine. To create the package I following this tutorial http://www.uquickstart.com/umbraco-tips-and-tools/package-up-your-umbraco-website.
After I create the package then installed it to another machine, All works fine for (document type, data type, templates, etc) however my content/page is not installed by this package.
P.S. I'm sure my packages already contain the content/page
One of my colleagues say that eventually sometimes we need to included the content/page from the parent to add the content/page. For example the news is under the home sections (Home -> News), so to add the news to the other machine we need to add the home as their basic parent.. Is this true?
Or are there another way or idea to package this item then installed on another machine.. Any idea would be helpful..
Thanks
In a word, yes. You'll also need to include in your package the Document Type for your home page. Basically, in order for your content to be included in the package and successfully created, you need to also include any parent nodes so that the Content Tree remains valid.
Even if your package includes the specified content nodes, because you haven't included the parent node those nodes won't be created because the resulting content tree would be invalid.
UPDATE:
If a home node exists already and your package adds another, then you will end up with two - the new one will have a unique name and may be unpublished though.
The other problem to consider is if a Document Type already exists with the same name as one included in your package - in this case, your new Document Type won't be created, but the package should still create a node based on the existing Document Type - this is where things get messy. I haven't tried in a long time, but the package install may simply fail to create the related content node as the properties won't necessarily match up.
(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.
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'. I've tried publishing out the whole site but I can't as it times out (I've tried increasing all the timeouts, but it's taking an hour to publish so I get a strange network error), and just re-publishing the whole 'Global' node and sub-documents doesn't fix things. Any other way to fix this? Also what is the purpose of the 'Alternative Links' and how are these determined?
as I suggested in your original post, I set up a very basic Umbraco v6.1.2 instance (using NuGet in Visual Studio) with a single doc type and an identical top-level structure to what you have described.
So:
Set umbracoUseDirectoryUrls to true in the web.config
The doc type, called "BasicPage" has a single property called "umbracoUrlName". This allows you to overwrite the path created by Umbraco based upon the title of the node. I assume you already have that in your doc type.
I set both English nodes to have a umbracoUrlName of "en".
I added two hostnames to the Root node - "localhost" and "mobile.localhost"
I published the Root node and all following nodes
As you can see, both the "Link to document" and "Alternative links" are as expected.
I suspect you may be right that trying to get the site to publish may fix the issue, so you may have to publish the site in bits, working from branch to branch.
However, I would advise creating a test Umbraco instance as I have done and then comparing what you have.
Alternatively, you can of course remove the hostname settings altogether if the entire content structure is going to be served using the same hostnames as these can simply be controlled in IIS. Umbraco doesn't actually need to know about them unless you have separate distinct sites in the same content tree.
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 have installed Umbraco 5 and Configured a site. Then I have added a document type in the settings section. As soon as I add a page in the Content section it's shows the error "A URL could not be generated for this node because the branch it is contained in requires that a hostname is assigned". Any idea?
It sounds like you have more than one root-level page. Without adding a host name, you can only have one root-level page under the Content directory -- this represents the home page of your site, and all other pages should be added hierarchically below it.