Forum Activity for @brian

form designer field permissions

Using Jamroom

OK try this one - I had the ID's backwards in the linkup function.

Hope this helps!

updated by @brian: 10/17/14 07:33:18AM

form designer field permissions

Using Jamroom

I took 10 minutes and created you a small module - jrLinkProfile - that "automatically" links user accounts to newly created profiles (in specific quota_ids).

Check out the Global Config help and let me know if that will work for you. For your existing "Crew" user you'll need to manually add existing profiles to their user account - the module does not work retroactively.

Let me know if you see issues.

Hope this helps!

updated by @brian: 10/16/14 09:46:33AM

JrCore_list

Genosis


I don't think jrCore_list is going to return the items as you would expect them - you can definitely do a jrCore_list call for jrGenEvent, but it has no way of knowing what an "upcoming" birthday or anniversary is - that's something that would have to have support coded in for it, and I'm not 100% sure it's really family tree related - that sounds more like a calendar of current events.

Let me know what you think.

Thanks!
updated by @brian: 12/29/14 09:23:55AM

support module

Using Jamroom


I will check this - I believe only admin users can actually delete a ticket, so it's probably a template issue just showing the button when it should not.


Mailgun must be parsing your incoming mail - i.e. mail for your domain must be sent to Mailgun. I believe right now you have your domain hosted with a different mail provider, so that's not going to work.

Basically you need to put Mailgun "in the middle" of your mail. Mailgun does not actually host any email, so what you do is set Mailgun to be your incoming mail server, but you setup a ROUTE that simply forwards any incoming mail to a different domain you have setup to receive email (or gmail, or whatever). The Mailgun can take care of the incoming router and also forward all mail received over to your IMAP server.

Hope this helps!
updated by @brian: 10/16/14 07:05:54AM

form designer field permissions

Using Jamroom

OK - I really think the best bet is to add the Crew user to each property profile, and NOT have them be an admin user - I think in the long run that is going to give you the proper setup when it comes to security.

To address the issue, what we need is a very small custom module that has a db_create_item listener that adds the new profile automatically to any Crew users that exists in the system (i.e. make sure they are in a specific profile).

I'll post some code for you first thing in the morning that should work - I'm a bit behind on some other issues here today and didn't have time to follow up until now, but will let you know.

Hope this helps!

Player Streaming Error

Using Jamroom


Glad to hear that

Thanks!

Recurring Error

Installation and Configuration

Yeah this is probably an error on Flickr's end, but also could be that cURL support on your server is not compiled with SSL support. You can check that by going to ACP -> System Check and click on the small "phpinfo" link in the PHP Version check - that will pop open a phpinfo screen. Scroll down until you get to the "curl" section and make sure it says "Yes" next to "SSL". If it does not say Yes, then contact your hosting provider and have enable SSL for curl.

Hope this helps!

form designer field permissions

Using Jamroom

So just to be sure I understand (I think I do) the "Crew" user needs to have access to the different properties (profiles) but also needs to NOT see specific fields when working in custom forms related to those profiles (or wherever).

Thanks!

To keep using JR or not?

Using Jamroom

Thanks for the detailed feedback - that's awesome - I appreciate you taking the time to type all that out for us. We definitely have a lot of modules and updates that are still behind wraps at this time, but you'll see a lot more stuff coming out over the next few months. JR has a really easy to work with module structure (IMO) so it makes adding things pretty easy. Where it almost always ends up being tricky though is how "integrated" we make stuff. There's a large number of our customers that really want to be able to customize almost every aspect of JR, and then at the other end you have users that just want to enable it and have it all integrated and "just work". So the trick is trying to find the right balance between those 2 points and hopefully come up with something that for most users "just works", and for the users that want to customize everything, they can at least customize the important parts of it.

Thanks again for the feedback!

Error Resource Limit Reached Frequently on Arvixe

Jamroom Hosting


Well it really depends on how Apache is configured - and that depends a lot on the app usage. For example, on Jamroom.net here we can support 150 people at once on 20-25 Apache processes, since we don't run with "KeepAlive" enabled. MOST hosting providers however are going to run with KeepAlive enabled - probably set to something like 5 seconds. What this means is that when a user browses to your site, for the next 5 seconds that Apache process is ONLY going to listen to them. For most sites this is not a problem, but if you get a quick influx of visitors you can quickly run out of processes that are basically just "hanging around" to see if the browser has any additional server requests. With that setup I would think you'd need on the order of 75-100 Apache processes.

So open a ticket with Arvixe and ask them what their keepalive setting is, and how many processes you are allowed to use - that will give you a better idea of the number of users you can support if they are all browsing at one time.

Hope this helps!