Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 UTC on 18 March 2024, to get $100 off your ticket.
In 8.9.0 version, I was getting pages, roles & content types settings at admin/structure/block/manage/mainmenu but after upgrade to 8.9.2 version, new options like "Node is sticky", "User is blocked", "Node is published" etc. are showing. I am not getting where I can configure page urls as I did in 8.9.0.
Comment | File | Size | Author |
---|
Comments
Comment #2
Devendra Mishra CreditAttribution: Devendra Mishra commentedComment #3
Devendra Mishra CreditAttribution: Devendra Mishra commentedComment #4
rinckoar CreditAttribution: rinckoar commentedI have the same issue, please how can I configure visibility per page o node type in 8.9.2.
Comment #5
shailja179 CreditAttribution: shailja179 at Srijan | A Material+ Company for Drupal India Association commentedHi @Devendra Mishra,
I can see these options even in 8.9.2 version.
Can you give the steps to reproduce this issue?
Comment #6
Devendra Mishra CreditAttribution: Devendra Mishra commentedHi Shailja, Thanks for helping!!
I was using 8.9.0 version, then I have ran drupal update using composer.json and now drupal version is 8.9.2. After drupal upgrade, blocks visibility options have changed. Now I can see "Node is sticky", "User is blocked", "Node is published" options instead of pages, roles & content types settings.
Comment #7
shailja179 CreditAttribution: shailja179 at Srijan | A Material+ Company for Drupal India Association commentedCan you elaborate that which theme, which block and in which region you were adding this block?
Because i updated my Drupal version to 8.9.2 and could not reproduce your issue.
As i have attached screenshot of block page in 8.9.2, these options are available there.
Comment #8
rinckoar CreditAttribution: rinckoar commentedHi Shailja, i have the same problem. I tried to put new blocks in different regions and the same happens in all of them, even when modifying old blocks only the options "Node is promoted" "the user is blocked" Entity is new "" Node is sticky "" Node is published "" data comparison " are displayed.
It also happened to me when updating to drupal version 8.9.2
Comment #9
Janner CreditAttribution: Janner commented+1 for the Content Type, User Role, and Page visibility options disappearing after upgrading to 8.9.2.
Fortunately, existing blocks appear to still respect the options that were set previously.
However, these options are simply not listed when editing an existing block or adding a new one.
In my case the upgrade was from 8.9.1 and the visibility options mentioned by some in this thread as being new were present for me previously.
I'm using the Bootstrap4 theme.
The behaviour is present in all block regions and for all types of block (core, module, or custom).
Comment #10
shailja179 CreditAttribution: shailja179 at Srijan | A Material+ Company for Drupal India Association commentedI could not be able to reproduce this issue. I have updated the version to 8.9.2 but no luck.
Attaching screenshots of version and block visibility.
Comment #11
peter63 CreditAttribution: peter63 commentedI also have "lost" the pages filter for blocks with 8.9. currently have no way to restrict block visibility
Comment #12
pameeela CreditAttribution: pameeela commentedThis is coming from Rules module, it was a known issue should be fixed in core with #2958785: ContextDefinition isSatisfiedBy() check fails for context using inherited class. There was a new release of Rules on July 20, for those seeing this, did you update Rules at the same time as core? Can anyone confirm they only updated core?
Comment #13
pameeela CreditAttribution: pameeela commentedI can confirm that the core tabs display on 8.9.2 with Rules 8.x-3.0-alpha5:
But not with 8.x-3.0-alpha6:
So I think this should go over to the Rules queue?
Comment #14
TR CreditAttribution: TR commentedPlease try the patch in #2927132-15: List of conditions includes Core conditions which do not work with Rules
Comment #15
Janner CreditAttribution: Janner commentedBingo!
The latest Rules release was indeed the culprit.
Having applied the patch mentioned above, all block visibility options are available again.
Thanks for figuring this one out for us.
Comment #16
Devendra Mishra CreditAttribution: Devendra Mishra commentedExcellent!!
Patch mentioned above is working, now I can see all the block visibility options.
Thank you very much for helping.
Comment #17
rinckoar CreditAttribution: rinckoar commentedThanks for the help, the patch works perfect
Comment #18
TR CreditAttribution: TR commentedPatch in #2927132-15: List of conditions includes Core conditions which do not work with Rules was committed. If you encounter this problem please apply the patch or update to the -dev version of Rules.
Comment #19
scott.whittaker CreditAttribution: scott.whittaker commentedThanks for figuring this out, only lost a few hours trying to debug. Uninstalled Rules, all better now.
Comment #20
Stephen OllmanBoth patch or 8.x-3.x-dev resolve the issue.
Comment #22
jukka792 CreditAttribution: jukka792 as a volunteer commentedI installed the Rules dev version and the Drupal block visibility settings have now "data comparison" and "data value is empty" -options.
Is it intended that rules module adds these new options to all block visibility settings?
Comment #23
jonathan1055 CreditAttribution: jonathan1055 as a volunteer commentedYes I also see these Rules tabs in addition to the Core ones.
Without Rules installed
With Rules installed
I don't think it is intended, or if it is, the conditions are not useable as there is no way to enable/disable them. Apart from the two 'data' tabs the rest are just empty except for a 'negate' checkbox.
Maybe a new issue should be raised, as this one was all about Rules accidentally hiding the Core conditions (and that is fixed now)
Comment #24
TR CreditAttribution: TR commentedRe #22, #23:
That's a long-standing core issue, #2284687: Redesign UI for better management of block visibility
Comment #25
TR CreditAttribution: TR commentedComment #26
jonathan1055 CreditAttribution: jonathan1055 as a volunteer commentedOK thanks for linking that issue.
So just to be clear, are you saying that it is correct for the Rules conditions to be shown on these block visibility pages?
Comment #27
TR CreditAttribution: TR commentedNo, I'm saying that Core needs to be selective about which conditions it shows - if Core can't use the condition, it shouldn't show it. Specifically, if the Block UI can't use the condition then the Block UI shouldn't show the condition. This is a problem not only with Rules conditions but with conditions provided by other modules, as described in that core issue. The Core block visibility list shows all @Condition plugins. Rules defines lots of @Condition plugins, as do some other contributed modules. The bock visibility UI should show only applicable conditions, as described in that Core issue.
Note that this was fixed in core at one point by #2958785: ContextDefinition isSatisfiedBy() check fails for context using inherited class, but it has evidently been broken again - I don't know where or by what, but this is a Core regression. It will take some work to find out how Core broke this and to revert/fix the Core commit that broke this.
There are also other Rules issues, like #2789051: Add schemas for Rules condition plugins, which potentially can contribute to a Core fix. But as far as I'm concerned, this problem has been around for many many years - it's not something that just started to happen - and needs to be fixed in Core, not in Rules.
Comment #28
jonathan1055 CreditAttribution: jonathan1055 as a volunteer commentedThank you @TR for the clarity, that is really helpful.
Yes I had noticed that the four conditions provided by Scheduler module which I maintain also get shown on the block visibility tabs, and are likewise not useable.
That is what I thought! This is the reason I was concerned that contrib had to make some changes now, and that we'd not been keeping up and had caused the regression.
I will follow those other issues, and try to help where I can.
Comment #29
jonathan1055 CreditAttribution: jonathan1055 as a volunteer commentedComment #30
aiphesFacing off this issue too but I have a working website which runs 8.x-3.0-alpha5, all others run 8.x-3.0-alpha6. All websites run on D896.
Difference is the same as screenshot in #23
Comment #31
jonathan1055 CreditAttribution: jonathan1055 as a volunteer commentedThanks aiphes. I have just posted on the core issue #2284687: Redesign UI for better management of block visibility which is th cause of the problem.
Comment #32
naveen20430 CreditAttribution: naveen20430 commented#14 Working for me
Comment #33
ddhuri CreditAttribution: ddhuri as a volunteer commentedThanks #14 works for me with Drupal 8.9.6 and Rules 8.x-3.0-alpha6
Comment #34
admirernepali CreditAttribution: admirernepali commentedThanks #14 worked for me with Drupal 8.9.10 as well as 8.9.9 and Rules 8.x-3.0-alpha6
Comment #35
aiphesPatch from #14 work on D8910 + 8.x-3.0-alpha6 on my Dev website.
Will do the same on prod websites to confirm.
Comment #36
WinkieWinkie CreditAttribution: WinkieWinkie commentedPatch from #14 worked on D8 version 8.9.10, on Production, was really thrown off with the missing Visibility options, then stumbled on this trail.
Comment #37
perfectcu.be CreditAttribution: perfectcu.be as a volunteer and commentedGoogle sent me here, but thanks to a pointer in the right direction from WinkieWinkie this patch from rules #issue 2927132 worked to restore path visibility in block configs.
Comment #38
theolem CreditAttribution: theolem commentedHi,
encoutering this issue again with Drupal 8.9.16 and Rules 8.x-3.0-alpha6. I can't see the core options for managing block display, on Rules ones.
The patch from #14 seems to have been commited, there was no need to apply it again on my side.
Any idea what changed ?
Comment #39
jonathan1055 CreditAttribution: jonathan1055 as a volunteer commentedYes the patch mentioned in #14 (which is on #2927132-15: List of conditions includes Core conditions which do not work with Rules) was committed to Rules dev in July 2020. It is OK for me on 8.9.16 so in principle it is working.
Comment #40
jonathan1055 CreditAttribution: jonathan1055 as a volunteer commentedJust realised that you might have though that the commited patch was in the latest release. The patch was committed, yes, but that was on 25 July 2020. However, the alpha6 release was on 20 July, i.e. before the commit. There has not been a new Rules release since then, so you need to use the -dev version of Rules, or apply the patch to alpha6.
Comment #41
theolem CreditAttribution: theolem commentedOh yes you're right, that was it. Switched to dev and all good. Thanks a lot !
Comment #42
jptillman CreditAttribution: jptillman commentedFriendly reminder that the recommended package version on the Drupal Rules project page breaks a fundamental Drupal functionality nearly all site designers need, and has been posted there for more than a year now.
Comment #43
gatorjoe CreditAttribution: gatorjoe as a volunteer commentedSame issue here with Drupal 8.9.19. Switching to the dev version of Rules was the fix.