Fine by me - in some ways hathor is already less accessible than isis anyway

Haha, I read that as Heathrow...

I'm all in for this. However, it would be bad if things break while using Hathor. As far I'm aware, the Admin Menu Manager feature breaks the Menu Manager in Hathor very badly.

Not implementing further features is fine. But not taking care of what already is there would be a fake B/C. In that case removing it would be way better option.

In case we decide to keep it for now, I'd suggest fixing broken things at least. From my end I can attempt to fix Menu Manager at priority. Please let me know if I should.

I agree with the proposal. ?

I agree here with @izharaazmi. If we don't support all features, then it is broken and thus needs to be removed from the installation package. The sites who do upgrade will still have it installed, so no change (despite the fact that not all features do work). But it should not be there on new installs. We need to clearly communicate that in the release notes that hathor is broken for upgrades and that it will not be available from 3.7 onwards.

IMHO should be removed ....... who is still using Hathor ?

Not only Admin menus, Multilingual associations have also issues.
Basically all modals have issues as they use Search Tools.

maybe we should be inserted an alert message in the control panel (like for the old PHP version or for the editor update ecc..) to display if the template Hathor is set to default.

@alexred suggestion is a good one

Something like

"We have detected that you are using the Hathor Admin template. This may not work well with some Joomla features and we recommend that you switch to use the Isis template "

Just did a test creating a menu item with Hathor... Then I switched to Isis and tried to create a menu item: I got a Fatal Error:

Fatal error: Cannot use object of type stdClass as array in /administrator/components/com_menus/models/item.php on line 603

My conclusion is that I think that we have at least to solve the menu issue and indeed display the Alert proposed above.

@izharaazmi I hope if things can be fixed then what else can be a better option.

maybe we should be inserted an alert message in the control panel (like for the old PHP version or for the editor update ecc..) to display if the template Hathor is set to default.

That would have to be a postinstall message. Please don't do messages in the cPanel itself.

Basically, if we do not do it, this is a release blocker.

I'm with @infograf768. We should not ship something which is broken and we have no intention to fix it.

I am trying to spare some time to fix it myself, though its likely not
possible before this weekend I guess.

However, I vote for removing hathor as menu manager is not the only issue
with it, and I don't know much about others.

If the 3.6.5 Hathor can work with 3.7, I'd say move it to a joomla-extensions/hathor repo and pull it from the distro with 3.7. Then if it ever gets functionally updated to work with 3.7 an update can be pushed out separate from the main release schedule (decoupled extension style). Otherwise it can sit there like the GeSHI content plugin and never get updated if there's no interest. But in the interest of fulfilling our B/C promises, we at least have to make it look like we're making an effort unless things are really just fatally broken (that same joke about there being 3 SQL Server users probably applies to Hathor too).

The problem is that unfortunately 3.6.5 state of Hathor too won't work with
3.7, as far as I know.

I tried fixing Menu manager but searchtools is heavily broken in hathor.
Can't do much about that.

I am doing a PR now to remove Hathor as a separator repo. Rest is on the
teams decision to accept it or close.

Fyi https://twitter.com/laoneo/status/849625687338221569, there are people using hathor so we need a proper way to migrate them.

Sounds like "migrating not working feature". )
p.s. from my personal experience with Hathor only

Migrating isn't hard. If Hathor isn't available anymore, they are migrated automatically to Isis (an error is shown that "the template isn't available for this view" and Isis is the fallback) :p

Is there anyone like Andy that can test accessibility anymore? @brianteeman aren't you well versed in that?

No idea what you are aksing @N6REJ but the reality from an a11y perspective is that hathor really isnt much better (if at all) than isis

Has there been a decision made about this?

not yet

I asked because of this comment by @franz-wohlkoenig

#14491 (comment)

as I said no decision is made

There has been a decision made. Hathor will continue to ship with J3.x however we do not guarantee feature parity of all Joomla features (i.e. everything that works now should continue to work but we don't guarantee new features like fields and associations etc will continue to work fully - although we won't obviously reject any PR's if they come in)