Luuuk

I found your topic here too. As I said earlier on Ehren's forum different browser might be a workaround:
 

Perhaps editing a CKEditor config file will help:
your site folder > applications > core > interface > ckeditor > ckeditor > ckeditor.js
See Filtering Pasted and Dropped Content + pasteFilter documentations.
Possibly something similar to this:
CKEDITOR.config.pasteFilter = '*[color]; *{color, background-color, text-decoration}';  

Hi,
Related to this topic.
Currently we have Editor Settings > Advanced > a selective GUI for ACF "to loosen the restrictions". I think we need also a complementary filter to do the opposite without disabling rich text. See Filtering Pasted and Dropped Content.
An additional filter (called paste filter) can be configured to handle pasted and dropped content. It will be applied independently from ACF, so it can be used as the only filter (with disabled ACF), or as a complementary filter (for example to filter pasted content with stricter rules than all other content).

One would be very useful there.

I don’t know. What would it solve exactly? Every password manager is already easy to use and it works on every website. Adding dedicated implementations for specific password managers only sounds beneficial to the provider of that one password manager. 
The concept of password-less logins is around the corner and I think that is more promising. 
https://www.apple.com/newsroom/2022/05/apple-google-and-microsoft-commit-to-expanded-support-for-fido-standard/
 

Ok. Thanks everyone.
 
So. First, update IPS to 4.7.1
Second. Updated Theme to 4.7.1
Will give it a go and report back. Thank you!

Agreed, update your IPS version and you should be good to go. No need to pay anyone, easy peezy. I have Ehren's themes too, and as stated his version themes typically mimic the theme version number of IPS, unless he specifically states no upgrade needed. In this case you do need to upgrade your community to work with the current theme you have. 🙂

@MeanGene
I see you use Ehren's theme. The latest version of the themes is compatible with 4.7.1 and you must have IPS 4.7.1 to use the theme.
In general, in case of Ehren's themes always a theme and IPS software should share the same version unless it is clearly stated by the author that no updates are required.

Who says I am not doing that? My argument was about ‘reading’ in general, which has little to do with the user’s experience. 
 
You can easily just claim that and the next person claims the opposite, since it is all just fictional examples without data behind them. If I am on the Files index page (e.g. on the Marketplace here) and want to look for an app, I just type something in, search and I get file downloads as I will probably expect. But with “Everywhere” as a default, I might get thousands of forum posts, which just happen to include a word from the search phrase, especially with Elasticsearch which picks up almost everything. Those are likely not the expected results and will leave the user overwhelmed and frustrated and could “cost you a member”. Same thing. These fictional examples don’t favour one solution over another. That’s why I said in my first post that there isn’t the one perfect solution. We don’t just have to put ourselves in the shoes of average users, we also have to consider all their potential searches. 
By the way: I could imagine a global search as default working very well *IF* the results page would offer a convincing way to narrow down the results dynamically, but at the moment it doesn’t do that and it won’t happen over night, so that option isn’t on the table when we just discuss the current search bar design. 
That’s also why the comparisons with Google services don’t do much for me. Google invests millions in guessing the context of a search query and ranking the results accordingly. That is why it works so well. It’s not because the search is so wide, it’s because Google usually guesses correctly what you are actually interested in and which results might be helpful to you. So, in a sense, the results we are dealing with are actually rather narrow instead of wide. But we don’t have that luxury with the IPS search. 

98% of using online communities is READING. You read the title before clicking it. You read the posts, because that’s what you are here for (or the Files titles and descriptions or whatever). The idea that people regularly and somehow mindlessly deal with a search bar without being able or willing to process anything that is part of the very box they are typing in, isn’t very realistic. I am not saying it can’t happen at all, but those people only have themselves to blame. Their lack of attention shouldn’t define the behaviour for everyone. 
Processing what is next to a search field is no different than processing what is next to the registration form fields. If one cannot do that, how are they even supposed to be community members. 

My only issue with the search box is that you look at it...it looks lovely...it entices you to type something in. So you think about what to type...what to search for...then you move your mouse, you type something, you hit return....and then you notice that the filter has appeared just after you moved your mouse into the field, and then you realised you have wasted a few seconds of time.
This before I hover:

...is more informative than this:

The same suggested here:
 

The "effect" visible in your screenshot was reported on Ehren's support forum too on 4.7.0 theme applied to 4.7.1 software. The fix is to revert the following template: core > front > global > quickSearch. Or reinstall a theme from scratch.

@JohnDar
For years I use a workaround by editing a theme template:
core > global > editor > attachedImage > remove the <p> tag at the beginning and at the end:
<p><a href="/{$url}" ..... alt="{$title}"></a></p> EDIT: The change will apply to the new content only. Old posts still need to be manually edited.
 

The same suggested here:
 

Exactly. I am very happy that after so long time the decision has been reverted!

Today it is like it was on IP.Board 3. They changed to Everywhere on IPS4 or at some point after that.
If I'm on a topic or a forum and I search for a specific word, I hope to find results in that specific area (Forums app). Why would I want to see results from a blog entry, for example?
The way it is now is the expected behavior.

There were complains about the previous default "Everywhere":
And I agree that the default setting should be limited to the current area the user is in.

Not sure. Quantity ≠ Quality necessarily? 

@Luuuk Right, but that only filters the list of conversations. It doesn't actually bring you to the content.

The "effect" visible in your screenshot was reported on Ehren's support forum too on 4.7.0 theme applied to 4.7.1 software. The fix is to revert the following template: core > front > global > quickSearch. Or reinstall a theme from scratch.

@JohnDar
I think no extra options needed and they just should remove the <p> tag. That would cover the most extreme scenarios when a lot of images are uploaded and posts get very long. If a user wish to place them vertically then that could be done manually (like it is now to place them horizontally).

@Luuuk Thank you for that, very helpful. 🙂
However, given the current climate, where theme modifications are being actively discouraged and some editing features removed, I think an ACP based solution is still a valid proposition.
 

For reference, I found also this old topic and the same "solution" was given via Ticket:
 

@JohnDar
For years I use a workaround by editing a theme template:
core > global > editor > attachedImage > remove the <p> tag at the beginning and at the end:
<p><a href="/{$url}" ..... alt="{$title}"></a></p> EDIT: The change will apply to the new content only. Old posts still need to be manually edited.