[#34908] - [4.0] Error "The template for this display is not available" after update from 3.10
- Closed
- 27 Jul 2021
- Medium
- Build: staging
- # 34908
Maybe that error it's ok, but I want to create issue. Or it's not ok?
Steps to reproduce the issue
- Install clean 3.9.28
- Update to 3.10 alpha 9
- Set update url https://update.joomla.org/core/test/310to4_list.xml
- Update to Joomla 4 rc-4
- See error at the screenshot on "Actual result"
Expected result
Update process without any errors
Actual result
System information (as much as possible)
PHP 8.0.8, Mysql 5.7.34
joomla-cms-bot
- | Labels |
Added:
?
|
||
It is well known that this is shown one time after the update and then disappears and doesn't come again when you start to navigate around in backend.
Everything is correct. However, I'm starting to curl my fingers how many more of these Issue will be created upon the release of the stable version 4.0.
Yes, that would be a pain. I'm just clarifying if we have some docs about it or if we need some or need more.
@richard67 maybe it will be better to show full description about this? When Joomla 4 goes to stable version, users will be ask questions about it.
For example, "The template Isis is not supported with Joomla 4 and now, after upgrade from Joomla 3.10, it was deleted"
For example, "The template Isis is not supported with Joomla 4 and now, after upgrade from Joomla 3.10, it was deleted"
It's an error message shown in general when the template is not available. We don't have one for that special case of just having updated from 3.10 to 4.0. So if we just change the message text as suggested, the message will be wrong in other cases of missing templates.
So maybe we should look at changing that so it is a specific error with a specific message OR work to prevent that message appearing in the first place.
Looking at the code and considering what situation would trigger this message I would suggest not outputting a message at all by removing the following line or replacing it with a log message (ie not displayed on screen)
The reality is that 99.99% of the time it will only be shown on updates and that is the one time that the message is incorrect and of no use.
Looking at the code and considering what situation would trigger this message I would suggest not outputting a message at all by removing the following line or replacing it with a log message (ie not displayed on screen)
I'd be ok with that. Opinions from others are welcome.
I'd be happy with a log message too. I think it's fairly consistent with things as it's not something that an end user can fix anyhow if they saw it in the frontend too.
this would only be in the admin but I will prepare a PR
| Status | New | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2021-07-26 11:26:16 |
| Closed_By | ⇒ | richard67 |
| Status | Closed | ⇒ | New |
| Closed_Date | 2021-07-26 11:26:16 | ⇒ | |
| Closed_By | richard67 | ⇒ |
Re-opening since the pull request has been closed.
Because we cannot use jerror for log there, and seems we do not have another appretiere category, so instead of introducing new category (that will be only here and no one will know about it) I suggest to remove that line.
A couple lines down there an exception if something crazy happen:
joomla-cms/libraries/src/Application/AdministratorApplication.php
Lines 275 to 283 in b892e8a
agree
| Status | New | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2021-07-27 15:28:51 |
| Closed_By | ⇒ | richard67 |
I was getting the same error when I upgraded from 3.9 to 3.10 to 4.0.