[jira] [Commented] (OPENMEETINGS-2010) Private chats will not be removed
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16766888#comment-16766888 ] Maxim Solodovnik commented on OPENMEETINGS-2010: Hello [~p_daehn], right now all personal chats with messages not older than 1 hour are being displayed to the user on enter to OM. This is done on purpose, same chat tabs will be opened in case browser window will be reloaded. I can add the code to close personal chat on room exit, would it be OK? > Private chats will not be removed > - > > Key: OPENMEETINGS-2010 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2010 > Project: Openmeetings > Issue Type: Improvement > Components: Chat >Affects Versions: 4.0.7 >Reporter: Peter Dähn >Assignee: Maxim Solodovnik >Priority: Minor > > If a private chat is open it will be shown to the (2) participants in the > chat panel even if they left the room or log out and in again. > It would be better to bind this to the room, where it is open as to let it > "follow" the user. And I think it should be closed after one participant left > the room. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (OPENMEETINGS-1996) If the list of activity notifications is collapsed, mods do not get any information about incoming requests
[ https://issues.apache.org/jira/browse/OPENMEETINGS-1996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Solodovnik resolved OPENMEETINGS-1996. Resolution: Fixed > If the list of activity notifications is collapsed, mods do not get any > information about incoming requests > --- > > Key: OPENMEETINGS-1996 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-1996 > Project: Openmeetings > Issue Type: Improvement > Components: UI >Affects Versions: 4.0.7 >Reporter: Peter Dähn >Assignee: Maxim Solodovnik >Priority: Minor > Fix For: 4.0.8 > > > A badge would be useful. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[openmeetings] branch master updated: [OPENMEETINGS-1996] badge for action is added
This is an automated email from the ASF dual-hosted git repository.
solomax pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/openmeetings.git
The following commit(s) were added to refs/heads/master by this push:
new 8044dca [OPENMEETINGS-1996] badge for action is added
8044dca is described below
commit 8044dca06c7c0758b2c38ba565a4c6f8f500d81b
Author: Maxim Solodovnik
AuthorDate: Wed Feb 13 13:59:43 2019 +0700
[OPENMEETINGS-1996] badge for action is added
---
.../apache/openmeetings/web/room/activities/ActivitiesPanel.html | 6 +-
.../org/apache/openmeetings/web/room/activities/activities.js | 8
openmeetings-web/src/main/webapp/css/raw-activities.css | 1 -
3 files changed, 13 insertions(+), 2 deletions(-)
diff --git
a/openmeetings-web/src/main/java/org/apache/openmeetings/web/room/activities/ActivitiesPanel.html
b/openmeetings-web/src/main/java/org/apache/openmeetings/web/room/activities/ActivitiesPanel.html
index ddaed09..4a1ea8c 100644
---
a/openmeetings-web/src/main/java/org/apache/openmeetings/web/room/activities/ActivitiesPanel.html
+++
b/openmeetings-web/src/main/java/org/apache/openmeetings/web/room/activities/ActivitiesPanel.html
@@ -21,7 +21,11 @@
http://wicket.apache.org;>
-
+
+
+ 42
+
+
diff --git
a/openmeetings-web/src/main/java/org/apache/openmeetings/web/room/activities/activities.js
b/openmeetings-web/src/main/java/org/apache/openmeetings/web/room/activities/activities.js
index 6ccbb04..f97dc53 100644
---
a/openmeetings-web/src/main/java/org/apache/openmeetings/web/room/activities/activities.js
+++
b/openmeetings-web/src/main/java/org/apache/openmeetings/web/room/activities/activities.js
@@ -86,12 +86,17 @@ var Activities = function() {
}
function _remove(id) {
$('#' + _getId(id)).remove();
+ _updateCount();
}
function _clearItem(id) {
if (aclean.prop('checked')) {
_remove(id);
}
}
+ function _updateCount() {
+ if (!inited) return;
+ $('.control.block .badge',
activities).text(modArea.find('.activity').length);
+ }
return {
init: function() {
@@ -123,6 +128,7 @@ var Activities = function() {
});
_updateClean(_load(), aclean);
inited = true;
+ _updateCount();
}
, toggle: function() {
if (!inited) {
@@ -163,6 +169,7 @@ var Activities = function() {
}
a.find('.activity-close').click(function() {
a.remove();
+ _updateCount();
_action('close', obj.id);
});
a.find('.activity-text').text(obj.text);
@@ -170,6 +177,7 @@ var Activities = function() {
if (aclean.prop('checked') && a.hasClass('auto-clean'))
{
setTimeout(_clearItem.bind(null, obj.id),
timeout);
}
+ _updateCount();
}
, remove: _remove
};
diff --git a/openmeetings-web/src/main/webapp/css/raw-activities.css
b/openmeetings-web/src/main/webapp/css/raw-activities.css
index ff9ecac..a53714d 100644
--- a/openmeetings-web/src/main/webapp/css/raw-activities.css
+++ b/openmeetings-web/src/main/webapp/css/raw-activities.css
@@ -31,7 +31,6 @@
}
#activities .control.block .label {
display: inline-block;
- padding-left: 20px;
text-overflow: ellipsis;
white-space: nowrap;
}
[jira] [Commented] (OPENMEETINGS-1996) If the list of activity notifications is collapsed, mods do not get any information about incoming requests
[ https://issues.apache.org/jira/browse/OPENMEETINGS-1996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16766861#comment-16766861 ] ASF subversion and git services commented on OPENMEETINGS-1996: --- Commit 8044dca06c7c0758b2c38ba565a4c6f8f500d81b in openmeetings's branch refs/heads/master from Maxim Solodovnik [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=8044dca ] [OPENMEETINGS-1996] badge for action is added > If the list of activity notifications is collapsed, mods do not get any > information about incoming requests > --- > > Key: OPENMEETINGS-1996 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-1996 > Project: Openmeetings > Issue Type: Improvement > Components: UI >Affects Versions: 4.0.7 >Reporter: Peter Dähn >Assignee: Maxim Solodovnik >Priority: Minor > Fix For: 4.0.8 > > > A badge would be useful. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[openmeetings] branch 4.0.x updated: [OPENMEETINGS-1996] badge for action is added
This is an automated email from the ASF dual-hosted git repository.
solomax pushed a commit to branch 4.0.x
in repository https://gitbox.apache.org/repos/asf/openmeetings.git
The following commit(s) were added to refs/heads/4.0.x by this push:
new fa38139 [OPENMEETINGS-1996] badge for action is added
fa38139 is described below
commit fa38139e1f3229305b79e3b9d778e3d5aac3dfb1
Author: Maxim Solodovnik
AuthorDate: Wed Feb 13 13:59:43 2019 +0700
[OPENMEETINGS-1996] badge for action is added
---
.../openmeetings/web/room/activities/ActivitiesPanel.html | 6 +-
.../apache/openmeetings/web/room/activities/activities.js | 13 -
openmeetings-web/src/main/webapp/css/raw-activities.css | 1 -
3 files changed, 17 insertions(+), 3 deletions(-)
diff --git
a/openmeetings-web/src/main/java/org/apache/openmeetings/web/room/activities/ActivitiesPanel.html
b/openmeetings-web/src/main/java/org/apache/openmeetings/web/room/activities/ActivitiesPanel.html
index ddaed09..4a1ea8c 100644
---
a/openmeetings-web/src/main/java/org/apache/openmeetings/web/room/activities/ActivitiesPanel.html
+++
b/openmeetings-web/src/main/java/org/apache/openmeetings/web/room/activities/ActivitiesPanel.html
@@ -21,7 +21,11 @@
http://wicket.apache.org;>
-
+
+
+ 42
+
+
diff --git
a/openmeetings-web/src/main/java/org/apache/openmeetings/web/room/activities/activities.js
b/openmeetings-web/src/main/java/org/apache/openmeetings/web/room/activities/activities.js
index 77c8503..3e437c3 100644
---
a/openmeetings-web/src/main/java/org/apache/openmeetings/web/room/activities/activities.js
+++
b/openmeetings-web/src/main/java/org/apache/openmeetings/web/room/activities/activities.js
@@ -84,12 +84,17 @@ var Activities = function() {
}
function _remove(id) {
$('#' + _getId(id)).remove();
+ _updateCount();
}
function _clearItem(id) {
if (aclean.prop('checked')) {
_remove(id);
}
}
+ function _updateCount() {
+ if (!inited) return;
+ $('.control.block .badge',
activities).text(modArea.find('.activity').length);
+ }
return {
init: function() {
@@ -121,6 +126,7 @@ var Activities = function() {
});
_updateClean(_load(), aclean);
inited = true;
+ _updateCount();
}
, toggle: function() {
if (!inited) return;
@@ -155,12 +161,17 @@ var Activities = function() {
} else {
fnd.hide();
}
- a.find('.activity-close').click(function() {
a.remove(); _action('close', obj.id); });
+ a.find('.activity-close').click(function() {
+ a.remove();
+ _updateCount();
+ _action('close', obj.id);
+ });
a.find('.activity-text').text(obj.text);
_hightlight();
if (aclean.prop('checked') && a.hasClass('auto-clean'))
{
setTimeout(_clearItem.bind(null, obj.id),
timeout);
}
+ _updateCount();
}
, remove: _remove
};
diff --git a/openmeetings-web/src/main/webapp/css/raw-activities.css
b/openmeetings-web/src/main/webapp/css/raw-activities.css
index ff9ecac..a53714d 100644
--- a/openmeetings-web/src/main/webapp/css/raw-activities.css
+++ b/openmeetings-web/src/main/webapp/css/raw-activities.css
@@ -31,7 +31,6 @@
}
#activities .control.block .label {
display: inline-block;
- padding-left: 20px;
text-overflow: ellipsis;
white-space: nowrap;
}
[jira] [Commented] (OPENMEETINGS-1996) If the list of activity notifications is collapsed, mods do not get any information about incoming requests
[ https://issues.apache.org/jira/browse/OPENMEETINGS-1996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16766858#comment-16766858 ] ASF subversion and git services commented on OPENMEETINGS-1996: --- Commit fa38139e1f3229305b79e3b9d778e3d5aac3dfb1 in openmeetings's branch refs/heads/4.0.x from Maxim Solodovnik [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=fa38139 ] [OPENMEETINGS-1996] badge for action is added > If the list of activity notifications is collapsed, mods do not get any > information about incoming requests > --- > > Key: OPENMEETINGS-1996 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-1996 > Project: Openmeetings > Issue Type: Improvement > Components: UI >Affects Versions: 4.0.7 >Reporter: Peter Dähn >Assignee: Maxim Solodovnik >Priority: Minor > Fix For: 4.0.8 > > > A badge would be useful. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OPENMEETINGS-2013) Openmeeting screen sharing function not working
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Solodovnik updated OPENMEETINGS-2013: --- Fix Version/s: (was: 4.0.3) > Openmeeting screen sharing function not working > --- > > Key: OPENMEETINGS-2013 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2013 > Project: Openmeetings > Issue Type: Bug > Components: Screen-sharing >Affects Versions: 4.0.3 > Environment: centos / apache open meeting 4.0.3 /mysql >Reporter: sufiyan thakur >Assignee: Maxim Solodovnik >Priority: Critical > Labels: performance > Attachments: jee-container.xml, red5-core.xml, red5.log, > screensharing.log > > > Team, > please help me out. m not able to access screen sharing option in my > openmeeting application. > In error log m not getting logs. but in java advanced console its showing > "pkix path building failed > sun.security.provider.certpath.suncertpathbuilderexception" But we are using > go daddy certificate so no need to occur such errors. > I Have attached log and container file. > pls suggest. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OPENMEETINGS-2013) Openmeeting screen sharing function not working
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16766782#comment-16766782 ] Maxim Solodovnik commented on OPENMEETINGS-2013: Hello [~sufiyan.thakur], As you can see from the log: your request goes to port 8443 (not 5443 or 443) It seems you have 8443 configured in Admin->Config . Please ensure you have valid ports Also check you have full chain of certificates in your keystore.screen file And check this article: https://jfrog.com/knowledge-base/how-to-resolve-unable-to-find-valid-certification-path-to-requested-target-error/ > Openmeeting screen sharing function not working > --- > > Key: OPENMEETINGS-2013 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2013 > Project: Openmeetings > Issue Type: Bug > Components: Screen-sharing >Affects Versions: 4.0.3 > Environment: centos / apache open meeting 4.0.3 /mysql >Reporter: sufiyan thakur >Assignee: Maxim Solodovnik >Priority: Critical > Labels: performance > Fix For: 4.0.3 > > Attachments: jee-container.xml, red5-core.xml, red5.log, > screensharing.log > > > Team, > please help me out. m not able to access screen sharing option in my > openmeeting application. > In error log m not getting logs. but in java advanced console its showing > "pkix path building failed > sun.security.provider.certpath.suncertpathbuilderexception" But we are using > go daddy certificate so no need to occur such errors. > I Have attached log and container file. > pls suggest. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (OPENMEETINGS-2015) Pointer shouldn't be scaled
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Solodovnik resolved OPENMEETINGS-2015. Resolution: Fixed Should be fixed > Pointer shouldn't be scaled > --- > > Key: OPENMEETINGS-2015 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2015 > Project: Openmeetings > Issue Type: Bug > Components: WhiteBoard >Affects Versions: 4.0.7 >Reporter: Peter Dähn >Assignee: Maxim Solodovnik >Priority: Minor > Fix For: 4.0.8 > > Attachments: image-2019-02-08-09-06-40-798.png, > image-2019-02-08-09-08-46-029.png, pointer.mp4 > > > Pointer will be scaled with the whiteboard. This is bad for smaller screens. > Usernames are not readable. One need to guess who used the pointer right now. > !image-2019-02-08-09-06-40-798.png! > !image-2019-02-08-09-08-46-029.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OPENMEETINGS-2015) Pointer shouldn't be scaled
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16766643#comment-16766643 ] ASF subversion and git services commented on OPENMEETINGS-2015: --- Commit 7df4cd90a1385ee55dec2a8fc95b6de676c6e56e in openmeetings's branch refs/heads/master from Maxim Solodovnik [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=7df4cd9 ] [OPENMEETINGS-2015] apointer should be fixed > Pointer shouldn't be scaled > --- > > Key: OPENMEETINGS-2015 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2015 > Project: Openmeetings > Issue Type: Bug > Components: WhiteBoard >Affects Versions: 4.0.7 >Reporter: Peter Dähn >Assignee: Maxim Solodovnik >Priority: Minor > Fix For: 4.0.8 > > Attachments: image-2019-02-08-09-06-40-798.png, > image-2019-02-08-09-08-46-029.png, pointer.mp4 > > > Pointer will be scaled with the whiteboard. This is bad for smaller screens. > Usernames are not readable. One need to guess who used the pointer right now. > !image-2019-02-08-09-06-40-798.png! > !image-2019-02-08-09-08-46-029.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[openmeetings] branch 4.0.x updated: [OPENMEETINGS-2015] apointer should be fixed
This is an automated email from the ASF dual-hosted git repository.
solomax pushed a commit to branch 4.0.x
in repository https://gitbox.apache.org/repos/asf/openmeetings.git
The following commit(s) were added to refs/heads/4.0.x by this push:
new a00e4c6 [OPENMEETINGS-2015] apointer should be fixed
a00e4c6 is described below
commit a00e4c6e3a34d18351dc9e61a09b13e0140cab1d
Author: Maxim Solodovnik
AuthorDate: Wed Feb 13 08:37:33 2019 +0700
[OPENMEETINGS-2015] apointer should be fixed
---
.../src/main/java/org/apache/openmeetings/web/room/wb/raw-wb-board.js | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
a/openmeetings-web/src/main/java/org/apache/openmeetings/web/room/wb/raw-wb-board.js
b/openmeetings-web/src/main/java/org/apache/openmeetings/web/room/wb/raw-wb-board.js
index d9e37de..b5d861b 100644
---
a/openmeetings-web/src/main/java/org/apache/openmeetings/web/room/wb/raw-wb-board.js
+++
b/openmeetings-web/src/main/java/org/apache/openmeetings/web/room/wb/raw-wb-board.js
@@ -801,7 +801,7 @@ var Wb = function() {
}
switch(o.type) {
case 'pointer':
- APointer().create(canvases[o.slide], o);
+ APointer(wb).create(canvases[o.slide],
o);
break;
case 'video':
Player.create(canvases[o.slide], o, wb);
@@ -834,7 +834,7 @@ var Wb = function() {
const o = _arr[i];
switch(o.type) {
case 'pointer':
-
_modifyHandler(APointer().create(canvases[o.slide], o))
+
_modifyHandler(APointer(wb).create(canvases[o.slide], o))
break;
case 'video':
{
[openmeetings] branch master updated: [OPENMEETINGS-2015] apointer should be fixed
This is an automated email from the ASF dual-hosted git repository.
solomax pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/openmeetings.git
The following commit(s) were added to refs/heads/master by this push:
new 7df4cd9 [OPENMEETINGS-2015] apointer should be fixed
7df4cd9 is described below
commit 7df4cd90a1385ee55dec2a8fc95b6de676c6e56e
Author: Maxim Solodovnik
AuthorDate: Wed Feb 13 08:37:33 2019 +0700
[OPENMEETINGS-2015] apointer should be fixed
---
.../src/main/java/org/apache/openmeetings/web/room/wb/raw-wb-board.js | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
a/openmeetings-web/src/main/java/org/apache/openmeetings/web/room/wb/raw-wb-board.js
b/openmeetings-web/src/main/java/org/apache/openmeetings/web/room/wb/raw-wb-board.js
index 2837bfb..9a956d5 100644
---
a/openmeetings-web/src/main/java/org/apache/openmeetings/web/room/wb/raw-wb-board.js
+++
b/openmeetings-web/src/main/java/org/apache/openmeetings/web/room/wb/raw-wb-board.js
@@ -811,7 +811,7 @@ var Wb = function() {
}
switch(o.type) {
case 'pointer':
- APointer().create(canvases[o.slide], o);
+ APointer(wb).create(canvases[o.slide],
o);
break;
case 'video':
Player.create(canvases[o.slide], o, wb);
@@ -844,7 +844,7 @@ var Wb = function() {
const o = _arr[i];
switch(o.type) {
case 'pointer':
-
_modifyHandler(APointer().create(canvases[o.slide], o))
+
_modifyHandler(APointer(wb).create(canvases[o.slide], o))
break;
case 'video':
{
[jira] [Commented] (OPENMEETINGS-2015) Pointer shouldn't be scaled
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16766641#comment-16766641 ] ASF subversion and git services commented on OPENMEETINGS-2015: --- Commit a00e4c6e3a34d18351dc9e61a09b13e0140cab1d in openmeetings's branch refs/heads/4.0.x from Maxim Solodovnik [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=a00e4c6 ] [OPENMEETINGS-2015] apointer should be fixed > Pointer shouldn't be scaled > --- > > Key: OPENMEETINGS-2015 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2015 > Project: Openmeetings > Issue Type: Bug > Components: WhiteBoard >Affects Versions: 4.0.7 >Reporter: Peter Dähn >Assignee: Maxim Solodovnik >Priority: Minor > Fix For: 4.0.8 > > Attachments: image-2019-02-08-09-06-40-798.png, > image-2019-02-08-09-08-46-029.png, pointer.mp4 > > > Pointer will be scaled with the whiteboard. This is bad for smaller screens. > Usernames are not readable. One need to guess who used the pointer right now. > !image-2019-02-08-09-06-40-798.png! > !image-2019-02-08-09-08-46-029.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (OPENMEETINGS-2015) Pointer shouldn't be scaled
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Solodovnik reopened OPENMEETINGS-2015: I'm sure it is broken not by this fix will take a look please reopen JIRAs so we can keep it tracked :) > Pointer shouldn't be scaled > --- > > Key: OPENMEETINGS-2015 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2015 > Project: Openmeetings > Issue Type: Bug > Components: WhiteBoard >Affects Versions: 4.0.7 >Reporter: Peter Dähn >Assignee: Maxim Solodovnik >Priority: Minor > Fix For: 4.0.8 > > Attachments: image-2019-02-08-09-06-40-798.png, > image-2019-02-08-09-08-46-029.png, pointer.mp4 > > > Pointer will be scaled with the whiteboard. This is bad for smaller screens. > Usernames are not readable. One need to guess who used the pointer right now. > !image-2019-02-08-09-06-40-798.png! > !image-2019-02-08-09-08-46-029.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (OPENMEETINGS-1990) Chat timestamps should use the receiver's datetime format
[ https://issues.apache.org/jira/browse/OPENMEETINGS-1990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Solodovnik reopened OPENMEETINGS-1990: I'll reopen to keep it tracked > Chat timestamps should use the receiver's datetime format > - > > Key: OPENMEETINGS-1990 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-1990 > Project: Openmeetings > Issue Type: Bug > Components: Chat >Affects Versions: 4.0.7 >Reporter: Peter Dähn >Assignee: Maxim Solodovnik >Priority: Major > Fix For: 4.0.8 > > Attachments: Auswahl_009.png > > > Currently the timestamp use the sender's date format which leads to different > time formats in the chat list if users with different settings chat in the > same room (mix of DD.MM. und MM/DD, AM/PM/24h) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OPENMEETINGS-2013) Openmeeting screen sharing function not working
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16766151#comment-16766151 ] sufiyan thakur commented on OPENMEETINGS-2013: -- Thanks maxim for your response.. please find my screen sharing log.. https and rtmps protocol both enable.. we are accesing side with URl - virtualmeeting.ril.com. URl hit to netscalar at 443 PORT and through netscalar request goes to backened application server at port 5443. (ssl bridge is there.) we are using RTMPS nattive..refering below URL for RTMPS protocol enabel in our application. https://openmeetings.apache.org/RTMPSAndHTTPS.html [^screensharing.log] > Openmeeting screen sharing function not working > --- > > Key: OPENMEETINGS-2013 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2013 > Project: Openmeetings > Issue Type: Bug > Components: Screen-sharing >Affects Versions: 4.0.3 > Environment: centos / apache open meeting 4.0.3 /mysql >Reporter: sufiyan thakur >Assignee: Maxim Solodovnik >Priority: Critical > Labels: performance > Fix For: 4.0.3 > > Attachments: jee-container.xml, red5-core.xml, red5.log, > screensharing.log > > > Team, > please help me out. m not able to access screen sharing option in my > openmeeting application. > In error log m not getting logs. but in java advanced console its showing > "pkix path building failed > sun.security.provider.certpath.suncertpathbuilderexception" But we are using > go daddy certificate so no need to occur such errors. > I Have attached log and container file. > pls suggest. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OPENMEETINGS-2013) Openmeeting screen sharing function not working
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sufiyan thakur updated OPENMEETINGS-2013: - Attachment: screensharing.log > Openmeeting screen sharing function not working > --- > > Key: OPENMEETINGS-2013 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2013 > Project: Openmeetings > Issue Type: Bug > Components: Screen-sharing >Affects Versions: 4.0.3 > Environment: centos / apache open meeting 4.0.3 /mysql >Reporter: sufiyan thakur >Assignee: Maxim Solodovnik >Priority: Critical > Labels: performance > Fix For: 4.0.3 > > Attachments: jee-container.xml, red5-core.xml, red5.log, > screensharing.log > > > Team, > please help me out. m not able to access screen sharing option in my > openmeeting application. > In error log m not getting logs. but in java advanced console its showing > "pkix path building failed > sun.security.provider.certpath.suncertpathbuilderexception" But we are using > go daddy certificate so no need to occur such errors. > I Have attached log and container file. > pls suggest. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OPENMEETINGS-1990) Chat timestamps should use the receiver's datetime format
[ https://issues.apache.org/jira/browse/OPENMEETINGS-1990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16766148#comment-16766148 ] Maxim Solodovnik commented on OPENMEETINGS-1990: Hello [~p_daehn], what do you mean by "Just if the language is set in profile." ? Date/time format is being determined by language, country and time zone of the user External or not it should be set to some value ... > Chat timestamps should use the receiver's datetime format > - > > Key: OPENMEETINGS-1990 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-1990 > Project: Openmeetings > Issue Type: Bug > Components: Chat >Affects Versions: 4.0.7 >Reporter: Peter Dähn >Assignee: Maxim Solodovnik >Priority: Major > Fix For: 4.0.8 > > Attachments: Auswahl_009.png > > > Currently the timestamp use the sender's date format which leads to different > time formats in the chat list if users with different settings chat in the > same room (mix of DD.MM. und MM/DD, AM/PM/24h) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OPENMEETINGS-1990) Chat timestamps should use the receiver's datetime format
[ https://issues.apache.org/jira/browse/OPENMEETINGS-1990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16766076#comment-16766076 ] Peter Dähn commented on OPENMEETINGS-1990: -- Just if the language is set in prolile. No change for external user. !Auswahl_009.png! > Chat timestamps should use the receiver's datetime format > - > > Key: OPENMEETINGS-1990 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-1990 > Project: Openmeetings > Issue Type: Bug > Components: Chat >Affects Versions: 4.0.7 >Reporter: Peter Dähn >Assignee: Maxim Solodovnik >Priority: Major > Fix For: 4.0.8 > > Attachments: Auswahl_009.png > > > Currently the timestamp use the sender's date format which leads to different > time formats in the chat list if users with different settings chat in the > same room (mix of DD.MM. und MM/DD, AM/PM/24h) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OPENMEETINGS-1990) Chat timestamps should use the receiver's datetime format
[ https://issues.apache.org/jira/browse/OPENMEETINGS-1990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Dähn updated OPENMEETINGS-1990: - Attachment: Auswahl_009.png > Chat timestamps should use the receiver's datetime format > - > > Key: OPENMEETINGS-1990 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-1990 > Project: Openmeetings > Issue Type: Bug > Components: Chat >Affects Versions: 4.0.7 >Reporter: Peter Dähn >Assignee: Maxim Solodovnik >Priority: Major > Fix For: 4.0.8 > > Attachments: Auswahl_009.png > > > Currently the timestamp use the sender's date format which leads to different > time formats in the chat list if users with different settings chat in the > same room (mix of DD.MM. und MM/DD, AM/PM/24h) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OPENMEETINGS-1990) Chat timestamps should use the receiver's datetime format
[ https://issues.apache.org/jira/browse/OPENMEETINGS-1990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16766027#comment-16766027 ] Raphael Fetzer commented on OPENMEETINGS-1990: -- Now works as expected. (y) > Chat timestamps should use the receiver's datetime format > - > > Key: OPENMEETINGS-1990 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-1990 > Project: Openmeetings > Issue Type: Bug > Components: Chat >Affects Versions: 4.0.7 >Reporter: Peter Dähn >Assignee: Maxim Solodovnik >Priority: Major > Fix For: 4.0.8 > > > Currently the timestamp use the sender's date format which leads to different > time formats in the chat list if users with different settings chat in the > same room (mix of DD.MM. und MM/DD, AM/PM/24h) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (OPENMEETINGS-2015) Pointer shouldn't be scaled
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16766006#comment-16766006 ] Peter Dähn edited comment on OPENMEETINGS-2015 at 2/12/19 1:02 PM: --- Hi Maxim, scale is good now, but (sorry for that) not synced with wb's of other user. Greetings Peter [^pointer.mp4] was (Author: p_daehn): Hi Maxim, scale is good now, but (sorry for that) not synced with wb's of other user. Greetings Peter[^pointer.mp4] > Pointer shouldn't be scaled > --- > > Key: OPENMEETINGS-2015 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2015 > Project: Openmeetings > Issue Type: Bug > Components: WhiteBoard >Affects Versions: 4.0.7 >Reporter: Peter Dähn >Assignee: Maxim Solodovnik >Priority: Minor > Fix For: 4.0.8 > > Attachments: image-2019-02-08-09-06-40-798.png, > image-2019-02-08-09-08-46-029.png, pointer.mp4 > > > Pointer will be scaled with the whiteboard. This is bad for smaller screens. > Usernames are not readable. One need to guess who used the pointer right now. > !image-2019-02-08-09-06-40-798.png! > !image-2019-02-08-09-08-46-029.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OPENMEETINGS-2015) Pointer shouldn't be scaled
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16766006#comment-16766006 ] Peter Dähn commented on OPENMEETINGS-2015: -- Hi Maxim, scale is good now, but (sorry for that) not synced with wb's of other user. Greetings Peter[^pointer.mp4] > Pointer shouldn't be scaled > --- > > Key: OPENMEETINGS-2015 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2015 > Project: Openmeetings > Issue Type: Bug > Components: WhiteBoard >Affects Versions: 4.0.7 >Reporter: Peter Dähn >Assignee: Maxim Solodovnik >Priority: Minor > Fix For: 4.0.8 > > Attachments: image-2019-02-08-09-06-40-798.png, > image-2019-02-08-09-08-46-029.png, pointer.mp4 > > > Pointer will be scaled with the whiteboard. This is bad for smaller screens. > Usernames are not readable. One need to guess who used the pointer right now. > !image-2019-02-08-09-06-40-798.png! > !image-2019-02-08-09-08-46-029.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OPENMEETINGS-2015) Pointer shouldn't be scaled
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Dähn updated OPENMEETINGS-2015: - Attachment: pointer.mp4 > Pointer shouldn't be scaled > --- > > Key: OPENMEETINGS-2015 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2015 > Project: Openmeetings > Issue Type: Bug > Components: WhiteBoard >Affects Versions: 4.0.7 >Reporter: Peter Dähn >Assignee: Maxim Solodovnik >Priority: Minor > Fix For: 4.0.8 > > Attachments: image-2019-02-08-09-06-40-798.png, > image-2019-02-08-09-08-46-029.png, pointer.mp4 > > > Pointer will be scaled with the whiteboard. This is bad for smaller screens. > Usernames are not readable. One need to guess who used the pointer right now. > !image-2019-02-08-09-06-40-798.png! > !image-2019-02-08-09-08-46-029.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
