- last update
about 2 years ago 223 pass - π§πͺBelgium Simon Govaert
Adding another solution I found for this particular problem. At first, installation seemed ok as I could enable scheduler module and fill (un)publishing dates on content. Although the (un)publishing dates were never saved. It gave a hint that the installation was not made properly.
It failed because of missing folders (default/files/tmp and default/files/translations). The installation made by "composer require" didn't tell where it failed.
- πΊπΈUnited States katebron
I am also getting locked out of uninstalling this module (2.1); for me, when i try to uninstall, i get an error message abut 'publish_on' not found in taxonomy_term_field_data. (Incidentally, i haven't set up scheduler to work with taxonomy terms at all). I have tried the patch in #22 and it doesn't help the problem, perhaps because it's looking at nodes only
- π³π±Netherlands yustinTR
Sorry my patches wont work i wanted to apply the previous patch and make it compatible with version 2.1.
- π©πͺGermany Grevil
I just ran into a similar issue with the same QueryException inside a scheduler integration for a custom entity. Both the entity data table and the entity revision data table had the "publish_on" column as expected, but the entity query got corrupted on SchdulerManager.php line 261:
$query->latestRevision();
The reason for this was that our custom entity had the "revision_table" entity Attribute set, but the "revision_data_table" key was missing. This lead to this issue because scheduler could not resolve the "revision_data_table" in the SchedulerManager $query->latestRevision() call, leading to the "publish_on" error not found (which is quite confusing, as it should say "could not resolve revision data table" but whatever...).
Here is the issue if anyone is interested: π Fix missing mandatory "AdContent" entity revision keys Active .