If my base url is
www.mysite.com
with a DNN site, how do I write this?? (I know this seems simple, but a google search did not show how to write this...
i.e.
Games
Toys
You can look up the PortalAlias via the PortalSettings if you ASCX file inherits from PortalModuleBase
PortalSettings.PortalAlias.HTTPAlias
Related
I am trying to create buttons on a web page that allow users to share links to PDF documents on LinkedIn. LinkedIn loads a window without any errors but offers no link or preview of the PDF or any indication of what is being shared.
Here are the two methods I have tried. First the plugin method.
<script type="in/share" data-url="http://example.net/DocumentDownload.aspx?Command=Core_Download&entryID=114"></script>
And, secondly with a custom url.
TEST
Encoding the url makes no difference.
The above links are direct document links from a DNN web site using Document Exchange. If I change the urls to any html page it works fine and LinkedIn seems to be able to extract the useful information right from the page and use that for the share details.
Can LinkedIn handle this kind of thing? There is nothing to guide me on the type of links that can be shared. I can't find any information about it. There are no errors in the web console.
Not sure, but you should try to provide LinkedIn with the link that has .pdf at the end, like http://example.com/documents/file1.pdf. I guess LinkedIn just checks the URL if it has .pdf file at the end to decide if it is a PDF document or not.
I have no problem sharing pdf's on LinkedIn. Check it out...
https://www.linkedin.com/sharing/share-offsite/?url=https://www.revoltlib.com/anarchism/the-conquest-of-bread/view.pdf
Works perfectly fine. And view.pdf is a script, not a file, either, so, it's not looking for a PDF file to analyze, so much as headers that indicate you have a PDF file available to analyze, so, in PHP, at DocumentDownload.aspx, we would do...
header('Content-type: application/pdf; charset=utf-8');
This header let's the sharing app know that it can analyze the document as a PDF file and extract useful information from it, as you can see from the screen shot.
We have our own custom DotNetNuke 7 skin based on Bootstrap 3. It includes a navbar in which I want to have a navbar-brand that links to the home page.
Is it possible to generate a link to the portal home page inside a skin?
On the documentation page I found a link to the Skin Objects Guide (pdf) suggesting [Portal:url], which I tried like this:
Home
Not surprisingly this doesn't work (the pdf is from 2009). The other links from the wiki are either dead or useless.
I've also tried looking through the "Gravity" and "Aphelia" skins that come with DotNetNuke, but nowhere do the ascx files seem to link to the portal home page.
Obviously I've also tried GoogleFu in various forms, e.g. "DotNetNuke skin create link to home page", but this leads nowhere.
Anyone know how to do this? Or much preferred even: where I could've found this- and related info? Or am I doomed to dive into the source code of DNN?
It's dangerous to go alone. Take this:
Home
NavigateUrl is your goto method to handle referencing another part of your portal. It goes through url rewriting so it will be consistent with the rest of your urls.
There a plenty of signature overloads for this function, where you can specify keys, controlkey, settings, etc. Have a look at the DotNetNuke.Common.Globals class for more info.
Note that if you use the abovementioned version, you'll need to have a "Home" page set for your portal under admin > site settings.
In DNN 7 it would be best to do this:
<%=DotNetNuke.Common.Globals.NavigateURL(PortalController.Instance.GetCurrentPortalSettings().HomeTabId) %>
Note the extra Instance. in there. The variant PortalController.GetCurrentPortalSettings() is obsolete.
I've tried to search for this both on Google and StackOverFlow, but simply can't find what I'm looking for, it might be that it's simply not possible, but thought I would ask anyway.
I'm looking for a way to make a file redirect the user to another page, the user would download the file by clicking on a button.
It's for a Prestashop downloadable product, I'm trying to redirect the user to another part of our site (which isn't directly visible) to be able to view magazines, etc. in a viewer.
Now Prestashop is natively set up to download the file, which is what we don't want, hence the use of the viewer, but there is no way to simply provide a link to send the user to instead of a physical file, like a PDF or something. I can't really modify the button as its generated by Prestashop, and if I add a PDF file with the link in there it defeats te purpose as I dont want people having the link in a document (I know they can find it from their history and so on). Hence I thought it would be easier to do it with a document that redirects if possible.
So in short, is it possible to make a file that would send people to a certain web page once they open/download this file on/to their computer?
And if yes, how would one go about it?
Can you make the user download an HTML file? If so, you can use "meta refresh" to redirect the user to your private page.
This does mean the unprotected link will be visible in downloaded HTML file - perhaps you can obfuscate this with JavaScript to make it a little more difficult for users to find your protected URL.
http://www.w3.org/TR/WCAG20-TECHS/H76
i'm using dot net nuke
and i need to rewrite my website urls
for example: from products.aspx to products-computers/home.aspx
I've tried modifying siteurls.config using this rule
<LookFor>.*/products.aspx</LookFor> <SendTo>~/products-computers/home.aspx</SendTo>
it doesn't work.
Please help!
If you are trying to change the URLs of your website, you will need to use a tool like URLMaster from Ifinity to get the ultimate flexibility
What you are doing with the siteurls.config appears to be is define that if someone requests /products.aspx that instead of loading a page called products.aspx, they load a page with a path (defined in DNN) as /products-computers/home.aspx
That means that you need to have a parent page called Products-Computers and a child page under there called Home.
I used to edit siteurls.config and it worked for me - you should be careful with syntax though. What I don't like re siteurls.config is that you're ending up on right page but with wrong address in address bar of the browser. So my preference is this solution that I investigated & tested personally and it was confirmed by stackoverflow community member as well:
redirecting old site pages to single page on dnn portal
i need to remove sitemap.aspx from the site.
In dnn 6,there is a sitemap.aspx page that simply shows an xml sitemap.i cannot edit/remove that file.so i need to remove that page and recreate it with a simple html sitemap.
NOTE:the page name should be sitemap.aspx
Sitemap.aspx isn't a physical page you can delete.
You can, however, rename it to something else. It's in your web.config file, under the 'handlers' section. Just look for sitemap.aspx, and change it to something else, like 'searchenginesitemap.aspx'. Don't forget to update your robots.txt file to point to the new sitemap name, or go to the various webmaster console pages in search engines and advise them of the new location.
The sitemap.aspx is used to create the xml sitemap for search engines. By changing this you break this functionality and limit the search-ability of your site.
That being said, in Host Settings->Advance Settings you could setup a new Friendly Url that would match .*/sitemap.aspx to another url/page on your site.
I have long stopped using DNN's native sitemap.aspx... ITS BUGGY!... and here is how i found out.
I generated my own "CLEAN" sitemap.xml using a free 3rd party tool. And uploaded it to the root of my DNN website.... re-submitted the the domainname.com/sitemap.xml to Google via web master tools and as a result we now get a 1ST PAGE and TOP 10 RANKING.
Mostly in the top 5... where as before using DNN's native sitemap.aspx we would get random errors which was pretty ANNOYING. Plus we got very bad Google Page Rank, But those were just my findings of better results. Note:I also place the location of the sitemap within the robots.txt file...
Although i will admit that it is extremely ANNOYING that you cannot just edit the DNN Sitemap url. This creates an issue if you've built the the site on a test server and then migrate over to production... your DNN Sitemap url only reads the firs portal alias from when you first developed the site.
Anyway, this was my findings... others may vary... just sharing.