Daniel F

Where's your Javascript code? This won't work without any additional JS which listens to the click event, stops the page from reloading, loads the content via AJAX and shows it then in the content area:)

You can hide/remove it via custom JS or css.

I love the idea and implementation, just the badges look weird on the index page . It's a minor thing, but the different lengths are triggering me each time I see them on a community. Personally I would prefer if they would have the same width, but that's just me..:D . I was never a fan of the different lengths

Yea, I'm also going to use the database feature for my bug & suggestions tracker, linklist, purchases database and I'm also debating with myself😄 if I'm going to use it for my future ticket system or not.

You won't have the file and the DB record if it's a new install and not an upgrade!

Looks like you haven't uploaded all the files

Images shouldn't be related to this. Feel free to send me a PM with the URL and I'll take a look

Exactly, click on delete in this row and that’s it.

Delete the "Promote" item in the core_menu database table and then clear your cache, which should resolve your issue! But only, really only if you're familiar with phpMyadmin / SSH:D

Multiple H1 tags on the same page are fine.

You can see them on the "My Purchases" page. https://invisioncommunity.com/marketplace/previous-purchases/

Absolutely not! Nothing on your installation will be changed, the only difference is the way how you'll install and upgrade them in the future.

No, your ACP is going to show the same notification and badge as you see now if they implement their own version check.

3rd party devs are still able to provide such update checks and notifications. TBH, they are now even able to implement much better approaches which would have probably been forbidden in our marketplace because of our guidelines. License checks, direct download from github for people with a license, etc..

A deprecates module was removed, not the feature!

You can still run the group check and include the necessary js/css files, or set the JS variables only when it’s needed.

The entry explains it already;) The menu templates will include the link that opens the menu, as well as the menu itself. You'll notice that the above contains a call to the hasContent() method. This method will check if the menu object has any elements inside; if a user does not have permission to any of the elements, nothing will be displayed.

Since it's a Raffle item, where you're in control of the class, you can do whatever you want with the menu. But for other applications, where you'll have to use the UIItem Extension, you're able to place it at the beginning or end

That said, you can also use always JS and CSS to manipulate the output.

Yea, it's already in the Content\Item and Content\Comment class, you'll just call it in your template or override the method in your content class if you want to add something own.

It depends on what you’re trying to achieve, but devs can indeed to do a lot with help of GraphQL, REST and webhooks.

The capability to change how most stuff in IPS works and enhance it with own features/apps isn't going away. What changed is how things have to be done. Some changes will be much easier, others will be probably annoying as hell for people who are used to how the hooks worked in v4, some will think that it is a huge step backward, but as Matt said, it had to be done, to provide a much more stable and faster-improving code base for v5, because we'll be able to alter or even deprecate methods, method parameters and even deprecate complete (internal) classes much faster, which also 3rd parties and clients will benefit from. With v5 I'm really expecting fewer "A new community release with some huge under-the-hood BC breaking changes is here, all my apps are now broken and need to be updated ASAP" scenarios. Code listeners are a quite common pattern used in modern applications, most php framework use this approach today. It's the perfect balance between none capability to change the core behavior via 3rd party code and the too-powerful proxy autoloader which we had in 4.x, which as powerful as it was, had also way too many problems. I've read about concerns about missing event locations which were common in v3 and that it took ages to have new hooks implemented => Keep in mind that we have now a monthly release cycle, so I'm quite sure it's not going to take now that long to ship improvements as long as they make sense and fit into the general vision of the product.

1. You should all cool down and wait for the upcoming news and also the final product before getting in such a panic rage. 2. Please see my reply in the SEO topic: 3. See the first point. We're listening to feedback and implementing changes based on it, just like Esther and Matt implemented changes today based on the provided feedback. 4. I think you're all way too scared. There's still so much that can be done, it's 2023, and there are other ways and solutions than to edit files.. ALPACAS! I'll repeat very very slowly just for you: AL PA CAS

Not sure about your first example, but the "Delete All System Logs Button" won't be a problem at all! As Matt or Esther said, just wait for our further blog entries, especially about the new UIExtensions

It's on the "Security and Privacy" page.