[#42408] - Invalid path in the template editor
- Closed
- 26 Dec 2023
- Medium
- Build: 5.0-dev
- # 42408
Joomla 4.4.0 (as well as 4.4.1 and 5.0.1) indicates the wrong path in the template editor. Because of this, it is impossible to edit files.
Steps to reproduce the issue
My actions are as follows: "System" -> "Site Templates", in the drop-down list I select: "Site", then "Cassiopeia Details and Files" and move to the editor.
Expected result
Root folders should be specified as "/templates/cassiopeia/" and "/media/templates/site/cassiopeia/".
Actual result
But in the editor, the root folders are listed as: "/administrator/templates/cassiopeia/" and "/media/templates/administrator/cassiopeia/".
System information (as much as possible)
PRETTY_NAME="Ubuntu 22.04.2 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.2 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
PHP 8.1.2-1ubuntu2.14 (cli) (built: Aug 18 2023 11:41:11) (NTS)
Server version: Apache/2.4.52 (Ubuntu)
Server built: 2023-10-26T13:44:44
Additional comments
When trying to open a file for editing, a message appears that "Source file not found."
Is this a bug? Being treated?
joomla-cms-bot
- | Labels |
Added:
No Code Attached Yet
|
||
And I have like this
Joomla 4.4.0
There is something seriouslty odd in your install as it is showing the tinymce editor which should not be displayed in that component
I had other editors disabled because TinyMCE stopped being displayed (remark: it was solved by resetting the browser cache). I turned on the other two editors, but nothing has changed along the way.
Can't confirm (J 5.0.
01):
What version of PHP do you have?
Are you using mysql? I use postgresql, maybe that's the reason?
What version of PHP do you have?
8.1.24
Are you using mysql?
mysql 8.0.34-cll-lve
i'm able to replicate with postgres
| Labels |
Added:
bug
|
||
| Status | New | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2023-12-26 10:44:55 |
| Closed_By | ⇒ | alikon |
Of course, I will test and describe the result in the near future. Now the main job takes up a lot of time. I myself am interested in the performance of joomla with postgres.
I have tested this change, I confirm it works.
Can't confirm (J 5.0.
01):