Forum Activity for @brian

understanding and debugging the core update process

Installation and Configuration


If it fails the checksum it will tell you. Since you've not reported you get a checksum error, then that's no happening.
updated by @brian: 01/27/17 08:02:36AM

understanding and debugging the core update process

Installation and Configuration

Try this - from your server, while logged in as the web user, run this:


And see how fast it downloads.

Ability to sort Smileys manually

Suggestions

Yeah that should work - if you still see the category, and are sure you've remove ALL images from that category, let me know so I can look in your DB and see what is up.

Thanks!

Elastic 2 Question

Design and Skin Customization


Are you just looking to rename a profile? What are you looking for documentation on?

Thanks!

Issue tracker resolution field strips out code

Using Jamroom

Thanks Steve - I'll check this out.

Ability to sort Smileys manually

Suggestions

Categories do not live "separate" from a smiley image. Once there are no more images in a category, the category is effectively deleted. So it sounds like you still have a smiley in the category if you are still seeing it.

Let me know if that helps.

understanding and debugging the core update process

Installation and Configuration

There's definitely something up with your server - this is not a marketplace or jamroom.net issue.

How it works:

1) Your marketplace module contacts jamroom.net and tells it the versions you are currently running
2) It responds with an UPDATE version, a URL to download the update from and an MD5 checksum of the file
3) the marketplace module on your site downloads the file to a temp location and verifies the checksum
4) it unzips the file and moves it to the versioned directory in the /modules directory
5) It swings the symlink to the new directory
6) It triggers the verify_module event so the updated module can do any work it needs as part of the upgrade process

Let me know if that helps.

weird sitemap crawl results after urlscanner update

Installation and Configuration

Reading through this I don't see how this is a Jamroom issue. Maybe you should open a ticket with the inspyder developers and have them make sure their software can't get stuck in a loop?

jrProfileTweaks bug

Using Jamroom

Yeah I think for now you should set Elastic 2 as the default profile skin and let the user choose Nova. There's a lot of "work arounds" inside Admin Skin that can result in weird issues just like this - to be honest if it weren't already being used by sites we would not make Admin Skin available - it's problematic as it requires us to hard code specific paths/views, and so anytime anything new is added, changed, or a site is customized, it is open to breaking.

I know that's probably not the answer you were looking for, and we will check it out and see if it is fixable, but for now having the defaults in admin skin and profile tweaks "line up" is your best bet.

jrProfileTweaks bug

Using Jamroom


We don't give out the master login for our demo sites - sorry!