Chris Anderson

The JavaScript approach for the template change is amazing and the way to go IMO! 

I think there is a critical mass of Improved Club Enhancements users who feel that Leaders need to have more permissions. At least the permission to add members. If not, what use do the leaders have? If they can't do anything more than a moderator, why have them at all?

I have added a wrapper div so you can target that with theme hooks.
 

@Andy MillneCould you please have the developers address this issue as part of the Calendar Improvements:
 

Something with this feature, please? 🙂 🙂
 

Yeah, linking or embedding a third-party solution is probably better. Invision Community has nothing to accommodate such events currently. I am currently using Pretix for online events and conferences, but of course there are many many providers from all around the world. 

So for example, if I want to set up a category for shops that offer equipment repair, theres no way of someone searching specifically for one thats in driving distance of them. I understand this isn't really the purpose of this app, but for my own use it would open up a whole new range of possibilities. I'd be prepared to pay for a secondary plugin for your app that would achieve this. Unless of course you were prepared to make it part of the core app which would be awesome.

Copy the highlighted value below into your cron job:

 

You can also use a third-party web service like cron-job.org which is free.  You just type the value into the url field and choose a 1-minute schedule. Be sure to save the settings in the ACP prior to starting a cron job or use a web service.  Verify that the tasks are running every minute after setting up either type of service.

Happy Hump Day, team! Sort of. 😔 
One of Invision Community's founding fathers, @Rikki, is amicably moving on from Invision Community to pursue another exciting opportunity. This is his last week with us. He has a few parting words to share with you:
 

Rikki has been an instrumental player in Invision Community's success; we're bummed to see him go, but at the same time excited for him to spread his wings. 
Please leave some well wishes for Rikki in the comments! 
---
Speaking of the team, @Matt Finger wrote a new dev blog post touching on the PHP8 Compatibility Scanner, our Pre-Upgrade Resource Checker and a full change log for our upcoming September release:
 
 
--- 
And last but not least, 4.7.2 Beta 1 is officially out. Check out the release notes here.
See you in the replies. 🙏 

you will not regret it... go for it 😉

You might consider checking out this app and the various add-ons that integrate with it:
 

Hi there
Could a feature be added for complete order data cannot be exported into a CSV/spreadsheet please?
It's very difficult to complete financial reporting without being about export this as well as transaction data.
Thanks

If you are selling your house, you want to get the best possible price. If you place lots of ads in the newspaper and social media and have loads of people show up, you are NOT guaranteed the best price if your house "looks" undervalued.
The CSS Project is akin to advertising and the continued improvement of the suite will go a long way towards upping the site's overall perceived value.  Also known as "curb appeal".
It doesn't do us much good having lots of folks knock on our door if they immediately walk away to check out one of the other bright and shiny houses down the street.

Wouldn't it be easier on your staff, third-party developers and customers to improve upon CSS in a phased approach?
Why not break down the CSS Project into sub-projects? 
One sub-project you concentrate your attention on commerce.  You develop the "new" features you want to offer for that module while addressing any appropriate CSS changes needed.  You concentrate many IPS developer's and testers eyes on just that section of your overall codebase.
By concentrating "lots" of eyes on "one" module of the suite you will make it easier to identify any underlying performance, security problems or bugs. At the end of such a CSS sub project, you will end up with a much better underlying codebase then trying to tackle the entire suite all at once. Once that CSS sub project is "golden" you move on to the next sub-project
Upon release of the "CSS Project - Sub Project X" the third-party developers, theme designers and your customer base only have to make appropriate changes to "one" section of the IPS suite not the entire suite. 
By adopting a more phased approach you will significantly lighten the load and make it much less stressful on your third-party developers, theme designers and your customer base.

You might consider checking out the following topic:
 

Wouldn't it be easier on your staff, third-party developers and customers to improve upon CSS in a phased approach?
Why not break down the CSS Project into sub-projects? 
One sub-project you concentrate your attention on commerce.  You develop the "new" features you want to offer for that module while addressing any appropriate CSS changes needed.  You concentrate many IPS developer's and testers eyes on just that section of your overall codebase.
By concentrating "lots" of eyes on "one" module of the suite you will make it easier to identify any underlying performance, security problems or bugs. At the end of such a CSS sub project, you will end up with a much better underlying codebase then trying to tackle the entire suite all at once. Once that CSS sub project is "golden" you move on to the next sub-project
Upon release of the "CSS Project - Sub Project X" the third-party developers, theme designers and your customer base only have to make appropriate changes to "one" section of the IPS suite not the entire suite. 
By adopting a more phased approach you will significantly lighten the load and make it much less stressful on your third-party developers, theme designers and your customer base.

You might consider checking out the following topic:
 

Issue 3 Fixed.
 

Thanks, and if you ever find it in your heart to add an option that allows leaders to do so again, that would be great.

Login as an Admin and click on the "Create" option, then select "Announcement":

If for some reason you want to delete an OAuth authorization it seems it can't actually be done.  See below for illustration:
If I click on "View Details":

The following screen appears:

If I click on the "X" button as shown the following screen appears:

I click on "OK" and the following screen appears:

The authorization "appears" to have been successfully deleted.
View the member's Oauth Apps and it shows there:

The "View Details" screen shows it back again:

So, it appears deleting an OAuth authorization actually doesn't delete it.  This behavior shows up in ver 4.6.12.1 and 4.7 Beta 3
 

@LIVIO If I understand you correctly you could create a member group and exclude any features you don't want members to be able to add.  See below:

Not sure how you can exclude "Pages" as I don't see that as an option to include/exclude.

If you are selling your house, you want to get the best possible price. If you place lots of ads in the newspaper and social media and have loads of people show up, you are NOT guaranteed the best price if your house "looks" undervalued.
The CSS Project is akin to advertising and the continued improvement of the suite will go a long way towards upping the site's overall perceived value.  Also known as "curb appeal".
It doesn't do us much good having lots of folks knock on our door if they immediately walk away to check out one of the other bright and shiny houses down the street.

Wouldn't it be easier on your staff, third-party developers and customers to improve upon CSS in a phased approach?
Why not break down the CSS Project into sub-projects? 
One sub-project you concentrate your attention on commerce.  You develop the "new" features you want to offer for that module while addressing any appropriate CSS changes needed.  You concentrate many IPS developer's and testers eyes on just that section of your overall codebase.
By concentrating "lots" of eyes on "one" module of the suite you will make it easier to identify any underlying performance, security problems or bugs. At the end of such a CSS sub project, you will end up with a much better underlying codebase then trying to tackle the entire suite all at once. Once that CSS sub project is "golden" you move on to the next sub-project
Upon release of the "CSS Project - Sub Project X" the third-party developers, theme designers and your customer base only have to make appropriate changes to "one" section of the IPS suite not the entire suite. 
By adopting a more phased approach you will significantly lighten the load and make it much less stressful on your third-party developers, theme designers and your customer base.

If you are selling your house, you want to get the best possible price. If you place lots of ads in the newspaper and social media and have loads of people show up, you are NOT guaranteed the best price if your house "looks" undervalued.
The CSS Project is akin to advertising and the continued improvement of the suite will go a long way towards upping the site's overall perceived value.  Also known as "curb appeal".
It doesn't do us much good having lots of folks knock on our door if they immediately walk away to check out one of the other bright and shiny houses down the street.