Phillyman

Sometimes I feel like poor little Pages gets no love, the built in Wiki feature is worth its weight in gold. To be able to stand up databases and leverage our members to create/modify those pages....is a HUGE feature. Lets try to flesh out the recognition of our member when they add in information. Right now we can assign points and achievements for creating records, but generally, if I am standing up a huge database....I want to have control over the initial record creation.
Why?
Well lets take video games, its very easy to go grab a list of every Nintendo Entertainment System game ever released in the USA. However, if I let USERS create those records, generally there may be duplicates, because when it comes to "The Legend of Zelda", how are we handling that name? Under T for The? Under L for Legend? So I generally pick the naming scheme and then dump in the records in mass. But then its up to members to add in the information of said records. But we currently do not recognize revisions in any meaningful way.
Lets look at Wikipedia...
https://en.wikipedia.org/wiki/The_Legend_of_Zelda
If you go to that page, you can drop down to the revisions....
https://en.wikipedia.org/w/index.php?title=The_Legend_of_Zelda&action=history
and you can then see who the contributors are, and drill down further....
https://en.wikipedia.org/wiki/User:Sergecross73
We can then see the following under his wikipedia profile....

As you can see, very easy to see this user has made 76,400+ contributions to Wikipedia....along with many other automatically recognized "stats". People like to be recognized for their hardwork, even when its just a few mentions on their profile of their accomplishments on a site.
 

I like this, because lets say once you set up the following....
 
Signed in 1 day in a row Signed in 7 days in a row Signed in 31 days in a row Signed in 90 days in a row Signed in 180 days in a row Signed in 365 days in a row Once a member gets thru that, there is nothing more to gain, unless admins keep expanding it indefinitely.  Or to your point, you let them repeat.
This member has won "Signed in for 7 days" three times!
etc...

I like this, because lets say once you set up the following....
 
Signed in 1 day in a row Signed in 7 days in a row Signed in 31 days in a row Signed in 90 days in a row Signed in 180 days in a row Signed in 365 days in a row Once a member gets thru that, there is nothing more to gain, unless admins keep expanding it indefinitely.  Or to your point, you let them repeat.
This member has won "Signed in for 7 days" three times!
etc...

Just thinking more about this. This might actually make Badges/Achievements catch up faster. Lets say you have 20,000 members, if the badges run backwards to check if they have been acquired, they only need to hit the highest achievement and then the system would know to give all the lower acheivements as well.
So if right now the system goes like this....
Member 1, Does he have 1 post? If so give achievement 1 post Member 1, Does he have 10 posts, If so give achievement 10 posts ..... Member 1, Does he have 100,000 posts, if so give achievement 100,000 posts  
Well that means Member 1 has to be run thru each level to see if he has met the condition. However if the badges are grouped, You could work backwards from 100,000 and lets say he only has 55,000 posts, then the check only has to do the following....
Member 1, Does he have 100,000 posts, if so give him achievement 100,000 posts Member 1, Does he have 50,000 posts, if so give him achievement 50,000 posts Condition met, Automatically skip/give 1-25,000  
If so, this could possibly speed up rebuilds against large communities with large amounts of badges/achievements.

So I love the new achievement, badges, ranks system. I plan to create the following badges
Created 1 Topic, 10, 25, 50, 100, 250, 500, 1000, 2500, 5000, 10,000, etc... Replied to 1 Topic, 10, 25, 50, 100, 250, 500, 1000, 2500, 5000, 10,000, etc... Uploaded 1 Image, 10, 25, 50, 100, 250, 500, 1000, 2500, 5000, 10,000, etc... Gave 1 Reaction, 10, 25, 50, 100, 250, 500, 1000, 2500, 5000, 10,000, etc... Submitted 1 File, 10, 25, 50, 100, 250, 500, 1000, 2500, 5000, 10,000, etc... Signed in for 1 day, 7 days, 1 Month, 3 Months, 6 months, 12 Months, 24 Months concurrently  
Anyhow, this is obviously going to lead to a TON of badges, My community has been running IPB since 2005. I want to give credit for past items created. So I would say let us create groups, put similar rules into those groups, and then choose to ONLY show the highest badge earned. So a user with 500 topics would only show the 500 Topics badge, and not the 6 previous badges. It's a given that if you have the 500 topics badge, that you would also have the 250, 100, 50....etc.
 

