🇧🇪Belgium @bart lambert

Having the same issue as #4

[Open] somebody marked this thread as solved but I sorry to tell that I don't see it that way!

Me and others still cope with this problem So it beter be left open and hopefully someone finds a correct fix!

So , do you mean on all the menu’s or just the management menu?

Found out that the downgrade to 10.2.7 was done because ‘rules’, although uninstalled, was still present in the composer.json file.

removing it triggered the update to 10.3.1 bit the menu’s were unfortunately gone again ,-(

The sites which encounterd the above problem recieved an automatic downgrade to core 10.2.7 whilst 10.3.1 is available.

structure and configuration menu’s reappeared and I was able to turn on the rules module without crashing the site.

wondering when those sites will upgrade to 10.3.1.

Forcing the update with composer to 10.3.1 did not work. The site mentioned an update available but running composer update gives a “nothing to install of update “ result.

any clues?

Following your lead I made a new configuration menu link but called it "configuration2" in order to find my way back.
Then I dragged the first submenu 'persons' with all the submenu's to "Configuration2".

Amazingly the original menu "Configuration" reappeared in my management menu on top of the page containing all the links except the submenu 'persons' with all his submenu's.
The self made menu "configuration2" is nowhere to be seen. If I Change the link here from admin/config to <nolink> everything disappears again.
But we're getting somewhere since most of the configuration menu is back on the screen.

Hi,

Struggling with the same problem here.

However I manage to get the 'structure' menu back in site by altering the weight of this item to "0".

However this did not work for the "configuration part". I started fiddling around with this one and made my "structure" disappear again.

But It seems link the address "admin/config" is completely missing and that seems very odd....

uninstalling the rules modules got my site back.

I have the same issue after update from 10.2.7 to 10.3.0

Same here on 3 of my 5 sites!

2 sites are totally unaccessible,

Drupal\Component\Plugin\Exception\PluginNotFoundException: The "user_role" plugin does not exist. Valid plugin IDs for Drupal\rules\Core\ConditionManager are: rules_data_comparison, rules_data_is_empty, rules_list_contains, rules_list_count_is, rules_entity_has_field, rules_entity_is_new, rules_entity_is_of_bundle, rules_entity_is_of_type, rules_ip_is_banned, rules_node_is_of_type, rules_node_is_promoted, rules_node_is_published, rules_node_is_sticky, rules_path_alias_exists, rules_path_has_alias, rules_text_comparison, rules_entity_field_access, rules_user_has_role, rules_user_is_blocked in Drupal\Core\Plugin\DefaultPluginManager->doGetDefinition() (line 53 of core/lib/Drupal/Component/Plugin/Discovery/DiscoveryTrait.php).

1 site throw errors on entering admin section

Drupal\Component\Plugin\Exception\PluginNotFoundException: The "request_path" plugin does not exist. Valid plugin IDs for Drupal\rules\Core\ConditionManager are: rules_data_comparison, rules_data_is_empty, rules_list_contains, rules_list_count_is, rules_entity_has_field, rules_entity_is_new, rules_entity_is_of_bundle, rules_entity_is_of_type, rules_ip_is_banned, rules_node_is_of_type, rules_node_is_promoted, rules_node_is_published, rules_node_is_sticky, rules_path_alias_exists, rules_path_has_alias, rules_text_comparison, rules_entity_field_access, rules_user_has_role, rules_user_is_blocked, webform in Drupal\Core\Plugin\DefaultPluginManager->doGetDefinition() (line 53 of core/lib/Drupal/Component/Plugin/Discovery/DiscoveryTrait.php).

Drupal\Core\Plugin\DefaultPluginManager->getDefinition('request_path') (Line: 16)
Drupal\Core\Plugin\Factory\ContainerFactory->createInstance('request_path', Array) (Line: 67)
Drupal\Core\Condition\ConditionManager->createInstance('request_path', Array) (Line: 21)
Drupal\rules\Core\ConditionManager->createInstance('request_path', Array) (Line: 81)
Drupal\Core\Plugin\DefaultLazyPluginCollection->initializePlugin('request_path') (Line: 80)
Drupal\Component\Plugin\LazyPluginCollection->get('request_path') (Line: 26)
Drupal\Core\Condition\ConditionPluginCollection->get('request_path') (Line: 149)
Drupal\Component\Plugin\LazyPluginCollection->getIterator() (Line: 88)
Drupal\block\BlockAccessControlHandler->checkAccess(Object, 'view', Object) (Line: 109)
Drupal\Core\Entity\EntityAccessControlHandler->access(Object, 'view', Object, 1) (Line: 329)
Drupal\Core\Entity\EntityBase->access('view', NULL, 1) (Line: 63)
Drupal\block\BlockRepository->getVisibleBlocksPerRegion(Array) (Line: 138)
Drupal\block\Plugin\DisplayVariant\BlockPageVariant->build() (Line: 270)
Drupal\Core\Render\MainContent\HtmlRenderer->prepare(Array, Object, Object) (Line: 128)
Drupal\Core\Render\MainContent\HtmlRenderer->renderResponse(Array, Object, Object) (Line: 90)
Drupal\Core\EventSubscriber\MainContentViewSubscriber->onViewRenderArray(Object, 'kernel.view', Object)
call_user_func(Array, Object, 'kernel.view', Object) (Line: 111)
Drupal\Component\EventDispatcher\ContainerAwareEventDispatcher->dispatch(Object, 'kernel.view') (Line: 186)
Symfony\Component\HttpKernel\HttpKernel->handleRaw(Object, 1) (Line: 76)
Symfony\Component\HttpKernel\HttpKernel->handle(Object, 1, 1) (Line: 53)
Drupal\Core\StackMiddleware\Session->handle(Object, 1, 1) (Line: 48)
Drupal\Core\StackMiddleware\KernelPreHandle->handle(Object, 1, 1) (Line: 28)
Drupal\Core\StackMiddleware\ContentLength->handle(Object, 1, 1) (Line: 32)
Drupal\big_pipe\StackMiddleware\ContentLength->handle(Object, 1, 1) (Line: 106)
Drupal\page_cache\StackMiddleware\PageCache->pass(Object, 1, 1) (Line: 85)
Drupal\page_cache\StackMiddleware\PageCache->handle(Object, 1, 1) (Line: 57)
Drupal\advban\AdvbanMiddleware->handle(Object, 1, 1) (Line: 50)
Drupal\ban\BanMiddleware->handle(Object, 1, 1) (Line: 48)
Drupal\Core\StackMiddleware\ReverseProxyMiddleware->handle(Object, 1, 1) (Line: 51)
Drupal\Core\StackMiddleware\NegotiationMiddleware->handle(Object, 1, 1) (Line: 36)
Drupal\Core\StackMiddleware\AjaxPageState->handle(Object, 1, 1) (Line: 51)
Drupal\Core\StackMiddleware\StackedHttpKernel->handle(Object, 1, 1) (Line: 741)
Drupal\Core\DrupalKernel->handle(Object) (Line: 19)

So still no new release available?

@cilefen, I read the whole issue #3359497 and it seems that this is a similar problem.
As I understand, this error is triggered in various modules. I think that in my case it is ADV_Ban but i'm not sure because there is no reference to any library whatsoever hence my question here.

I tried to apply patch 3359497-13.patch and it seems to be working. I'll keep monitoring it.

However, as far as I understand this patch is only a work around and not a definitive solution to why the error is popping up.
So It should be on the module developers worklist to correct their modules or not?

This happens only when logged in as administrator

bart lambert → created an issue.

I'm having the same issue.
Applied patch issue_3414301.patch but i'm now getting following error:

Warning: Undefined array key "field_url_van_de_video" in Drupal\gdpr_fields\Form\GdprFieldSettingsForm::buildFormFields() (line 263 of modules/contrib/gdpr/modules/gdpr_fields/src/Form/GdprFieldSettingsForm.php).

So I think somewhere there is still something missing....

Any Idea's how To fix this?

It is indeed similar but what i'm missing is the possibility for a colorbox with bigger pictures that can popup when you click in on the image field.

In addition to the start of this issue I can add following info.

When the errors were present, maps were not shown. I had a marker but no map, only a grey surface.

I was able to restore this issue by changing the settings to google maps and than back to OSM Mapnik.
By re-saving the contenttype, the errors were gone and the maps were displayed as before!

I did not commit the requested patch.

bart lambert → created an issue.

So still no new release available?

Now that the module Image Effects had an upgrade, the file_mdm ^3 was upgraded automatically.
Upgrade of imagemagick is now succesfull.
So I think this may be closed

Same here,

I'm also using the module "image_effects" and there mdm ^2.5 is required so update can not be performed because of the restriction of MDM.

2 possible solutions:

image effects upgrades its use of mdm to 3.x

or

imagemagick makes its module backwards compatible to mdm ^2.X

thank you! updated to rc3 and error is gone, mails are resend without problem!!!

I'm praying for a quick new beta version with above patch included so I can install it using Composer on D10.

It only happens on this form. The others are doing just fine.

That's the message I get when trying to resend the confirmation mail.

I made a form to subscribe for a dinnerparty.
During the subcription they have to enter name, email, number of persons and then their choice for entree/main course and dessert.
At the end the see a resume, pimped up with some twig for error detection (comparison of number of people vs total entree/main course and dessert.

At the end they have to check a GDPR box and a math-captcha and then they send the form to the site.

On receiving a confirmed entry, they get a confirmation mail with a summary of there demands and a twig calculates the price they have to pay.

On constructing the form, there has been a lot of 'trail and error' and also deleting and adding elements, division into pages ....

You can have a look here, and make a trail run if you like, I know which persons are allowed in the group some false entries can be deleted afterwards.
https://lsvo.be/Inschrijvingen/viering-jong-gepensioneerden-2022-2024 (I hope you readers don't misuse the link to much ;-) )

Untill here everything works fine but when I want to resend the mail (because someone has delete the original one) I get this error.

2 screenshots added: 1 error, 1 logbook extract

bart lambert → created an issue.

OK, I figured this one out myself!

On some of my sites i'm using the project Drupal Mega Menu ( https://www.drupal.org/project/we_megamenu → ).
To avoid double menu's I must activate tis menu and deactivate the standard menu in the Block regions.

I just removed the standard menu and then the error occurs.
Putting the standard block menu back but disabling it so it is not visible removed the error.

So in fact it is a problem of interaction between AT Tool and Drupal Mega Menu.

On D9 however this problem did not occur!

OK, I figured this one out myself!

On some of my sites i'm using the project Drupal Mega Menu ( https://www.drupal.org/project/we_megamenu → ).
To avoid double menu's I must activate tis menu and deactivate the standard menu in the Block regions.

I just removed the standard menu and then the error occurs.
Putting the standard block menu back but disabling it so it is not visible removed the error.

So in fact it is a problem of interaction between AT Tool and Drupal Mega Menu.

On D9 however this problem did not occur!

In my newly made AT Theme I turned on all extensions in the settings of the Theme.

I think the problem arises with the extension "responsive menu"
If I open this one, I'm not able to change the menu (see screenshot). I Only have a drop-down arrow but the list is empty or does not exist.

This happen son more then one of my recently upgraded D10 sites. On those sites, I had to rebuild the theme because I coould not access the settings at all.

One side however works fine. see The second picture I added of how ik looks like on the other site without an error

So somehow, somewhere something has gone wrong.

I would be very gratefull if somebody can offer me a solution.

After correcting the color_submit.php file according MR4! following error is thrown when I want to change te colors:

ArgumentCountError: Too few arguments to function Drupal\Core\Asset\CssOptimizer::__construct(), 0 passed in /data/sites/web/modelspoorhobbybe/subsites/empa2019.modelspoorhobby.be/themes/contrib/adaptivetheme/at_core/forms/color/color_submit.php on line 132 and exactly 1 expected in Drupal\Core\Asset\CssOptimizer->__construct() (line 34 of core/lib/Drupal/Core/Asset/CssOptimizer.php).

bart lambert → created an issue.

bart lambert → created an issue.

Hoi Tim, you saved my day! Browser Cache was not cleared. now everything is fine thanks for the help

bart lambert → created an issue.

Added to pictures to clarify:

D9 is working fine
D10 is only 1 dropdown list

@tim-diels: yup applied patches without result

Bumping into the same issue.

I have a field where I need to choose a taxonomy term.
My taxonomylist has main categories , categories en sub categories.

EXAMPLE/
main cat. 1
cat 1.1
sub cat 1.1.1
sub cat 1.1.2
cat 1.2
sub cat 1.2.1
sub cat 1.2.2

In D9 everything worked fine: I had to choose a Main category, then a new dropdown window appeared to choose the next level and so on until I reach the last one.

I use "force deepest level" as option

After upgrading to D10 I just get a dropdownlist on the form of my content

hope this will be looked at and fixed very soon

bart lambert → created an issue.

Why won't this be fixed?
drupal_get_path() is removed and can't be called upon in D10.It is still present in the color_submit.php file which is part of AdaptiveTheme.
So as far as I understand it should at least be corrected here before we can carry on.

There is still an error in the patch from #13!

in the line to be added, your " ' " is in the wrong position!

It reads:
+ $info['core_version_requirement'] = '^8 || ^9' || ^10;
while it should read:
+ $info['core_version_requirement'] = '^8 || ^9 || ^10';

then it works....

worked for me aswell!

@drupal-ramesh

I think this is because you are logged in as administrator (supe-user). Try a other non-admin account and you will see it is ok.
(I think?)

@bill_redman : I applied all changes under "Merge request4!"

Ok, This trick #7 worked!

Changing jquery_ui_accordion in my composer.json file from '^1.1' to '^2.0' and then composer update fixed the update.

But it shouldn't be that way imho. Every update should work out of the box. Not all amateur-webmasters are so handy in to solve these kind of problems.

OK Thanks, as it is solved in 6.2 i'm happy. Meanwhile i'll wait for the stable version!!! ;-)

bart lambert → created an issue.

Same here!

same here like #4

@bonchak

In D8 the "Stable" module was incorporated in the core. As far as I understand is At-tools using stable to work.
In D9/D10 stable is deprecated/remove so somebody revived it for those users who need it to keep using their themes in de newer Drupal Core versions.

more info is found here:

https://www.drupal.org/docs/contributed-themes/stable →
https://www.drupal.org/node/3309392 →

@bonchak
Stable module is indeed necessary to have at_tool working but when you create a new theme using the them generator you still have to change the core requirements manually and that can not be the goal.

I hope Matt Bloomfield (@mattbloomfield) will surface one of these days to solve the issues for D10 compatibility.

Ok, thanks, I hope they release a small update very soon

@goodboy
Applied test version and errors on "drush updb"
Also checked with "upgrade status"-module and no problems were found there either!
Thanks for your efforts!

Tried the dev version today and update failed, site crashes.

Running "drush updb" throws following error:

The command "/data/sites/web/modelspoorhobbybe/www/vendor/bin/drush updated
b:status --no-entity-updates --strict=0 --uri=default --root=/data/sites/we
b/modelspoorhobbybe/www" failed.

Exit Code: 255(Unknown error)

Working directory:

Output:
================

Error Output:
================
[success] No database updates required.
PHP Fatal error: Declaration of Drupal\advban\AdvbanMiddleware::handle(Sym
fony\Component\HttpFoundation\Request $request, int $type = self::MASTER_RE
QUEST, bool $catch = true): Symfony\Component\HttpFoundation\Response must
be compatible with Symfony\Component\HttpKernel\HttpKernelInterface::handle
(Symfony\Component\HttpFoundation\Request $request, $type = self::MASTER_RE
QUEST, $catch = true) in /data/sites/web/modelspoorhobbybe/www/modules/cont
rib/advban/src/AdvbanMiddleware.php on line 44

PHP Fatal error: Declaration of Drupal\advban\AdvbanMiddleware::handle(Symfony\Component\HttpFoundation\Request $request, int $type = self::MASTER_REQUEST, bool $catch = true): Symfony\Component\HttpFoundation\Response must be compatible with Symfony\Component\HttpKernel\HttpKernelInterface::handle(Symfony\Component\HttpFoundation\Request $request, $type = self::MASTER_REQUEST, $catch = true) in /data/sites/web/modelspoorhobbybe/www/modules/contrib/advban/src/AdvbanMiddleware.php on line 44

Hi,

Thanks for pointing it out to me! I did not.
Applied the patches and now it all works fine!

Thanks!!!

Maybe somebody could add an new version update.

Seems like you also have an other version of the /src/Form/LogintobogganRegister.php file (see attached screenshot of my original (not patched file)

Hi,

Applied the patch and now the "Upgrade Status"-module gives green light for the module but still finds 2 problems (see attached file)

bart lambert → created an issue.

Hi,

I just update flexslider to the d10 compatible dev version. Unfortunately the Upgrade Status module refuses putting is d10 Compatible. 4 more issues are found . see attached file.

Apparently there is still a little work left in order to get ik compatible

Hi Wim,

Clearing the caches did not really solve the problem but you've put me on the right track!

On the bottom of the page there are settings to "bandwidth-optimailisation". "Javascript bestanden samenvoegen" was on!

I switched it off and on again "like the IT Crowed" and I got ik all Back!

thanks for the guidance!!!!

bart lambert → created an issue.

bart lambert → created an issue.

hi,

see attached screenshot.

I always use Chrome. I maintain different sites, all with the same provider (combell). This is th eonly side in which i have this problem

bart

bart lambert → created an issue.

Thanks!