You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If i run a queued static publish job from within the CMS(withouth a user selected) all the urls that get published have ?stage=Live in the url. If i run it from the CLI it works as expected.
Looking at the QueedJobService.php file, I overwrite to use userId 0:
// no user provided - fallback to job user default// if ($userId === null && $job instanceof UserContextInterface) {$userId = $job->getRunAsMemberID();
// }// still no user - fallback to current user// if ($userId === null) {// if (Security::getCurrentUser() && Security::getCurrentUser()->exists()) {// // current user available// $runAsID = Security::getCurrentUser()->ID;// } else {// // current user unavailable// $runAsID = 0;// }// } else {$runAsID = $userId;
// }$jobDescriptor->RunAsID = $runAsID;
I use default config. I use Fluent and SS 4.8.0.
I think currently it is not possible to start a job from the CMS and run it without a user.
The text was updated successfully, but these errors were encountered:
If i run a queued static publish job from within the CMS(withouth a user selected) all the urls that get published have ?stage=Live in the url. If i run it from the CLI it works as expected.
Looking at the QueedJobService.php file, I overwrite to use userId 0:
I use default config. I use Fluent and SS 4.8.0.
I think currently it is not possible to start a job from the CMS and run it without a user.
The text was updated successfully, but these errors were encountered: