Forum Activity for @michael

Moving Genosis to new server

Genosis

Thanks Bill for putting the solution into easy steps for the next guy. Thats awesome!

Jamroom Install on Amazon EC2 instance

Installation and Configuration

here's that table. its in SQL format so import it to your DB. I've never seen that error before, lets see if adding the table fixes it.

Moving Genosis to new server

Genosis

reinstall them from the MARKETPLACE in the ACP after you've reinstalled. renaming is safer but slower. your call.

Moving Genosis to new server

Genosis

the other option is just to delete the /modules folder and then download the open source version from here:

https://www.jamroom.net/networkmarket/core_download/jamroom-open-source.zip

and upload that. It would be the same as renaming all those files.

Jamroom Install on Amazon EC2 instance

Installation and Configuration

run the repair system.

There is a file in the root folder called repair.php.html rename that to repair.php and access it at your-site.com/repair.php

Docs: "Somethings wrong, what do I do?"
https://www.jamroom.net/the-jamroom-network/documentation/troubleshooting/114/somethings-wrong-what-do-i-do#if-you-cannot-get-in-to-the-acp

Moving Genosis to new server

Genosis

yes, you want to do that with all the modules. and its OK to not have an index.php, Thats the new structure, instead you'll find a /views folder in the module.

Some index.php files were getting too big to work on so the individual views got moved each to their own file.

Jamroom Install on Amazon EC2 instance

Installation and Configuration

Ive never run it from EC2 so don't really know, but the first thing would be to change it from an ipaddress to a domain name. That's often the cause of issues.

Need to make sure mod-rewrite is enabled, is EC2 apache? i dont know.

Here's the requirements doc

Docs: Server Requirements
https://www.jamroom.net/the-jamroom-network/documentation/getting-started/774/server-requirements

Moving Genosis to new server

Genosis

AH!! your simlinks are gone.

Delete every copy of each file except for the latest so if you have
/modules/jrCore-release-6.1.1
/modules/jrCore-release-6.1.2
/modules/jrCore-release-6.1.3

Delete 6.1.1 and 6.1.2 then rename 6.13 to just:
/modules/jrCore

OR If you still have access to the old site then run the tool at ACP -> MODULES -> DEVELOPER TOOLS -> TOOLS -> REBASE MODULES and it will do the same thing.

OR you could make the symlinks again from modules/jrCore to modules/jrCore-the-latest-version

When the marketplace updates a module it saves it to the file system then once its finished saving it updates the symlink. Doing it this way means there's no downtime for your users when modules are updated.

Moving Genosis to new server

Genosis

need to check the server's error log that "Internal Server Error" will be logged there, it will tell you what the problem is. Copy+paste the end of that here and we can help.

--edit--
make sure your server has mod_rewrite on and there is a hidden .htaccess file in the root folder.
updated by @michael: 01/05/23 12:29:17PM

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

Using Jamroom

Most of the time you don't want to modify any of the jamroom files because those changes will be over-written if there is a module update. Instead what you want to do is use the "Events and Listeners" system to adjust other modules by building your own.

Then you know that since your custom module will never be updated other than by you that your changes will always work.

Docs: "Events and Listeners"
https://www.jamroom.net/the-jamroom-network/documentation/module-developer-guide/1011/events-and-listeners

If its not possible to get to the point you want to adjust without changing a core module let us know and we'll add in an event close to the point you're after or adjust the core module with the change.