Forum Activity for @michael

michael
@michael
12/23/22 10:15:50AM
7,791 posts

Jamroom Install on localhost


Installation and Configuration

Jamroom needs to have a domain name so you cant access it via http://localhost:8080/jamroom it needs to be on http://yoursite.test or other real domain name.

you can set domain names to resolve to just your machine by editing the /etc/hosts file on linux
sudo nano /etc/hosts
then adding a domain name that resolves locally.

There's a guide here thats a bit old but still has the main gist of setting up a server.
https://www.jamroom.net/brian/documentation/contents

particularly useful is this page:
https://www.jamroom.net/brian/documentation/guides/1211/configuring-apache-for-virtual-hosting

Which will allow you to have any number of sites on the same server.
michael
@michael
11/27/22 06:03:16PM
7,791 posts

Premium modules


Installation and Configuration

This account that you're using is not attached to a premium membership. Did you buy it with a different account?

Once we figure out which account is the premium one you then need to enter the details found at
JAMROOM.NET -> YOUR PROFILE -> JAMROOM SITES

then enter them in your sites marketplace section
ACP -> MODULES -> MARKETPLACE -> SYSTEM UPDATES

If you can send a receipt to support at jamroom dot net of the payment we can help track down where the premium licesnse is.
details.png details.png - 111KB
michael
@michael
11/26/22 11:17:26PM
7,791 posts

"Already used" in User profile edit page. using Japanese


Using Jamroom

Ok, I can see the issue and why it was done that way. The technical reason is: Because there is no way to preg_match just japanese characters.

The closest code I found to matching hiragana and katakan and kanji is:
preg_match('/[^a-zA-Z0-9\p{Katakana}\p{Hiragana}\p{Han}]', $value)
but the problem with that is it does allow * and ? through and probably more.

So since we cant be SURE that what the user is passing in as their profile_name does not contain code used to hack the site the use of those characters are limited to admin users only.

Admin will be able to change a profile name to japanese characters but a regular user will not be able to.

Unless I can locate some validation system that will ONLY let valid characters through but not extra code then this can't be changed.

Maybe Japanese programmers have a way to do it, but I don't know it unfortunately.
michael
@michael
11/22/22 09:52:30PM
7,791 posts

"Already used" in User profile edit page. using Japanese


Using Jamroom

Sorry I haven't got to this yet, been a bit busy. I will get a test environment setup and find the cause.
michael
@michael
11/19/22 11:54:29PM
7,791 posts

"Already used" in User profile edit page. using Japanese


Using Jamroom

I tested what I thought might work and it didn't work. I'll look into the code and see if there's some way to get it going.
michael
@michael
11/19/22 12:36:11AM
7,791 posts

"Already used" in User profile edit page. using Japanese


Using Jamroom

The profile_name_url needs to be in A-Z characters. Jamroom doesnt have a translitteration system to change 'マイケル' to 'michael' so what happens is the characters gets stripped and it becomes '' which is the same for anyone else using all japanese characters.

Try using the FORM DESIGNER on the profile update page to add the form field profile_name_url and enter a-z characters in there.

There is no issue with 2 profiles using the same profile_name but there is an issue with 2 profiles using the same profile_name_url because thats what gets used at yoursite.com/profile_name_url
michael
@michael
11/11/22 11:15:32PM
7,791 posts

PHP Fatal error with Audio update


Using Jamroom

:) Well done. Good luck with your sites.
michael
@michael
11/11/22 10:54:19PM
7,791 posts

PHP Fatal error with Audio update


Using Jamroom

Thanks for the very specific error report that makes finding the issue easy.

It looks like this issue has already been fixed for the next core version.

The issue was from the "select_date" form field type.

--edit--
That form field is probably only on the UPDATE form designer since thats the only one having the error.
date.png date.png - 161KB

updated by @michael: 11/11/22 10:54:55PM
michael
@michael
11/11/22 09:29:28PM
7,791 posts

PHP Fatal error with Audio update


Using Jamroom

Adding a audio_description field as an 'editor' field works. When I open the CREATE form or the UPDATE form for an audio item I do not see the same error as you.

What are the steps to get to the page where that error shows? or what is the URL of the page where the error shows.

My guess is the issue is that some other module is causing problems, not the editor form field.
form.png form.png - 120KB
michael
@michael
11/11/22 09:14:04PM
7,791 posts

PHP Fatal error with Audio update


Using Jamroom

Can you go to ACP -> MODULE -> CORE -> SYSTEM CORE -> TOOLS -> SYSTEM CHECK and take a screenshot of it please.

I'm interested in what version of php you're running. Changes in php 8 have broken some older functions which I suspect might be the case for your situation.

I'll try to reproduce it here.
tools.png tools.png - 203KB
  25