Forum Activity for @brian

brian
@brian
05/17/15 06:40:36AM
10,149 posts

Quota settings not sticking
Using Jamroom

I've seen this once before, a few months back on another user's site - if I remember right it's because there were some invalid entries in the DB related to the quota, but it was a while a back and I am not sure - I'd have to have access to the system to see what's up.
brian
@brian
05/17/15 06:35:05AM
10,149 posts

Video Problem
Using Jamroom

Sounds like the new size is not taking - try restarting the web server, then run an integrity check within Jamroom (JR will update the max allowed sizes during an integrity check).

Let me know if that helps.
brian
@brian
05/17/15 06:34:16AM
10,149 posts

About using jamroom-4.1.9 - 4.1.9 skin packs and the old flash player modules


Installation and Configuration

Just an FYI that we no longer support JR4 and won't be able to assist if you run into issues...
brian
@brian
05/17/15 06:33:14AM
10,149 posts

Template Cache directory issues
Jamroom Developers

yeah something is messed up - I would suspect a corrupt database or files on the server - try deleting all subdirectories within data/cache and run REPAIR TABLE on your DB tables and see if that helps.
updated by @brian: 05/17/15 06:33:23AM
brian
@brian
05/17/15 06:31:51AM
10,149 posts

Tag cloud from specific profile quota
Design and Skin Customization

You only need to do:

{jrTags_cloud height=300 profile_id=8}

Let me know if that helps.
brian
@brian
05/17/15 06:30:03AM
10,149 posts

one all issues


Using Jamroom

izhmel:
I just started getting the message below without making ay changes

Given URL is not allowed by the Application configuration: One or more of the given URLs is not allowed by the App's settings. It must match the Website URL or Canvas URL, or the domain must be a subdomain of one of the App's domains.

You will want to contact OneAll for assistance - something is not setup right in your OneAll config.
brian
@brian
05/16/15 07:28:33AM
10,149 posts

Disappearing Events
Genosis

Thanks for the update - that's not how it should work - each event is independent and you should be able to set whatever date you want on them, so I will check it out.

Thanks!
brian
@brian
05/16/15 07:27:36AM
10,149 posts

Template Cache directory issues
Jamroom Developers

luis789:
Could you please help. After updated Jamroon to the latest version. Both of my sites have some random images with the x mark and no image. When I log in with the admin account, I'm getting the below error.

CRI: Unable to copy modules/jrCore/templates/page_tool_entry.tpl to template cache directory: data/cache/jrCore

CRI: Unable to copy modules/jrCore/templates/page_search.tpl to template cache directory: data/cache/jrCore
CRI: Unable to copy modules/jrPlaylist/templates/playlist_button.tpl to template cache directory: data/cache/jrCore

Basically error every where

Make sure you have not run out of disk space on your server. Those errors means exactly that they say - the copy() operation by PHP failed.
brian
@brian
05/16/15 07:26:37AM
10,149 posts

Problems after updating Core Module
Genosis

gebhard:
Hi Michael,
thank you for your fast response. After several error messages I chose the radical way: New installation :-)
After the new installation, I tried to import my Gedcom-File, which was already successful imported and now the message appears: "invalid import tree_id - please try again".
Before installation I deleted also the SQL-DB, cleaned the cache etc. but it doesn't help.

Make sure you have first created a new Tree via Trees -> Tree Browser -> New Tree Name and "save". This will become your "active tree" and when you go back to Tree Tools and do the import it will show you that is the tree you are going to import to.

Let me know if that helps.

Thanks!
brian
@brian
05/16/15 07:25:05AM
10,149 posts

system update
Using Jamroom

paul:
I have seen in the past that when clicking that button, all modules get reported as updated but when done and the page refreshes they are still showing as needing an update.

I too have seen this in the past, and have worked on it on and off for a while - the latest marketplace update should take care of this and get it working 99% of the time. The root cause is actually fairly complicated and has to do with how PHP "sees" changes to scripts - there's some tricks we have to do in the marketplace update to trick it into seeing the new versions. Should be working pretty well now though.
  371