Princess Celestia

Please consider splitting the "Bypass word and link filters?" group-level setting (it's under Content > Moderation when viewing a group's settings in the ACP) into two separate settings for bypassing the word and link filters. This is the one:

"Bad words" and "bad links" are conceptually different in how they can harm a community so coupling them together in this setting seems weird, to say the least, and is limiting.
In my site's case, I'm using the link filter as a spam control measure for new users until they "graduate" to a more privileged group but wish to enforce the word filter across all groups. I was dismayed to learn that this is impossible - enabling the link filter for new users meant giving up the seemingly unrelated word filter for everyone else.

Please consider splitting the "Bypass word and link filters?" group-level setting (it's under Content > Moderation when viewing a group's settings in the ACP) into two separate settings for bypassing the word and link filters. This is the one:

"Bad words" and "bad links" are conceptually different in how they can harm a community so coupling them together in this setting seems weird, to say the least, and is limiting.
In my site's case, I'm using the link filter as a spam control measure for new users until they "graduate" to a more privileged group but wish to enforce the word filter across all groups. I was dismayed to learn that this is impossible - enabling the link filter for new users meant giving up the seemingly unrelated word filter for everyone else.

We've had this on our internal roadmap for a while, there isn't a set release or date, but it's something we do want to do.

Currently they are...
Everyone can see this album Only the owner can see this album I want to choose who can see this album It would be better if it were like this...
Everyone on the web can see this album Only Registered Members can see this album Only the owner can see this album I want to choose who can see this album The reasoning is that some members don't mind their sharing their photos with fellow community members, but they don't want it exposed to innumerable random guests perusing the site.

Yeah, Stripe and PayPal are very unfriendly and steal from you on currency exchange rates. Even worst local currency exchange shops do not have such bad rate as PayPal - fair enough I can put currency exchange differences as company cost but still loosing on it. With Revolut I pay pretty fair commission and still a lot is left in my pocket.

Hi,
Revolut becoming very popular way of getting pay. It is beating alternative for PayPal in aspect of fees while keeping even better Customer experience because it is very simple way of paying. While PayPal is only financial institution, Revolut is a bank already, so you have real bank account that allows you to take card payments, wired payments, payments on @nickname, or payment for mobile number. It is a way quicker than PayPal and way more modern for now days. IPS, @Matt, @Lindy, please consider a gateway for Revolut Pay: https://developer.revolut.com/

Is the Pages (and Commerce) documentation still on the way? Only Core, Forums, Gallery and Blogs are documented at present.
Thank you!

I have a question about IPS Spam Defense and the GeoIP module.
If I uncheck the Send repots back checkbox, exactly what data does IPS receive, is it stored and to which country is it sent?
And what data IPS receives when I enable the GeoIP module?
Sorry to ask this, but in the EU such a module in its current form is a bit difficult to use and we have problems with spam.
Kind regards,
Vakarian

Support for MySQL transactions in v5?
Database operations that insert/update rows in multiple tables should be grouped into a single transaction. This improves data replication and avoids data inconsistency from accumulating over time. This mainly affects content creation/modification.
Support for spatial data types and queries in v5?
I'd like to see full support for spatial indexes and queries on at least lat/long points.
Support for date and time types in v5?
I'd like to see full support for YEAR, DATE, TIME, DATETIME, and TIMESTAMP including fractional seconds for times stored in the database, e.g., TIMESTAMP(6) and TIME(6). 
Also support many of the remaining data types as you can including binary and json data types.
I feel like the database layer has been neglected over the years in favor of the UX and hope that v5 will address this side of the SDK.
 
 
 

I am always paranoid that someone is going to press a button and the app do part of the updating and then something go wrong and screw everything up. In apps I have made it's pretty typical to need to insert rows into several tables and use those ids in other tables etc... Also, sometimes I have to have an update that affects hundreds of rows, in a way where if it were to stop in the middle it would be a real problem.

Code clean up ✅
Import over FQN ✅
Better use of traits ✅
Search code clean up ✅
Happy PHPStorm without hacks/class_alias ✅
More recent PHP versions needed ✅
Better use of newer PHP functions ✅
More to follow, but I think you’ll be content with the changes to be announced.

