[4.0] Simpler configuration. Defaults setup. [suggestion]

[mrownicki]

Steps to reproduce the issue

Joomla 4 must be a more friendly configuration for start. (Fresh, fast and simpler)
No need login to ftp and change htaccess.txt to .htaccess This is not friendly approach.
Kerwords Google not using. 90% people using google maybe more.
If we're using some defaults options and they are obvious that they will always be on, there is no need to show them.

Expected result

Joomla after install start in .htaccess
Search Engine Friendly URLs - Yes (defaults) but remove
Use URL Rewriting - Yes (defaults) but remove
Send mail - YES (defaults) but remove.
FTP - remove completly.
Gzip - YES (defaults) or Brotli YES (defaults)
Force https - Only administrator (REMOVE) change to Yes on NOT
Keywords - Remove
Autor meta tag - move to article options
Joomla version - OFF (defaults) but remove
Cookie setting - I don't know if anyone uses it. (if no need remove)

Actual result

System information (as much as possible)

Additional comments

Joomla must be better and simpler for SEO and configuration. Newbie user expects working simple solution.
I go further and don't show this options.
This in my option to bring more good for newbie user who install and immediately write article. They don't want to play setting the mass of options because they don't have time for it.
What do you think about this?

If you don't hear about brotli https://medium.com/oyotech/how-brotli-compression-gave-us-37-latency-improvement-14d41e50fee4

[mbabker]

Joomla supports more web servers than Apache. Blindly renaming the htaccess.txt file won’t work for IIS or nginx.

Joomla’s default .htaccess does not work on all hosting providers (usually because of an issue with that host), blindly renaming the file would cause more issues than it solves.

Removing the option to disable mail sending makes no sense. There are valid reasons for defaulting it on and allowing a site admin to turn it off.

The URL rewriting options must be used in conjunction with web server configuration, it is not “turn this on in Joomla” or “turn this on at the web server level”. Also keep in mind it allows use of human friendly URLs even if the web server isn’t configured in the right way (you just have URLs like /index.php/foo/bar).

Cookie settings is an advanced thing. But it should not be flat out removed.

[mrownicki]

Joomla not need support all hosting provider. Come on.
If we require J4 php 7.3 then why can't we require mod_rewrite in Apache ??

No remove mass maill only send mail ;) If you have infection provider hosting cut off phpsendmail in 99% case.

Nobody need /index.php

Joomla’s default .htaccess does not work on all hosting providers (usually because of an issue with that host), blindly renaming the file would cause more issues than it solves.

Maybe we need fix that. I don't write blind ;) In most case mod_rewrite must be on. Simple. Sorry, but I didn't meet a provider who wouldn't offer a rewrite module on apache.

---

_{This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/26876.}

[mbabker]

Joomla not need support all hosting provider. Come on.

Joomla is designed to be able to run on multiple web server platforms; this includes Apache, NGINX, IIS, and LiteSpeed. Not all of these platforms utilize .htaccess for configuration directives and it is pretty narrow sighted if you're suggesting that every Joomla user must run their site on an Apache server.

If we require J4 php 7.3 then why can't we require mod_rewrite in Apache ??

URL rewriting is a 100% optional feature and not necessary for Joomla to function properly. To my knowledge this module being enabled is only a hard requirement for use of Drupal, other CMS's I use or have evaluated do not impose this requirement.

Joomla’s default .htaccess does not work on all hosting providers (usually because of an issue with that host), blindly renaming the file would cause more issues than it solves.

Maybe we need fix that.

It has more to do with whether mod_rewrite is available or not. The default file in 4.0 wraps everything that can be inside of conditionals to determine if a feature is available, but there is still the Options directive which may be disabled for whatever reason or a user needing to adjust the RewriteBase directive for proper URL rewriting in some scenarios. The point here is that Joomla as a web application is not in a spot to blindly turn on a web server configuration file and if it breaks be unable to help users fix that issue (because if the .htaccess is borked then you're not getting into the UI at all in most cases).

Maybe you and I run all of our sites in optimal server configurations, and maybe you only use Apache for your web server of choice, but there are a lot more server configurations out there and a "you must have an optimal server configuration to use Joomla" approach is kind of disrespectful to those who aren't technically savvy.

[mrownicki]

https://prnt.sc/pqsc2u
Apache, Ngnix 70% world usage. (lightspeed, ISS, Cloud other 25%) = 70+25=95% this is still very good.
I don't agree this is approach is kind of disrespectful. This is smart.
Why joomla does not support plugins from version 1.5 This is so disrespectful for develeopers ;) (There is no support to get rid of technological debt.)
Joomla does not have to run on every server. It is supposed to run on the most popular ones.
An opportunity arises to give up unused technologies and change something with J4, why not do it.
Not all Joomla users are programmers ... and many people get the impression that joomla is too difficult and written by programmers for programmers.

Joomla using in the world drop in 3.0% to 2.7% (in 2019)

Please, think to gain in the market and not lose. :(

---

_{This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/26876.}

[Hackwar]

I'm sorry, but @mbabker is right here. We can't simply assume everybody is using Apache and we can't force everybody to use mod_rewrite SEF URLs, etc. The simple fact that there are thousands of websites out there without mod_rewrite URLs and we would invalidate all their URLs by forcing them to use mod_rewrite, makes this a non-starter. Yes, we can improve Joomla quite a bit, but your proposals aren't things we can do.