opentype

Who’s records should they edit? Because for other people’s records, there are just two choices: you make those members admins you turn on the Wiki functionality Otherwise members will only be able to edit their own records, if the permissions are granted and it is turned on for the database: This might also be of interest:

For streams: you would have to choose “Content items, comments, and reviews”. That would include new entries for comments. There is no comments-only option. A widget for Pages comments is still missing. There was a plugin available once, but not anymore.

It’s a quick “fix”, but a proper guest checkout should come anyway to comply with EU regulations. https://invisioncommunity.com/forums/topic/467795-commerce-app-requirement-for-guest-checkout/

You would have to override the “float” of the menu items, which are <li> elements. However setting them float:right would also reverse the order of the menu. Not a good idea. There is also JavaScript acting on the menu, which can mess things up. I wouldn’t do these kind of “tweaks” unless it serves a clear need and you are absolutely sure you know what you are doing.

In the Guides section. Scroll down to “CSS Framework” https://invisioncommunity.com/4guides/welcome/about-invision-community-r7/

Yeah, linking or embedding a third-party solution is probably better. Invision Community has nothing to accommodate such events currently. I am currently using Pretix for online events and conferences, but of course there are many many providers from all around the world.

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/

Where exactly does it appear? As part of which area or form?

You can’t change the default block position this way. Those are containers with templates executed within them. Moving the containers couldn’t do anything to stuff inside them. But if you create what you need in those slots as a Pages block, you can then inject it at any place you want in the theme templates. {block="your-block-key"}

You would have to customize this theme template: cms → front → submit → topic

By the way: you ask in the community forum, but you also show as client. As such, you could post in the official Help & Support forum and let IPS staff log in on your site and fix the problem.

There is nothing simple or better about it. It’s just unreliable. What if use a smaller browser window on desktop? The site would break since it can’t be displayed properly. Because with your method, the code for smaller screens would have been removed. What if PHP can’t detect the device clearly for some reason? Again, the site could break because the wrong version could be delivered. All in all, the benefits of stripping a few lines of unused code don’t outweigh the potential negative consequences. After all, it IS about the screen size, not the “type” of device. The break points are called “desktop”, “tablet” and “mobile” but that is just a convention. The device doesn’t really matter, so recognizing it isn’t the point. It must work for whatever screen size is available and that is something determined (and possibly even changed) on the client side.

Yes, the regular subscriptions are meant like that. You pick ONE of the options. The Commerce product subscriptions can do more more. But they have no option to switch between “plans” as the products are independent.

If it helps, this was a product with different prices for different options. Maybe that makes a difference.

There is a chance, but it wouldn’t be my first guess. I had such problems myself after conversions, but it was always just faulty permissions somewhere. You could try to narrow down the problem by adding forums. Start fresh with a new category and forum. Does it show up? If yes, the problem is inside the existing forum. If not, there is some global issue affecting all forums. Then possibly proceed by creating a new forum inside that existing category … Stuff like that.

Try clearing the browser cache and the cache of the website in the ACP. The editor opens dynamically via Javascript. If it doesn’t, as in your case, it usually means the JavaScript is failing.

No, we can’t. That’s the point. The users could edit the quoted text itself, but that is not the problem here. They want to quote the text as it is. The problem is the false attribution of that quote which is created by the IPS code. Everything about it is wrong: The name. The time. The link. And users are actually prevented from correcting that. Not to mention that they usually don’t even notice. And then the wrong user gets a notification about having claimed something they never said.

What about the forums themselves? They have their own permissions.

I had users complain about being regularly quoted with things they never said. I checked it out and this is indeed easy to replicate. Example: Let’s say I see this post from Nigel quoting Daniel: I can select the text in the quote and hit “Quote selection”. But the result will be this: The quote gets misattributed to Nigel, even though it was said by Daniel! It shouldn’t work like that. Either the quote should be attributed correctly, or if that is not possible, the inline quote functionality should be suppressed within already quoted text.

Have you set a matching background color?

The only stock option I can think of: Pages blocks have the ability to ignore permissions. So, one could create topic/feed blocks to let guests see snippets from the closed areas. Other than that it sounds like a job for a custom app.

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.

To put this in perspective: I have a Pages database where each record needs to get its own CSS. So far, I created those files in ”Theme → cms → front → custom” but IPS has removed that ability with 4.7. So now I need an alternative way to create and call custom CSS from a template.