Forum Activity for @brian

Problem with Simple Custom Forms

Design and Skin Customization

There are 2 issues here:

form_content - this is a LOCKED field, and is currently required. You CAN however change the groups to have it only show to say "admins", and that should hide it.

the name of your "customer name" field is "form_name" - this needs to be changed to something like "form_customer_name". The problem is that "form_name" is already being used internally, and that internal usage overrides yours.

So I will get a ticket open to make sure that fields cannot be created that could clash with the custom forms module (since the form designer is handled by the CORE and the custom forms just uses the core functionality).

Beta 6.1 Updating errors

Using Jamroom

Same thing there - had to reset the cache in the jr_jrcore_cache table. Note that newer versions of the Marketplace module are better at doing that, so you should be good going forward. Note that you also could run the "repair.php" file (renamed from repair.php.html) and that would have fixed this up as well.

Thanks!

Beta 6.1 Updating errors

Using Jamroom


Is it a "live" site? If not - go for it and let me know. It should be good

Beta 6.1 Updating errors

Using Jamroom

OK I have that fixed on your site - just needed caches to be reset. I've pushed an updated Core 6.1.0b1 that should be a bit smoother upgrade going forward. Let me know if you see any more issues.

Thanks!

Beta 6.1 Updating errors

Using Jamroom

That looks like the upgrade was only partial - the jrCore_form_create_session function was moved into a separate form_session.php library. Is this on your hosted server? I will log in and check it out.

Jamroom 6.1 Beta Kickoff

Announcements


Yep - it will be part of the core.

Thanks!

Beta 6.1 Updating errors

Using Jamroom

Thanks Steve - if you can, take note of the version you're upgrading from so I can check it on this end. I would suspect an old version of the marketplace module is likely to blame.

Beta 6.1 Updating errors

Using Jamroom

Did you manually update or was this through the marketplace? The function(jrCore_db_delete_table_column) is defined in the lib/mysql.php file, so this appears that the core schema upgrade was run BEFORE the file was updated, but that doesn't make sense.

I've not seen this on sites I've updated to 6.1, so I'm not sure where to look on this one, but I can probably update the schema.php file to check for that function before running it (since it is a 6.1 function).

Jamroom 6.1 Beta Kickoff

Announcements

Today we're kicking off the Jamroom 6.1 Beta:

https://www.jamroom.net/the-jamroom-network/blog/93/jamroom-61-beta-kickoff

That blog should cover the details, but please let us know if you have any questions or comments

Thanks!
updated by @brian: 11/27/17 07:40:32PM

Proxima Bridge Setup

Installation and Configuration


You must use Proxima User or Proxima won't work for you. The Proxima sessions are separate from Jamroom's user sessions. Note that there is no support in Proxima for OneAll. OneAll does support mobile, but it works differently, so you will need to read their documentation on that and integrate that on your end.