New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[3.9.0] Checks need to guide you on where to fix them #22869
Comments
Please test |
Set to "closed" on behalf of @Quy by The JTracker Application at issues.joomla.org/joomla-cms/22869 |
@PhilETaylor |
Folks and @mbabker TestSet SEF OFF Although it will indeed display the form in the frontend French interface, this is quite useless as I do not see anyone using this link to go fill such a request in frontend as it is much easier to just go to Also, when there is no menu item at all, the Itemid of the link is the one of the Default Home page set to ALL languages, which is not used at all in multilang. Test 2Delete the en-GB menu item. Create a fr-FR menu item, publish it. My thought on this: What do you think? |
The intent was to be able to easily provide a link to the frontend page at all times. Not a link to the menu manager. |
This comment was marked as abuse.
This comment was marked as abuse.
The status check module isn't a walkthrough system and I'd be very hesitant to start throwing random create or edit links into the UI unless you can guarantee they're going to be crystal clear for what the suggested action is. And just dropping someone on the Menu Manager without that guided walkthrough IMO is a worse idea than not having a "click here to go to the Menu Manager to fix this issue" action. |
This comment was marked as abuse.
This comment was marked as abuse.
In any case, even if the intent is to provide a link to the frontend page (which I still think is useless), it does not do the job right as it does not work correctly when multilang is on as I demonstrated in details above. |
Please test #22909 |
Each check should be hyperlinked to the page where it can be resolved.
For example, to "set a privacy policy" is a million clicks to the plugin manager,, search for the plugin, and then edit the plugin - whereas it could be a single click on the check to take you to (eg) http://example.com/administrator/index.php?option=com_plugins&view=plugin&layout=edit&extension_id=485
The text was updated successfully, but these errors were encountered: