SeNioR-

What's New in Version 2.1.1
IPS 4.7.12 compatibility.

Switching to GD seems to cure the problem. Whew....I really really hope that turns out to be true. But I need to run with GD for a couple of days to be sure. 
Why in the world would ImageMagick "suddenly" start causing problems? Could it have anything to do with upgrading to PHP 8.whatever?

We love updating things because Elon got bored. 

is it really supposed to work like that? what nonsense

On a site with a lot (really a lot) of clubs, the function \IPS\Member\Club::clubs() becomes rather slow because there are no indexes for the suggested columns in the phpDoc text:
/** * Get all clubs a member can see * * @param \IPS\Member $member The member to base permission off or NULL for all clubs * @param int $limit Number to get * @param string $sortOption The sort option ('last_activity', 'members', 'content' or 'created') * @param bool|\IPS\Member|array $mineOnly Limit to clubs a particular member has joined (TRUE to use the same value as $member). Can also provide an array as array( 'member' => \IPS\Member, 'statuses' => array( STATUS_MEMBER... ) ) to limit to certain member statuses * @param array $filters Custom field filters * @param mixed $extraWhere Additional WHERE clause * @param bool $countOnly Only return a count, instead of an iterator * @return \IPS\Patterns\ActiveRecordIterator|array|int */  
The description for $sortOption mentions 4 columns (last_activity, members, content, created), but the only indexes available are created and members. The other columns, including name (which isn't even listed in phpDoc), have no index, and any query ordering results by those becomes slower the more clubs the site has.
Not to mention that there are queries based on club type, and the type column doesn't have an index either. And finally, there is an index on location_lat, but none on location_long. If you're trying to filter clubs based on location, you'd probably need an index on both columns, not just one. 🤨
 
We noticed the issue because the site has several Pages blocks that load clubs (2000+) based on various specific queries.
 
P.S.: It would also be nice to have the option to filter the clubs based on their type in case you want to load only public or open clubs only. But that's more feedback that a bug. Just something to consider if you end up updating the clubs() function. (Or maybe look into it for v5. 😉)

@Matt Another big issue that comes to mind is forms. Currently, it's really difficult to add new fields to most forms (or even modify them), and it's even worse trying to manipulate the values after the form is submitted because there are no hook points available inside the $form->values() IFs that are executed on submission.
 
If each form had a unique ID, with preDisplay() and preSave() hook points, it would save a lot of trouble. We could extend the form class and target the unique ID more easily. I've had to get really creative in some instances to add fields to some forms in 4.x... 🙄

All excellent points. Let me run through them.
1) Agree, that restriction will be lifted in 5.
2) I'll check to see if we have an easier solution for this in 5.
3) Easier in v5.
4) Easier in v5.
5) Will check to see if we have a solution for this in 5.
6) Fixed in v5.

Keep an eye out for the UIExtension news coming soon for form fields. 

After receiving a push notification, it would be nice if, when clicked, it redirected immediately to the list of notifications and not to the homepage.

Twitter has discontinued this

From a non-developer point of view: There's so much. For example,
I hope for an easier user search, so that more connections among users are created. And I hope for the possibility to use tables of contents in Pages. The tag sites should not look like a simple search results page, we should at least be able to add an image and an intro. And they should be indexable for Google, for example. I would also like to be able to create custom fields in Events. Surprise me!

@Michael.J r u k?

Well, that's what I would have liked to see asked before you guys started working on v5. Nothing's going to change at this point, even if we answer. 🤷‍♂️

Setting up a renewal payment does not force the developer to maintain their product for their entire life, the developer may have other problems, employment. 

