[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 ] Peter Dähn reopened OPENMEETINGS-2015: -- pointer clicks will not shown to others > 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-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, 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-1988) Display the same repeated request for room rights only once
[ https://issues.apache.org/jira/browse/OPENMEETINGS-1988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16766994#comment-16766994 ] ASF subversion and git services commented on OPENMEETINGS-1988: --- Commit f20675e7bb87d4dba17aef8bcf49d3a57a18ddee in openmeetings's branch refs/heads/4.0.x from Maxim Solodovnik [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=f20675e ] [OPENMEETINGS-1988] dublicated action requests are filtered > Display the same repeated request for room rights only once > --- > > Key: OPENMEETINGS-1988 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-1988 > Project: Openmeetings > Issue Type: Bug >Affects Versions: 4.0.7 >Reporter: Peter Dähn >Assignee: Maxim Solodovnik >Priority: Major > Fix For: 4.0.8 > > > If a user happens to request the same right (e.g. mod rights) multiple times > it is possible to "spam" the activity window. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[openmeetings] branch master updated: [OPENMEETINGS-1988] dublicated action requests are filtered
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 8009a74 [OPENMEETINGS-1988] dublicated action requests are filtered
8009a74 is described below
commit 8009a740cac9ae4c68919514bf9c2be30fe1367e
Author: Maxim Solodovnik
AuthorDate: Wed Feb 13 16:50:37 2019 +0700
[OPENMEETINGS-1988] dublicated action requests are filtered
---
.../web/room/activities/ActivitiesPanel.java | 22 ++
.../openmeetings/web/room/activities/activities.js | 8
2 files changed, 22 insertions(+), 8 deletions(-)
diff --git
a/openmeetings-web/src/main/java/org/apache/openmeetings/web/room/activities/ActivitiesPanel.java
b/openmeetings-web/src/main/java/org/apache/openmeetings/web/room/activities/ActivitiesPanel.java
index 043fb8e..b7789d3 100644
---
a/openmeetings-web/src/main/java/org/apache/openmeetings/web/room/activities/ActivitiesPanel.java
+++
b/openmeetings-web/src/main/java/org/apache/openmeetings/web/room/activities/ActivitiesPanel.java
@@ -48,6 +48,7 @@ import org.apache.wicket.spring.injection.annot.SpringBean;
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;
+import com.github.openjson.JSONArray;
import com.github.openjson.JSONObject;
public class ActivitiesPanel extends Panel {
@@ -87,7 +88,7 @@ public class ActivitiesPanel extends Panel {
}
switch (act) {
case close:
- remove(id, target);
+ remove(target, id);
break;
case decline:
if
(room.getClient().hasRight(Right.moderator)) {
@@ -171,6 +172,12 @@ public class ActivitiesPanel extends Panel {
if (shouldSkip(self, a)) {
return;
}
+ if (a.getType().isAction()) {
+ remove(handler, activities.entrySet().parallelStream()
+ .filter(e ->
a.getSender().equals(e.getValue().getSender()) && a.getType() ==
e.getValue().getType())
+ .map(e -> e.getValue().getId())
+ .toArray(String[]::new));
+ }
activities.put(a.getId(), a);
String text = "";
final String name = self ? getString("1362") : a.getName();
@@ -241,9 +248,16 @@ public class ActivitiesPanel extends Panel {
handler.appendJavaScript(new
StringBuilder("Activities.add(").append(aobj.toString()).append(");"));
}
- public void remove(String uid, IPartialPageRequestHandler handler) {
- activities.remove(uid);
-
handler.appendJavaScript(String.format("Activities.remove('%s');", uid));
+ public void remove(IPartialPageRequestHandler handler, String...ids) {
+ if (ids.length < 1) {
+ return;
+ }
+ JSONArray arr = new JSONArray();
+ for (String id : ids) {
+ arr.put(id);
+ activities.remove(id);
+ }
+
handler.appendJavaScript(String.format("Activities.remove(%s);", arr));
}
@Override
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 f97dc53..7ce2d68 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,8 +84,10 @@ var Activities = function() {
function _action(name, val) {
activityAction($('.room.box').data('room-id'), name, val);
}
- function _remove(id) {
- $('#' + _getId(id)).remove();
+ function _remove(ids) {
+ for (let i = 0; i < ids.length; ++i) {
+ $('#' + _getId(ids[i])).remove();
+ }
_updateCount();
}
function _clearItem(id) {
@@ -168,8 +170,6 @@ var Activities = function() {
fnd.hide();
}
a.find('.activity-close').click(function() {
- a.remove();
- _updateCount();
_action('close', obj.id);
});
a.find('.activity-text').text(obj.text);
[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=16766995#comment-16766995 ] Peter Dähn commented on OPENMEETINGS-2010: -- that would be great! > 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] [Commented] (OPENMEETINGS-1988) Display the same repeated request for room rights only once
[ https://issues.apache.org/jira/browse/OPENMEETINGS-1988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16766996#comment-16766996 ] ASF subversion and git services commented on OPENMEETINGS-1988: --- Commit 8009a740cac9ae4c68919514bf9c2be30fe1367e in openmeetings's branch refs/heads/master from Maxim Solodovnik [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=8009a74 ] [OPENMEETINGS-1988] dublicated action requests are filtered > Display the same repeated request for room rights only once > --- > > Key: OPENMEETINGS-1988 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-1988 > Project: Openmeetings > Issue Type: Bug >Affects Versions: 4.0.7 >Reporter: Peter Dähn >Assignee: Maxim Solodovnik >Priority: Major > Fix For: 4.0.8 > > > If a user happens to request the same right (e.g. mod rights) multiple times > it is possible to "spam" the activity window. -- 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=16767000#comment-16767000 ] Peter Dähn commented on OPENMEETINGS-2015: -- 10 Minutes ago and works as expected. > 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] [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 ] Peter Dähn resolved OPENMEETINGS-2015. -- Resolution: 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] [Resolved] (OPENMEETINGS-1988) Display the same repeated request for room rights only once
[ https://issues.apache.org/jira/browse/OPENMEETINGS-1988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Solodovnik resolved OPENMEETINGS-1988. Resolution: Fixed > Display the same repeated request for room rights only once > --- > > Key: OPENMEETINGS-1988 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-1988 > Project: Openmeetings > Issue Type: Bug >Affects Versions: 4.0.7 >Reporter: Peter Dähn >Assignee: Maxim Solodovnik >Priority: Major > Fix For: 4.0.8 > > > If a user happens to request the same right (e.g. mod rights) multiple times > it is possible to "spam" the activity window. -- 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=16767014#comment-16767014 ] Peter Dähn commented on OPENMEETINGS-2015: -- works as expected. thanks! > 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=16766997#comment-16766997 ] Maxim Solodovnik commented on OPENMEETINGS-2015: Hello [~p_daehn] have you checked the most recent build? > 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-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=16766935#comment-16766935 ] Peter Dähn commented on OPENMEETINGS-1990: -- External user get the used language on room entry (1 and 2). This ends up in different languages in the room for them (3 and 4). But the date format in the chat is equal (5 and 6). !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, 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)
[openmeetings] branch 4.0.x updated: [OPENMEETINGS-1988] dublicated action requests are filtered
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 f20675e [OPENMEETINGS-1988] dublicated action requests are filtered
f20675e is described below
commit f20675e7bb87d4dba17aef8bcf49d3a57a18ddee
Author: Maxim Solodovnik
AuthorDate: Wed Feb 13 16:50:37 2019 +0700
[OPENMEETINGS-1988] dublicated action requests are filtered
---
.../web/room/activities/ActivitiesPanel.java | 22 ++
.../openmeetings/web/room/activities/activities.js | 8
2 files changed, 22 insertions(+), 8 deletions(-)
diff --git
a/openmeetings-web/src/main/java/org/apache/openmeetings/web/room/activities/ActivitiesPanel.java
b/openmeetings-web/src/main/java/org/apache/openmeetings/web/room/activities/ActivitiesPanel.java
index 0624b29..c1de34e 100644
---
a/openmeetings-web/src/main/java/org/apache/openmeetings/web/room/activities/ActivitiesPanel.java
+++
b/openmeetings-web/src/main/java/org/apache/openmeetings/web/room/activities/ActivitiesPanel.java
@@ -49,6 +49,7 @@ import
org.apache.wicket.request.resource.JavaScriptResourceReference;
import org.red5.logging.Red5LoggerFactory;
import org.slf4j.Logger;
+import com.github.openjson.JSONArray;
import com.github.openjson.JSONObject;
public class ActivitiesPanel extends Panel {
@@ -88,7 +89,7 @@ public class ActivitiesPanel extends Panel {
}
switch (act) {
case close:
- remove(id, target);
+ remove(target, id);
break;
case decline:
if
(room.getClient().hasRight(Right.moderator)) {
@@ -170,6 +171,12 @@ public class ActivitiesPanel extends Panel {
if (shouldSkip(self, a)) {
return;
}
+ if (a.getType().isAction()) {
+ remove(handler, activities.entrySet().parallelStream()
+ .filter(e ->
a.getSender().equals(e.getValue().getSender()) && a.getType() ==
e.getValue().getType())
+ .map(e -> e.getValue().getId())
+ .toArray(String[]::new));
+ }
activities.put(a.getId(), a);
String text = "";
final String name = self ? getString("1362") : a.getName();
@@ -240,9 +247,16 @@ public class ActivitiesPanel extends Panel {
handler.appendJavaScript(new
StringBuilder("Activities.add(").append(aobj.toString()).append(");"));
}
- public void remove(String uid, IPartialPageRequestHandler handler) {
- activities.remove(uid);
-
handler.appendJavaScript(String.format("Activities.remove('%s');", uid));
+ public void remove(IPartialPageRequestHandler handler, String...ids) {
+ if (ids.length < 1) {
+ return;
+ }
+ JSONArray arr = new JSONArray();
+ for (String id : ids) {
+ arr.put(id);
+ activities.remove(id);
+ }
+
handler.appendJavaScript(String.format("Activities.remove(%s);", arr));
}
@Override
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 3e437c3..3b5563c 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
@@ -82,8 +82,10 @@ var Activities = function() {
function _action(name, val) {
activityAction($('.room.box').data('room-id'), name, val);
}
- function _remove(id) {
- $('#' + _getId(id)).remove();
+ function _remove(ids) {
+ for (let i = 0; i < ids.length; ++i) {
+ $('#' + _getId(ids[i])).remove();
+ }
_updateCount();
}
function _clearItem(id) {
@@ -162,8 +164,6 @@ var Activities = function() {
fnd.hide();
}
a.find('.activity-close').click(function() {
- a.remove();
- _updateCount();
_action('close', obj.id);
});
a.find('.activity-text').text(obj.text);
[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=16767005#comment-16767005
]
Maxim Solodovnik commented on OPENMEETINGS-1990:
Hmm,
As I stated in one of the previous comments format depends on 3 things:
language, country and time zone
Example: English US vs English GB
Could provide me with "language, country and time zone" of your 2 users, so I
can check?
Can be get from DB as follows:
{code}
SELECT ou.language_id, ou.time_zone_id, a.country FROM openmeetings.om_user ou
INNER JOIN openmeetings.address a ON (ou.address_id = a.id)
WHERE ou.id IN (1, 2);
{code}
> 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, 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-1988) Display the same repeated request for room rights only once
[ https://issues.apache.org/jira/browse/OPENMEETINGS-1988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16767030#comment-16767030 ] Peter Dähn commented on OPENMEETINGS-1988: -- I get a build error. [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile (default-compile) on project openmeetings-web: Compilation failure [ERROR] /home/worker/om_bauen/4.0.x/openmeetings-web/src/main/java/org/apache/openmeetings/web/room/sidebar/RoomSidebar.java:[369,27] no suitable method found for remove(java.lang.String,org.apache.wicket.core.request.handler.IPartialPageRequestHandler) [ERROR] method org.apache.wicket.Component.remove(org.apache.wicket.behavior.Behavior...) is not applicable [ERROR] (varargs mismatch; java.lang.String cannot be converted to org.apache.wicket.behavior.Behavior) [ERROR] method org.apache.openmeetings.web.room.activities.ActivitiesPanel.remove(org.apache.wicket.core.request.handler.IPartialPageRequestHandler,java.lang.String...) is not applicable [ERROR] (argument mismatch; java.lang.String cannot be converted to org.apache.wicket.core.request.handler.IPartialPageRequestHandler) > Display the same repeated request for room rights only once > --- > > Key: OPENMEETINGS-1988 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-1988 > Project: Openmeetings > Issue Type: Bug >Affects Versions: 4.0.7 >Reporter: Peter Dähn >Assignee: Maxim Solodovnik >Priority: Major > Fix For: 4.0.8 > > > If a user happens to request the same right (e.g. mod rights) multiple times > it is possible to "spam" the activity window. -- 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=16767113#comment-16767113 ] sufiyan thakur commented on OPENMEETINGS-2013: -- Hi maxim thanks for your reply.. Application is running on 5443 PORT. (HTTPS protocol) . Please suggest me , which PORT i need to use for rtmps ??because screen sharing option using rtmps protocol..either i need to use default port that is 8443 or application port 5443.. on which port rtmps request need to hit? Regards Sufiyan > 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-2015) Pointer shouldn't be scaled
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16767108#comment-16767108 ] Maxim Solodovnik commented on OPENMEETINGS-2015: Thanks for checking :) > 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-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=16767178#comment-16767178
]
Maxim Solodovnik commented on OPENMEETINGS-1990:
Please check documentation:
https://openmeetings.apache.org/openmeetings-db/apidocs/org/apache/openmeetings/db/dto/user/UserDTO.html
You can set {{languageId}} and country (via {{address}})
> 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, 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-1988) Display the same repeated request for room rights only once
[ https://issues.apache.org/jira/browse/OPENMEETINGS-1988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16767093#comment-16767093 ] ASF subversion and git services commented on OPENMEETINGS-1988: --- Commit 238c2f4e4786f1ee55b648a3c9eec62c1daf23d2 in openmeetings's branch refs/heads/4.0.x from Maxim Solodovnik [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=238c2f4 ] [OPENMEETINGS-1988] build is fixed > Display the same repeated request for room rights only once > --- > > Key: OPENMEETINGS-1988 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-1988 > Project: Openmeetings > Issue Type: Bug >Affects Versions: 4.0.7 >Reporter: Peter Dähn >Assignee: Maxim Solodovnik >Priority: Major > Fix For: 4.0.8 > > > If a user happens to request the same right (e.g. mod rights) multiple times > it is possible to "spam" the activity window. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[openmeetings] branch 4.0.x updated: [OPENMEETINGS-1988] build is 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 238c2f4 [OPENMEETINGS-1988] build is fixed
238c2f4 is described below
commit 238c2f4e4786f1ee55b648a3c9eec62c1daf23d2
Author: Maxim Solodovnik
AuthorDate: Wed Feb 13 19:07:14 2019 +0700
[OPENMEETINGS-1988] build is fixed
---
.../main/java/org/apache/openmeetings/web/room/sidebar/RoomSidebar.java | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
a/openmeetings-web/src/main/java/org/apache/openmeetings/web/room/sidebar/RoomSidebar.java
b/openmeetings-web/src/main/java/org/apache/openmeetings/web/room/sidebar/RoomSidebar.java
index bd706c9..b895c3d 100644
---
a/openmeetings-web/src/main/java/org/apache/openmeetings/web/room/sidebar/RoomSidebar.java
+++
b/openmeetings-web/src/main/java/org/apache/openmeetings/web/room/sidebar/RoomSidebar.java
@@ -366,6 +366,6 @@ public class RoomSidebar extends Panel {
}
public void removeActivity(String uid, IPartialPageRequestHandler
handler) {
- activities.remove(uid, handler);
+ activities.remove(handler, uid);
}
}
[openmeetings] branch master updated: [OPENMEETINGS-1988] build is 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 461393f [OPENMEETINGS-1988] build is fixed
461393f is described below
commit 461393f5d8a323c3db142bcb7b10af9b5914ca8c
Author: Maxim Solodovnik
AuthorDate: Wed Feb 13 19:07:14 2019 +0700
[OPENMEETINGS-1988] build is fixed
---
.../main/java/org/apache/openmeetings/web/room/sidebar/RoomSidebar.java | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
a/openmeetings-web/src/main/java/org/apache/openmeetings/web/room/sidebar/RoomSidebar.java
b/openmeetings-web/src/main/java/org/apache/openmeetings/web/room/sidebar/RoomSidebar.java
index e9a4665..5be3cda 100644
---
a/openmeetings-web/src/main/java/org/apache/openmeetings/web/room/sidebar/RoomSidebar.java
+++
b/openmeetings-web/src/main/java/org/apache/openmeetings/web/room/sidebar/RoomSidebar.java
@@ -303,6 +303,6 @@ public class RoomSidebar extends Panel {
}
public void removeActivity(String uid, IPartialPageRequestHandler
handler) {
- activities.remove(uid, handler);
+ activities.remove(handler, uid);
}
}
[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=16767170#comment-16767170 ] Peter Dähn commented on OPENMEETINGS-1990: -- I used the right ids ;) And yes, by using UserService wsdl > 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, 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=16767041#comment-16767041 ] Peter Dähn commented on OPENMEETINGS-1990: -- Hi Maxim, language_id | time_zone_id | country -+---+- 2 | Europe/Berlin | DE 2 | Europe/Berlin | DE But these are extrenal user. As far as we see there is no way to set this during user-creation/room-entry. > 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, 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] [Comment Edited] (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=16767105#comment-16767105
]
Maxim Solodovnik edited comment on OPENMEETINGS-1990 at 2/13/19 12:20 PM:
--
Please use your "real" ids here {{ou.id IN (1, 2)}} instead of 1 and 2 :)
Are you using your own code for creating external users?
was (Author: solomax):
Please your "real" ids here {{ou.id IN (1, 2)}} instead of 1 and 2 :)
Are you using your own code for creating external users?
> 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, 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=16767105#comment-16767105
]
Maxim Solodovnik commented on OPENMEETINGS-1990:
Please your "real" ids here {{ou.id IN (1, 2)}} instead of 1 and 2 :)
Are you using your own code for creating external users?
> 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, 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-1988) Display the same repeated request for room rights only once
[ https://issues.apache.org/jira/browse/OPENMEETINGS-1988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16767239#comment-16767239 ] Peter Dähn commented on OPENMEETINGS-1988: -- build fixed, works as expected (y) > Display the same repeated request for room rights only once > --- > > Key: OPENMEETINGS-1988 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-1988 > Project: Openmeetings > Issue Type: Bug >Affects Versions: 4.0.7 >Reporter: Peter Dähn >Assignee: Maxim Solodovnik >Priority: Major > Fix For: 4.0.8 > > > If a user happens to request the same right (e.g. mod rights) multiple times > it is possible to "spam" the activity window. -- 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=16767348#comment-16767348 ] sufiyan thakur commented on OPENMEETINGS-2013: -- hi by default keystore.screen file was not present on server. i have created it manually with copy of keystore.jks.. import cert chain certificate as well but still getting same error.. pls suggest.. > 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, > red5.properties, 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=16767342#comment-16767342 ] sufiyan thakur commented on OPENMEETINGS-2013: -- Hi maxim i try the PORT 443 for rtmps as well. still getting same error. "PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target" i have attached my red5 properties file.. Pls go through it and suggest me where i did wrong??? [^red5.properties] Regards Sufiyan > 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, > red5.properties, 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: red5.properties > 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, > red5.properties, 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)
