I am working to create dynamic landing pages for a site, using panels. The first step in the process is to designate the path. I want the landing pages to have the same path as the nodes, just ending in "home" for the landing page. For example, I have "departments" that will have landing pages, so the path looks like:
department/%department_name/home
That works fine. However, I am also trying to create a series of paths based on a set of vocabularies. They all have different names, but they work essentially the same. I want this:
%vocabulary/%terms/home
But then I get this error:
"The first element in a path may not be dynamic."
Why not? I don't want to have to create variants for each vocabulary. Isn't there some way to by-pass this error?
Thanks!
You cannot by-pass this error. Drupal's menu system simply does not support % as the first placeholder.
See an explanation at a related Drupal.org discussion.
A simple solution here is to use a generic static argument for the whole site (like site, live, new etc) as a starter path. Some developers also use this by default so they can alter it later on upcoming versions or on new functionality (for example they may have path /a/%some_args and a new version will be /b/%some_args).
Related
I need to do an hyperlink to an external page in Guidewire Policy Center.
I am using a function in a gsx enhancement file that returns a String with the url according some parameters.
The problem is that I don't know how to use the url to redirect to another page.
As Carlos mentioned you need to create / use an ExitPoint PCF. The documentation is linked in his answer so I won't do it again, however in case it becomes invalid for some reason here's the long and short of it.
You need to create a new PCF file and make of type exitpoint
In there you make an exitPointParameter, fill out the necessary fields, and you're set.
Then you can put your link wherever you want and just put in the action nameOfExitPointPCF.push("http://www.google.com")
You can put other parameters in there, and it'll build it for you, just refer to the documentation.
For really simple external links, there's one called ExternalUrl.pcf that I assume is in the out of the box configuration.
You must create a ExitPoint PCF file. You can read about that in module documentation. Open the page with Firefox...
PolicyCenter/doc/wwhelp/wwhimpl/js/html/wwhelp.htm#href=Configuration Guide/pagefunc.34.4.html
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.
The project I am working with is using an old version (v.2.1.0.1) of N2CMS.
To start with, I want to avoid upgrading to the latest N2 version, not because I don't like new things (because I do) but because since I am using such an old version it would take a lot of efford trying to upgrade it and if there's a way to solve this issue in a more time efficient way then I need to do that instead.
What I need to do is to enable the url to set the languageroot for the website and having it not only rely on the /lang. For example, i want my website.se to point towards /sv and my website.no to point towards /no. Right now .se is default so no matter the URL, swedish is the language shown. The twist is, and the reason for why I need it done this way, that I am loading data from another database and showing it on the site, list of categories and products (/keyrings for example). These things don't have the /sv or /no in the url. The result here is that even if I get /no to working along side the .no url, as soon as I click on an item in that list without the language code in the url then I will automatically be redirected to the default swedish languageroot. So I want to completely rely the N2CMS languageroot on the URL and not the /lang. I know that this is possible in the later versions of N2CMS but I am hoping there's a workaround in the older versions as well.
In this version I have a startpage and under the startpage i have languageroots. Each language root has the option to enter an URI Name, in my case i have swedish and norwegian so that's /sv and /no. An example from the site could look like this: /sv/om-oss, the norwegian way would be /no/om-oss.
In the later versions (that I use for other and newer projects) I have just the startpage and in its settings I am able to enter the hostname, this is what I want for my site (not necessarily have it changable in N2CMS, it's easier to just have it coded in).
Does anyone have any experience in this, or knowledge deeper than mine when it comes to these sort of things?
Just for record, this problem got solved http://n2cms.codeplex.com/discussions/397494
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 :)
I have created a dashboard for an Umbraco site and I want to link from it to various node in the tree.
From what I can tell Umbraco uses editcontent.aspx?id={thenodeid} and javascript:opencontent({nodeid}).
Whenever I try to use these they always fail.
Does anyone know how to open a display a node in the Umbraco back end?
Like Tim Saunders said you really just need to target the correct iframe. The openContent function looks like this:
function openContent(id) {
parent.right.document.location.href = 'editContent.aspx?id=' + id;
}
So you need to target the 'right' iframe.
I've tested editContent.aspx?id=1234 on my Umbraco installation and it seems to work correctly.
I'm assuming you are replacing {thenodeid} with the actual node id you want?
Umbraco uses iFrames in the backend for the content tree and the content areas etc. This means that you do not always have full access to the Javascript libraries from the frame that you are in.
Therefore you may need to either include the library in the page you are working with or try and reference the method calls by walking up the dom.
I can't find any documentation for this so it may be a case of looking at the HTML source and working out what is going on.