Patch file that resolves the issue is attached.
I have the same on multiple existing sites updating to 10.3.1. If I disable the Admin Toolbar Extra Tools module, it goes away. After re-enabling the module, the dblog messages return.
I tried to reproduce this bug this morning to put them here, but i updated to core 10.3.0 over the weekend and now the warnings are no longer in my dblogs. Not sure if this should be closed or not.
r0nn1ef → created an issue.
Here is the patch file generated from the fork.
@sweetchuck, that is how the module was designed. I didn't want to re architect the whole thing. That is a whole different discussion that should probably be had because it makes sense.
I have not tried this, but this fork could possibly be a solution for ✨ Add support for Stage File Proxy Needs review .
I tested the fork, but the only way that I could get this to work properly was to also enable the content moderation workflow and add a content block type to the workflow. I'm assuming this is is related to ✨ UI for publishing/unpublishing block_content blocks Needs work because blocks don't expose the publish status checkbox and are always published. Am I correct in this assumption and setting this up or did I miss something somewhere?
Here is a patch to add pagination to the admin listing page that is configurable.
There are several different ways to achieve this within the Drupal ecosystem and after discussion with others, should not be tied to a specific implementation. The decision is best left to site builders and developers to implement the solution that best fits his/her needs.
I would like to take ownership of this project. The project page I wish to take over is https://www.drupal.org/project/nasa_apod →
I currently have a github repo which is basically the same as this module (https://github.com/r0nn1ef/apod) but built with more "Drupaly" features such as composer installation, services, dependency injection, etc. and is D9 and D10 ready.
I was going to move my github project to Drupal.org, but found this and do not want to clutter the community with duplicate functionality .... especially for such a simple task.
It turned out to be a caching issue. I cleared the caches and all seems to be well now.
Closing this issue as outdate.
Closing this issue as outdate.
Closing this issue as outdate.
Closing this issue as outdate.