Closed (fixed)
Project:
Scheduler
Version:
2.x-dev
Component:
User Interface
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
27 Feb 2022 at 20:18 UTC
Updated:
3 May 2024 at 09:56 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
jonathan1055 commentedThanks arlingtonvoicellc for reporting this.
1. Just so I understand you correctly, you are allowing users access to admin/content/scheduled but you are not allowing them to view the admin theme?
2. It will need investigation (and fixing) at Scheduler 2.x first. Have you tried that yet?
Comment #3
arlingtonvoicellc commentedSorry, I had the wrong version selected. I'm using 1.4.
The affected URL is user/UID/scheduled.
Steps to reproduce:
1. Enable scheduler and dependencies
2. Assign 'schedule content publication' permission to authenticated role
3. Set scheduler field settings for node type and add/schedule a piece of content as authenticated user
4. After content is scheduled, visit /user/UID/scheduled (admin theme shown here)
You probably don't have to assign any content. You can probably just visit user/UID/scheduled as an authenticated user after assigning the permission to see the admin theme displayed.
Comment #4
arlingtonvoicellc commentedComment #5
jonathan1055 commentedThanks @arlingtonvoicellc that makes sence now, I thought you were saying the problem was on admin/content/scheduled. I have confirmed this is a bug, at both 8.x-1.x and 2.x (I switched the version on this issue, it was not your mistake). The problem was introduced in #3128187: Content List View for a user - change theme to admin not front-end default theme and should be simple to fix.
Comment #7
jonathan1055 commentedThe MR is on the 2.x branch, but the identical fix applies to 8.x-1.x, here's a patch for you to try.
Comment #8
jonathan1055 commentedAll seems OK, needs review. @arlingtonvoicellc let me know how you get on with the patch. You will have to clear the cache to get the updated
SchedulerThemeNegotiatorto become active.Comment #9
arlingtonvoicellc commentedThe patch works great! Thank you for this.
Comment #12
jonathan1055 commentedThanks for testing.
Committed to 2.x and 1.x