Forum Activity for @brian

Jamroom Paypal Callback

Jamroom Developers

Specifically you will want to listen for the 'webhook_parsed' event from the "jrPayment" module.

ISSUE from Last update 6.5.0

Using Jamroom

This was Michael's last response to your support ticket last night:


So we were waiting on the SFTP info for your site. The Core module needs to be reloaded on your server.

Upgrading to Jamroom 6.5.0

Announcements


Awesome - thanks for that It's been a fun ride for the last 17(!) years!

ISSUE from Last update 6.5.0

Using Jamroom

Turn off the 2 ultrajam modules - those are for older versions of the editor - that could be the issue. If you have DB access just change the "module_active" column to "0" for those 2 modules in the jr_jrcore_module table, then truncate the jr_jrcore_cache, jr_jrcore_cache_value and jr_jrcore_cache_profile_id tables.

Let me know if that helps.

ISSUE from Last update 6.5.0

Using Jamroom

Yeah that should really "just work" - Sage is an older skin that is pretty simple. Are you using any 3rd party modules that could be messing with things?

ISSUE from Last update 6.5.0

Using Jamroom

If you can't click buttons, that's a javascript issue - running the repair.php SHOULD have fixed that since it resets the cache. Log in to your server and delete all .js files in site.com/data/cache/(activeskin) -i.e. something like data/cache/jrElastic2

Let me know if that helps.

Video Upload Form Gone

Using Jamroom


Sorry for the frustration - send me your site login and URL to support [at] jamroom [dot] net and I can check it out.

Thanks!

Video Upload Form Gone

Using Jamroom

Yeah this looks weird - when resetting caches make sure and check the "Reset Form Session Cache" option. Also - try with a different browser just to be sure it's not something screwed up with the browser.

Upgrading to Jamroom 6.5.0

Announcements

Upgrading from Jamroom 6.4.x (and earlier) to Jamroom Core 6.5.0:

- As a master admin, login and go to the ACP -> Marketplace -> System Updates
- You will see the update for the Jamroom Core 6.5.0 - update
- You should be redirected to the list of module updates that are available - if you receive any error here refresh your browser
- Once you see the module list, click on the "update" button to the right of the MARKETPLACE module
- Once the marketplace module is updated, RESET CACHES. If you get a "not found" after updating the marketplace module, refresh and go back in to the ACP -> Marketplace -> System Updates
- Reload the "System Updates" screen and you can now click the "Update All" button to install all updates

If you don't follow these steps, it's not a big deal - you just may see some modal window errors or "communication" errors since the way that modules are updated using the Marketplace module has changed a little bit and requires new Javascript to get loaded. If you see any errors you just refresh your browser and reload the System Updates screen.

If you have any issues upgrading let us know - for Jamroom Hosting customers please open a tracker and we can help get you updated. Please make sure and

If you have any questions let us know.

Thanks!
updated by @brian: 06/24/23 10:16:42AM

Fixing Errant HTML Content

Jamroom Developers

Yeah - just use jrCore_clean_html() - it will fix up errant HTML for the most part - i.e.


It uses DOMDocument:

https://www.php.net/DOMDocument

to basically "rewrite" the HTML which ensures everything gets closed.

If you are loading offsite URLs and need to get the HTML, I would highly recommend not using cURL yourself directly and instead just use the jrUrlScan_get_url_with_wget() function that is provided by the Media URL Scanner module - it does a lot of extra work to look like a "real" browser to the remote site. If you are just using curl you will find a lot of sites that will not load properly and/or will just "hang" - these sites use 3rd party CDN's and accelerators like Cloudflare that see the curl call like a "bot" and will reject it. The jrUrlScan_get_url_with_wget() module is setup to work like a "real" browser in that it fully accepts cookies, session cookies, uses a real user agent, accepts gzipped content, etc. - all the headers and stuff it sends out masquerades as a real browser and you will get the HTML. So I would do this:


Let me know if that helps.