Jump to content
Search In
  • More options...
Find results that contain...
Find results in...
Advanced Search

softworks

Member
  • Content Count

    37
  • Joined

  • Last visited

  • Days Won

    1

softworks last won the day on May 5 2016

softworks had the most liked content!

7 Followers

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Please read number 3f) of the descripton. You have to adapt the injections points for your template. You will need JS/YUI/CSS skills.This tutorial was a proof of concept mainly targeted for developers. For customers i offer an enhanced and extended commercial script supporting several templates. The script does not yet support the Skye Family (Ready template) - but i could built in support. You can send me a mail to info@soft-works.biz if you are interested.
  2. @Matouche - I will contact you under your mail address. Yes i can build this for the Skye template. This requires setting up a blog for each single language used.
  3. Hi @AnnaM , it also works for Bedford and other templates. But, as I described in my post, you need to adapt the injection points for each template family, because the html differs from template to template. You can do this on your own (requires skills in JS, HTML, CSS, YUI) or book me. I have an adapted commercial multitemplate version of the script with additional features running out of the box for lots of templates. In case of questions you can contact me via mail: registrar@soft-works.biz.
  4. Hi @lazalee. As I described in my post, you need to adapt injection points for each template family.You can do this on your own (requires basic skills in JS, HTML, CSS, YUI) or book me. I have an adapted commercial multitemplate version of the script.
  5. Hi @maxkloosterman. Solution 1: You would have to createa mapper function to define therelations between the pages, eg. theurl for the german disclaimer andthe url for the english disclaimer.Disadvantage - If you often changeyour page this will be hard work tomaintain, as you do this manually. Solution 2:You have to build urls by convention, e.g. en/disclaimer, de/disclaimer. Disadvantage - you are goona loose the url for seo purposes.In both cases you will have to change the logic of the script.
  6. Hi @Fabpax you need to adapt the script for each template. Basically it should work, i use it e.g. for Hunter and Brine - they are in same template family like Sonora. But I haven't tested this with Sonora yet.I have developed a multitemplate version of the script for my customers, please contact me directly per mail if you are interested - registrar(at)soft-works(dot).biz
  7. @kristjan - probably your home resides in "not linked" section in Squarespace Backend? Or it has no language specific url?Make a home per language or use a cover page for a multilingual version. Your home is the url defined in language configuration of the script. One improvement i made in commercial version of my script - the logo url is changed to the configured home url per language, so that the logo always points to the home of the current language.
  8. @kristjan you probably misconfigured your english URL.Please configure an abolute Url for each language starting with a slash. In your case: /en/our-service
  9. @Simonhuesler, basically this should work with css and media queries. if you did not find a solution yet, send url of your sqs page.
  10. @Jason_Fu as i wrote: This will not work for onepager designs with jump urls (sections urls) in main navigation. Technically you cannot set a sections url to something like /en/section as RFC for sections does not allow slashes in sections. So: it does not work for all designs with index pages that use the subpages/sections inside the main navigation.
  11. As i wrote in the article - you have to adapt injections points per layout.I have a developped a version of the script for multiple layouts and it will be adapted for each derivative sub layout. Pls contact me for conditions. And see post below - techically this cannot work for onepager designs, where section pages are used for main navigation.
  12. @octopus - I agree with some points but not with all. The "ridiculously bloated" code could be written shorter. But it is readable and understandable. If you have ideas to improve it - don't hesitate to post your ideas. Whats wrong with duplication - SQS does the same. It is not the best technically. It does not offer side by side translation. You can create each language with a different structure. Right, blog elements not translated - easy to map them in js or use css. Answers are here in the forum. (I did not use the blog in the sample project).
  13. Hallo @hausecec Template FIVE Adaptions You need to adapt the Javascript as described in f) as each template has another html structure. You need to adapt the CSS as stated in the post as each template has another html structure Adaption of Javascript a) Change the selector variable. Because i cannot see in the five demo if there is a secondary navigation, perhaps you need to add the code for the secondary navigation if you need a multilingual secondary nav. var selector = [ '#mainNavigation > ul > li > a:not([data-href*=\"/' + language + '/\"])', '#mobileNavigation > ul > li > label:not([data-href*=\"/' + language + '/\"])', '#mobileNavigation > ul > li > a:not([href*=\"/' + language + '/\"])' ]; b) Change the output injections point in case you want to use the dropdown menu: you have to try this out and you have to adapt the css for the injection point. // output: append to main and mobile navigation if(output){ Y.one('#page-header-wrapper').append(buildLanguageMenuHTML(language, allowedLanguages, 'right top')); } Adaption of CSS You need to adapt the css for the injection point. #page-header-wrapper #langNavigation .folder-toggle-label{ background: #1d1a1a; border-radius: 50px; padding: 0; line-height: 3em; width: 3em; } #page-header-wrapper #langNavigation.top{ top:-3px; }
  14. There is a much easier way, using the same technique.A lot of multilingual websites use the iso-2 code to differ the urls, e.g. /de/url or /en/url oder de/ordner/seite and en/folder/page. Using this technique together with YUI/JS manipulation is much more robust and does not depend on Ids. It just depends on manipulated Url slugs and a properly configured script: Works for main and secondary nav, mobile nav, layered nav Script remains the same and detects new and deleted pages or modified pages. Script autmatically set html lang tags Script does not depend on order of pages or ids. Script optionally produces a fully styleable and adaptable language menu Script is configurable for each template Script works for all page types: page, collections, links, blogs all you have to do is define url slugs. I wrote a tutorial for this, take a look here:https://answers.squarespace.com/questions/124120/how-to-build-a-multilingual-site-in-squarespace-7.html
  15. This code was used together with the PACIFIC template. The configured selectors have to be adapted for other templates. If anyone uses this code with other templates please post the selectors here. Any improvements are welcome. Thank you.
×
×
  • Create New...