Be sure you didn't disable it at ACP > Configuration > Options > Modules > User > Team Page
ACP > Content > CMS > Pages > Search for "Team"
Then it should give you the URL of that page.
If there is no default menu item (footer I think), you can add one (ACP > Content > CMS > Menu > Choose the menu you want > Add menu item) using the internal Link option and selecting the Team Page:
(German, but I think you'll get the main idea.)
That looks more like the team page, maybe that's already what you might want to use.
Example Members List:
Example Team Page:
7 ads just to view an image in order to help you for free? No way. Use the internal attachment system please.
The email I received was this: http://puu.sh/APivl/79487aba52.png
Please use the internal attachment system.
Also to remove WoltLab Suite? (Do I need to purchase the ability to remove WoltLab from there) I browsed through the Styles but could not find anything related to email template design.
Did you already change the header/logo within your styles (ACP > Appearance > Styles > … > second tab)? And did you change the website's title at Configuration > Options > General > Page? The second one should it be.
Also, is there a way to view email history that was sent to users?
No, since this feature is not designed for a newsletter-usage. It's more like inform the users about important things like privacy or terms changes.
so how it could be a pain with WoltLab..
My installation has about 5GB, there's no way this could be handled properly by PHP.
That might work for very very small installations, but not for bigger ones - depending on the PHP-settings, every installation, the webserver-settings and much more. So it's impossible to create safe backups - and as we all know the user is going to think it's safe and cries if it's not because this solution would be shitty.
Groups everyone and guests should have no permission.
There are some more, but I'll never know every single platform.
PS: this could be useful too: https://packagesniffer.mysterycode.de/package-list/
The filebase is designed like an archive of files and versions. Like over here you actually don't remove the old versions.
And then there are the other ones who want to have the current version only - because of the available disk space or because it's more clean or whyever. Just two different ways to think and design the software.
Upload a new version (and delete the old one).
There should be a small plus-icon at the bottom of the versions-tab.
Does this site also require a license?
YOU need a license. Otherwise you won't get help by customers who paid a lot of money.
Regarding a license in persons who were unable to pay a license
If you can't pay for it, you can't use it. Seems logical, doesn't it? So if you don't have the money for a license, you're not permitted to use the software and you have to delete your installation until you got a license.
If they find out that you're using a ripped software (software piracy) they might contact their lawyers and the justice.
The sitemap-feature is a feature of WSC 3.1 and the plugin is not in the store anymore, so yes you'll have to upgrade your WoltLab Suite Core.
If you got some experience you could do some changes in order to get WBB 5.0 into WSC 3.1 - but it's not recommended because WSC 3.1 won't get tested with WBB 5.0. See also: Can't upgrade to RC1
Why are there sooo many problems/warnings regarding the sitemap?
The board-sitemap includes empty boards which return HTTP 404.
The user-sitemap is enabled but I blocked the /user/*-URLs via robots.txt
The page-sitemap (Fireball) returned some inaccessible pages earlier too.
Since it's German and I didn't find the language setting: Google Search Console > Your property (website) > Crawling > Sitemaps > Add the sitemap /sitemaps/sitemap.xml (if WSC is in /, otherwise fix the path).
Compatibility is a lot about testing each and every chance against all relevant bits of the code.
As I already said via conversation:
You could display a warning before an upgrade, that it's on the administrators own risk and you'll get support only in that one case when you're using all packages with the newest version (in that case still meh). So it's possible to upgrade the WSC and use it's new features like the contact form or other cool things without spending much money in something you might not actually need or you just don't have that money because you're a child or idk.
I think that would be a good/better solution.
Mixing up versions build for different versions of the Core quickly lead to highly inconsistent feature-sets and a fragmented user experience for your users.
Of course it does. But everyone could do some optical corrections if it looks strange - or buy the new version.
Especially given the unified appearance it won't make sense that the same feature in app A behaves totally different than the feature in app B, (this also true with only a single app, because the Core also provides various features directly).
Do you have an example for that? Since most things end up within Core-features after passing xyz other methods.
For example, the sitemap consists of the core API that is provided by the Core and the individual implementation in the app to have it work to it. A sitemap with Core 3.1, but Forum 5.0 would lead to a generated sitemap that includes all the Core's pages (e. g. user profiles), but without any posts and threads, because this was implement with Forum 5.1. Worst of all, this can be easily missed and users start viewing this as an error in the software ("Why is the forum missing in the sitemap?"), but in reality this is just the result of mixed versions.
Hmm, yes. But it's kinds bad example (as you're already saying), because you can implement that by using a plugin and then it would be a complete sitemap.
For the question of "why blabla?": You can tell them it's a new feature and you'd need to implement it on your own or buy an upgrade. No problem or bad image for me.