Lol sorry for bombarding this repo with so many issues. I'm leveraging the SSI variant in a sandbox for something I'm working on and reporting issues as I stumble upon them.

Anyways, try this out:

1. Create a folder under /demos/ssi/ (such as /demos/ssi/subfolder/)
2. Copy over a content page template (such as cont-eng.shtm) into the subfolder.
3. Make another copy of cont-eng.shtm, rename it to index.shtm, and place it in the subfolder
4. Open up /demos/ssi/subfolder/cont-eng.shtm

If your test has the same outcome as mine, in step 4 you'll see what looks like the subfolder's index.shtm page's HTML code getting pulled in like 5 times over where the breadcrumb should be :O. The culprit seems to be something within bt-fa.shtm.

Thanks :).

PS: This may be related to issue #13.

Hi,

I happened to notice that some of the SSI variant's multilingual splash page templates seem to be missing content (compared to what's in the main repository).

Specifically, the English/French multilingual splash page is missing "Terms and conditions"/"Avis" links for the other languages.

As for the French/English multilingual splash page, it doesn't seem to currently contain any multilingual content (looks like a mirror of the standard French/English splash page's content).

Links (for reference):

• English/French example - Multilingual
• (wet-boew) http://wet-boew.github.com/wet-boew/demos/theme-gcwu-fegc/sp-pe-mult-eng-fra.html
• (wet-boew-ssi) http://wet-boew.pub.rcmp-grc.gc.ca/demos-ssi/theme-gcwu-fegc/sp-pe-mult-theme-gcwu-fegc-eng-fra.shtm
• French/English example - Multilingual
• (wet-boew) http://wet-boew.github.com/wet-boew/demos/theme-gcwu-fegc/sp-pe-mult-fra-eng.html
• (wet-boew-ssi) http://wet-boew.pub.rcmp-grc.gc.ca/demos-ssi/theme-gcwu-fegc/sp-pe-mult-theme-gcwu-fegc-fra-eng.shtm

Thanks :).

@jeffdavidgordon @MaddyDaigle We need to send the SSI variant to the working groups soon to ensure there is enough time for testing before the WET v3.0 release in September. Please set up working examples that can be shared with the working groups for testing purposes.

Hi there,

Is this project still supported to some degree?

I would like to test it with NGINX, and to ask if it can be adapted easily to use the GCWeb theme given that the GOC sites are all moving to that theme.

Thank you,
Dustin

WET core is AJAXing in the mega menus to save around 5 - 6 kb of downloads per page (so cached independently). Noticed that you are instead using a server-side include so the mega menu can't be cached separately. Should use the AJAXing approach rather than a server-side approach to maximize caching potential.

I'm in the process of moving from 3.1.x to 4.0.4 using the latest master of wet-boew-ssi and documenting a migration guide.

The demos work fine, but for our site, I want to have http://example.com/eng/index.shtm and http://example.com/fra/index.shtm, rather than the index-${pg-lang1}.shtm. Is that easy to configure?

I tried it but the include regex seems to want to navigate down and include all index*.shtm, which ends up in an endless loop of inclusions if I rename index-${pg-lang1}.shtm to just index.shtm.

Building the site such that it's transparent to update the dist-ssi and dist-gcwu-fegc directories is easy, but if there are viable updates in the demos-ssi (What sites would be built from), then it would be nice to get those, too. It may not be feasible though, I'm not sure. Any suggestions?

Many thanks,
Dustin

@pjackson28 Just a note about adding the inc files into the build as I think I mentioned this a few weeks ago. Should we be putting the base inc files (which apply to all pages in the gcwu theme) in the src folder as part of the build process, or should it remain outside the build? If yes, I can get it working for the next stable release if you'd like.

Hi,

Check out the "Welcome"/"Bievenue" breadcrumb link in any standard content page template (such as cont-eng.shtm). They seem to point to the same page that the user is already on. I presume they're meant to point to index.shtml?

PS: I think the trail in these kinds of breadcrumbs typically start off with a "Home" link to a home page template (as opposed to a "Welcome"/splash page link), since the user's preferred language has already been established if they've on a content page.

