Jump to content

Community

Alismora

Members
  • Content Count

    174
  • Joined

  • Last visited

1 Follower

About Alismora

  • Rank
    Member
  • Birthday November 12

Contact Methods

Profile Information

  • Gender
    Female
  • Location
    US

Recent Profile Visitors

726 profile views
  1. Is there a way that the Manage setting can be group based similar to how permissions are set for topic creation? I only want specific groups to be able to set covers on new topics and existing topics. Currently, turning Manage on will allow all topic authors, regardless of group, to add a topic cover to their topics.
  2. Sorry, can't edit my post, but I'd still like to request this feature. I can't get the uploader to work at the top of the topic when I make the change.
  3. Is there a way to set which groups can manage topic covers on existing topics? I'd like to make this an exclusive feature for members of a specific group, however, I'm not able to give them access to upload/update a topic cover on an existing topic or after a topic is created. Never mind, I added an if array statement within the nbTopicCover template and it's done what I needed. Would be a nice built-in feature, though.
  4. Alright, I'll just leave that here as a possible feature request. I'm still interested in buying this, but I'll hold off until 4.4 releases before I add new things to our site.
  5. I'm very interested in this. Is there a way to set a limit to how many topics can be pinned in each forum section automatically? Let's say I only want 5 topics pinned at a time in Forum A and there's already 5 topics pinned. If someone attempts to purchase a pin in Forum A, the options will be grayed out. Is this doable?
  6. @TheJackal84 Is there a way I can move the social media icons to the bottom of the authorpane after all of the custom fields and post count/rep?
  7. I can confirm that it works if you have it set to delete content when the tool is used. Was already on my test site so decided to try it out because I wasn't aware it did all of that myself. If you don't trust your moderators with that power, they shouldn't have access to the button so that you're able to use it at its full potential. There are other alternatives that can be used to stop a spammer without using that tool by accessing their ACP profile that your moderators can utilize. (Ban them, restrict from posting, etc.) I have a custom script on my site that removes cover photos, background photos(custom), and reverts the profile photo to the set default when someone is moved out of our member and staff groups; in this case banned. That's an option as well if you don't want to use the spam tool, though you'll need to commission a developer for that.
  8. Guests can't view it, but the arrowchat website displays what the chat looks like, though I do not use apps or have the full bar displaying.
  9. I added arrowchat to my site and it's the best option for what we needed, which was an IM system with the ability to create simple chatrooms. We didn't want to add any discord-like chat systems to our site because we would rather our member's utilize clubs instead of creating rooms with custom channels.
  10. Looking at how big the bug list got after this beta dropped. I think I'll wait for a few more updates to try the beta out on my test site.
  11. Would be great if there was an option to show an error page when people visit profiles of banned users so that other members can't interact with it any longer.
  12. This was an option in 4.2 that was removed in 4.3 and I'm not sure why. They also removed the ability to view the display name history from the member's ACP profile as well. Both of these features were very useful for my community and would love to see them implemented back. We would use the option to clear name change histories when rebuilding accounts that existed before we switched to IPB, and now we can no longer do that, which leads to some very messy history lists.
  13. That's absolutely understandable. Knowing the max we can use for now will help us until 4.4 releases and you're able to update! Thanks a lot for your continued support.
  14. Besides adding permission to a staff group so they could submit applications, nothing was changed to my knowledge. I will test a few things out and come back to you to make sure we did everything exactly the same as before. Edit: I've found where we went wrong. I made a test application with Number of Places set to 5, no error. Another with Number of Places set to 100, no error. A third one with Number of Places set to 1000, received this error. UPDATE `staffappsystem_applications` staffappsystem_applications SET `sas_app_title`='Test 1000',`sas_app_title_seo`='test-1000',`sas_app_description`=' <p> Test </p> ',`sas_app_nr_available`=1000,`sas_app_position`=1,`sas_app_group_to_promote`='0',`sas_app_image`='',`sas_app_applicants_fields`='1',`sas_app_restriction_posts`=0,`sas_app_restriction_reppoints`=0,`sas_app_restriction_daysjoined`=0,`sas_app_restriction_age`=0,`sas_app_restriction_groups`='*' WHERE sas_app_id=3 IPS\Db\Exception: Out of range value for column 'sas_app_nr_available' at row 1 (1264) #0 /home/gasrforu/public_html/system/Db/Db.php(990): IPS\_Db->preparedQuery('/*IPS\\Patterns\\...', Array) #1 /home/gasrforu/public_html/system/Patterns/ActiveRecord.php(492): IPS\_Db->update('`staffappsystem...', '`sas_app_title`...', 'WHERE sas_app_i...') #2 [internal function]: IPS\Patterns\_ActiveRecord->save() #3 /home/gasrforu/public_html/init.php(460) : eval()'d code(120): call_user_func_array('parent::save', Array) #4 [internal function]: IPS\Patterns\rules_hook_ipsPatternsActiveRecord->save() #5 /home/gasrforu/public_html/init.php(460) : eval()'d code(324): call_user_func_array('parent::save', Array) #6 /home/gasrforu/public_html/applications/staffappsystem/sources/Applicationrecord/Applicationrecord.php(690): IPS\rules_hook_ipsContent->save() #7 /home/gasrforu/public_html/system/Content/Item.php(330): IPS\staffappsystem\_Applicationrecord->processForm(Array) #8 /home/gasrforu/public_html/applications/staffappsystem/sources/Applicationrecord/Applicationrecord.php(1163): IPS\Content\_Item::createFromForm(Array, Object(IPS\staffappsystem\Category), true) #9 /home/gasrforu/public_html/system/Content/Item.php(85): IPS\staffappsystem\_Applicationrecord::createFromForm(Array, Object(IPS\staffappsystem\Category)) #10 /home/gasrforu/public_html/applications/staffappsystem/modules/front/general/submit.php(82): IPS\Content\_Item::create(Object(IPS\staffappsystem\Category)) #11 /home/gasrforu/public_html/system/Dispatcher/Controller.php(85): IPS\staffappsystem\modules\front\general\_submit->submit() #12 /home/gasrforu/public_html/applications/staffappsystem/modules/front/general/submit.php(28): IPS\Dispatcher\_Controller->execute() #13 /home/gasrforu/public_html/system/Dispatcher/Dispatcher.php(146): IPS\staffappsystem\modules\front\general\_submit->execute() #14 /home/gasrforu/public_html/index.php(13): IPS\_Dispatcher->run() #15 {main} So it looks like we set the number of places too high.
×
×
  • Create New...