Just thinking more about this. This might actually make Badges/Achievements catch up faster. Lets say you have 20,000 members, if the badges run backwards to check if they have been acquired, they only need to hit the highest achievement and then the system would know to give all the lower acheivements as well.
So if right now the system goes like this....
Member 1, Does he have 1 post? If so give achievement 1 post Member 1, Does he have 10 posts, If so give achievement 10 posts ..... Member 1, Does he have 100,000 posts, if so give achievement 100,000 posts  
Well that means Member 1 has to be run thru each level to see if he has met the condition. However if the badges are grouped, You could work backwards from 100,000 and lets say he only has 55,000 posts, then the check only has to do the following....
Member 1, Does he have 100,000 posts, if so give him achievement 100,000 posts Member 1, Does he have 50,000 posts, if so give him achievement 50,000 posts Condition met, Automatically skip/give 1-25,000  
If so, this could possibly speed up rebuilds against large communities with large amounts of badges/achievements.

So I love the new achievement, badges, ranks system. I plan to create the following badges
Created 1 Topic, 10, 25, 50, 100, 250, 500, 1000, 2500, 5000, 10,000, etc... Replied to 1 Topic, 10, 25, 50, 100, 250, 500, 1000, 2500, 5000, 10,000, etc... Uploaded 1 Image, 10, 25, 50, 100, 250, 500, 1000, 2500, 5000, 10,000, etc... Gave 1 Reaction, 10, 25, 50, 100, 250, 500, 1000, 2500, 5000, 10,000, etc... Submitted 1 File, 10, 25, 50, 100, 250, 500, 1000, 2500, 5000, 10,000, etc... Signed in for 1 day, 7 days, 1 Month, 3 Months, 6 months, 12 Months, 24 Months concurrently  
Anyhow, this is obviously going to lead to a TON of badges, My community has been running IPB since 2005. I want to give credit for past items created. So I would say let us create groups, put similar rules into those groups, and then choose to ONLY show the highest badge earned. So a user with 500 topics would only show the 500 Topics badge, and not the 6 previous badges. It's a given that if you have the 500 topics badge, that you would also have the 250, 100, 50....etc.
 

So I love the new achievement, badges, ranks system. I plan to create the following badges
Created 1 Topic, 10, 25, 50, 100, 250, 500, 1000, 2500, 5000, 10,000, etc... Replied to 1 Topic, 10, 25, 50, 100, 250, 500, 1000, 2500, 5000, 10,000, etc... Uploaded 1 Image, 10, 25, 50, 100, 250, 500, 1000, 2500, 5000, 10,000, etc... Gave 1 Reaction, 10, 25, 50, 100, 250, 500, 1000, 2500, 5000, 10,000, etc... Submitted 1 File, 10, 25, 50, 100, 250, 500, 1000, 2500, 5000, 10,000, etc... Signed in for 1 day, 7 days, 1 Month, 3 Months, 6 months, 12 Months, 24 Months concurrently  
Anyhow, this is obviously going to lead to a TON of badges, My community has been running IPB since 2005. I want to give credit for past items created. So I would say let us create groups, put similar rules into those groups, and then choose to ONLY show the highest badge earned. So a user with 500 topics would only show the 500 Topics badge, and not the 6 previous badges. It's a given that if you have the 500 topics badge, that you would also have the 250, 100, 50....etc.
 

Also wondering if this mod will be updated for 4.6.

Of course. 