Thanks :).

Now that we are approaching WET v4.0, we will be aligning with i18n conventions and changing our file name suffixes from eng/fra to en/fr. If you use eng/fra suffixes for any of your files then please migrate to the en/fr suffixes at your convenience.

To ensure you don't disrupt search engine results, please use either 301 redirects or canonical rels to help search engines transiton from providing results with eng/fra to en/fr (WET core is using canonical rels because GitHub gh-pages doesn't support 301 redirects).

The HTML5 spec doesn't support "none" for the robots metadata so please use "noindex, nofollow, noarchive" instead.

@MaddyDaigle, @jeffdavidgordon

To get language toggling working in the SSI variant's applicable working example pages, what would you think of something like this?

1. Remove gc-cmblang-href-eng and gc-cmblang-href-fra's declarations from /demos/ssi/config.shtm.
2. Set a variable such as pg-alt-lang-path directly within page content alongside the declarations for the other pg-... variables.
3. Adjust header-entete.shtm accordingly.

I could send in a pull request with the aforementioned changes soon-ish if everyone's on board.

Thanks :).

Hi there,
I'm very anxious to try version 4.0 of both the SSI and the main WET GCWU theme.

The documentation has two lines in it, but it's not clear how they connect. Meaning, I'm running a Debian server, and my document root is /var/www/html. In there I have a dist link that points to the wet-boew-dist-4.0.0-rc1 directory, and a dist-ssi that points to the wet-boew-ssi-4.0/dist-ssi directory. I also have a themes-dist/theme-gcwu-fegc link that points to the themes-dist-4.0.0-rc1-theme-gcwu-fegc directory.

Do I have everything in place? I also have a demos-ssi link in my document root that points to the wetb-boew-ssi-4.0/demos-ssi, but it doesn't run properly since the dist-ssi/subsite.shtm is looking for /index.shtm, which isn't in the root. In short, here is my setup:

/var/www/html (Document Root)
demos-ssi -> wet-boew-ssi-4.0/demos-ssi
dist -> wet-boew-dist-4.0.0-rc1
dist-ssi -> wet-boew-ssi-4.0/dist-ssi
themes-dist/theme-gcwu-fegc -> themes-dist-4.0.0-rc1-theme-gcwu-fegc
themes-dist-4.0.0-rc1-theme-gcwu-fegc/
wet-boew-dist-4.0.0-rc1/
wet-boew-ssi-4.0/

Could you please provide a bit more info to the installation?

Much obliged, and thanks for the work on this.
Dustin

The supporting files are really out of date so please refresh them along with the SSI files after fixing issue #5.

Hi there,

For pages with no left menu, the

I think it should be wrapped in a div with class="container" like here:
http://wet-boew.github.io/themes-dist/theme-gcwu-fegc/content-secmenu-et.html

Thanks!
Dustin

There were a lot of external links in WET core that did not have rel="external" so make rel="external" is added to each of your external links in your variant.

All the links to the SSI working examples at http://wet-boew.github.com/wet-boew/demos/ssi/index-eng.html are broken. Please fix the links and/or the working examples.

Hey @jeffdavidgordon,

I've recently noticed that all the SSI variant links on http://wet-boew.github.io/v3.1-ci/demos/ssi/index-en.html are no longer functioning, possibly due to a bad redirect on the RCMP site.

For example:
http://wet-boew.pub.rcmp-grc.gc.ca/demos/ssi/cont-eng.shtm
redirects to
http://www.rcmp-grc.gc.ca/demos/ssi/cont-eng.shtm.

Any chance this could be looked into/resolved?

Thanks :).

The current 4.0 Alpha versions with the released GCWU 4.0 theme does not show the secondary menu (little white icon in the black bar) in mobile view.

Recreate:

• Open GCWU theme in demos-ssi
• Go to mobile view (Shrink window, flip tablet to portrait position, etc.)
• Click on Content page - Secondary menu
• White icon for secondary menu and mega menus is missing.

IIS doesn't support the #if/#else/#endif construct or #set.