Davyc

I vote no. Leave it to a plugin.
If there were one I'd like to put my true identification which is none of the above listed. I identify as a "Rainbow Princess Unicorn of the Fourth Order" in which I would feel both left out and angry because my identification isn't listed there.
I feel that this is a niche need and therefore needs a niche solution. Plugin. Plugin. Plugin.
 
Edit: To be clear I joke because I believe that this opens up a pathway for people to attack others because of their gender preference. I have removed gender options completely from my community and people can choose to identify in their introduction, in their about me or not at all. It is up to them to make that choice, not me.

Please keep this madness out of IPB.

I think this is better as a plugin.
It's a seriously infected issue that will cause division in the user base. Personally I would never add it, unless my community is based around a community that think this is important. The reason for that is that it is pretty much a safe bet that people will behave just as bad as on Twitter and I think we have enough trolls to worry about to not add strife amongst our members if we can prevent it.
I am all for expressing yourself and adding whatever labels you feel is appropriate to your community, but this is what custom fields are for and this is what plugins should be used for in my opinion.

Running IPS 4.6 on my upcoming site (it's going to be a while before it launches) and so far everything is working the way I expected it.  Not using a custom theme on this site, but I am customising the default theme and it's working out great.  Sample from the forums below:

A few of @opentype plugins seem to be working OK in theme as is @onlyME Friends app - the support section is showing them as Important Issues, but they work:

That's 2 plugins, 1 app and the default theme which I've customised.
All I can say is, fantastic work guys - love the new Achievements and I'll be tinkering with those too.  I'll have to hold off updating my Movie Buffs site until all the apps and plugins I use are updated, but that's no big issue.  So far, loving it.

We love a cross promotion 😅

Running IPS 4.6 on my upcoming site (it's going to be a while before it launches) and so far everything is working the way I expected it.  Not using a custom theme on this site, but I am customising the default theme and it's working out great.  Sample from the forums below:

A few of @opentype plugins seem to be working OK in theme as is @onlyME Friends app - the support section is showing them as Important Issues, but they work:

That's 2 plugins, 1 app and the default theme which I've customised.
All I can say is, fantastic work guys - love the new Achievements and I'll be tinkering with those too.  I'll have to hold off updating my Movie Buffs site until all the apps and plugins I use are updated, but that's no big issue.  So far, loving it.

Please make it 8PM on a Friday (EST) and be sure to run the upgrader on mobile with 2% battery life left. Thanks and tell the boys in support Lindy sent you!

I imagine you could just do this with Forum/Group permissions.. Restrict all groups from posting new topics in that forum and then make a group which has permission, and add yourself to that group.

Hi @Michael R I'm always happy to help out with anything to do with CSS - I've spent hundreds of hours tracking down codes to make changes with CSS across a number of platforms, so if you need help with anything PM me with the changes you want, with links, so I can take a look and advise you.  If you will pardon the analogy, my custom CSS file is like a christmas tree lol.  But it's fun tracking things down and making changes.
With regards to not being able to find specific movies, that's down to TMDB which is a different database to IMDB.  TMDB allows you to add movies once you've registered with them - if you do this yourself then those movies will become available for you to add to your own database.  You can add the movie title, poster images, actors, directors, crew, YT trailers, and general images and whole bunch of other data.  It's fun to be able to do that too, because you get to add what's important for you.
Always happy to help 🙂
 

I love Polaroid photos. ( We had a camera, but I replaced it with a modern approach  => replace the camera with a Polaroid printer:D )
Make 10 pics on the iPhone or camera and then send the best to the Polaroid printer🤣 Old School Results where nobody knows if the baby on the pic is me or my daughter... MUCH MORE FUN!!!

He had an actual Polaroid camera for reasons I still do not understand. 

I wasn't expecting Charles to be so young looking.  I had this impression in my mind that Charles was in his early 50's, grey hair, tall with a stern look about him.  He looks like a really nice chap that I could easily have a beer with 🙂
 

When doing your refresh can you also take a look at the help files?  Some are way out of date and most don't give clear examples on how to implement some of the options available.  Not everyone is a PHP coder, but many don't mind getting their hands dirty now and then to make some positive changes to their sites.
An example would be (and this is just an example as it comes to mind) - how to implement Google Maps.  The instructions are out of date and it was a minefield navigating how to set it up - I gave up at the finish.  Another would be how to use custom fields and how to best use them, including any CSS examples that are needed to dress those fields so they look the part. Plain English examples are needed.
I'm sure that a lot of people would appreciate being able to make changes without any horror stories occurring.  As the suite evolves so should the help files and if you are including community enhancements that involve third parties, who are also evolving, then the help files should reflect this.  I believe this is just as important as a site refresh and apologies for hijacking the topic, but a refresh should be more than just some site cosmetics 🙂
 

I can second this - most of the changes on my own site are just down to CSS changes in the custom.css file.  Once you know which descriptors affect which elements you can nail things down pretty much the way you visualise it in your mind.  It's well worth looking into - a good place to start is: https://www.w3schools.com/css/
@christopher-w those are some really nice layouts you have there.  I know your site has been a WIP for a long time, but the dividends are paying off for taking your time; I look forward to seeing the finished works when you publish them 🙂
 

I think there are two different use cases:
Editor for user-generated content. Should be simple, not too many options, clear and foolproof. I think that the actual IPS editor fulfills the requirement. Editor for articles wrote by admin. Should be powerful, have many options (text positioning, blocks, columns, grids, custom code pieces, custom styles, extendable with SEO and other plugins, have additional extensions via Marketplace etc.) For this case, the actual IPS editor is not enough. 

If a guide is out of date, just hit the report button and let us know. Someone will update it soon after we're aware. (Google and Facebook especially change their interfaces very often).

When doing your refresh can you also take a look at the help files?  Some are way out of date and most don't give clear examples on how to implement some of the options available.  Not everyone is a PHP coder, but many don't mind getting their hands dirty now and then to make some positive changes to their sites.
An example would be (and this is just an example as it comes to mind) - how to implement Google Maps.  The instructions are out of date and it was a minefield navigating how to set it up - I gave up at the finish.  Another would be how to use custom fields and how to best use them, including any CSS examples that are needed to dress those fields so they look the part. Plain English examples are needed.
I'm sure that a lot of people would appreciate being able to make changes without any horror stories occurring.  As the suite evolves so should the help files and if you are including community enhancements that involve third parties, who are also evolving, then the help files should reflect this.  I believe this is just as important as a site refresh and apologies for hijacking the topic, but a refresh should be more than just some site cosmetics 🙂
 

Thanks Dave, it's been a while since we first discussed this when I was in St Ives.
We haven't been working non stop though - it comes and goes. We go through cycles of love/hate with the suite. Every now and again we come up against a silly gotcha which takes all the enthusiasm out of the project. And then after a couple of months or so, refreshed, we try again. And on it goes. 
But anyway, we are getting closer, albeit increasingly using less and less of the Invision UI. We are also starting to write our first plugins which seem easy to put together, hopefully leading to less reliance on the marketplace. 
Thanks for your support. I am equally impressed with what you've done with Star Trek, which looks to be unique 🙂.

When doing your refresh can you also take a look at the help files?  Some are way out of date and most don't give clear examples on how to implement some of the options available.  Not everyone is a PHP coder, but many don't mind getting their hands dirty now and then to make some positive changes to their sites.
An example would be (and this is just an example as it comes to mind) - how to implement Google Maps.  The instructions are out of date and it was a minefield navigating how to set it up - I gave up at the finish.  Another would be how to use custom fields and how to best use them, including any CSS examples that are needed to dress those fields so they look the part. Plain English examples are needed.
I'm sure that a lot of people would appreciate being able to make changes without any horror stories occurring.  As the suite evolves so should the help files and if you are including community enhancements that involve third parties, who are also evolving, then the help files should reflect this.  I believe this is just as important as a site refresh and apologies for hijacking the topic, but a refresh should be more than just some site cosmetics 🙂
 

When doing your refresh can you also take a look at the help files?  Some are way out of date and most don't give clear examples on how to implement some of the options available.  Not everyone is a PHP coder, but many don't mind getting their hands dirty now and then to make some positive changes to their sites.
An example would be (and this is just an example as it comes to mind) - how to implement Google Maps.  The instructions are out of date and it was a minefield navigating how to set it up - I gave up at the finish.  Another would be how to use custom fields and how to best use them, including any CSS examples that are needed to dress those fields so they look the part. Plain English examples are needed.
I'm sure that a lot of people would appreciate being able to make changes without any horror stories occurring.  As the suite evolves so should the help files and if you are including community enhancements that involve third parties, who are also evolving, then the help files should reflect this.  I believe this is just as important as a site refresh and apologies for hijacking the topic, but a refresh should be more than just some site cosmetics 🙂
 

To recap:
You do not need to enable the new rules, badges and ranks. There is an option pre-upgrade that asks you if you want to switch to the new system or not. If you choose not to, then you retain the existing ranks you already have.


The upgrade will also move any custom titles across to a new custom profile field.

If you want to show the custom member title under the user's photo in a post, then just switch on these custom field settings which are off after the upgrade.


 
 

Thanks again Davyc, will get this uploaded right away!

Wrap it in {{ }}

@opentype Hi Ralf, is there anyway to turn off the sidebar in the listings view? I have the system categories block on the index page which is fine, but I don't want it to appear in the actual record view as it takes up real estate on the page and it would be better for the listing to have more breathing room.
I understand that \IPS\Output::i()->sidebar['enabled'] = FALSE; can be used to turn off the sidebar, but I can't find where to place this (if indeed it can be placed) in which template, but only for the record view page.
With thanks 🙂