jsimonis → created an issue.
jsimonis → created an issue.
jsimonis → created an issue. See original summary → .
jsimonis → created an issue.
Yeah, it was crazy because I have a ton of them on my personal site about gardening.
I won't be working on the site again, so I won't need to revisit that one. But I may get the pro one at some point for my personal sites. It would be nice to have more control over the size.
There was no option for Juicebox unless I chose "Image with Dimensions." That's the only time it showed up.
I'm not working on the site anymore, so I'm just going to say this can be closed.
Okay, added a media field straight to the content type instead of via the paragraph. Re-added the photos. Set the format on the manage display page to be the slideshow. Still getting the same thing.
I uploaded new screenshots.
Here's the one I made the changes to: https://celestine10.nl-sandbox.xyz/node/77
Yea, it's a media (image) field right now with unlimited images. The formatter is definitely affecting them, as they change sizes depending on what I put as the options for the slideshow. It's just not using the slideshow.
I'll have to try it as a field in the content. But that won't work for some of these others where we need the paragraphs.
Yup, mine is a media field with several images in it.
I wonder if it has something to do with it being in a paragraph that is then added to a content type. I've never had issues with it like this before. Normally, the field formatter is super simple.
I'm using it as a field formatter ("Basic Field-Based Galleries (the Field Formatter" from the documentation page).
The paragraph field has it set on the "Manage Display" page (screenshot attached).
jsimonis → created an issue.
jsimonis → created an issue.
Thanks. Unfortunately, I can't post over on the Drupal one because I had a question flagged by the AI bot as not having enough info. That's a huge problem with moving everything over there - the bot causes a lot of issues. I don't have problems on any of the other Stack Exchange, only the Drupal one.
heikkiy:
For me, it happens when I am trying to create a set of vertical tabs. So, I create the "tabs" and then the "tab". I drag the tab up under the tabs, then add the content to the tab. Save. The content stays under the tabs item, but the tab has moved down to disabled.
jsimonis → created an issue.
I see this is apparently only in the dev version. Are there plans to update the recommended version soon?
I've tried every single class and id that shows for the menu and the area it's in, and I cannot find a single one that switches it to the responsive menu for anonymous users.
ertiepie:
Same. Thankfully, I do run a backup of our account before running updates, so I completely reverted back.
Yeah, I'm stuck not being able to run my database updates for module updates because of this. I've tried removing VBO, but that doesn't seem to fix the problem. Anyone happen to know?
It seems to be using the same ids/classes whether I am logged in or not. I've added every one I can think of to use and none seem to be affecting it for anonymous users.
Here's an example page: https://jenni.nu-look.net/web/biography
jsimonis → created an issue.
Had a similar issue pop up: Upgrade manager told me that this permission was assigned to a role in a text format called php_code. There was no such text format. I created one, assigning it to the role the Upgrade Status page said had it, and saved that. Refreshed the Upgrade Status page and now there's no error.
This site was never D7. It's a fresh D9 site from scratch. Nothing brought over from the D7 site. We're working on upgrading to D10.
Any update on this? I've tried the patch. It said it patched correctly, but I am not seeing any change on my page. As you can see, I get one item for the image, another for the body.
I used Option #1. Even ran the command twice. No library was added. I manually added it. Cleared my cache and everything. Still breaks ckeditor. I used the link from #9 and I'm using the 3.0.0-beta1 version of the module.
Anyone had any luck with this? I'm still getting:
Problem 1
- drupal/fontawesome_iconpicker[3.0.0-alpha1, ..., 3.0.0-alpha2] require composer/installers ^1.9 -> found composer/installers[v1.9.0, v1.10.0, v1.11.0, v1.12.0] but it conflicts with your root composer.json require (^2.2).
- Root composer.json requires drupal/fontawesome_iconpicker ^3 -> satisfiable by drupal/fontawesome_iconpicker[3.0.0-alpha1, 3.0.0-alpha2].
Wouldn't I lose anything related to those modules if I do that? If that's the case, I would have to rebuild enough of the site that it would make more sense to just start from scratch.
Yeah, it's all the same ones that I ran the command on to use the D10 version instead. I'll try this out in a bit. Running down issues on the live site after a PHP update... fun, fun.
Well, I went through and ran the command for every one of them based on the version for 10. I did it both with and without the single quote on them. Here's what I ran:
composer require 'drupal/block_field:^1.0@RC' --no-update
composer require 'drupal/classy_paragraphs:^1.0@RC' --no-update
composer require 'drupal/crop:^2.3' --no-update
composer require 'drupal/dropzonejs:^2.10' --no-update
composer require 'drupal/easy_breadcrumb:^2.0' --no-update
composer require 'drupal/editor_advanced_link:^2.2' --no-update
composer require 'drupal/entity_clone:^2.0@beta' --no-update
composer require 'drupal/extlink:^1.7' --no-update
composer require 'drupal/field_group:^3.4' --no-update
composer require 'drupal/fontawesome:^2.26' --no-update
composer require 'drupal/google_analytics_reports:^3.1' --no-update
composer require 'drupal/linkit:^6.1' --no-update
composer require 'drupal/media_library_form_element:^2.0' --no-update
composer require 'drupal/menu_block:^1.10' --no-update
composer require 'drupal/menu_link_attributes:^1.3' --no-update
composer require 'drupal/metatag:^2.0' --no-update
composer require 'drupal/node_export:^1.1' --no-update
composer require 'drupal/recaptcha:^3.2' --no-update
composer require 'drupal/scheduler:^2.0' --no-update
composer require 'drupal/smart_trim:^2.1' --no-update
composer require 'drupal/superfish:^1.7' --no-update
composer require 'drupal/taxonomy_import:^2.0' --no-update
composer require 'drupal/taxonomy_manager:^2.0' --no-update
composer require 'drupal/twig_tweak:^3.3' --no-update
composer require 'drupal/typed_data:^1.0@beta' --no-update
composer require 'drupal/views_bootstrap:^4.4' --no-update
composer require 'drupal/views_data_export:^1.4' --no-update
composer require 'drupal/webform:^6.2' --no-updateWith each command, it said json was updated. But when I run the check for the upgrade, it shows the same issue as before.
Here's just a snippet since it's just the same as before:
[userid@server public_html]$ composer prohibits drupal/core 10.2.3
drupal/block_field 1.0.0-rc2 requires drupal/core (^8.7.7 || ^9)
drupal/classy_paragraphs 1.0.0-rc1 requires drupal/core (^8 || ^9)
drupal/core-recommended 9.5.11 requires drupal/core (9.5.11)
drupal/crop 2.2.0 requires drupal/core (^8.8 || ^9)
drupal/dropzonejs_eb_widget 2.6.0 requires drupal/core (^8.8 || ^9)Here's the current json file:
{
"name": "drupal/recommended-project",
"description": "Project template for Drupal 9 projects with a relocated document root",
"type": "project",
"license": "GPL-2.0-or-later",
"homepage": "https://www.drupal.org/project/drupal",
"support": {
"docs": "https://www.drupal.org/docs/user_guide/en/index.html",
"chat": "https://www.drupal.org/node/314178"
},
"repositories": [
{
"type": "composer",
"url": "https://packages.drupal.org/8"
}
],
"require": {
"composer/installers": "^2.2",
"drupal/address": "^2.0",
"drupal/addtoany": "^2.0",
"drupal/admin_toolbar": "^3.4",
"drupal/anchor_link": "^3.0@alpha",
"drupal/asset_injector": "^2.19",
"drupal/better_exposed_filters": "^6.0",
"drupal/block_class": "^2.0",
"drupal/block_field": "^1.0@RC",
"drupal/bootstrap": "^3.25",
"drupal/bootstrap_paragraphs": "^2.0@beta",
"drupal/bootstrap_styles": "^1.1",
"drupal/captcha": "^2.0",
"drupal/charts": "^5.0",
"drupal/chosen": "^4.0",
"drupal/classy_paragraphs": "^1.0@RC",
"drupal/colorbox": "^2.0",
"drupal/content_access": "^2.0",
"drupal/context": "^4.1",
"drupal/core-composer-scaffold": "^10.2",
"drupal/core-project-message": "^10.2",
"drupal/core-recommended": "^10.2",
"drupal/crop": "^2.3",
"drupal/csv_serialization": "^2.1",
"drupal/ctools": "^4.0",
"drupal/devel": "^5.0",
"drupal/draggableviews": "^2.0",
"drupal/dropzonejs": "^2.10",
"drupal/ds": "^3.13",
"drupal/dynamic_entity_reference": "^1.16",
"drupal/easy_breadcrumb": "^2.0",
"drupal/editor_advanced_link": "^2.2",
"drupal/embed": "^1.7",
"drupal/entity": "^1.4",
"drupal/entity_browser": "^2.10",
"drupal/entity_clone": "^2.0@beta",
"drupal/entity_embed": "^1.2",
"drupal/entity_print": "^2.6",
"drupal/entity_reference_revisions": "^1.10",
"drupal/entity_type_clone": "^1.7",
"drupal/eu_cookie_compliance": "^1.24",
"drupal/extlink": "^1.7",
"drupal/fakeobjects": "^1.2",
"drupal/faqfield": "^7.1",
"drupal/feeds": "^3.0@beta",
"drupal/field_group": "^3.4",
"drupal/field_permissions": "^1.1",
"drupal/file_browser": "^1.3",
"drupal/file_download_link": "^2.0",
"drupal/fontawesome": "^2.26",
"drupal/google_analytics": "^3.1",
"drupal/google_analytics_reports": "^3.1",
"drupal/google_analytics_reports_api": "^3.1",
"drupal/image_widget_crop": "^2.3",
"drupal/imce": "^3.0",
"drupal/inline_entity_form": "^1.0@RC",
"drupal/jquery_ui": "^1.6",
"drupal/jquery_ui_accordion": "^2.0",
"drupal/jquery_ui_datepicker": "^1.3",
"drupal/jquery_ui_slider": "^2.0",
"drupal/jquery_ui_touch_punch": "^1.0",
"drupal/layout_builder_iframe_modal": "^1.3",
"drupal/layout_paragraphs": "^2.0",
"drupal/link_target": "^1.4",
"drupal/linkit": "^6.1",
"drupal/login_destination": "^2.0@beta",
"drupal/masquerade": "^2.0@RC",
"drupal/maxlength": "^2.0",
"drupal/media_library_form_element": "^2.0",
"drupal/media_library_importer": "^2.0@beta",
"drupal/menu_block": "^1.10",
"drupal/menu_link_attributes": "^1.3",
"drupal/metatag": "^2.0",
"drupal/migrate_source_csv": "^3.6",
"drupal/module_filter": "^4.1",
"drupal/node_export": "^1.1",
"drupal/page_manager": "^4.0@beta",
"drupal/paragraphs": "^1.16",
"drupal/paragraphs_edit": "^3.0",
"drupal/paragraphs_features": "^2.0@beta",
"drupal/paragraphs_sets": "^3.0",
"drupal/pathauto": "^1.12",
"drupal/profile": "^1.7",
"drupal/quick_node_clone": "^1.15",
"drupal/recaptcha": "^3.2",
"drupal/redirect": "^1.9",
"drupal/rules": "^3.0@alpha",
"drupal/scheduler": "^2.0",
"drupal/search_api": "^1.23",
"drupal/simple_sitemap": "^4.1",
"drupal/smart_trim": "^2.1",
"drupal/smtp": "^1.0",
"drupal/super_login": "^2.1",
"drupal/superfish": "^1.7",
"drupal/svg_image": "^3.0",
"drupal/tablefield": "^2.3",
"drupal/taxonomy_import": "^2.0",
"drupal/taxonomy_manager": "^2.0",
"drupal/text_field_formatter": "^2.0",
"drupal/token": "^1.13",
"drupal/twig_tweak": "^3.3",
"drupal/typed_data": "^1.0@beta",
"drupal/upgrade_status": "*",
"drupal/views_aggregator": "^2.0",
"drupal/views_bootstrap": "^4.4",
"drupal/views_bulk_edit": "^2.6",
"drupal/views_bulk_operations": "^4.2",
"drupal/views_conditional": "^1.9",
"drupal/views_data_export": "^1.4",
"drupal/views_field_view": "^1.0@beta",
"drupal/views_infinite_scroll": "^2.0",
"drupal/views_load_more": "^2.0@alpha",
"drupal/viewsreference": "^2.0@beta",
"drupal/webform": "^6.2",
"drush/drush": "^12"
},
"conflict": {
"drupal/drupal": "*"
},
"minimum-stability": "stable",
"prefer-stable": true,
"config": {
"sort-packages": true,
"allow-plugins": {
"composer/installers": true,
"drupal/core-composer-scaffold": true,
"drupal/core-project-message": true,
"dealerdirect/phpcodesniffer-composer-installer": true
}
},
"extra": {
"drupal-scaffold": {
"locations": {
"web-root": "web/"
}
},
"installer-paths": {
"web/core": [
"type:drupal-core"
],
"web/libraries/{$name}": [
"type:drupal-library"
],
"web/modules/contrib/{$name}": [
"type:drupal-module"
],
"web/profiles/contrib/{$name}": [
"type:drupal-profile"
],
"web/themes/contrib/{$name}": [
"type:drupal-theme"
],
"drush/Commands/contrib/{$name}": [
"type:drupal-drush"
],
"web/modules/custom/{$name}": [
"type:drupal-custom-module"
],
"web/profiles/custom/{$name}": [
"type:drupal-custom-profile"
],
"web/themes/custom/{$name}": [
"type:drupal-custom-theme"
]
},
"drupal-core-project-message": {
"include-keys": [
"homepage",
"support"
],
"post-create-project-cmd-message": [
"<bg=blue;fg=white> </>",
"<bg=blue;fg=white> Congratulations, you’ve installed the Drupal codebase </>",
"<bg=blue;fg=white> from the drupal/recommended-project template! </>",
"<bg=blue;fg=white> </>",
"",
"<bg=yellow;fg=black>Next steps</>:",
" * Install the site: https://www.drupal.org/docs/8/install",
" * Read the user guide: https://www.drupal.org/docs/user_guide/en/index.html",
" * Get support: https://www.drupal.org/support",
" * Get involved with the Drupal community:",
" https://www.drupal.org/getting-involved",
" * Remove the plugin that prints this message:",
" composer remove drupal/core-project-message"
]
}
},
"require-dev": {
"drupal/core-dev": "^10"
}
}
Thanks for all your help!
Yeah, that's the funny thing - Upgrade Status had me at 100% ready. Clearly it was wrong.
Looks like "require" and the "--no-update" part are added to what is listed on the module's page. Plus the single quote mark is missing. I'll run through them all tonight.
Thanks for all the help. It's been a pain trying to get this all done while also dealing with a concussion, so it's slow going.
Clearly, something went wrong with the Upgrade Manager.
Now, I understand what you were meaning about searching. I'll go through and get all those upgraded. I've been admin for Drupal sites since 2004, but all this composer stuff I'm still learning.
Do I just grab the code for D10 off the module pages and add the "--no-update" to the end of the line?
drupal/block_field 1.0.0-rc2 requires drupal/core (^8.7.7 || ^9)
drupal/classy_paragraphs 1.0.0-rc1 requires drupal/core (^8 || ^9)
drupal/core-recommended 9.5.11 requires drupal/core (9.5.11)
drupal/crop 2.2.0 requires drupal/core (^8.8 || ^9)
drupal/dropzonejs_eb_widget 2.6.0 requires drupal/core (^8.8 || ^9)
drupal/easy_breadcrumb 2.0.3 requires drupal/core (^8 || ^9)
drupal/editor_advanced_link 2.0.0 requires drupal/core (^9.2)
drupal/entity_clone 1.0.0-beta6 requires drupal/core (^8 || ^9)
drupal/extlink 1.6.0 requires drupal/core (^8 || ^9)
drupal/field_group 3.2.0 requires drupal/core (^8.8 || ^9)
drupal/fontawesome 2.23.0 requires drupal/core (^8 || ^9)
drupal/google_analytics_reports_api 3.0.0-rc3 requires drupal/core (^8 || ^9)
drupal/linkit 6.0.0-beta3 requires drupal/core (^8.7.7 || ^9)
drupal/media_library_form_element 2.0.3 requires drupal/core (^8 || ^9)
drupal/media_library_theme_reset 1.1.0 requires drupal/core (^8 || ^9)
drupal/menu_block 1.8.0 requires drupal/core (^8 || ^9)
drupal/menu_link_attributes 1.2.0 requires drupal/core (^8 || ^9)
drupal/metatag 1.21.0 requires drupal/core (^9)
drupal/node_export 1.0.0-alpha1 requires drupal/core (^8 || ^9)
drupal/recaptcha 3.0.0 requires drupal/core (^8 || ^9)
drupal/scheduler 1.4.0 requires drupal/core (^8 || ^9)
drupal/smart_trim 1.3.0 requires drupal/core (^8 || ^9)
drupal/superfish 1.4.0 requires drupal/core (^8 || ^9)
drupal/taxonomy_import 2.0.5 requires drupal/core (^8 || ^9)
drupal/taxonomy_manager 2.0.7 requires drupal/core (^8.8 || ^9)
drupal/twig_tweak 3.1.3 requires drupal/core (^9.0)
drupal/typed_data 1.0.0-beta1 requires drupal/core (^8.8.2 || ^9)
drupal/views_bootstrap 4.3.0 requires drupal/core (^8 || ^9)
drupal/views_data_export 1.1.0 requires drupal/core (^8.8 || ^9)
drupal/webform 6.1.3 requires drupal/core (^8.8 || ^9)
drupal/core 10.2.3 requires symfony/console (^6.4)
drupal/recommended-project - does not require symfony/console (but v4.4.49 is installed)
drupal/core 10.2.3 requires symfony/dependency-injection (^6.4)
drupal/recommended-project - does not require symfony/dependency-injection (but v4.4.49 is installed)
drupal/core 10.2.3 requires symfony/event-dispatcher (^6.4)
drupal/recommended-project - does not require symfony/event-dispatcher (but v4.4.44 is installed)
drupal/core 10.2.3 requires symfony/filesystem (^6.4)
drupal/recommended-project - does not require symfony/filesystem (but v4.4.42 is installed)
drupal/core 10.2.3 requires symfony/finder (^6.4)
drupal/recommended-project - does not require symfony/finder (but v4.4.44 is installed)
drupal/core 10.2.3 requires symfony/http-foundation (^6.4)
drupal/recommended-project - does not require symfony/http-foundation (but v4.4.49 is installed)
drupal/core 10.2.3 requires symfony/http-kernel (^6.4)
drupal/recommended-project - does not require symfony/http-kernel (but v4.4.50 is installed)
drupal/core 10.2.3 requires symfony/mime (^6.4)
drupal/recommended-project - does not require symfony/mime (but v5.4.13 is installed)
drupal/core 10.2.3 requires symfony/routing (^6.4)
drupal/recommended-project - does not require symfony/routing (but v4.4.44 is installed)
drupal/core 10.2.3 requires symfony/serializer (^6.4)
drupal/recommended-project - does not require symfony/serializer (but v4.4.47 is installed)
drupal/core 10.2.3 requires symfony/validator (^6.4)
drupal/recommended-project - does not require symfony/validator (but v4.4.48 is installed)
drupal/core 10.2.3 requires symfony/process (^6.4)
drupal/recommended-project - does not require symfony/process (but v4.4.44 is installed)
drupal/core 10.2.3 requires symfony/yaml (^6.4)
drupal/recommended-project - does not require symfony/yaml (but v4.4.45 is installed)
drupal/core 10.2.3 requires twig/twig (^3.5.0)
drupal/recommended-project - does not require twig/twig (but v2.15.5 is installed)
drupal/core 10.2.3 requires doctrine/annotations (^1.14)
drupal/recommended-project - does not require doctrine/annotations (but 1.13.3 is installed)
drupal/core 10.2.3 requires guzzlehttp/guzzle (^7.5)
drupal/recommended-project - does not require guzzlehttp/guzzle (but 6.5.8 is installed)
drupal/core 10.2.3 requires guzzlehttp/psr7 (^2.4.5)
drupal/recommended-project - does not require guzzlehttp/psr7 (but 1.9.1 is installed)
drupal/core 10.2.3 requires asm89/stack-cors (^2.1)
drupal/recommended-project - does not require asm89/stack-cors (but 1.3.0 is installed)
drupal/core 10.2.3 requires psr/log (^3.0)
drupal/recommended-project - does not require psr/log (but 1.1.4 is installed)
Now this is what I have:
Problem 1
- drupal/better_exposed_filters[6.0.1, ..., 6.0.2] require drupal/jquery_ui_slider ^1.1 -> found drupal/jquery_ui_slider[1.1.0] but it conflicts with your root composer.json require (^2.0).
- drupal/better_exposed_filters 6.0.3 requires drupal/jquery_ui_datepicker ^2.0 -> found drupal/jquery_ui_datepicker[2.0.0] but it conflicts with your root composer.json require (^1.3).
- Root composer.json requires drupal/better_exposed_filters ^6.0 -> satisfiable by drupal/better_exposed_filters[6.0.1, 6.0.2, 6.0.3].
Gotcha! There must've been something up with it since it was at 100% and told me I was ready to upgrade. It has you remove it before you start the upgrade process, so I can't look now. I'm gathering this new bug popped up recently. I did it all back in early to mid December.
Wonder why the upgrader didn't catch those. I'll see about removing those and trying again. Thanks so much!
Thanks for answering. My question gets deleted over at StackExchange, brought back up, deleted again... this has been going on for 2 months and I'm about to pull my hair out.
It did indeed still have issues. This is what I got:
Problem 1
- zendframework/zend-feed[2.11.0, ..., 2.12.0] require php ^5.6 || ^7.0 -> your php version (8.1.27) does not satisfy that requirement.
- laminas/laminas-feed[2.12.0, ..., 2.12.3] require php ^5.6 || ^7.0 -> your php version (8.1.27) does not satisfy that requirement.
- symfony-cmf/routing[1.4.0, ..., 1.4.1] require php ^5.3.9|^7.0 -> your php version (8.1.27) does not satisfy that requirement.
- drupal/core[8.9.11, ..., 8.9.20] require php ^7.0.8 -> your php version (8.1.27) does not satisfy that requirement.
- drupal/core[9.0.10, ..., 9.0.14] require php ^7.3 -> your php version (8.1.27) does not satisfy that requirement.
- laminas/laminas-feed[2.13.0, ..., 2.14.1] require php ^7.3 || ~8.0.0 -> your php version (8.1.27) does not satisfy that requirement.
- Root composer.json requires drupal/viewsreference ^1.8 -> satisfiable by drupal/viewsreference[1.8.0].
- drupal/core-recommended 10.2.2 requires drupal/core 10.2.2 -> satisfiable by drupal/core[10.2.2].
- Conclusion: don't install drupal/core 10.2.2 (conflict analysis result)
- drupal/core-recommended 10.2.3 requires drupal/core 10.2.3 -> satisfiable by drupal/core[10.2.3].
- Conclusion: don't install drupal/core 10.2.3 (conflict analysis result)
- drupal/core-recommended 10.2.4 requires drupal/core 10.2.4 -> satisfiable by drupal/core[10.2.4].
- Conclusion: don't install drupal/core 10.2.4 (conflict analysis result)
- drupal/core[8.6.0, ..., 8.9.10] require symfony-cmf/routing ^1.4 -> satisfiable by symfony-cmf/routing[1.4.0, 1.4.1].
- drupal/core[8.8.0, ..., 8.8.12] require zendframework/zend-feed ^2.12 -> satisfiable by laminas/laminas-feed[2.12.0, ..., 2.19.0], zendframework/zend-feed[2.12.0].
- drupal/core-recommended 10.2.1 requires drupal/core 10.2.1 -> satisfiable by drupal/core[10.2.1].
- Conclusion: don't install drupal/core 10.2.1 (conflict analysis result)
- drupal/viewsreference 1.8.0 requires drupal/core ^8.6|^9.0 -> satisfiable by drupal/core[8.6.0, ..., 8.9.20, 9.0.0, ..., 9.5.11].
- You can only install one version of a package, so only one of these can be installed: drupal/core[8.0.0, ..., 8.9.20, 9.0.0, ..., 9.5.11,10.0.0, ..., 10.2.4].
- You can only install one version of a package, so only one of these can be installed: drupal/core[8.7.0, ..., 8.9.20, 9.0.0, ..., 9.5.11,10.0.0, ..., 10.2.4].
- drupal/core-recommended 10.2.0 requires drupal/core 10.2.0 -> satisfiable by drupal/core[10.2.0].
- Root composer.json requires drupal/core-recommended ^10.2 -> satisfiable by drupal/core-recommended[10.2.0, ..., 10.2.4].
Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
[tgcid9@server public_html]$
Never mind, I figured it out. Somehow my modules page got switched to showing only enabled modules.
jsimonis → created an issue.
I just finally got a chance to loop around to this. I don't have the ability to connect to the site in a way that allows me to disable via drush. I only have FTP (can't use SSH when I'm logged in that way) and Cpanel. And Terminal isn't turned on by their hosting company.
I'll try it again, but I have disabled it and reenabled it that way previously and nothing changed.
jsimonis → created an issue.
Got this:
Could not find a matching version of package npm-asset/fonticonpicker--fonticonpicker. Check the package spelling, your version constraint and that the package is available in a stability which matches your minimum-stability (dev).
Has anyone gotten this working? I tried the composer code listed above, but got:
Could not find a matching version of package npm-asset/fonticonpicker--fonticonpicker. Check the package spelling, your version constraint and that the package is available in a stability which matches your minimum-stability (stable).
They ended up inputting every option manually. They had the feature in the previous version of the site, which was D7.
We're having the same issue. Other rates are coming through, but media mail is $0.