Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Introduction:

Flex is a new theme created by Synergetic, to create a responsive and more usable experience for users on mobile and smaller devices. It provides advanced layout techniques to repaint the current look and feel of the whole website.

...

  • Upgrade to a minimum version of 68.35 or 69.07
  • Remove or test any additional site CSS changes you have made (..\Site\CSS)
  • Use Chrome, Firefox or Safari (Mac/iOS) web browsers
  • Student Results page
    • If displaying Markbook, check configuration key (CommunityPortal | Students | Results | Markbook | DisplayMode)
      • Best look is DisplayMode: 2
      • It is NOT recommended to have the following keys as TRUE due to display on phone/tables
        • CommunityPortal | Students | Results | Markbook | ShowMarkOutOfFlag
        • CommunityPortal | Students | Results | Markbook | ShowResultTypeFlag
        • CommunityPortal | Students | Results | Markbook | ShowWeightingFlag
  • Events page
    • If pagination active, when attempting to select a button (right side of grid) in most cases the screen will select the next page

      • Recommendation to increase size of paging (CommunityPortal|Events|Paging|Size)

FAQ

QuestionAnswer

Users are not seeing the reported fixes?

  • JavaScript changes
  • Refresh Browser

In some cases, where resolution requires a JavaScript code fix users may be required to refresh their browser cache.

We will recognise this and notify where a JavaScript change has been made in Flex - Download and Installation

Synergetic has actively used JavaScript in its products for many years. The refresh is not required as it is handled by versioning for each suite release. If you receive a new version of the Synergetic Community Portal the detection of new JavaScript would be identified without users needing to do anything. As Flex is custom code outside of the normal supported suite, users are required to refresh their cache or a a new version of the Community Portal is deployed to your site.

A useful article on how to refresh the cache in multiple environments: https://en.wikipedia.org/wiki/Wikipedia:Bypass_your_cache

(source: Wikipedia)Bypassing your cache means forcing your web browser to re-download a web page from scratch, which can often solve website display glitches. It is also required after installing user scripts. Bypassing your cache is simple, safe, and causes no permanent changes.

How is this supported?

At present, this is treated as custom functionality and will fall outside of standard product support.

Feedback or suggestions can be shared in Discourse - Synergetic may review and consider feedback for potential inclusion in future revisions of this custom content.

See Flex - Responsive Community Portal skin for updates

Why is there an initial display of the original Portal then the new Flex skin applied?

This is due to the Flex CSS being a skin on top of the original Community Portal.  It was implemented this way to provide clients with a responsive Portal in rapid time, without requiring a high degree of change to the original code. In essence the 'regular' Community Portal page loads, then the Flex style overrides this display a moment later.

Update 05/09/2018 - v1.1 now supports a blank 'loading' page appearing instead of showing the original Portal display. These files are backwards compatible (v68.35+/v69.07+) but the initial display of the original Portal skin will continue to show until the Community Portal is upgraded to v68.37+/v68.09+

Will my Community Portal page configuration and security settings be affected?No - As the regular Community Portal logic loads the page first before the Flex style overlays, your user/role based security and page configuration settings will be respected.

Why is this placed in the ..\Site\Flex folder and not in ..\Site\CSS folder to avoid the initial load of the non-flexible?

Due to some browsers code base not supporting this (for example Internet Explorer/Edge) detection of the browser is required.  If it was placed in the Site\CSS folder it would apply to all browsers and would have unpredictable behaviour.

Can I make further changes to this?

Yes, see Customisation

I have the Pacific - A Community Portal CSS Theme applied?

It is highly recommended to remove this theme as there will be clashes between the two.

  • A simple way to remove this but retain the file for reference (if your own further custom changes were made) would be to append the file name, e.g. rename site.css to site.css.OldPacific
  • Please retest against at least IE/Edge (non-flex supported browsers) and Chrome/Firefox/Safari (flex supported browsers)

What testing was completed on this?

Each page was tested against Functionality and Usability

  • Functionality
  • Usability
DeviceOperating System
ChromeWindows
FirefoxWindows
IEWindows
EdgeWindows
iPhoneiOS
iPadiOS
Samsung GalaxyAndroid
Samsung TabletAndroid
SafariMacOS


Is there an easy way to see how it would look on most devices?

Many browsers can emulate the look and feel of multiple devices.  Below is one way to do this using the Chrome browser

Please note: This is emulation and not exactly true to how the actual device will operate

  • Open the Chrome desktop browser 
  • Access your Community Portal URL
  • Press F12 to open the Developer Tools
  • You can change where this docked window appears by locating the three dots and selecting an appropriate 'Dock side'

    • Select the following Icon (Ctrl + Shift + M) to display the Device Toolbar

    • Using the drop down you can emulate many devices

...