Forum Activity for @jimmy

Random Thoughts

7a. I was more talking about a expanded @ system which would be unique. Normal @brian does what it does... but how cool would it be if I could do @brian+video+desc and it would display a list 5 videos in a post. So, if I were to say, "That guy Brian is a really good music video producer. You should check out his last couple of videos: @brian+video+new+desc" @brian+video+new+desc would output a list which could be stylized by the admin. Kind of like jr_list but using @. This would be something I haven't seen anywhere.

8. I hear you on that. I do use priority a lot on IPS. Also, people can charge for certain priorities. If the user selects "paid support" they are directed to the store after they submit the ticket. Not saying this would be useful to Jamroom Inc. support here, but on other sites people might want to sell support or use priorities as departments. Just some thoughts.

9. Yea, it had me for a loop.

Random Thoughts

7. Adding a number to the support tickets so I can or some kind of identifier so people can reference back to past support ticket if needed. Right now, I'd have to copy and paste the support ticket link. https://www.jamroom.net/ticket/64486/cant-install-for-3-days. I can extract the number from the link, but having a reference number in the ticket might be helpful. I do realize that a number could be added to my template somewhere.

Maybe a support ticket number that is like short names: @brian. If I wanted to reference a support ticket I would enter @sup1234567 and that would reference a support ticket.

7A. Taking that a step further... a whole @ system when items can use their ID + number. Specific video @vid339849, specific audio @aud399482, all @brian's audio @brian+all-audio, @brian+all-audio-down.

8. Support ticket priority. Ability to set custom priorities for tickets. If I was to open a support ticket which wasn't super important I could set it to low, notifying the admin that my request wasn't that important.

9. Maybe the possibility that when you clone a skin:
A. the developer prefix is set automagically if the site owner has set a developer prefix.
OR
B. there is a separate field for a developer prefix which is added before whatever name is entered.

When I cloned a skin I couldn't figure out why JR kept cropping the first 2 letters of my name. Someone else also might run into the issue.
updated by @jimmy: 04/06/18 06:24:46PM

Random Thoughts

1. I guess it makes sense that two users have to agree to engage in a PM. On thing just occurred to me, not sure where I read this, but I remember reading how some people were moving away from using "private" in Private Messages / Private Notes / etc. naming. It became a legal question. Are private notes really private? If admin or staff look at those notes, even if it's outlined in the terms, members might not consider those private in today's "encrypted" world. Anyway, they ended up calling them just Messages. Not a big deal for me because I put a big warning at the top saying that messages aren't private and can be reviewed at any time by staff. If someone has a different meaning of private from the one the site admin has, it might create an issue.

2. I think if a module was created called discourse which allowed a user to start a thread in the sitewide module but was also replicated in the users profiles (only his / her threads) in their discourse section. Each thread would be in a category and categories could be searched or listed in the front end discourse module.

As funny as it sounds, it's like your chat box but just on the site. Chat box really isn't profile centric. Chat has chat rooms, discourse has categories. Chat rooms can be private, categories can be private. In the end, it's what it is, a town square. A place were people can chat and come together under the supervision of the admin - a neutral ground - versus in someone's profile.

Anyway, that's my sales pitch. LOL!

4. I think if a system got really busy, people would need some kind of warning system.

5. Will look into that.
updated by @jimmy: 04/03/18 01:29:52AM

Random Thoughts

5. Might want to change the /r/ in the URL Redirection (or give the option to use something else). The reason I mention it is that a lot of affiliates use /r/xxxxx as their aff link. In the example in the docs you use http://example.com/r/search_engine anyone on my sites would view that link as a referral link and not click on it.

6. I haven't got to the support tickets modules yet, but before I forget, I have a real problem on my other site with people replying to support ticket email (when I reply to a ticket) from the site. Since I don't have piping setup, a reply to a support ticket email means I start dealing with the support ticket in email instead of the support system. Anyway, having the ability to set a perm header to the email or pre-populate the text area with a header when I reply to a support ticket would be great. This header outlines that the user needs to respond to the support ticket via the website and not to the email. IPS doesn't even have this feature. I have to copy paste the header in the support ticket reply. Yes, I could remove the content from the email or I could use a noreply@ address.
updated by @jimmy: 03/31/18 04:16:15PM

Random Thoughts

Just some random thoughts about JR modules, etc.

1. Private Notes module should have a limit on the number of Private Notes a quota can send based on day or time, etc. I have a real problem with people signing up and spamming via Private Notes in other software I use. That software has a setting allowing me to limit the number based on user group. For new users I have like 5 a day. Over time that increases.

2. Might want to include instructions on how to make a forum appear to be a sitewide forum. You specifically state in the Forum module docs that the forum is for profiles only. In one of your prebuilt templates (video template) forum is featured as a main top link on the main page of the demo. Using a @community account the forum appears to be sitewide. Maybe including instructions on how people can create a mock site forum would be helpful.

Personally, I'd love to see the forum module as a site module AND in the profiles. I think a lot of people would use a sitewide forum. Something that was easy to turn on and have the forum module be a forum.

3. Warning system. A close ended notice to a member. If I go to a piece of content which breaks a site rule, I need to be able to warn that person and assign points. I would need to be able to setup custom warnings which I could send on the fly. Warning can be 0 to XXX amount of points. After so many point they get restrictions up until being banned.

It would be cool if a warning system had three levels of warnings. Notice, Warning, Points. Each notice would look different. Notice is friendly, warning is a nudge, and points are punishment.

4. Outdated email. I see there is a kickbox module. I have a module on my other site where I can outdate a persons email. It requires a member to change their email when they visit the site again. I use this when I get a bounced email back from Amazon SES.

I've never used kickbox. But I know it costs money. I get about 2-3 bounces from member per day on my forum. I just manually visit their profile in the admin and check "outdated email" - which flags the email as outdated, halts all emails from the system, and requires the user to enter and validate a new email upon next visit to the site.
updated by @jimmy: 03/31/18 02:43:08AM

Problems Installing

Thank you! I appreciate your and @michael help!

Problems Installing

Not sure, actually I only need the 6 mentioned above now. When I actually go live with a site, I'll need to buy more. Better yet, when I need them I'll hit you up and we can talk about a price for 10 or 15 licenses total (including the test licenses).

Problems Installing

Everything is working on my end. Just installed premium module from the marketplace.

Problems Installing

Excellent! How much is it to bump that up to 10 licenses?
updated by @jimmy: 03/26/18 01:37:30PM

Problems Installing

You're good to go.