Forum Activity for @michael

Admin logged out immediately after logging in

Using Jamroom

Good to hear

Unable to symlink new skin jrProximaAlpha - check file permissions

Proxima

Might be easier to spin up one of our servers, there's a 7 day free trial and you can install proxima on it.

Wamp is going to be an issue, I can see others have tried in the past ( https://www.jamroom.net/the-jamroom-network/forum/new_posts/37352/install-on-localhost-wamp/search_string=wamp ) and been directed to linux.

Or setup a linux server in a virtualbox so then you have a local linux version.
https://www.virtualbox.org/

Unable to symlink new skin jrProximaAlpha - check file permissions

Proxima

What jamroom does when installing skins or modules via the marketplace is to use a symlink to link to the most current version.

When you install jamroom the file system will look like this:
/modules/jrCore/*

but then when you update core or any other module or skin via the marketplace, it will change the file system from the above directory being a real folder, to it being a symlink to the latest version.

In the file system you will have:
/modules/jrCore
/modules/jrCore-version-5.2.3
/modules/jrCore-version-5.2.4
/modules/jrCore-version-5.2.5
...
and the symlink on /modules/jrCore will point to the highest version.

If you're system doesnt support symlinks (maybe because its windows Wamp) then you might try not using the marketplace for updates and just download the modules from jamroom.net and upload them to your system.

This should get around the need for symlinks, but you'll probably run into other issues. Jamroom does not run on windows.

Docs: "Requirements"
https://www.jamroom.net/the-jamroom-network/documentation/appendix-about-jamroom/774/requirements

2 jamroom sites, 1 database

Installation and Configuration

Thats what you need, a way to differentiate that the request is coming from the app, then brians idea is the best one.

so add a page and put a {debug} in that page then see if you can find anything in that debug to identify that the request is coming from the app.

Docs: {debug}
https://www.jamroom.net/the-jamroom-network/documentation/jamroom-developers-guide/1477/debug

Or if the app can add something extra to the urls it requests like ?__theapp=true then you can make a module to check for that and add the required replacements.

E-Commerce, Service Shop, Merchandise Shop and payment gateways

Genosis

Currently only foxycart. We chose foxycart so that we wouldn't have to build payment gateways.

Payfast gateway is already supported by foxycart:
https://forum.foxycart.com/discussion/5621/south-african-payment-gateways


There is another payment system in the works that will allow you to build your own payment gateway connection system if you don't want to use foxycart.

add quotas

Using Jamroom

Lots has changed from JR4, the exact answer to your question is here:

Docs: "Quota: Create a new quota"
https://www.jamroom.net/the-jamroom-network/documentation/jamroom-admin-handbook/2985/quota#creating-a-new-quota

but also checkout the rest of the manual here, there's some new stuff.

Doc: Table of contents
https://www.jamroom.net/the-jamroom-network/documentation/contents

Adding Social Log In Options

Installation and Configuration

Just tested it here and all that was needed to get google+ login button to appear on the signup screen was enabling it in the GLOBAL CONFIG -> NETWORK CONFIG tab of the module in the ACP.

So if thats not doing it, then probably there might be a limitation on the oneall.com site, see if you can see any settings there.

Adding Social Log In Options

Installation and Configuration

Check the checkboxes for google+ are checked in the ACP and also oneall is setup for it at oneall.com

Prefix before download links

Installation and Configuration

First thing to try would be this module:

Docs: "Template Injection"
https://www.jamroom.net/the-jamroom-network/documentation/modules/1629/template-injection

Im not sure where the URL you're seeing is coming from but best guess is from a template, so if you ran this replacement it would probably get what you're after:

2 jamroom sites, 1 database

Installation and Configuration

Haven't done it so don't have the code for you, but for concepts I would test to see if these were possible:
* use the events and listeners system to pick up on any request to the 'settings' table and change its destination database. (i worry that might effect the other tables too though.)

* During the jrCore_init() function the /data/config/config.php file brings in all of the connection information. When settings stuff is coming in, change the variables for $_conf['jrCore_db_name'] $_conf['jrCore_db_user'] and $_conf['jrCore_db_pass']. Same issue as above though, how to do it for just the single table you're interested in.

* maybe store the settings table in a third separate database and make a script so that both sites are connecting to the same 3rd database which would mean the same codebase on both sites.

* maybe use a different prefix. inside the jrCore_db_table_name() function that goes and gets the correct database table name, have a different prefix for each site, but a single actual database. then you'd just need to adjust the $_conf['jrCore_db_prefix'] to determine which database to use. This probably has the most merit I would think.