Thanks for the quick reply, no rush. I just am planning my upgrade from 4.4.X and have a few mods that I need to know if I am taking into the future or looking for other ways to accomplish. 🙂

I know Invision Power Board is old, but some people still use and maintain it like me.
I am willing to pay up to 1000$ if somebody is willing to make a payment gateway for Nexus.
Accepting BTC/LTC/ETH (LTC and ETH are optional).

This plugin will display files from subcategories when the category you're browing hasn't files.
 
 

What's New in Version 1.0.1:
Script optimization to list files from all subcategories levels

This a THOUSAND TIMES OVER.
Example, I run a video game forum. I should be able to create the following Gallery categories....
Box Art Manuals Cartridge/CD Scans Screenshots Then I should be able to go create an IP Content Database called Video Games, create sub categories for Super Nintendo, Sega Genesis....and then add database fields for......
Box Art Manuals Cartridge/CD Scans Screenshots Which then I should have an option to choose "Gallery Media" as a field type and reference those images from within my Databases. It is redundant to ask my members to upload images to the Gallery, and then upload them again into IP Databases as attachments.
 
P.S. - This also applies to the IP Downloads and their screenshots. On some parts of my site I now have 3 copies of the same image
P.S.S - Lets also get an IP Downloads field type for the databases, so we can natively call files from our databases. Would be nice to also have a Blog Database field for calling blog entries. If my members are writing their own blog reviews of games, they should be able to have those show up on the database records as well.
 

This is too large of a scope for a single feature suggestion. I'll be starting a gallery review feedback topic in the client lounge this week and we should include this to formulate a game plan. 

Would be helpful to my site also, I have certain video game forums, which I would like the system attached as the suffix

ex.
Super Mario World (Super Nintendo)


My members wont see the benefit, but my search engine results will :)

You know, 14 hours is far too long to just let a ticket go without even bothering to respond to it.
Of course, during that time, I was able to find and handle the issue myself, but if this is the typical 'response time', I'll find somewhere else to take my business.

I'm not an impatient guy, 4-5 hours is reasonable, at least as long as things are submitted during business hours (which this was), but 14 hours is pushing it.
Even better? A second reply took 45 minutes or less. Kinda ironic.

The moral of the story? DON'T keep your customer waiting. If they open a ticket, they deserve a non automated reply, same business day, urgent or not.

Or its only acceptable if you kiss their arse :ermm:

Someone's a little short tempered.

Arguably your post is feedback, but it's obviously a bug in the software and would be more easily addressed in the bug tracker. And yeah, people read it, especially those who matter: people who actually fix the bugs. The very nature of the bug tracker will pretty much guarantee acknowledgement from a staff member. You posted in a public forum: expect public responses.

Are you staff or just trying too hard?

I am pretty good when it comes to thinking of ways to misuse a system. As such it would be nice to have these two features built into the Reputation System to prevent abuse.

1) Set a maximum number for how many Negatives/Positives a certain member can assign another. I have my system set up to allow 10 positive and 5 negative votes per day. It would be nice to set up a monthly or weekly limit so that one member cant constantly use his pos/neg votes against 1 member. Maybe like "Only allow 10 Negative votes per month against any given member", the same would have to be done for the Positives so people couldnt just buddy up to inflate their numbers.

2) Another way to abuse would be going back and voting on EVERY post that a member made. As such I think we should have the ability to only let people rate the last (30,60,90) days worth of posts. People should not be able to go back 3 years and give Reputation.

I think those two items will prevent people from abusing the Reputation System, It would also be nice to have a way to search members by their Reputation levels and sort them Acc/Dec.

Well if suggestion #1 is put in place, then this could be allowed. But as it is right now, the system can be abused. People should not be able to assign out Negative points to a member over and over again. Even at my low number of 5....thats still 150 points per month that could be used against a member. I have yet to find a way to SEE or PREVENT the abuse that could happen in this system. Are there log files for the Rep system that I can view? I think it would be important to limit the overall number of reputation that one member can directly assign another.