Hello @HeadStand,
first, I'd like to say, that it's a great app and we've been using it for years. Unfortunately however it appears, that recently, after we performed a community upgrade around July 20th to be exact, we have encountered an issue - the custom fields suddenly stopped appearing when creating topics.
These custom fields were untouched for a long time. We tried disabling every single app and plugin, but the fields still weren't showing up.
Just to be sure, I installed your app on fresh local test installation (by the way it doesn't seem like Invision likes this type of troubleshooting for some reason, had to go with workarounds to get the app there) and configured some fields to see if the app works in clean environment - it did, so I started digging in our current configuration of that app.
After reverse-engineering all the settings, it turns out, that the "Editor" Field Type;

- causes the entire Template Set to stop appearing during topic creation. The fields along with their contents are still normally present in topics created in the past, these just don't show up when creating and editing the topics.
When I add fields with other types, these normally show up, but the moment I add an "Editor" field to the set, it causes all to disappear, making topic creation show only the default content field. I've checked if it can be recreated in the aforementioned clean installation, and the same issue occurs.
 
As a workaround, we have been considering swapping the type of that field from "Editor" to "Text Area", which honestly would be fine and works, but even though the settings do not show the following warning in this scenario:

- we're still worried it might negatively impact existing content, and there's a lot of it there, so we've decided to not risk losing it, and contact you instead.
Is it something you'd be able to patch?
Thank you in advance.

v1.6.0 is currently pending approval
NEW
"External login filters on Members table" CHANGES
Little moving around of settings in the ACP, because them not being properly alphabetical was annoying me (cue one still being out of order)

Small tweak to not load JS and CSS for guests as they don't have access to the Messenger anyway.
Hook cssFiles.php:
\IPS\Output::i()->cssFiles = array_merge( \IPS\Output::i()->cssFiles, \IPS\Theme::i()->css( 'livemessenger.css', 'livemessenger', 'front' ) ); to
if ( \IPS\Member::loggedIn()->member_id ) { \IPS\Output::i()->cssFiles = array_merge( \IPS\Output::i()->cssFiles, \IPS\Theme::i()->css( 'livemessenger.css', 'livemessenger', 'front' ) ); } and
\IPS\Output::i()->jsFiles = array_merge( \IPS\Output::i()->jsFiles, \IPS\Output::i()->js( 'front_livemessenger.js', 'livemessenger', 'front' ) ); to 
if ( \IPS\Member::loggedIn()->member_id ) { \IPS\Output::i()->jsFiles = array_merge( \IPS\Output::i()->jsFiles, \IPS\Output::i()->js( 'front_livemessenger.js', 'livemessenger', 'front' ) ); }

The new version is pending approval.
New Features:
Add the ability to manage tags in Fluid View and forum combined fluid view Tool to remove prefixes/tags from all topics from a specific forum with one click  

 
 

That is why you should also be adding decent Q&A challenges, ones that are in your niche and not easily Googled. hCAPTCHA and that will put a good dent in preventing spam. 

So in recent weeks my forum has had a wave of spammers who have been able to freely post blatantly obvious spam on the site. Word filtering is absolutely ineffective to preempt them, and in the most recent case, isn't stopping them at all despite the terms being added to the post filter. In the support thread I filed, it was made clear your current anti-spam system only deals with user accounts, NOT with the content of the things they're posting. I'd say that's proven to be more or less useless. What IPS needs is preemptive/proactive spam defense, not reactive flagging and content deletion.
To that end, I'd like to very strongly suggest that IPB set up a partnership with the Akismet anti-spam service that's widely used by Wordpress blogs and a number of other sites and applications. Their system works by analyzing the actual content being posted and will return a yes/no type of response as to whether they think it's spam or not. From my own experience, they're rarely wrong about that. I'm using it on a bug tracking site I wrote myself, along with an obsolete forum package I still keep online for an old MUD.
A properly implemented Akismet setup will flag spam and store it in a temporary place for moderator review. From there, the content can be checked. If it's not spam, the moderators can click a button to indicate this, and a false positive is sent to Akismet for the system to learn from it. If it is spam, you can either delete it on the spot or let it sit in the pool until a specified expiry time (on my other 2 sites, I use the suggested 30 days). If a post actually does manage to hit the forum, the moderators can click a button there to have it reported as spam and their system learns from that as well. So it's very adaptable. What's even cooler, is the content scanning is done in real time so there's no having things sitting in some queue for days before it's evaluated by their servers.
There's a great deal more useful information to be found at https://akismet.com/ such as developer support and API documentation etc. I'm sure they could explain the gory details a lot better than I can. In the end though, this would be a wildly more effective way of dealing with spam than what we currently have.

v1.4.0 will be up next - with the release of that version, I believe that will be the last version into which I put existing functionality made available via a freebie I've thrown out somewhere.
The following is the only candidate for inclusion right now:
<A better name than the one I gave it originally>  

We will be improving the mobile experience in v5.

We can probably work on the labelling, but I'm not keen on making it a high level item like that. It's not something most people will want to think about when they are on the site.

No, that matches up to what I'm seeing.

No worries.

As the person who wanted this, thank you very much for adding it! ❤️
I had my bug report all written up and ready to submit when I saw your new post come in saying you already fixed it, haha. Thanks for being so on the ball with this (free!) app!

v1.3.1 is currently pending approval.
FIXES
fixed minor save issue which occurs when the following are in effect: the "Enable "Additional Pages media types"?" setting is enabled the "Allow all file types?" setting is enabled the "Allow these additional file types" setting is blank.  
Workaround for the above issue: prior to saving, toggle "Allow all file types?" off, and add an entry in the "Allow these additional file types" field, then toggle "Allow all file types?" back on.
 

If it's what I refer to in the post above yours, no need.