Forum Activity for @michael

Forums no longer accessible – being logged out?

Using Jamroom

You could delete it from the file system
/modules/jrSiteBuilderConstructionKit/

Not sure of the exact module name its been a long time gone. What slightly concerns me is if your site is using it then you won't want to delete it.

Site Builder used to be 3 or so modules then got combined into one module. If you had both of them on the site that could cause issues.

Might be better to copy it to a local folder rather before deleting so it can be restored.

If you want to send admin level user info to support at jamroom dot net I can take a look.

Forums no longer accessible – being logged out?

Using Jamroom

Yeah 'quota' = set of features. So if you have a paid quota and a non-paid quota then paying moves the profile from one quota to the other.

Its hanging on 'site builder - construction kit' thats a depreciated module that's no longer in the marketplace. If you disable it then run the integrity check again it should complete.

Changing subdomains – jR & DNS configuration requirements

Installation and Configuration

As far as the site, you'd just make it so that its visible on new_sub.domain.tld then change the /data/config/config.php file to point to that domain instead. The database stuff is likely the same.

Don't know about the SEO part sorry.

Forums no longer accessible – being logged out?

Using Jamroom

"....I was updating quota permissions...." - That looks like the first place to look at. Go see if whatever quota the 'community' profile is in still has forum module access.

If that is all good, reset the caches and run the integrity check.

Having trouble to login admin after server issues

Installation and Configuration

Login via SFTP to the server and delete the contents of
/data/cache/(delete everything in here)

Or use the repair script.

Login and rename repair.php.html to repair.php then access it at yoursite.com/repair.com

making member invisible to others

Using Jamroom

That change had to be rolled back. It blocked private tracker systems from informing work members of updates. Will need to look at this again.

making member invisible to others

Using Jamroom

Update the jrComments module to the latest 2.4.3. That will not inform owners that they have a comment if they can not go to the location of the comment and see the new comment.

It might pay to use the LOG OFF button in the USER ONLINE tab of the dashboard to log that user out if your users are continuously logged in. That will make sure the 'profile_active' key matches what its set to. Might not be needed but if the emails still go out after this update then do that.

making member invisible to others

Using Jamroom

Yeah I hear you. We've had similar. Ban one user then another user account gets created and co-incidentally all they want to talk about is how right that just banned user was and that they themselves are definitely not that user but another totally separate user who just happens to agree that that previous users ban was totally unjust.

You look for the setting, I'll build a quick module to filter out user ids from being sent that you can install.

making member invisible to others

Using Jamroom

If you did put them into a separate quota then you could turn on the comments ITEM APPROVAL system then any comment left by them would turn up in DASHBOARD -> PENDING -> COMMENTS. That might be a nice way to do it.

making member invisible to others

Using Jamroom

You could adjust the modules/jrComment/templates/email_new_comment_message.tpl template to remove the {$comment_text}

but that would be for everyone.