Forum Activity for @brian

Image Raw URL

Design and Skin Customization

I have a feeling it is related to the HEAD request. What is the URL to one of your images so I can check it out from here? I can look at it in the AM and let you know. The URL shouldn't matter and I don't think that is the issue.

ERROR - MySQL

Using Jamroom


For Jamroom 4 you have to enable the OLD "mysql" extension - that's been removed in newer versions of PHP. Jamroom 5+ uses only mysqli.

simple forms phone number

Suggestions

The problem with phone numbers is there is about 100+ different ways of inputting them. With Core 6.4.1 there will be a new "phone_number" validator for the form designer - it will just verify the characters entered are 0-9, -, (, ), + and spaces.

Page content box not showing

Using Jamroom

You have entered invalid content - what the error says

CSS Not Loading, ReferenceError: jQuery is not defined, ReferenceError: $ is not defined

Design and Skin Customization


Look in the data/logs directory for the error_log - newest entries are at the bottom - it can help you find the error in a template.

Important TinyMCE upgrade in Jamroom Core 6.4.0

Announcements

Sorry for overlooking your follow up here Strumelia! Unfortunately there is no way at this time to change the icon size in TinyMCE 5 - apparently this is something they are working on, so hopefully it is configurable soon.

Image Raw URL

Design and Skin Customization

There is no "raw" image URL in Jamroom - all image requests must go through Jamroom's Image support module. However, you can use the "original" size to get what you want. Just make sure the "Block Original Download" option is UNCHECKED in the Core -> Image Support -> Global Config, then you can request the "original" size image - just use "original" instead of large, xlarge, etc.

Note that this is done so Jamroom can properly handle profile privacy.

Let me know if that helps.

redis issue

Installation and Configuration

The root cause of this is your Redis server (or server) is overloaded and is taking longer than 5 seconds to respond to the Redis command, which causes a READ timeout on the socket.

So right now key functions all expect a true/false return and are not wrapped in a try/catch structure. Since the root cause of these errors is a server failure I will try to add additional try/catches in as I update the module, but it's not a high priority.
updated by @brian: 09/04/19 11:20:03AM

one thing i DO NOT like about the new editor

Suggestions

This has been fixed in Jamroom Core 6.4.0. Thanks!

Updating the Documentation Module

Using Jamroom


No - that's not what you would want do. You _could_ do that, but that is a waste of effort. Michael outlined the 2 choices you would want to use.

Let me know if that helps.