Well, will have to find another video application, since this one is Out of Service and its creator disappeared, overnight and start all over again:( Cool! 
As I said, you pay every 6 months and no new update of September 19, 2022, had to suspect and stop paying!
We should almost ask for the reimbursement of the sums paid for nothing!
Thanks to @Adriano Faria for his valuable help 👍



OK, but in this case, you ask for a price to sell your app and you don't ask for a subscription (additional fees) if you're not sure to continue, since it's a hobby
I have been creating websites for 25 years by hobby and so voluntarily, if I ask for money, I assume the duties that go with it

Hi,
I enabled topic/post archiving here, with the following parameters:
last post: more than 10 years unpinned The system informs that there are 95.305 topics that match this condition, which represent 7% of our total topics.
After several days, these posts were archived, but we ended up with several really old topics that weren't archived. The 95.305 number seemed off, since we are online 20+ years with over 1 million topics.
Upon further investigating this, I found out that topics that contained the value '3' in the forums_topics.topic_archive_status columns weren't archived. I don't know what this value '3' represents. Maybe a flag for topics that shouldn't be archived? We used archiving several years ago, and disabled it, and maybe because of that all topics that were archived then got this status?
Also, I see several new topics being created with this '3' value, mostly topics that are reserved for article comments in Pages. But not all.
I just need this confirmation, so I can manually fix this!
See below how we could actually archive 830,438 topics, and not only 95,305. The missing 735,133 topics have this '3' status:
SELECT count(*) FROM forums_topics WHERE pinned='0' AND last_real_post < 1374439854; 830438 SELECT count(*) FROM forums_topics WHERE pinned='0' AND topic_archive_status = '1' AND last_real_post < 1374439854; 95305 SELECT count(*) FROM forums_topics WHERE pinned='0' AND topic_archive_status = '3' AND last_real_post < 1374439854; 735133 Please advise.
Cheers,
Gabe.

yeah, I am almost positive that I ran into issues is why it simply has those columns titled home team and away team. Maybe because of it being a number type of input. So I'll just have to see what I can figure out. I always wished I could have gotten that picking form to be much better, but I was working within some premade ip.suite elements. Same thing with brackets. I spent a ton of time getting picking teams in the bracket to work, then realized the issue where the ip.suite wizard I was using would not give an error if they left a pick blank. Honestly, for brackets, it may come down to me HAVVING to have a default pick on each game where they can't even possibly leave it unpicked. But just would suck because it's not good having either team as defaults where a member could complain that they didn't mean to pick that one, but didn't notice it.
One thing I need to add to this app at some point is member stats pages or top lifetime members as far as best at picking winners, etc... I have tons of stats being stored, just haven't made pages showing them.

This is his website where we get help
https://www.devfuse.com/forums/profile/1-michael/
LAST VISITED: May 8
This the post here I let him know there are so many problems with his app 
 

Totally agree.. I just added my 3 cents here. 🙂

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.

A new UI, hopefully from @Ehren. Cleaned up code (if needed). More SEO (if needed). Faster rendering time (if needed). Maybe some fun new features like when Ranks were introduced. 

Will code hooks disappear?

Full in-depth developer documentation with proper real-life full working examples on how to implement framework features.

constant adoption of new php features and faster bumps in the min. required PHP. PHP is releasing newer versions faster than ever before and killing off the older versions just as fast. the biggest problem i had with IPS 4.x, was that it never really evolved. sure it changed, but it never really embraced features even found in php 5.4, let alone features added thru out 7's life.  Adoption of PSR for your code standards. gonna be honest here, i find your "coding standard" (the formatting of your code) to be the visual equivalent of an angry monkey biting down on a vibrator.  it is a serious amount of unpleasantness to view your code. i think the adoption of PSR, would be more welcoming to third party who has worked out in the wild on other things that use the PSR standard (which most frameworks/libs do now days and by nature a lot of apps have just adopted it from them).  this is a minor one, the embracing of imports+aliases when needed over FQN. FQN can make code look ugly,messy and add a fair amount of bulk. using imports, i can just look at the top of the file and see instantly what it is using. full adoption of semantic versioning. a lot of the problems that you have with 3rd party is cause you guys never stuck with a standard. you would throw in backward breaking changes in patch versions. it is pretty insane that a professional level software company wouldn't use a standard like semantic at the very least. Events Manager. i like the hook system just as much as the next guy, but i think polling of all the apps in the market place to see what is being hooked and how often, and then prioritize event triggers for those, you could probably ease a lot of your woes.  a better form class. i've said it plenty of times over the last several years, i really dislike the form building in 4. i think it was a step in the right direction, but i honestly think it could've been done better. i think it produces an extremely ugly code that could've easily been abstracted better. better use of traits/interfaces/abstract.  there are a lot of times where traits/interfaces/abstract classes should be used in 4.x, and they are simply not. a good example of this is extensions. there have been times where you have updated an extension, where you have removed methods or added in new ones and i had no idea. this is a good place where each extension gets an abstract class, where you can add/remove these methods, so if we don't implement them, they wont blow up.  search. have the search actually use the objects. you currently have things like "titleFromIndexData" and "urlFromIndexData", amongst other methods that attempt (and poorly i might add) to usurp the object class you have given us to do these very things. there are a few of my apps, who do not use the cookie cutter nature you've assigned here, so these methods require addition work from me and at times, impossible to do anything with the provided data, so i have to load the object anyway.  clubs. clubs are sort of a nightmare to implement. cause they are implemented on the item class, but god forbid you use a container/sub container class. then it becomes a huge annoyance to properly implement. clubs should be seriously revisited and much better implemented. i'm sure i have more, but i get the feeling as it is, its already too late in the development of 5.x to serious take into consideration anything i would like to see changed. too bad you guys didn't ask this at more of the start of the development, we might've been able to create something wonderful together :). 

I didn't know that you are using cloud. In that case you have nothing to worry about. You don't need to do a backup as your site data is in very safe and capable hands.