Forum Activity for @brian

new "performance test" accuracy

Installation and Configuration

Use whatever the stable version is that has been created for your distribution. This means that if you are on CentOS, use whatever is installed via "yum" - i.e.

yum install mysql-server

This is likely what you are already using, and I would not change it.

Events missing from Top Nav - and home page

Installation and Configuration


We have a ticket on this, but it's not a "quick add" so will take some time. We will get to it, but for now you just want to add your text string in to your template where needed (since you are going to have to modify the template anyway as you would have to add the {jrCore_lang} call in to pull in your custom lang string). So it's not super high priority.

Thanks!

After deleting a discussion, getting returned to the wrong page

Installation and Configuration


No.. your changes are never overwritten. When you upgrade a skin or module, the new version is installed into a separate directory, and the "active" link is updated to point to it. So at no time is anything you've customized ever overwritten.

If you make changes directly to templates (say skins/jrNingja/index.tpl) then when you update the NEW index.tpl will take over. You would have to copy your old index.tpl file (now in a directory like skins/jrNingja-release-1.0.11) back over into the "active" directory (just named "jrNingja").

However, that's not the way you want to be customizing your site

Instead do it this way:

- go to ACP -> Tools -> Developer Tools -> Tools -> Clone Skin and make a CLONE of the jrNingJa skin. This will include any customizations you have made to this point. Name it something like myCustomNingja, and make it your active skin.

- now, whenever a new Ningja skin update comes out you can safely update, since jrNingja is not your active skin.

- after the update, go into the "templates" tab for your custom skin and use the "compare" button to compare your custom templates to the same templates in the new jrNingJa update. If you see a template has changed and you want to incorporate those changes in to your custom skin, you can click on the button at the bottom to overwrite your custom template with that template from the jrNingja. If you have other customizations and don't want to overwrite them, you can see what the changes are and manually copy them in to your template.

Let me know if that helps.

Meta Information on Playlist shares

Installation and Configuration


We just cross posted - update to ShareThis 1.0.9 that I just released and this should be working.

Meta Information on Playlist shares

Installation and Configuration

I've just pushed out version 1.0.9 of the ShareThis module that should handle this for you now - update and you should see the og:description meta tag in the head section.

Hope this helps!

new "performance test" accuracy

Installation and Configuration

Jamroom will use the output of lscpu BEFORE /proc/cpuinfo, and your lscpu reports 1600mhz. Most likely this is the "idle" speed of the CPU OR it could be getting throttled due to a thermal issue - either way I would contact your hosting provider and have them check.

Meta Information on Playlist shares

Installation and Configuration

I've looked at this, and I think the easiest route is have the ShareThis module check for a "description" or "desc" field - i.e.

audio_description

and use that if found. The only way it is actually going to work right now would be to create a custom template just for the module, and there's no reason to do that for every module if you just want the description added in. Since og:description is a valid Open Graph tag, we'll just follow the same naming scheme.

I'll get that worked in and a new release out that should get this working.

Hope this helps!

new "performance test" accuracy

Installation and Configuration


None of the CPU detection code has changed. Try this - log in to your server via SSH and run (as root):


If you get no output or "command not found" run:


and send the output to me at support [at] jamroom [dot] net.

Thanks!

Proxima Alpha

Installation and Configuration


Cool - most likely they are using the DS (it's pretty much the standard for every module), so this module would basically add a JSON API layer "in front of it" so you could manipulate the data in your module.

I'll try to get that moving forward as soon as I can and get it online.

Hope this helps!

After deleting a discussion, getting returned to the wrong page

Installation and Configuration

The changes you are looking for would be handled at the skin level - not at the Group Discussion module level.

We have a ticket open on this exact issue right now, and Douglas is working on it, so we should have that out fairly soon.

Hope this helps!