Forum Activity for @brian

brian
@brian
08/30/17 08:57:29AM
10,162 posts

emergency after core update mysql uses 100% cpu


Installation and Configuration

If you have checked the "repair modules" option, the DB tables are all upgraded to InnoDB - this could take a bit on the server if you have a very large amount of data - you want to just let it run - don't jump in there and restart stuff. You can do:

SHOW PROCESSLIST;

when logged in to MySQL as the root user and see what queries are being run - make sure any ALTER TABLE queries are complete before you shutdown or restart the server.
brian
@brian
08/30/17 08:50:07AM
10,162 posts

Jamroom 6.1 has been released!


Announcements

SteveX:Thanks Team!

Very smooth upgrade :)

That's what I like to hear - thanks Steve!
brian
@brian
08/30/17 08:06:58AM
10,162 posts

Jamroom 6.1 has been released!


Announcements

Strumelia:Thanks! :)
I'm assuming that will work for all types of videos- uploaded, YT, and Vimeo.

It's just for the Video module - YouTube and Vimeo are not affected.
brian
@brian
08/29/17 10:37:27AM
10,162 posts

Dependent Listeners


Jamroom Developers

Awesome - glad that it is working now :)
brian
@brian
08/29/17 10:00:19AM
10,162 posts

Dependent Listeners


Jamroom Developers

Sorry - should have mentioned you need to run an integrity check after making the change - the priority is stored in the module table in the DB, and updates with an integrity check.

Let me know if that helps.
brian
@brian
08/29/17 08:38:51AM
10,162 posts

Dependent Listeners


Jamroom Developers

Each module in Jamroom can be given a "priority" - this determines the load order of the module, and thus determines the order that event listeners are called when multiple modules have registered to listen to a specific event. In this case, if you look in the jrComment/include.php file at the "meta" function that the comment modules priority is set to "250" (which is low). the very lowest priority is 255, so in your custom module meta function just make sure you set your module priority to be 251 - that way your event listener will always run AFTER the comment module listener.

Let me know if that helps.

Thanks!
brian
@brian
08/29/17 08:36:05AM
10,162 posts

Jamroom 6.1 has been released!


Announcements

As long as everything gets updated and you get the integrity check run, you should be good :)
brian
@brian
08/29/17 07:53:34AM
10,162 posts

Jamroom 6.1 has been released!


Announcements

I've just finished updating the Marketplace with a ton of new releases for Jamroom Core 6.1. Jamroom 6.1 has been in beta for much longer than normal - I want to thank everyone for your patience and feedback during the beta. The fact that it dragged on longer than normal all falls on me - I'm in the process of moving and didn't anticipate how crazy the last 6 weeks would be getting a house ready to sell.

Jamroom 6.1 brings a ton of improvements, tweaks and fixes - our plan at this time is to have Jamroom 6.1 be a fairly "long term" release - i.e. there are no plans a this time to jump into Jamroom 6.2 (at least not yet lol).

If you are upgrading from Jamroom 6.0.x here's what you want to do:

1) Log in to your site - go to the Marketplace and the System Updates tab.
2) Update to Jamroom Core 6.1.0
3) Run an integrity check with "repair modules" and "reset caches" checked
4) Go back to the Marketplace and update the "Marketplace" module
5) Reset caches again
6) Go back to the System Updates and update the modules individually - if you use the "update all" it's likely to get stuck. If upgrading a single module takes more than 30 seconds, refresh and try again and it should install
7) When all done, run a final integrity check with "repair modules" checked and reset caches
8) Go back to the Marketplace and install the new "System Tools" module - this is a core required module going forward
9) Go to to the ACP -> System Check and make sure everything is green.

9a) You may need to go to the Dashboard and enable workers - on some updates (depending on what you are updating from) the queue worker pause mechanism has changed and you may need to manually re-enable the queues.

9b) If you are running the Video Module, go into the ACP -> Profiles -> Video -> Tools section and run the "Verify Video Files" tool.

That should do it. I know this is a bit more involved than a normal update, but there's some underlying database updates and changes that need to be applied correctly. If for some reason you don't do it in the order outlined about, no worries - you just may notice the marketplace updater showing you that something hasn't updated (when you think it has) - just reset caches and update.

We're excited to get 6.1 moving forward now - maintaining 2 versions of modules is a lot more time consuming.

If anyone has any questions or feedback, please let us know.

If you are a hosting customer and need assistance with the upgrade, please don't hesitate to open a ticket and let us know - we can help.

We hope everyone loves Jamroom 6.1!

Thanks!
updated by @brian: 05/21/18 04:13:02PM
brian
@brian
08/28/17 10:40:41AM
10,162 posts

Proxima Bridge List Users


Installation and Configuration

To be honest, "listing all users" is something you just don't want to do - it's not scalable. Think of how many mobile apps you have that allow you to list all the users on their service?

You should be able to do it with Proxima Bridge though - it uses the same search operators as the data service (all do):

https://www.jamroom.net/proxima/documentation/using-proxima/2018/the-proxima-data-service#get-search-a-collection-for-matching-objects

i.e.

/api/bridge/profile?search1=_item_id%20gt%200

Let me know if that helps.
brian
@brian
08/28/17 10:30:07AM
10,162 posts

Still don't fully understand Proxima


Installation and Configuration

One thing that is important to understand is that Proxima Bridge is NOT going to give you a full API into Jamroom modules - it's primary design was to allow listing of datastore modules outside Users.

You would not use Proxima Bridge to list user information - that is done via the Proxima User module.

Proxima was built with the idea that it would be a "back end" to a mobile app - not an add-on to a Jamroom site.
  111