-
-
Notifications
You must be signed in to change notification settings - Fork 825
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
Removes Joomla Sidebar #27252
Removes Joomla Sidebar #27252
Conversation
CSS fix for stripping sidebar
Removes old markup specific to the sidebar, and fixes padding.
Removes extra </div>
🤖 Thank you for contributing to CiviCRM! ❤️ We will need to test and review this PR. 👷 Introduction for new contributors...
Quick links for reviewers...
|
Thanks @vingle! It would be great if you could fix the linting errors caught here and an added bonus if you could squash the commits down to one. |
@colemanw thanks - will do. Am keen to clean up joomla.css completely, but that's probably a separate PR. |
I think in some drupal themes like Garland it could have its own side bar but yes. I think if we are doing this and completely gutting the sidebar can I suggest we get rid of https://github.com/civicrm/civicrm-core/blob/master/CRM/Core/Invoke.php#L216 and https://github.com/civicrm/civicrm-core/blob/master/CRM/Core/Joomla.php#L32 and https://github.com/civicrm/civicrm-core/blob/master/templates/CRM/Block/blocks.tpl. Just also noting that JMA currently has 2 clients that still use Joomla 3 for mainly joomla plugin / module reasons |
That's true. I think it's D8 onwards it's no longer seen, have changed.
That would be a big improvement to the PR – but it's not something I feel confident to do. (removing the function from /core/Joomla.php seems to make that file unnecessary too?)
Is it possible to get a sense if they value the sidebar? There hasn't been any pushback to removing it on the Gitlab issue but it's maybe not been seen by so many Joomla users. |
@vingle I'll see if I can get someone to check in with them. |
Fixes linting errors, including missing semicolon & makes line-space consistent
@colemanw – I've cleaned up the css spacing/bug, but struggled to squash - either thru the desktop or webUI (because one commit is a merge?). If you can squash on merge, that's appreciated - or I can make a new PR? Not sure about implementing Seamus's suggestions as I don't know how best to check if it would impact other things than Joomla's UI beyond lots of testing on the different CMSs. |
@vingle I did a quick test on Joomla 3 (as requested on Mattermost). No major problems but I did notice 2 minor things:
|
@andrewpthompson thanks alot for doing the check. I foolishly haven't left any J3+Civi dev spaces to test against, but will set one up, fix and resubmit. The shrinking font-size is a little unexpected. |
@seamuslee001 could you also do a runtime test and include testing of your suggested code improvements to patch then get @monishdeb to QA. @Edzelopez could you check with one or both of our J3 clients? |
@andrewpthompson - I've just setup a J3 and Civi to test and while I can't replicate the lack of gap on the edges after refreshing the browser (see below), I can see the font-size shrinks from the already too small 13px to 11px. This is because sizes are set in |
Tested on Joomla 3/4, to fix issue raised here #27252 (comment)
@vingle... really appreciate your work on this! |
Thanks for your work on this @vingle |
Overview
As discussed here: https://lab.civicrm.org/dev/joomla/-/issues/45 - Joomla 4 has a sidebar, which defaults open, and means the Civi sidebar squashes the main content more. This PR removes that sidebar.
As Joomla 3 is end-of-life, probably most Joomla users will be on Joomla 4. The sidebar was unique to Joomla, and not present in WordPress or Drupal 9+. Removing the sidebar also stops Civi's main content from being loaded inside a table.
Before
After
Technical Details
Changes impact two Joomla-specific files – joomla.css and joomla.tpl – so shouldn't impact other CMSs. Joomla 3 is End-of-life since August 17, other than the paid Extended Support Release programme, and this hasn't been tested there.
Comments
If Joomla 3 support is required, this needs testing on Joomla 3.