Joomla 4 website's backend not working after renaming htaccess.txt to .htaccess Topic is solved

[ahmed1308]

Hello.
I got a issue after renaming htaccess.txt to .htaccess in the public_html folder of my Joomla 4 website I renamed it in order to get rid of "index.php" in the URLs.

Steps to reproduce the issue

1. Download Helix Ultimate 2 Beta 1 Quickstart Package (https://github.com/JoomShaper/helix-ult ... 0.0-beta.1), upload it to the public_html folder of your website, unzip it and then follow the standard Joomla installation procedure.
2. Upgrade your website to Joomla 4 Beta 7.
3. Set "Use URL Rewriting" to "Yes" (In the Global Configuration tab of the Joomla administrator panel).
4. Rename htaccess.txt to .htaccess in the public_html folder of your website.
5. Delete the cookies and website data, then refresh the Joomla administrator panel's tab.

Expected result

The website's backend looking like it was (before renaming htaccess.txt to .htaccess) and working fine.

Actual result

The administrator panel looking weird and not working (There is no interactivity when clicking on any button).

System information

LiteSpeed-based server
PHP: 7.3 lsphp
Joomla: 4 Beta 7
Helix Ultimate: 2 Beta 1

Additional comments

Here is what I got in the logs file:

WARNING ... assets No asset found for com_modules.module.92, falling back to com_modules

I also don't think that the problem is related to the website's template (Helix Ultimate 2 Beta 1) since the issue only occurs for the backend and not the frontend.

[AMurray]

I see this has been reported on https://issues.joomla.org.

If it appears to be Helix ultimate issue, it should be reported to joomshaper.com

Does the same thing happen when using Helix Ultimate Beta 1 on Joomla 3.9.25 or when using the default front-end template Cassieopia in J4 (and not using Helix in J4).

Steps to reproduce the issue

1. Download Helix Ultimate 2 Beta 1 Quickstart Package, upload it to the public_html folder of your website, unzip it and then follow the standard Joomla installation procedure.
2. Upgrade your website to Joomla 4 Beta 7.

Answer 1. What version of Joomla did the Helix Ultimate Beta 1 Quickstart Package come with to start with? Joomla 3.9.x, 3.10, or 4.x (beta7)?

Answer 2. The upgrade path to 4.x is 3.9.x to 3.10 to 4.x. Did the joomla update go smoothly? Bearing in mind, quickstart packages are not the best way....and the Joomla 4 releases are test packages only (3.10 still in Alpha and J4 in Beta).

Could you try again, but this time use the latest J4 beta nightly build release and install that directly, then install the Helix Ultimate Beta 1 template as normal, through the Extension Manager?

[ahmed1308]

Hello @AMurray and thank you for replying.

I installed Joomla 4 on an empty website (https://www.dv2025.com) via J4 Beta 5 Full Package (https://github.com/joomla/joomla-cms/re ... .0.0-beta5) and the result was similar after renaming htaccess.txt to .htaccess (The backend not working and looking strange). In addition to that, the problem is also present in the frontend for https://www.sitename.com, but it isn't for https://sitename.com (So, https://www.dv2025.com looks strange, but https://dv2025.com doesn't).

I didn't install Helix Ultimate in the website, thus the problem isn't related to it.

[Per Yngve Berg]

Beta 5 is very outdated. Why didn't you use Beta 7?

There is a completely new Bootstrap. (version 5)

https://github.com/joomla/joomla-cms/re ... .0.0-beta7

[ceford]

Your site is not loading css or js files. When I click on them in the source my browser says

Content Encoding Error

I suggest you install the latest beta. Did you set SEO / Search Engine Friendly URLs to Yes in Global Configuration?

[darb]

Latest b8 you find here https://developer.joomla.org/nightlies/ ... ackage.zip

[Richard67]

@ahmed1308 Did you also read the FAQ for Joomla 4 Beta 5? It tells that there is an extra step to do in SQL, e.g. in phpMyAdmin.

Please report back if you had followed these instructions or not, and please do as advised above and try with the latest Joomla 4 Beta, which is Joomla 4 Beta 7 and can be found here: https://github.com/joomla/joomla-cms/re ... .0.0-beta7 , and report back the result here. This beta doesn't need that additional SQL step anymore. Thanks in advance.

[ahmed1308]

@Per Yngve Berg and @ceford The problem still persists with Joomla 4 Beta 7.

Did you set SEO / Search Engine Friendly URLs to Yes in Global Configuration?

Yes, I did.

@Richard67 Same issue after using Joomla 4 Beta 7 (See https://github.com/joomla/joomla-cms/issues/32892)

[darb]

Hello have you tested with Helix Ultimate v 2 beta 2?

Ask support from Joomshaper Sajeb in Github there too.

[ahmed1308]

@darb The problem isn't related to Helix Ultimate.

[darb]

ok its not related to Joomla

[Richard67]

See https://github.com/joomla/joomla-cms/pull/33097 .