? Pending

User tests: Successful: Unsuccessful:

avatar ggppdk
ggppdk
2 Aug 2018

Pull Request for Issue #21360 ([4.0] Side menu does not work anymore)

Summary of Changes

Fix CSS rule introduced by #21316
causing 2nd level menu not be shown

Testing Instructions

Click to open various 2nd level menus

Expected result

They open

Actual result

They do not open

Documentation Changes Required

Nove

avatar ggppdk ggppdk - open - 2 Aug 2018
avatar ggppdk ggppdk - change - 2 Aug 2018
Status New Pending
avatar joomla-cms-bot joomla-cms-bot - change - 2 Aug 2018
Category Administration Templates (admin)
avatar ggppdk ggppdk - change - 2 Aug 2018
The description was changed
avatar ggppdk ggppdk - edited - 2 Aug 2018
avatar ggppdk
ggppdk - comment - 2 Aug 2018

@wojsmol
@franz-wohlkoenig
@Magnytu2

I have made this PR to fix issue #21360

avatar ggppdk ggppdk - change - 2 Aug 2018
The description was changed
avatar ggppdk ggppdk - edited - 2 Aug 2018
avatar ggppdk ggppdk - change - 2 Aug 2018
The description was changed
avatar ggppdk ggppdk - edited - 2 Aug 2018
avatar wojsmol
wojsmol - comment - 2 Aug 2018

@ggppdk AFAIK you should only commit scss changes and tester should compile this to css. @dgrammatiko please confirm this

avatar ggppdk
ggppdk - comment - 2 Aug 2018

@wojsmol

a tester re-compiling is surely a good / proper thing

but PRs until now always included the updated CSS too
this because the template CSS files continue to be tracked,
thus you would not want them to be "stale" when the PR gets merged ... , right ?

I don't think that this PR makes a difference
#21217 (Remove vendor folders ?)

avatar wojsmol
wojsmol - comment - 2 Aug 2018

I don't think that this PR makes a difference
#21217 (Remove vendor folders ?)

Not #21217 php vendor but latests changes from @dgrammatiko for assets and because I'm not sure then I used "AFAIK" and ask for confirmation.

avatar infograf768
infograf768 - comment - 3 Aug 2018

This solves nicely the main issue, which is that the second level menus do not display in present 4.0.
It also solves here #21353

avatar infograf768 infograf768 - test_item - 3 Aug 2018 - Tested successfully
avatar infograf768
infograf768 - comment - 3 Aug 2018

I have tested this item successfully on 9919161


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/21367.

avatar wilsonge wilsonge - change - 3 Aug 2018
Title
Fix 2nd level menu (atum template) not showing
[4.0] Fix 2nd level menu (atum template) not showing
avatar wilsonge wilsonge - edited - 3 Aug 2018
avatar wilsonge
wilsonge - comment - 3 Aug 2018

For now templates specifically are still committing the compiled CSS (as we have the discussion about where to move the uncompiled to - whether also to media or just the template dir) - hence the compiled files are still in the repository here.

avatar franz-wohlkoenig
franz-wohlkoenig - comment - 3 Aug 2018

@wilsonge does your Comment mean J4-PR can be tested by Patchtester?

avatar wojsmol
wojsmol - comment - 3 Aug 2018
avatar franz-wohlkoenig
franz-wohlkoenig - comment - 3 Aug 2018

@wojsmol all PR (as before npm-, ...-Changes)?

avatar ghazal ghazal - test_item - 3 Aug 2018 - Tested successfully
avatar ghazal
ghazal - comment - 3 Aug 2018

I have tested this item successfully on 9919161


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/21367.

avatar franz-wohlkoenig franz-wohlkoenig - change - 3 Aug 2018
Status Pending Ready to Commit
avatar franz-wohlkoenig
franz-wohlkoenig - comment - 3 Aug 2018

Ready to Commit after two successful tests.

avatar wilsonge wilsonge - change - 3 Aug 2018
Status Ready to Commit Fixed in Code Base
Closed_Date 0000-00-00 00:00:00 2018-08-03 11:43:30
Closed_By wilsonge
Labels Added: ?
avatar wilsonge wilsonge - close - 3 Aug 2018
avatar wilsonge wilsonge - merge - 3 Aug 2018
avatar wilsonge
wilsonge - comment - 3 Aug 2018

Thanks guys!

avatar wojsmol
wojsmol - comment - 3 Aug 2018

@franz-wohlkoenig See #21367 (comment) - for now changes in templates are don't requiring npm so good for patch tester.

avatar franz-wohlkoenig
franz-wohlkoenig - comment - 3 Aug 2018

@wojsmol thanks, so i will test Front- and Backend-PRs.

avatar wojsmol
wojsmol - comment - 3 Aug 2018

@franz-wohlkoenig I was not as precise as I wont:

avatar franz-wohlkoenig
franz-wohlkoenig - comment - 3 Aug 2018

if /files include *.css > Patchtester, correct?

avatar franz-wohlkoenig
franz-wohlkoenig - comment - 3 Aug 2018

https://github.com/joomla/joomla-cms/pull/21384/files have 1 php-File so not testable by Patchtester.

avatar dgrammatiko
dgrammatiko - comment - 3 Aug 2018

If PR has some files touched in media folder then it cannot be tested with patch tester

avatar franz-wohlkoenig
franz-wohlkoenig - comment - 3 Aug 2018

@ggppdk #21384 can be tested by Patchtester.

avatar wojsmol
wojsmol - comment - 3 Aug 2018

@franz-wohlkoenig In #21384 Files changed 6tam on github content o0nly *.php file so yes
@dgrammatiko Please update https://docs.joomla.org/J4.x:Setting_Up_Your_Local_Environment with description when node.js is required to test PR.

avatar mbabker
mbabker - comment - 3 Aug 2018

That doc page is not for testing pull requests, it is a "how to get started once you git clone the repository" guide. Other documentation regarding pull requests should be updated instead to reflect the changes in 4.0.

avatar wojsmol
wojsmol - comment - 3 Aug 2018

@mbabker You are right that thus page is not a best place but for now I wont to have written this info somewhere.

Add a Comment

Login with GitHub to post a comment