(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.
Related
Video: https://www.screencast.com/t/nZr2b9KBRSf7
Opening Google Search Results in a new tab results in non functionining pages for me. However if I hit REFRESH on those problematic pages it takes me to the desired site without any issues.
The issue only appears to affect Microsoft EDGE and not Google Chrome. And the broken links seem to only be problematic when opening Google Search results in a new tab.
I reset my browser settings back to default.
I also added the following registry entry as described below for RendererCodeIntegrityEnabled:
https://browserhow.com/how-to-fix-microsoft-edge-status_access_violation/
Finally I changed the shortcut of EDGE to disabled the rendered cod eintegrity as well:
"C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe" – disable-features=RendererCodeIntegrity
...
On the problematic pages, the parameters in the URL look like the following:
https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=&ved=2ahUKEwiYu8Th97
url: 'sa=t'
rct: 'j'
q: [null]
esrc: 's'
source: 'web'
cd: [null]
This resolved itself after a Windows Update. Weird bug...
I searched for this one, but found nothing ...
My old site is: cs.abc.edu/~cs4096
My files were at: cs4096#cs.abc.edu/public_html
My personal site: myname.com
My Github Pages site: myname.github.io
When a user requests cs.abc.edu/~cs4096 they are served cs.abc.edu/~cs4096/index.html and so on.
Via the ISP hosting myname.com, I setup a CNAME pointing teaching.myname.com to myname.github.io .
I want references to the old site, including pages below the top index.html, to be sent to teaching.myname.com where through the magic of DNS CNAME the URL goes to the myname.github.io site. In other words, users still go to the cs.abc.edu/~cs4096 but they are served from github.io.
The teaching.myname.com -> myname.github.io bit is working fine. It’s the initial redirect/rewrite that is failing. The problem is that the ~cs4096 is included in the URL when it is passed to myname.com .
That is, this
http://cs.abc.edu/~cs4096
ends up as
http://teaching.myname.com/index.html~cs4096
instead of
http://teaching.myname.com/index.html
and this
http://cs.abc.edu/~cs4096/Schedule
ends up as
http://teaching.myname.com/index.html~cs4096/Schedule
instead of
http://teaching.myname.com/Schedule
And, if you wonder WHY I’m doing two “redirects” here, it is because want the automatic rebuild of github pages that I can’t get at abc.edu or myname.com .
Thank you all
Never mind ... I abandoned this idea and used an HTML Redirect. It will mess up “Back” in the Browser, but it works.
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'm hoping someone can help me because this is driving me crazy.
I have a multilingual DrupaL 7 site set up with English being the main language and French being the secondary language. I have url aliasing set up and for the most part it works correctly.
The problem arises when I have pages that I don't want included in a menu, so I leave the "provide a menu link" box unchecked. Even if the "Generate automatic URL aliases" box is checked for those pages without a menu link, the page completely ignore any url alias patterns I have set up and the url always shows up as 'node/31' instead of 'my-content-page'. If I hardcode in a URL alias via the URL path settings on the page, it WILL take those, but this is not what I want. I want it to take the url alias pattern I've set up for it. I even installed the "Pathauto persistent state" module and forced the "Generate automatic URL aliases" to remain checked just in case, but my alias patters are still ignored.
Both English and French pages do this if the page is not provided a menu link.
Has anyone seen this behaviour before? Does anyone have any ideas what might be wrong?
Thanks!
This can happen when you have tokens in your URL alias pattern that doesn't work for any reason. In your case it sounds like you have a pattern including a "menu item" token, so when you save your node without a menu item, the URL alias is not created.
The solution would be to either include a menu item, manually add your URL alias, or change anything looking like [node:menu-link] in your URL alias patterns to something else.
I think I had the same problem, and the point was that the "Basic Page" content-type needed to have available the menus of the appropiate languages in its "menu settings" (in admin/structure/ then "edit" basic-page) .
Hope this will work for you too.
If your have a non english site, follow the issue: https://drupal.org/node/1847444 and patch or solution.
I had the same problem and I solved it, "I hope forever", by reading the comment written by enzipher:
This can happen when you have tokens in your URL alias pattern that
doesn't work for any reason.
I'm using a custom pattern and I solved it by following these steps:
I went to pattern page, deleted custom token and save
I went to node and edit, then saved the node and url alias had been created like domain/language/title_node
I went to pattern page, insert same custom token and saved
I went to node again and edited it, then saved and the correct node url alias has been created
domain/language/custom_token_content/title_node
Created a new Publishing site to serve a portal for our division. It contains several custom coded webparts that fetch data from the db and/or RSS feds and outside links.
I found it absolutely dumb that as a owner I'm having to approve my own page. Is there was to turn off this functionality? Or modifying so that only a document library runs through the approval process?
In the edit mode, there is a link "Reminder: Check for Unpublished Items" and if I click it all of my web parts and all the links, pictures, and other contents within these web parts are highlighted with a fat dotted red line. How do I get rid of this since what sharepoint is complaining about is embedded in these webpart?
If I try to create a doc library called "Announcements" I get an error:
"The resource cannot be found.
Description: HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable. Please review the following URL and make sure that it is spelled correctly.
Requested URL: /Announcements/Forms/AllItems.aspx"
For some reason it does not like the word, as I can call it BuggsBunny and all is fine. Is "Announcements" a key word of some kind in SharePoint? I really need to create a list with this name.
Thanks,
Risho
I found it absolutely dumb that as a
owner I'm having to approve my own
page. Is there was to turn off this
functionality? Or modifying so that
only a document library runs through
the approval process?
You should choose, when you are creating your site, a "Publishing site" template rather than a "Publishing site with workflows". The main difference between these two is the fact that you'll approval workflow on nearly everything activated with the later while the former is free of it but still allows you to activate it if needed
there is a link "Reminder: Check for
Unpublished Items" and if I click it
all of my web parts and all the links,
pictures, and other contents within
these web parts are highlighted with a
fat dotted red line. How do I get rid
of this since what sharepoint is
complaining about is embedded in these
webpart?
Don't know where you are hosting your webpart ressources (style library, document library, image library ? outside of SharePoint ? On the 12 hives ?) but if they are within SharePoint libraries and the content is not published with a 1.0 version available for the readers, you'll have this error. Deactivate the approval workflow or publish AND approve theses items. Please also note that external content will probably trigger this red link, but I suggest you to use a limited "visitor" account to check up the final rendering. The "outlining" is a nice addition but it's not always working as expected, mainly with external content.
If I try to create a doc library
called "Announcements" I get an error:
"The resource cannot be found.
Description: HTTP 404. The resource
you are looking for (or one of its
dependencies) could have been removed,
had its name changed, or is
temporarily unavailable. Please review
the following URL and make sure that
it is spelled correctly.
There is a default annoucement list in SharePoint (with its dedicated template, not sure that you have one provisioned with the publishing template that you picked, that might be a reason why you have this strange error. The default announcements list or its template is not a document library. If you want a document library with that name, and that specific name gives you that error, I suggest that you create a document library called AnnouncementsDocuments and then change its title for "Annoucements", that way the url will be clean of the dreaded name and you'll have the specified title.
For the error message, have a look within the source of the error message page, you might have, in some comments, more information that might help us to help you.
Hope it will help :)