Please let us know of any issues you may be experiencing with EES and we will make every attempt to keep the following list up to date so you don't have to go looking. In some cases we may have to provide bug fixes straight away but for the majority of issues they will be addressed as a part of EES phase 2.
Known EES Phase 1 Issues
[list=1]
Issue 1 - Content Screen: div pop ups hidden from view onclick. [Fixed in next release]
[*]Solution/workaround - scroll up the page to find. This issue will be apparent on lengthy scrollable content only.
[*]Issue 2 - Content Screen: When snippets are configured, and the wysiwyg option 'Snippet Keyword Replace' is checked in Global Preferences the content screen won't load.
[list]
[*]Solution/workaround - Disable 'Snippet Keyword Replace' for WYSIWYG Plugins under System Configuration -> Global Preferences.
[/list]
[*]Issue 3 - File Preview: can not navigate back to origin after file upload using browser back button. FF3 specific.
[list]
[*]Solution/workaround - manually change URL. We know this is a big usability issue and will definitely address by end of phase 2.
[/list]
[/list]
I think on the Metadata screen, if there is no metadata applied, it should say so. Right now, mine is just blank. Or is this a bug, and something should be showing?
[quote]
I think on the Metadata screen, if there is no metadata applied, it should say so. Right now, mine is just blank. Or is this a bug, and something should be showing?
[/quote]
This wasn't intended to happen so I've replicated it, and added it to our internal bug tracking.
[quote]
I think on the Metadata screen, if there is no metadata applied, it should say so. Right now, mine is just blank. Or is this a bug, and something should be showing?
[/quote]
What Anthony said. Nice pick up Nic. Not a big issue so won't add to the top of the post listing because it's pretty obvious there is no metadata and the interface does not break , but one that we will include with our next round of fixes.
[quote]
Should the Preview screen show the complete page in the whole window?
Mine displays in a very small scrollable div.
[/quote]
Hey Aleks. We support IE7 & 8, FF3+, Safari 4+ on the PC and Safari 4+ on the Mac, with minimal testing on FF3+ for the Mac. Anything outside of that is at your own risk.
Bear in mind we bring in a lot of existing Matrix data like the WYSIWYG which in itself only supports a few browser/browser versions, so we have to limit our support around that.
[quote]
We support IE7 & 8, FF3+, Safari 4+ on the PC and Safari 4+ on the Mac…
[/quote]
Just curious if there are any plans to support IE6 or Chrome.
I thought Chrome would probably work as it uses the same rendering engine as Safari, but the EES interface doesn't load in Chrome (blank white screen) - maybe a small JS bug.
I can understand if you are considering dropping IE6 support (since EES relies heavily on JavaScript), but would like to remind you that some organisations still tend to use IE6 on employees' desktops (mine included) which means they would have to consider upgrading or installing an alternative browser on the desktops of those using the CMS.
[quote]
Just curious if there are any plans to support IE6.
[/quote]
No! Any time we go out of our way to support IE6, we give those using it no reason to upgrade. We need to clear the web of IE6, for the good of all of us!
[quote]
they would have to consider upgrading or installing an alternative browser on the desktops of those using the CMS.
[/quote]
There is the alternative to install portable apps of Firefox and Chrome. A portable app means you can install into your own home directory without any changes to registry or you do not need sys admin status to install. Find more at www.portableapps.com. Hope that helps anyone :rolleyes:
[quote]
Just curious if there are any plans to support IE6 or Chrome.
I thought Chrome would probably work as it uses the same rendering engine as Safari, but the EES interface doesn't load in Chrome (blank white screen) - maybe a small JS bug.
I can understand if you are considering dropping IE6 support (since EES relies heavily on JavaScript), but would like to remind you that some organisations still tend to use IE6 on employees' desktops (mine included) which means they would have to consider upgrading or installing an alternative browser on the desktops of those using the CMS.
[/quote]
Just say 'No' to IE6 hmmkaayy.
Although it would have been nice to accommodate IE6, with our short time frame to produce EES that requirement would have meant you probably would not have gotten phase 1 until the end of the year, at which time IE6 use would probably be down to less than 3% - woot! EES is a good reason to upgrade your browser :)!
Regarding the no browser support 'continue' link bug (getting blank screen), we are aware of this and will include in phase 2 release with bug fixes for other known issues.
Thanks, I agree with this comment but also wanted to clarify the official stance on IE6 for this project (and Matrix 4, I presume). I am currently in discussion with our IT staff about our browser upgrade options.
[quote]Regarding the no browser support 'continue' link bug (getting blank screen), we are aware of this and will include in phase 2 release with bug fixes for other known issues.[/quote]
Okay, so Chrome may work in the future given that EES is compatible with Safari.
[quote]There is the alternative to install portable apps of Firefox and Chrome.[/quote]
Also, thanks Ben for mentioning portable apps. I hadn't considered this and it may be a less invasive solution for the short-term.
For EES, IE6 will not be supported in the future. Chrome will be supported in the future.
For MySource Mini (which you refer to as Matrix 4), IE6 is not supported and will not be supported in the future. Safari and Chrome are currently not supported but will be supported in the future.
For the MySource Matrix administration interface, IE6 is supported and will continue to be supported in the future.
Should the EES honour the security restrictions set on a group?
I've created a group and assigned restrictions to it - just the basics: page_standard (details, content, metadata). Logging in as the user in the group I go into the admin interface and on the page in question can only see the three screens (in the drop down list) so it's working. I then go to the easy edit interface (EES) and can see all the screens available within it and can view/make changes to those that should be blocked e.g. URL.
To test this further I switched to the Simple Edit interface and it honoured the restrictions by only showing the three screens.
Currently the JS API doesn't tap into the security restrictions of the users group. The screens you see in Easy Edit are not true representations of the screens used in the normal Matrix interface. We will add this to our list of development features.