Can Admin change the user name settings to allow simple user names?
Using Jamroom
I had no issue creating an account with that user name. There must be something else at play.
Possible to do a screen recording of it failing?
Forum Activity for @michael
Using Jamroom
I had no issue creating an account with that user name. There must be something else at play.
Possible to do a screen recording of it failing?
Can Admin change the user name settings to allow simple user names?
Using Jamroom
What was the combination of letters that made up the simple string of connected lower case letters?
That warning message should only fire if there are characters that are not fit for a url.
* brian
* michael
* jim
should all be ok, but
* bri@n
* mi"ch;ael
would trigger that error.
The profile name is derived from the user name so it needs to be a valid url structure
yoursite.com/michael
yoursite.com/brian
It can not be changed. but if there is a valid error we'll try to fix that.
Jamroom forum not sending notifications
Using Jamroom
I did not fix anything, Only thing that I did that may have had an effect was to run the integrity check tool.
glad its working.
Jamroom forum not sending notifications
Using Jamroom
I used the login details you sent and logged in, then created a new user account 'michael' then wrote a new forum post.
Then logged as the first user you gave me and replied. I did get notified.
updated by @michael: 06/18/20 02:16:17AM
Jamroom forum not sending notifications
Using Jamroom
If you like I can try to debug it on your server or download the database and debug it on my server. Send the admin logins to support at jamroom dot net if you'd like to do that.
Otherwise: Lets examine what we have.
* The database should be the same as it was
* the connection between users and the things they are following do exist in the database
* The integrity check would have been run after the transfer so the system should be the same
* all the modules that existed on your previous hosting also exist on your new hosting.
* email does get sent when tested
* no errors are showing in the system check
* Did you try a manual reset of the caches (I don't think this is related, but we're stretching here)?
Docs: "Manually clearing caches"
https://www.jamroom.net/the-jamroom-network/documentation/troubleshooting/114/somethings-wrong-what-do-i-do#manually-clearing-caches
IDEA: Try creating a NEW user and get them to watch a thread/category then make a new thread/category post and see if it notifies new users.
we need to identify where the blockage is.
Jamroom forum not sending notifications
Using Jamroom
Just setup and ran a couple of tests here, the sending system does seem to be working, so:
* could you check that the yellow follow indicators are on for the categories/threads of a user who is supposed to be getting notified.
WHY: the guess is that maybe the 'following' table did not get imported correctly during the import and now nobody is following anything.
updated by @michael: 06/16/20 10:39:40PM
Jamroom forum not sending notifications
Using Jamroom
What are the steps you're taking in forum and expecting that an email will be triggered? I'll setup and debug it.
Feels like the email is not being triggered if the email sending system is working. Need to figure out why.
--edit--
Another idea you can try if you like is to set the email sending system to "Send to activity log", if they do show up in the activity log then the issue points to the email sending system beyond jamroom.
updated by @michael: 06/15/20 07:32:27PM
livesearch field id has changed
Jamroom Developers
From brian:
Quote: This is all in place to prevent Chrome from auto-filling live search fields, which breaks them. I ended up trying A LOT of things to get this working correctly - I don't remember why I'm going that with the class, but it was needed for some reason.
So the best thing to do is probably patch your sites modules/jrCore/lib/form.php
This part has changed:
if (!empty($_field['class'])) {
$cls .= ' ' . $_field['class'];
$cls .= ' live_search_' . $_field['live_search_original_name'];
unset($_field['class']);
}
That will be there in the next core release and overwrite your patch so your code based on it will keep working.
It will give you a unique class to target that wont get removed.
livesearch field id has changed
Jamroom Developers
Does too, not sure why that .removeClass('lve_search_text') is there. I'll need to look into it. did not notice that.
