Ryan Ashbrook

IPS Staff
  • Content count

  • Joined

  • Last visited

  • Days Won


Ryan Ashbrook last won the day on April 21

Ryan Ashbrook had the most liked content!

About Ryan Ashbrook

  • Rank
    Keeper of the Real
  • Birthday 03/16/1988

Contact Methods

IPS Marketplace

  • Resources Contributor
    Total file submissions: 8

Profile Information

  • Gender
  • Location
    Cincinnati, Ohio
  • Interests
    Forums and Music. That's basically it.

Recent Profile Visitors

39,089 profile views
  1. I actually have a genuine interest in podcasting, though I've never actually done anything with it. I did one about ten years ago, but it never saw the light of day, thankfully lol
  2. Yes, this has been an option for some time - it was in 3.x as well, if I recall.
  3. Plugins can extend the default extensions for the System application.
  4. Of course. The system is built on application extensions, so applications can create their own steps. We will provide developer specific updates soon on how to integrate with this feature, and others in 4.2.
  5. To expand on this - yes. So say, for example, you do not require users to set a profile photo, but then add a step so that it is required, then all users who did not set one previously will then be prompted to do so.
  6. Completing long and complex forms online is tedious. It can be off putting having to fill in a lot of information before you can join a site or service. You may find that potential members never bother to convert from a visitor. How to convert guests into regular members is an often asked question. The simple answer is to lower the barrier to entry. Invision Community 4 already allows you to register with Facebook, Twitter, and other networks with ease. "Complete My Profile" is a system that will lower the barrier of conversion. Guests only have to complete a very basic form to gain membership. Members are then asked to complete any custom profile fields you require. You can also set up steps that group items together to encourage existing members to add more information to their public profile. Members with a complete profile and user photo provide others with much more engagement and personality. Registering If we look at registering first. Clicking "Sign Up" will only show a simple modal form with as few fields as possible. If you have required steps, and after any member validation flow, the complete your profile wizard is shown. This enforces required fields and the member cannot skip them or view other pages until completed. Of course, you may have steps that are not set to required. These are available too, but are skippable. Members can complete skipped steps later. A dismissible progress bar shows to members that have uncompleted steps. Once dismissed, it no longer displays in the header of the site. This same progress bar is always shown in the members' settings overview panel, in the user control panel. This will prompt members with incomplete steps. If you set up a new required step, members have to complete the step before being able to browse again. This will ensure that all regular members have completed profiles. Admin Control Panel You will create new steps in the Admin Control Panel. Each step can contain multiple elements of a single group. This step can be set to required to enforce completion or suggested to allow it to be skipped. The basic profile group contains things like user photo, birthday and cover photo. Choose any of these for this step. The custom profile field group contains any fields you have set up already. You can switch off this system if you feel it does not fit your needs. When disabled, you get the normal registration form. Reducing the complexity of membership can only help convert more guests into contributing members. Enforcing required steps ensures that you capture data across your membership. We hope you enjoy this feature and you see an increase in guest conversion with Invision Community 4.2.
  7. The Pages app comes with an Articles database by default which is very close to our News page. As Rikki mentioned, we've only made a few small theme adjustments.
  8. The underlying architecture for Reactions is completely different from the old reputation system, actually. While some of it is still there ("reputation points" for instance, and various settings), the two systems are actually completely different and those similar elements have been adapted to suit.
  9. The only time I ever drink Coke Zero is when I'm at a meet-up.
  10. I actually wanted to come back around and give Reactions a specific mention. I wrote the backend and Rikki did the interface, and it was really fun to watch the whole feature evolve from start to finish. Actually, that's not true! You also added DailyMotion as an oEmbed provider. I remember because I was sitting next to you when you did it lol
  11. Not at this time, I'm afraid.
  12. Groups, with permission, can still see Display Name History on the front-end on profiles. That particular area will only show name changes, however - not all of the other data. What that sentence means is just that the underlying system to store those changes has been moved over from it's own system, to this one, for consistency. The same applies to Commerce customer history - there is no longer an independent system to store information on transactions, support requests, etc. That has all been migrated to this new central system, though the relevant data will still display on the Commerce customer information page.
  13. Our PHP / MySQL requirements have not changed (PHP 5.6 as a minimum - PHP7 or higher recommended, and MySQL 5.1 as a minimum with 5.6 or higher recommended).
  14. You see all IP's ever used, right down to specific actions (such as posting). As of 4.2 we can track devices as well.
  15. Speaking as a user - I don't think it's really feasible to get rid of Emoticons entirely. For instance, there is no Emoji replacement for my personal favorite: I definitely agree, though - we can place more emphasis on Emoji once we are able to officially require MySQL 5.5.3 as the minimum version (currently, it's 5.1 - at least 5.5.3 is required to use full unicode in MySQL).