AlexWright

Well I can't make any promises, but I can say that improvements to how we deliver, group and present notifications is on our radar and is under discussion.

Is there a way to disable the Stripe javascript everywhere outside of the Store pages that it's needed on?

Yeah, sadly this work around only works on self-hosted licenses, as @Rhett mentioned. Until there's a fix for this ^^;

Ok so I've found a way around this, but it's more for advanced users. @forumdev99, this should work for you:
For FORUMS: Find the folder public_html/applications/forums/
Open up the furl.json in your chosen editor (I use Brackets). Inside this file, you should find the following code:
/** * Friendly URL Structure * * For each value in the $furl array: * The key should be the "SEO Template" - an identifier which you'll use when displaying a URL. * The value should be an associative array with two or three elements: 'friendly' and 'real', and optionally 'verify': * 'friendly' * The friendly URL to use - encase variables in {curly braces} containing a symbol, followed by the name of the parameter that matches in the "real" URL * The symbol should be # for numbers or @ for strings * For example, if the "real" URL contains id=XXX, where XXX is a number, you should include {#id} somewhere in the friendly URL. * You can also use the tag {?} for the "SEO Title" (that is, any variables that shouldn't be part of the real URL, such as the name of the topipc being viewed). * If you want to support more than one SEO Title, you can give them zero-indexed keys like so: {?0} {?1} {?2} * 'real' * This should be the base of the real URL. You should not include parameters which will be parsed out from the friendly URL. * 'verify' * This should be the name of a class that contains a loadFromUrl() and an url() method. The dynamic URL (i.e. app=core&...) will be passed to loadFromUrl(), and the url() * method will subsequently be called to retrieve the correct URL, ideal with ActiveRecord pattern classes. * * IMPORTANT: Ensure values are listed with the most specific ones first. This is to ensure that non-FURL redirects are done correctly. For example, if you have these FURLs: * /index.php?app=myapp&module=mymodule&controller=mycontroller&do=myaction -> /myfolder/myaction * /index.php?app=myapp&module=mymodule&controller=mycontroller -> /myfolder * They must be provided in that order, otherwise the former will redirec to /myfolder/?do=myaction rather than /myfolder/myaction */ { "topLevel": "forums", "pages": { "forums_rss": { "friendly": "forum/{#id}-{?}.xml", "real": "app=forums&module=forums&controller=forums&rss=1" }, "forums_forum": { "friendly": "forum/{#id}-{?}", "real": "app=forums&module=forums&controller=forums", "verify": "\\IPS\\forums\\Forum" }, "topic_copy": { "friendly": "topic/{#id}-{?}/copy", "real": "app=cms&module=database&controller=topic" }, "forums_topic": { "friendly": "topic/{#id}-{?}", "real": "app=forums&module=forums&controller=topic", "verify": "\\IPS\\forums\\Topic" }, "forums": { "friendly": "", "real": "app=forums&module=forums&controller=index" }, "topic_create": { "friendly": "submit", "real": "app=forums&module=forums&controller=forums&do=createMenu" }, "topic_non_forum_add_button": { "friendly": "startTopic", "real": "app=forums&module=forums&controller=forums&do=add" } } } The things to change here would be the "friendly" parts. For instance, to change it from yoursite.com/forums/ to yoursite.com/forum/, replace "topLevel": "forum".
This is in the same location for -all- installed applications. After reuploading the file to the same place, you will need to run "Something isn't working" in your "System -> Support" page. After that, you can edit or install language files to deal with the rest of it.
 
Regards

@AlexWright 
Hi,
Please report the issue to IPS 🙂 
 
 

Add this to custom.css 
.ipsColumn_veryWide.cBlogInfo{width:auto}  
 
 

Please report it to IPS 
if you want a quick fix i can help if you provide a link to check 🙂 

This 1000x this. And it has to work for All content. Not just forum content.

and moderate!!!

Is there a possibility of including the favorite link in non-lightbox for gallery content? We disabled opening lightbox for browsing easier. Would be very helpful to get the Favorite link on the default gallery page.

A new version was submitted to fix the Gallery issue. It's pending approval.

This is a frustration that has irked us since 4.0. The gallery uploader for images needs to have a confirmation dialogue before it can be closed. Along the lines of 'Are you sure you want to close the uploader? All progress will be lost." It is annoying to accidentally hit escape or click outside of the box and have it close.

Yes, agree, we need this. I've requested it:
 

NGL, I get people asking me daily if there's a "block" feature. I would love to implement this somehow. If a user wants another user to not be able to downvote them / stop seeing their posts / threads / profile at all, they block them and voila. 🙏 

This is a frustration that has irked us since 4.0. The gallery uploader for images needs to have a confirmation dialogue before it can be closed. Along the lines of 'Are you sure you want to close the uploader? All progress will be lost." It is annoying to accidentally hit escape or click outside of the box and have it close.

This is a frustration that has irked us since 4.0. The gallery uploader for images needs to have a confirmation dialogue before it can be closed. Along the lines of 'Are you sure you want to close the uploader? All progress will be lost." It is annoying to accidentally hit escape or click outside of the box and have it close.

Oh yes, I can confirm I'm receiving Gallery notifications even not selected and taking a look on Gallery image model, it has a bunch of notifications methods there so probably something has to be done directly on them.
We'll take a look closer during the weekend.
----------------------
EDIT: Yes, confirmed. Gallery (and Downloads) sends notifications via Queue task, that's why they are not using the plugin restrictions. Will take a look.

Well, obviously this is not the expected behavior. I tested this on 4.5 one month ago or earlier and it was working fine.
I’ll re test it during the weekend. 
@SJ77, is this the bug in core you mentioned last week on a private message?
It was something related to status updates. 

They show up automatically here.

DELETE FROM core_member_history WHERE log_member = X AND log_type = 'display_name'; X is member ID.

Good Evening,
 
Just looking to see when the update for the 4.5 will be coming I tried to activate on my forum and it killed my Admin CP access along with half the site. 

+1ing this.

Since the Automation Rules app is now defunct, I need help on finding a resource that will add a secondary group to a member automatically based on their age determined by the birthday they input on their profile.

It would be very useful if we could add an age (in years) to use the Promote feature. This is handy as it would help sites that have age-restricted areas. Right now we are using Kevin's Rules application to handle this, but a built in option would be much better.

Removing the .htaccess if it has rewrites will cause a 404 on /login, because the rewrites would rewrite the index.php?/login to just /login (its a friendly url setting). It must be disabled in the ACP, which will generate a new htaccess file. As for why it would download the index.php file instead of opening it for display, that I am unsure of.