jrComments feature request
Suggestions
You can select the type of files you want to allow in the Comments -> Quota Config.
Hope this helps!
Forum Activity for @brian
Suggestions
You can select the type of files you want to allow in the Comments -> Quota Config.
Hope this helps!
I-Pad Smiley truncates text in comment field?
Using Jamroom
I've got a new system in place for JR 5.3.1 that will handle emoji's - were in the process of testing it right now, but this should be fixed fairly soon.
Share this error (during customization)
Using Jamroom
izhmel:414 Request-URI Too Large
Are you getting this error when you click on the ShareThis button? If so, contact ShareThis - sounds like they need to update their web server to handle long URLs.
Jamroom 5.3 is now out of beta!
Announcements
Strumelia:1) Am I going to lose the hundreds of major and minor customizations that were done on both my old Core and on so many of my modules? (The customizations were done BOTH via ACP, and directly on the server...both by members of the JR Team and by myself.) What am I in danger of losing and what do I need to especially look out for?
I believe you are using a custom skin? If so no - nothing changes.
Quote:2) would it be advisable to update only the Core first, and see how it behaves for a few days... before then slowly updating the modules maybe two or three at a time and checking that they haven't lost my tweaks?
You can, but I don't think there is a need to. JR 5.3 is not a NEW core - it's new features built on 5.2, so things that were working in 5.2 should continue to work the same (or better) in 5.3.
Quote:3) what safety precautions can I take before updating? Is there a way to revert back if I see the Core update has wiped out lots of customizations, added custom functions, or style tweaks on my site? What's the worst that can happen?
The problem with reverting is that you can't revert the DB changes, so in this case your best bet would be to restore from a backup if you find it doesn't work for you.
We've updated A LOT of sites from 5.2.41 to 5.3.0 - we've seen a couple small issues (mainly around the Marketplace giving you a 404 not found or something - cache reset fixes it) but so far I feel the upgrade is a smooth one.
Signup form
Design and Skin Customization
Nmaster88:That seems cool, but using my custom skin i have problems using the site builder am i missing something?
Your skin must be setup to use Site Builder - go into your templates section for your skin and use the "compare" tool to see the differences between your custom skin and the skin you cloned from.
Let me know if that helps.
Proxima Bridge: getting data from specific module
Installation and Configuration
amartins:Let's say that I have a module called "myJrModule" with some fields that I need to retrieve to my mobile app, like a list. How can I link bridge to use it? What is the url structure?
Can you help me with this?
Can you help me with this?
The URL structure is like:
yoursite.com/api/bridge/[module_url]
So if you wanted to GET audio items it would be a GET request to:
yoursite.com/api/bridge/audio
Let me know if that helps.
Showcase Member Sites
Announcements
johnchansa:My JR site used to featured a while ago but not anymore.
You site is on page 2:
https://www.jamroom.net/showcase/sites/p=2
Login with user name or email instead of user id
Installation and Configuration
amartins:brian:
Ahh - got it - that makes sense. I just pushed out version 1.0.6 of the Proxima User module - you can now sign in by passing a "user_name", "user_email" OR "id" parameter, along with password. The response will now include the "_id" key - so even if they sign in using a user_name or user_email, you will now get the correct _id that should be used on the client.
Let me know if that works for you.
Hope this helps!
That's all that we needed. I tested it, working fine! Thanks very much.
I have a question about bridge, should I open new thread?
Ahh - got it - that makes sense. I just pushed out version 1.0.6 of the Proxima User module - you can now sign in by passing a "user_name", "user_email" OR "id" parameter, along with password. The response will now include the "_id" key - so even if they sign in using a user_name or user_email, you will now get the correct _id that should be used on the client.
Let me know if that works for you.
Hope this helps!
That's all that we needed. I tested it, working fine! Thanks very much.
I have a question about bridge, should I open new thread?
Yep - if you can that would be great.
Thanks!
