I am facing very strange issue in my DotNetNuke website (8.04 Version). I have dual language installed (German and English) in which German is default language.
From the homepage i can switch to English or German which is working fine, but from all other pages (including host and admin pages) I can only able to switch English but can not change to German. When i choose German, Page is reloaded but language is always English, if i need to switch to German, only option i have is to go to home page. Any help will be appropriated.
Thnx
This is quite standard behaviour if you have not yet translated the pages from one language to the other.
Follow these steps:
Navigate to Admin > Advanced Settings > Languages
Select the page that you want to translate, using the dropdown menu
In the German language column, translate the page title, description and module titles
Tick the checkbox that says "translated".
Hit update and repeat steps 1-5 for every page you need to translate.
Here's an image that shows the same
Ref: DNN documentation
Related
I have a Joomla website here and when you click on an article from the homepage it stills displays all of the home page modules. I went thru the settings for each module, and it is set to display only on the home menu page. I go to the menu setting that the articles are under and the settings stated the modules are published but not displayed. Any help would be appreciated!
I discovered the issue was due to a category error. The category is supposed to auto create a page for itself, however, it did not happen for whatever reason. So I had to delete the category and then make the category again and everything was fine. The reason the home page modules were appearing on articles is because that's the default behavior of Joomla when it can not find a specific page.
Where can I go to change the Terms as well as the Privacy policy in DNN 9?
In previous version you could go the Languages option to change this, but DNN 9 does not have an international Language team to work on this anymore. Where to go now?
Go to Manage > Sites. Then select your portal settings by clicking it's settings icon.
In the Site Settings, go to the Languages and click the last icon after the Culture.
You then get to the Translate Resources tab and you can select the language file you want to edit.
You need the GlobalResources.resx > MESSAGE_PORTAL_TERMS.Text and MESSAGE_PORTAL_PRIVACY.Text
Step 1
Step 2
Step 3
You can do this with a simple page as well, just use the url "/terms" (for single language sites) or "/(language)/terms" (for multi language sites), then you can add an HTML module and write your terms as needed. The skin object is exactly pointing to that Url. You may hide the page from the menu as well, if you want.
Same for privacy declaration, the Url is then "/privacy" or "/(language)/privacy".
To change the Url of a page go to page settings :: Advanced :: S.E.O.
Happy DNNing!
Michael
I am working on a news website, trying to implement amp. We are using Mobile_Detect.php to serve desktop pages to desktop and tablets, and mobile version to mobile phones and that works OK, our pages are mobile friendly according to Google for some time now, no problem.
Now, I started to enter the code for amp pages and encountered a situation I can' resolve. URL for the amp version have .amp at the end. Depending on the user's device, we are generating the page from the database and serving different pages to different devices.
Now, PageSpeed Insights and Mobile-Friendly Test shows that the page is mobile friendly but amp validator is pulling the desktop page, I can see by the source code it prints out, instead of a mobile page. I'm on the desktop, Chrome, but I'd expect it to work with mobile pages.
You can see that here: https://validator.ampproject.org/#url=http%3A%2F%2Fwww.poandpo.com%2Fbusineasdfasdfas-usual%2Fpublic-housadfadf-kong-972016223.amp
I installed Chrome amp extension and it says "AMP available" but when I click on it it also pulls the desktop version of the page and it's blank. I would expect the extension to load the mobile page but it doesn't.
We do have links canonical and amphtml, that's why the extension says there is an amp page.
So, how to tell validator to pull the mobile version of the page? The amp implementation is not done yet and I know there are some things missing, but without a validator is a bit hard to program.
Another interesting things is that when I open "Inspect" in Chrome and toggle to responsive design, it shows the mobile version of the webpage correctly. It also says "Powered by amp" and shows no errors although there are errors because we didn't even implemented all tags.
If anybody has any suggestion how to make amp validator to show the mobile page I'd appreciate that. Thank you.
I had a quick look at your pages but it appears that the amphtml reference but there appears to be a problem in the URL you are generating in the href= field. If you take a close look, the AMP URL is missing a '/'.
Broken: http://www.poandpo.com/business-as-usualmexicans-work-longest-hours-germans-the-least-97201645.amp
Works: http://www.poandpo.com/business-as-usual/mexicans-work-longest-hours-germans-the-least-97201645.amp
How we can change text and wording of "Terms of Use" and "Privacy Statement" pages in Dot Net Nuke from admin?
Those texts are part of the resources files.
Go to menu "Admin > Languages" and click for edit its content for the site or the host.
Keep on the edition of the "GlobalResources" file.
Search for "MESSAGE_PORTAL_PRIVACY.Text" and "MESSAGE_PORTAL_TERMS.Text" and modify them.
If you modify the system version, a future upgrade of your DNN installation could overwrite your customization.
Host mode will impact all websites on the instance.
Site mode will impact only the current website.
I know this is old, but it might still help someone:
Tested with DNN 08.00.04 there are different methods to get a custom terms page without editing the language files (which feels a bit cumbersome)
To have your own /terms page you just create named "terms" in the navigation root.
DNN will show up your newly created page if you browse yoursite.com/terms
You can also redirect to another page from there (create a "link" page instead of "content" page, this in case you want to call your page AGB and have this in the url (yoursite.com/agb)
If you have https://dnnurlmanagement.codeplex.com/ installed you can simplifiy the steps above with just adding a "custom page URL" 301 redirect rule with "/terms" to any page you want to show up as /terms.
Go to site admin section here Admin -> Language -> edit host -> find your required field "Terms of use" and "Privacy". you can change here or edit it.
I am trying to set up a multilingual site using wordpress. I went through http://codex.wordpress.org/Multilingual_WordPress#Plugins_that_direct_you_to_external_translation_services and decided to use this option Plugins like Multisite Language Switcher and the newcomer Multilingual Press link together separate WordPress network (multisite) installations for each language by pinging back and forth..
Now i installed the Multilingual press and set up a network. The url of my site was wordpress.private.net and next on is it.wordpress.private.net. Both the domains are served from same folder. But still when i visit the it.__ site it shows in english language and that too without all the posts.
I get this error on network dashboard
You didn't setup any blog relationships! You have to setup them first to use Multilingual Press. For this, go to Network » Sites » and choose a blog to edit. Then go to the tab "Multilingiual Press" and set up the relationships.
But there is no option to set up the relationships in the tab "Multilingiual Press. Please guide me where am i going wrong?
Any other way to set up is also welcome.
My main moto is to run my wordpress site in two languages
I'm also developing a website in two languages.
I haven't used what you are using, so I cannot help you in that regard.
For my project I installed qTranslate plugin and I haven't had any problems with it so far.
In the plugin settings you specify language you want to use and other settings like how the language will appear in URL (?lang=en , /en/ in front of URL , http://en.yoursite.com)
When you edit post or page, you will have additional tab in the editor, one for each language, so it is really easy to use it.
It also supports qTranslate Services, that ables you to use professional human translation services with a few clicks, but I haven't used that yet.
A general note:
Do NOT auto translate your pages with Google Translate. This is basically spamming the google index.
If you want to autotranslate your page, use the google translate widget.
You can read that somewhere in the google guidelines too.
About your plugins:
qTranslate is fine and simple. But it does store all translations into one post. So if you later decide to change to a different plugin, you are toast.
I've heard about Multilingual, but I think it might still be a bit unstable.
The most commonly used is WPML. Might not be the best and it's not free. But it works and I have many clients that use it happily.
But again, DON'T auto translate your page. It's useless and will get you down ranked.