We just released 2.8.1. Please let us know if you see any issues.
We just released [http://moxie.jamessocol.com/bugstats/sumo/2.8.1 2.8.1]. Please let us know if you see any issues.
SUMO community discussions
SUMO 2.8.1 just went out
-
-
The previewing error is displayed in each English or French articles I edited and tried to preview.
In the French reviewers dashboard (2.8.2), the German most visited & unreviewed articles are displayed.
The '''previewing error''' is displayed in each English or French articles I edited and tried to preview. In the [https://support-release.allizom.org/fr/dashboard/5 French reviewers dashboard] (2.8.2), the German most visited & unreviewed articles are displayed. -
"Previewing error"? Can you be more specific?
The dashboard on support-release that you linked to is actually just called "Reviewers" and should be in German--that's how it's configured in the admin.
"Previewing error"? Can you be more specific? The dashboard on support-release that you linked to is actually just called "Reviewers" and should be in German--that's how it's configured in the admin. -
jsocol said
"Previewing error"? Can you be more specific?
The error is: "There was an error generating the preview".
Click the Preview button for instance on https://support.mozilla.com/en-US/kb/Firefox%20crashes/edit or on any other KB articles.
The dashboard on support-release that you linked to is actually just called "Reviewers" and should be in German--that's how it's configured in the admin.
Here is an extract from the Users & Groups PRD: "For example, "Contributors" may all be people who work on the KB but some work on English articles and some localize those articles into German. Those contributors can all have the same permissions (from the Contributors group) but we can also put them in en-us and de groups. Putting them in those locale groups would give them access to that group's dashboard."
Kadir took the example of German contributors because it is German, but by default, the Group dashboard (Reviewer button) of a contributor should be for the language defined in the profile (Preferred language for email). If the defined language is English, it should not be displayed.
''jsocol [[#post-31302|said]]'' <blockquote> "Previewing error"? Can you be more specific?</blockquote> The error is: "''There was an error generating the preview''". Click the Preview button for instance on https://support.mozilla.com/en-US/kb/Firefox%20crashes/edit or on any other KB articles. <blockquote> The dashboard on support-release that you linked to is actually just called "Reviewers" and should be in German--that's how it's configured in the admin.</blockquote> Here is an extract from the [https://wiki.mozilla.org/Support/Kitsune/Users_and_Groups Users & Groups PRD]: "''For example, "Contributors" may all be people who work on the KB but some work on English articles and some localize those articles into German. Those contributors can all have the same permissions (from the Contributors group) but we can also put them in en-us and de groups. Putting them in those locale groups would give them access to that group's dashboard.''" Kadir took the example of German contributors because it is German, but by default, the Group dashboard (Reviewer button) of a contributor should be for the language defined in the profile (Preferred language for email). If the defined language is English, it should not be displayed. -
OK, article previewing I can repro and have a lead on.
As for the group dashboards, let me explain a little about how they work:
- A dashboard is connected to a group. That is, if you are a member of a group, and that group has an associated dashboard, you can see it. So, if you are in a "Contributors" group (which doesn't exist right now) you can see the Contributors group's dashboard (if it has one). (And you inherit any permissions granted to the Contributors group.)
- There are multiple types of dashboards. Right now we have two, a
LocaleDashboardand aQuestionsDashboard. So each Dashboard belongs to a group, and has a type. - Some types of dashboards are configurable. For example, the
LocaleDashboardtakes alocaleargument to tell it which locale to find content for. This configuration is per group. So, for example, the "German Contributors" group and the "French Contributors" group would both use aLocaleDashboard, but with differentlocalevalues (de and fr, respectively). Again, these groups do not exist right now. - Dashboards will have UI in whatever language the site is: e.g., if you find the "German Contributor" group's dashboard at
/dashboard/5, then going to/de/dashboard/5will put the dashboard's UI in German, but/fr/dashboard/5will put the UI in French. However, in the case ofLocaleDashboards, the content is not determined by the UI, but by the value of thatlocaleparameter.
To illustrate the last point, the group whose dashboard you linked to is not called "French reviewers," just "Reviewers," and it's
localeparam is set to de. The UI is in French because you went to/fr/dashboard/5. It can just as easily be in German. But the content doesn't vary.Also, keep in mind that anything in the database of a staging server (including groups, group memberships, group dashboards, all content, permissions, etc) has no bearing on production. We change things just to test that changes work and don't usually bother changing them back.
OK, article previewing I can repro and have a lead on. As for the group dashboards, let me explain a little about how they work: # A dashboard is connected to a group. That is, if you are a member of a group, and that group has an associated dashboard, you can see it. So, if you are in a "Contributors" group (which doesn't exist right now) you can see the Contributors group's dashboard (if it has one). (And you inherit any permissions granted to the Contributors group.) # There are multiple ''types'' of dashboards. Right now we have two, a <code>LocaleDashboard</code> and a <code>QuestionsDashboard</code>. So each Dashboard ''belongs to'' a group, and ''has'' a type. # Some ''types'' of dashboards are configurable. For example, the <code>LocaleDashboard</code> takes a <code>locale</code> argument to tell it which locale to find content for. This configuration is ''per group''. So, for example, the "German Contributors" group and the "French Contributors" group would both use a <code>LocaleDashboard</code>, but with different <code>locale</code> values (''de'' and ''fr'', respectively). Again, these groups ''do not exist'' right now. # Dashboards will have UI in whatever language the site is: e.g., if you find the "German Contributor" group's dashboard at <code>/dashboard/5</code>, then going to <code>/de/dashboard/5</code> will put the dashboard's UI in German, but <code>/fr/dashboard/5</code> will put the UI in French. ''However'', in the case of <code>LocaleDashboard</code>s, the ''content'' is '''not''' determined by the UI, but by the value of that <code>locale</code> parameter. To illustrate the last point, the group whose dashboard you linked to is not called "French reviewers," just "Reviewers," and it's <code>locale</code> param is set to ''de''. The ''UI'' is in French because you went to <code>/fr/dashboard/5</code>. It can [https://support-release.allizom.org/de/dashboard/5 just as easily be in German]. But the content doesn't vary. Also, keep in mind that anything in the database of a ''staging'' server (including groups, group memberships, group dashboards, all content, permissions, etc) has no bearing on production. We change things just to test that changes work and don't usually bother changing them back. -
I'm curious:
Has marking threads on the support forum as solved been disabled?I've seen a few threads were people wrote that clicking the "Solved it" button give a Access Denied error.
I'm curious: <br /> Has marking threads on the support forum as solved been disabled? I've seen a few threads were people wrote that clicking the "Solved it" button give a Access Denied error. * [/questions/817567] * [/questions/815730] * [/questions/816804]Modified by cor-el on
-
jsocol said
OK, article previewing I can repro and have a lead on.
It won't be possible to edit any article before the release of SUMO 2.8.2. This important feature (and may be others) should be tested automatically for each release.
As for the group dashboards, let me explain a little about how they work
Thanks for the explanation. It is now clear for me.
''jsocol [[#post-31395|said]]'' <blockquote> OK, article previewing I can repro and have a lead on.</blockquote> It won't be possible to edit any article before the release of [http://moxie.jamessocol.com/bugstats/sumo/2.8.2 SUMO 2.8.2]. This important feature (and may be others) should be tested automatically for each release. <blockquote> As for the group dashboards, let me explain a little about how they work</blockquote> Thanks for the explanation. It is now clear for me. -
Click the Edit Article button on http://support.mozilla.com/en-US/kb/Firefox%20crashes, enter your login and password, then click the Log-in button. An Access Denied error is displayed. You need to click again the Log-in button to log in.
Click the Edit Article button on http://support.mozilla.com/en-US/kb/Firefox%20crashes, enter your login and password, then click the Log-in button. An Access Denied error is displayed. You need to click again the Log-in button to log in. -
We're working to fix previews ASAP. I agree that it should be part of our automated coverage. We made a necessary change for security and now we're seeing some gaps in our coverage from it. We will work to address those.
Thanks for that report, Cor-el. Looking into it now.
I'll also look into logging in via the 'Edit Page' link.
We're working to fix previews ASAP. I agree that it should be part of our automated coverage. We made a necessary change for security and now we're seeing some gaps in our coverage from it. We will work to address those. Thanks for that report, Cor-el. Looking into it now. I'll also look into logging in via the 'Edit Page' link. -
Thanks for bringing these issues to our attention! You all are a really key part of our (sumo-dev's) feedback loop and you will become even more important in the future.
We'll be pushing out a hotfix resolving article preview and marking questions solved as soon as all our test runs pass.
Thanks for bringing these issues to our attention! You all are a really key part of our (sumo-dev's) feedback loop and you will become even more important in the future. We'll be pushing out a hotfix resolving article preview and marking questions solved as soon as all our test runs pass. -
We've pushed 2.8.1.2 and the Article Preview and Question Solving issues are resolved.
Thanks again for the reports!
We've pushed 2.8.1.2 and the [https://bugzilla.mozilla.org/show_bug.cgi?id=654827 Article Preview] and [https://bugzilla.mozilla.org/show_bug.cgi?id=655006 Question Solving] issues are resolved. Thanks again for the reports! -
cor-el said
I'm curious:
Has marking threads on the support forum as solved been disabled? I've seen a few threads were people wrote that clicking the "Solved it" button give a Access Denied error.I just tried it and didn't see any problem. But I just got a "Access denied" when I tried to post this reply for the first time.
James, could that be related to our latest change of tokens?
''cor-el [[#post-31397|said]]'' <blockquote> I'm curious: <br /> Has marking threads on the support forum as solved been disabled? I've seen a few threads were people wrote that clicking the "Solved it" button give a Access Denied error. * [/questions/817567] * [/questions/815730] * [/questions/816804] </blockquote> I just tried it and didn't see any problem. But I just got a "Access denied" when I tried to post this reply for the first time. James, could that be related to our latest change of tokens? -
KadirTopal said
I just tried it and didn't see any problem.
We pushed the fix for that yesterday morning.
But I just got a "Access denied" when I tried to post this reply for the first time. James, could that be related to our latest change of tokens?
That's likely because you had an old session with an old token. You should be fine now.
''KadirTopal [[#post-32016|said]]'' <blockquote> I just tried it and didn't see any problem.</blockquote> We pushed the fix for that yesterday morning. <blockquote>But I just got a "Access denied" when I tried to post this reply for the first time. James, could that be related to our latest change of tokens? </blockquote> That's likely because you had an old session with an old token. You should be fine now. -
Is it possible to update the server that host the CSS file used in https://github.com/jsocol/kitsune/ (d3nwyuy0nl342s.cloudfront.net) to use a more modern cipher?
Currently d3nwyuy0nl342s.cloudfront.net only supports security.ssl3.rsa_rc4_128_md5
I have disabled all 128 bit and other weak Diffie-Hellman ciphers, so the stylesheet isn't loaded unless I enable that pref. Most other servers switch to an 168 bit or better cipher.
Is it possible to update the server that host the CSS file used in ''https://github<i></i>.com/jsocol/kitsune/'' (<b>d3nwyuy0nl342s<i></i>.cloudfront<i></i>.net</b>) to use a more modern cipher? Currently <b>d3nwyuy0nl342s<i></i>.cloudfront<i></i>.net</b> only supports security.ssl3.rsa_rc4_128_md5 I have disabled all 128 bit and other weak Diffie-Hellman ciphers, so the stylesheet isn't loaded unless I enable that pref. Most other servers switch to an 168 bit or better cipher. -
I don't know if it has been introduced by SUMO 2.8.1, but if the Review button is selected in my dashboard everything in the page is bold except the first posts until this post which is the only one with bold characters. If I click My Profile or Edit My Profile buttons, everything become OK again.
I don't know if it has been introduced by SUMO 2.8.1, but if the Review button is selected in my dashboard everything in the page is bold except the first posts until [/forums/contributors/706222#post-32163 this post] which is the only one with bold characters. If I click My Profile or Edit My Profile buttons, everything become OK again. -
@Scoobi, can you file that, please?
@cor-el, do you mean the server that Github uses to host their own CSS? We have no control over that at all, and since it's on CloudFront, you'd probably have to talk to Amazon. You could file a Github support request.
@Scoobi, can you file that, please? @cor-el, do you mean the server that Github uses to host their own CSS? We have no control over that at all, and since it's on CloudFront, you'd probably have to talk to Amazon. You could file a [http://support.github.com/ Github support request]. -
''jsocol [[#post-32340|said]]'' <blockquote> @Scoobi, can you file that, please? </blockquote> I filed [https://bugzilla.mozilla.org/show_bug.cgi?id=655965 bug 655965].