Forum Activity for @brian

brian
@brian
12/29/15 05:39:53AM
10,149 posts

CRI: Query Error since updating to 5.3.0b9


Using Jamroom

The session_data field can only hold up to 64K of data - this error means that MORE than 64K of data is trying to be saved in your session table for YOUR session.

For the next beta release I've made it so it can handle up to 16 megabytes of data - that should be enough to handle your unique situation.
brian
@brian
12/26/15 08:49:03AM
10,149 posts

Index Not Found


Installation and Configuration

jimmyk:
I'll give that a try. Did you get those images to work in the ACP?

Everything is working 100%.
brian
@brian
12/26/15 08:48:45AM
10,149 posts

linode


Installation and Configuration

You don't need suhosin. I need to update the guide as it's designed for Ubuntu 12.04, and we're using 14.04 now.
brian
@brian
12/26/15 08:48:10AM
10,149 posts

page_short_url


Using Jamroom

ShareThis does have a URL shortner (specifically for it's own use in OG Tags - it's not for use out side the module) but it does not expose that as a variable you can use.
brian
@brian
12/26/15 05:29:24AM
10,149 posts

Index Not Found


Installation and Configuration

I had a little time over the last couple days and got an nginx setup running. JR works with this as the nginx config:

server {
        listen 80 default_server;
        listen [::]:80 default_server ipv6only=on;
        client_max_body_size 256M;
        root /usr/share/nginx/html;
        server_name ubuntu.jamroom.net;
        access_log /var/log/nginx/access.log;
        error_log /var/log/nginx/error.log;

        location @rewrite {
            rewrite ^(.*)$ /modules/jrCore/router.php?_uri=$1 last;
        }

        location / {
            autoindex on;
            index index.html index.php sitemap.xml /modules/jrCore/router.php;
            try_files $uri $uri/ @rewrite;
        }
        location ~ \.php$ {
                fastcgi_split_path_info ^(.+\.php)(/.+)$;
                fastcgi_pass unix:/var/run/php5-fpm.sock;
                fastcgi_index index.php;
                include fastcgi_params;
                fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
        }
}

However the INDEX page will not work until I get the next beta out - there's a small tweak in the core router that is needed for nginx since it sets it uses a slightly different URI on the index than Apache.

Also - change this:

server_name ubuntu.jamroom.net;

to use your actual domain name. I believe that is working 100%.

Hope this helps!
updated by @brian: 12/26/15 05:30:30AM
brian
@brian
12/23/15 02:44:55PM
10,149 posts

Video Stream Error


Jamroom Developers

Natedogg265:
Whenever I upload an flv video file I get a stream error when trying to play it. I'm assuming the problem is in conversion.

Make sure you have updated to the latest Video module (the beta version) - there was an issue with FLV conversions, but it should be fixed now.
brian
@brian
12/23/15 11:13:07AM
10,149 posts

jrAction_item_index


Jamroom Developers

This is fixed in Profiles module version 1.4.0b9 - update and let me know if that fixes it for you.

Thanks!
brian
@brian
12/23/15 11:12:28AM
10,149 posts

one All issue still not solved


Using Jamroom

izhmel:
This is not an individual problem is why I thought if the JR team contact OneAll the complain would carry more weight coming from a developer ...

I contacted them lets see what they says about this ongoing issue other people has posted in other threads.

Thanks

This is NOT a JR issue - these errors are coming from the OneAll Javascript (which loads from oneall.com - NOT your JR site), and is likely due to a bad configuration in your Facebook app. Only OneAll can tell you for sure.
brian
@brian
12/23/15 11:03:01AM
10,149 posts

jrAction_item_index


Jamroom Developers

I think I see what you're getting at - basically the profile_item_list.tpl is being used on the timeline index - it should be profile_item_index.tpl.

I'm not sure why that is but am checking it out.
brian
@brian
12/23/15 10:58:49AM
10,149 posts

one All issue still not solved


Using Jamroom

izhmel:
I think if the JR team contact OneAll the complain would carry more weight coming from a developer rather than a client who don't have the technical language to explain exactly what the on going issue is..

They are more likely to say it is a JR issue


Thanks

We don't contact them, since we don't control your account. You will need to contact them since it is your One All account.

Thanks!
  292