...
| Question | Answer | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 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 0305/09/2018 - Synergetic are working to add an improvement to both Flex and Community Portal logic, to support v1.1 now supports a blank 'loading' page appearing instead of showing the original Portal display first. This will be released via an updated set of Flex files, and will require a minor update of Synergetic to a newer build to handle this change. More information will be added to this page once the change is finalised.. 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.
| ||||||||||||||||||||
What testing was completed on this? | Each page was tested against Functionality and Usability
| ||||||||||||||||||||
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
|
...