Yes looks like the room crashing has been resolved. Thank you for the prompt fix.
The profile image I am referring to is the default profile image that is located at /webapps/Openmeetings/images/profile.* But I see why the issue. Looks like the default image format was changed from .jpg to .png and in my customization script I was importing profile.jpg so I changed the script to .png and this resolved that issue. Didn't notice the file extension had changed. The last issue I am seeing is the import from the previous backup. It is importing all the users data for the database account name / password / contact info / .etc, but it is not importing the users profile image they had uploaded. The import was placed at /webapps/Openmeetings/upload/import/import_2018_08_04_05_59_04/roomFiles/profiles/ so when a returning user logs in their profile is created: /webapps/Openmeetings/upload/profiles/ But just now looking as I uploaded a new profile picture for myself as a test I see the reason. It looks like it stems from the file format change. The backup has everything as profile.jpg where it is looking for a .png file. Just a heads up for anyone taking an older backup from a previous version, you will have to manually copy each users profile.jpg file from the import folder to each users profile space as a .png file For me this was an example: cp /opt/current/webapps/trade-group/upload/import/import_2018_08_04_05_59_04/roomFiles/profiles/profile_2/profile.jpg /opt/current/webapps/trade-group/upload/profiles/profile_2/profile.png this must be done for each user or tell each user that they just have to re-upload their image if they want one. -----Original Message----- From: Maxim Solodovnik <[email protected]> Sent: Friday, August 3, 2018 11:08 PM To: Openmeetings user-list <[email protected]> Subject: Re: Conference Room creation update error Just have tried, profile images in jpg format are being displayed as expected Could you please tell me what were your exact steps to reproduce? BTW Thanks a lot for checking latest nightly :))) On Sat, Aug 4, 2018 at 9:39 AM Maxim Solodovnik <[email protected]> wrote: > > Hello Aaron, > > page crash was just fixed > Will take a look at profile image issue (most probably caused by > migration from JPG to PNG) > > According to new install, then import I would recommend to use command > line admin in this case > http://openmeetings.apache.org/CommandLineAdmin.html > the options I'm using: -file --skip-default-objects On Sat, Aug 4, > 2018 at 9:26 AM <[email protected]> wrote: > > > > Looks like my 1st attachment did not have the complete debug in it. > > Attached is the full log. > > > > > > > > Looks like also whatever is causing this error is also what is > > causing the import not to work properly. I use a different > > profile.jpg image for default users (located at > > /webapps/openmeetings/images/profile.jpg) and that does not get > > shown on the users profile. It is pulling the image that is the > > standard image that has the question mark in the body. Not even > > sure where it is pulling that from since the file was replaced with > > a different file all together. When you copy the image location it > > states (/profile/1?anticache=1532949138000) > > > > > > > > I re-installed the official release and that one works as expected > > (room configuration and changed default image) > > > > > > > > From: [email protected] <[email protected]> > > Sent: Friday, August 3, 2018 9:19 PM > > To: [email protected] > > Subject: Conference Room creation update error > > > > > > > > Looks like an old error is back. I just installed the latest > > nightly build and now get thrown to the internal error page if you > > try to update and existing conference room or when you type the > > first letter for a new room name. Looks like the old error where > > even if the user was granted admin access Group Admin Access is > > denied (see attached log) > > > > > > > > Version4.0.5-SNAPSHOT > > > > Revisionb154bef > > > > Build date2018-08-03T10:13:48Z > > > > > > > > Also looks like when doing the import there is a problem. When you are > > 1st setting up your new install of OM you create an admin account; so in > > the database that is “Profile 1”. Where the problem lies is when you do > > an export from your old system it also exports the old “admin” account > > (which on the old system was also profile_1) but when you do the import > > since there is already a profile_1 it moves everything down 1 so the old > > admin account become id 2 on down the line. My account when exported > > was profile_2 but now my account is now labeled as profile_3 so the > > image is not there but the old admin account has my profile.jpg. (also > > in attachment) > > > > > > > > > > > > -- > WBR > Maxim aka solomax -- WBR Maxim aka solomax
