Jump to content

Welcome to DevFuse Forums

Sign In  Log in with Facebook

Create Account
Welcome to DevFuse Forums, like most online communities you must register to view or post in our community, but don't worry this is a simple free process that requires minimal information for you to signup. Be apart of DevFuse Forums by signing in or creating an account.
  • Start new topics and reply to others
  • Subscribe to topics and forums to get email updates
  • Get your own profile page and make new friends
  • Send personal messages to other members.
Guest Message by DevFuse

(View All Products)Featured Products

  • Donations

    Help fund your forum with donations, setup goals and track member donations. Offer rewards for members donating.
  • Timeslips

    Have your members submit their race times and share with others.
  • Videos

    Allows your members to submit their own videos for community viewing. Support is included for all the major video sites.
  • Forms

    Build your own forms for your members without coding experience. Support included for pm, email and topics.
  • Collections

    Build a community database of items for your members. Full features custom fields included.


[IPS] Minimum Posts to Use Fast Reply

This topic has been archived. This means that you cannot reply to this topic.
No replies to this topic

#1 News Bot

News Bot

    Dedicated Member

  • Members
  • PipPipPipPipPip
  • 1,909 posts
  • IP.Board Version:N/A

Posted 28 April 2012 - 02:24 PM

This is a very basic hook that will remove the Fast Reply from Topic View for those who have less than the configurable amount of posts.Installation and Documentation (like it's needed... there's only one setting lol) are included in the Download, in the install.txt file.The hook is very basic in nature, and may be expanded in the future. It was just something I quickly wrote. Note, that there is a bug in IP.Board in regards to the mobile skin that requires a bit of a workaround. I've added code to workaround the issue, and to pre-emptively adjust itself for the next version when the bug is fixed (assuming it's fixed in 3.3.2 - at time of writing, the issue is still confirmed.)Of course, if it's not fixed in 3.3.2, I'll release a new version as necessary.

View Resource