Forum Activity for @michael

PHP errors after upgrade

Using Jamroom

Check that your server has symlinks enabled.

When a module is initially installed its in a location like:
/modules/jrCore
then when it gets updated, whatever was on /modules/jrCore gets moved to a location with its version number
/modules/jrCore-version-6.4
and a new version also gets added
/modules/jrCore-version-6.5
Then /modules/jrCore turns into a symlink to the most recent version of the module.

If your server does not allow symlinks then that would cause an issue.

Are you able to access the ACP?

Invalid Access Key

Genosis

I've tried to reproduce your steps to see the issue happening here, but I can not get "Invalid Access Key" to appear.

If you'd like me to take a look at it happening on your site, send me the login details for an account where it happens to support at jamroom dot net along with a link to this thread and the admin login details for your site.

Alternatively some more steps to be able to recreate it or a video of it happening post that here.

Charts acting strange after 6.5 Upgrade

Using Jamroom

The issue is that 1 day of data is not there, if you request 2 days of data, then you get the most recent charts.

Did 1 day of data used to work?

(your site).com/chart/days=2

does show the 1 day data.

--edit--
Still haven't figured it out, the code looks ok. My current best guess is your Daily Maintenance listener is firing off late in the day causing results to be not there when searched for.
updated by @michael: 05/16/20 12:27:45AM

Jamroom Paypal Callback

Jamroom Developers

It depends on what modules you're using. It could be in jrPayment, jrPaypal or jrFoxyCart.

Whichever one its in, if your developer is planning on changing code in any of those modules it will break as soon as an update comes out.

The correct way to adjust something is via

Docs: "Events and Listeners"
https://www.jamroom.net/the-jamroom-network/documentation/module-developer-guide/1011/events-and-listeners

There will be an event in the location that you're after to change whatever you want to from within your own module so no code needs to be changed in the jamroom modules.

That will keep your code safe when things are updated.

Charts acting strange after 6.5 Upgrade

Using Jamroom

It looks like its only the 1 day chart that is out of order. I suspect it will fix itself by tomorrow if that's the case.

If you'd like me to debug it, send the admin login details to support at jamroom dot net along with a link to this thread.

I'll download the chart related data and put it on a local server to figure out whats going on.

Are you seeing it in any other location than:
( YOUR SITE ).com/chart/days=1

( YOUR SITE ).com/chart/days=7
( YOUR SITE ).com/chart/days=30
Look like its working correctly
updated by @michael: 05/14/20 05:59:35PM

ISSUE from Last update 6.5.0

Using Jamroom

yeah the issue is jQuery is not available so the many of the buttons are not working. If you do find yourself in a situation of wanting to click a button you can use the browsers developer tools to remove the
and change the input type to "submit" and that usually gets the buttons to work. I needed to do that to login with the details you sent me.

ISSUE from Last update 6.5.0

Using Jamroom

It looks like your site is online, if the issue is still just buttons not working in the ACP and you'd like me to take a look at it, send your admin login details to support at jamroom dot net with a link to this thread and I'll take a look.

ISSUE from Last update 6.5.0

Using Jamroom

yeah, you can change the skin in the database. Its in the jr_jrCore_settings table. The setting name is 'active_skin'. Here's a screeenshot of the value to change.

--edit--
Change the value, then clear the caches.

either by running the repair.php like you did before, or by clearing out /data/cache via SFTP

updated by @michael: 05/14/20 03:46:52PM

Video and audio uploads not converting

Using Jamroom

'NO' to wordpress. It's too buggy and will get your server hacked. Wordpress is not allowed on jamroom hosting.

Issues following the updates

Using Jamroom

Everyone having to re-login could be an expected side-effect of updating the code, but that should stick after they do it the first time. You're saying they have to do it each time? That would be a bug.