That was it, thank you!
Just installed dev and cleared cache and still not getting the selectors set.
<!-- BEGIN OUTPUT from 'modules/contrib/office_hours/templates/office-hours-status.html.twig' -->
<div>
Currently Open!
</div>
<!-- END OUTPUT from 'modules/contrib/office_hours/templates/office-hours-status.html.twig' -->This is what I get even after I make the css edit. I'm not a full time developer, so I may be wrong, but how could it be CSS if the selector is not getting added?
calebwalker → created an issue.
It was on my MAMP. Nothing live. It’s all also in GitHub. And , I could have reverted back to the GitHub version but didn’t even think of that. What a dummy.
Thank you. Got it updated. Had a funny issue on permissions on default.services.yml. Once I got the issue I ran the update with sudo, then went back and changed owners again. Not sure whats up with that file. Also had to install ckeditor and rdf, then remove ckeditor later. Alls is good thanks again for the help.
1. Is this from a backup? I didn't back this file up. But I will after this fiasco of an upgrade. Or is there something I can do to revert the json file? I looked online for things to this effect, and I get self-update, update, etc. None of them work. I am on my mac and I have gotten permissions errors but I have reset permissions with chown -R on everything and plus I chmod -R on everything. It started with default.services.yml but permissions were good. I also tried to run these commands with sudo which are not recommended, but they still give errors.
2. Inside Admin, google maps is updated, but as you can see composer doesnt think so. I have tried to remove both of these modules in composer and they do not work either.
3. Drush is set to uninstall and if I just do a composer remove drush/drush, I get errors similar to all of them I have sent thus far.
4. Yeah, still cant get that becuase steps 1-3 are still broken.
5. yeah. not yet.
I do appreciate your help on this. Thank you.
I think something is messed up with Composer then.
I cannot remove either google map field or office hours. What does it mean when it says this package is "fixed" to 9.5.11?
% composer remove drupal/google_map_field
./composer.json has been updated
Running composer update drupal/google_map_field
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Root composer.json requires drupal/core-composer-scaffold ^10, found drupal/core-composer-scaffold[10.0.0, ..., 10.2.1] but the package is fixed to 9.5.11 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
Problem 2
- Root composer.json requires drupal/core-project-message ^10, found drupal/core-project-message[10.0.0, ..., 10.2.1] but the package is fixed to 9.5.11 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
Problem 3
- Root composer.json requires drupal/core-recommended ^10, found drupal/core-recommended[10.0.0, ..., 10.2.1] but the package is fixed to 9.5.11 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
Removal failed, reverting ./composer.json to its original content.
Removal failed, drupal/google_map_field is still present, it may be required by another package. See `composer why drupal/google_map_field`.
This is the version I have installed:
https://www.drupal.org/project/google_map_field/releases/2.0.1 →
I'm just doing this on my test area so I can make sure all this works. So I'll remove these but it doesnt seem to work.
I tried to remove Office Hours so I did in the admin page but nothing works still. I then did this:
% composer why drupal/office_hours
drupal/legacy-project dev-main requires drupal/office_hours (^1.7)
and I get this error. What? how are these depending on office_hours?
but drush wont remove.
Problem 1
- Root composer.json requires drupal/core-composer-scaffold ^10, found drupal/core-composer-scaffold[10.0.0, ..., 10.2.1] but the package is fixed to 9.5.11 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
Problem 2
- Root composer.json requires drupal/core-project-message ^10, found drupal/core-project-message[10.0.0, ..., 10.2.1] but the package is fixed to 9.5.11 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
Problem 3
- Root composer.json requires drupal/core-recommended ^10, found drupal/core-recommended[10.0.0, ..., 10.2.1] but the package is fixed to 9.5.11 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
% composer why drush/drush
drupal/core 9.5.11 conflicts drush/drush (<8.1.10)
Not sure what these mean. They dont seem to be tied to a module I've installed.
% composer prohibits drupal/core ^10
drupal/core-recommended 9.5.11 requires drupal/core (9.5.11)
drupal/google_map_field 1.14.0 requires drupal/core (^8 || ^9)
drupal/office_hours 1.7.0 requires drupal/core (^8 || ^9)
drupal/core 10.2.1 conflicts drush/drush (<12.4.3)
drupal/core 10.2.1 requires symfony/console (^6.4)
drupal/legacy-project dev-main does not require symfony/console (but v4.4.49 is installed)
drupal/core 10.2.1 requires symfony/dependency-injection (^6.4)
drupal/legacy-project dev-main does not require symfony/dependency-injection (but v4.4.49 is installed)
drupal/core 10.2.1 requires symfony/event-dispatcher (^6.4)
drupal/legacy-project dev-main does not require symfony/event-dispatcher (but v4.4.44 is installed)
drupal/core 10.2.1 requires symfony/http-foundation (^6.4)
drupal/legacy-project dev-main does not require symfony/http-foundation (but v4.4.49 is installed)
drupal/core 10.2.1 requires symfony/http-kernel (^6.4)
drupal/legacy-project dev-main does not require symfony/http-kernel (but v4.4.51 is installed)
drupal/core 10.2.1 requires symfony/mime (^6.4)
drupal/legacy-project dev-main does not require symfony/mime (but v5.4.13 is installed)
drupal/core 10.2.1 requires symfony/routing (^6.4)
drupal/legacy-project dev-main does not require symfony/routing (but v4.4.44 is installed)
drupal/core 10.2.1 requires symfony/serializer (^6.4)
drupal/legacy-project dev-main does not require symfony/serializer (but v4.4.47 is installed)
drupal/core 10.2.1 requires symfony/validator (^6.4)
drupal/legacy-project dev-main does not require symfony/validator (but v4.4.48 is installed)
drupal/core 10.2.1 requires symfony/process (^6.4)
drupal/legacy-project dev-main does not require symfony/process (but v4.4.44 is installed)
drupal/core 10.2.1 requires symfony/yaml (^6.4)
drupal/legacy-project dev-main does not require symfony/yaml (but v4.4.45 is installed)
drupal/core 10.2.1 requires twig/twig (^3.5.0)
drupal/legacy-project dev-main does not require twig/twig (but v2.15.6 is installed)
drupal/core 10.2.1 requires doctrine/annotations (^1.14)
drupal/legacy-project dev-main does not require doctrine/annotations (but 1.13.3 is installed)
drupal/core 10.2.1 requires guzzlehttp/guzzle (^7.5)
drupal/legacy-project dev-main does not require guzzlehttp/guzzle (but 6.5.8 is installed)
drupal/core 10.2.1 requires guzzlehttp/psr7 (^2.4.5)
drupal/legacy-project dev-main does not require guzzlehttp/psr7 (but 1.9.1 is installed)
drupal/core 10.2.1 requires asm89/stack-cors (^2.1)
drupal/legacy-project dev-main does not require asm89/stack-cors (but 1.3.0 is installed)
drupal/core 10.2.1 requires psr/log (^3.0)
drupal/legacy-project dev-main does not require psr/log (but 1.1.4 is installed)
Your requirements could not be resolved to an installable set of packages.
Problem 1
- drupal/core-recommended 10.0.0 requires drupal/core 10.0.0 -> found drupal/core[10.0.0] but these were not loaded, likely because it conflicts with another require.
- drupal/core-recommended 10.0.1 requires drupal/core 10.0.1 -> found drupal/core[10.0.1] but these were not loaded, likely because it conflicts with another require.
- drupal/core-recommended 10.0.2 requires drupal/core 10.0.2 -> found drupal/core[10.0.2] but these were not loaded, likely because it conflicts with another require.
- drupal/core-recommended 10.0.3 requires drupal/core 10.0.3 -> found drupal/core[10.0.3] but these were not loaded, likely because it conflicts with another require.
- drupal/core-recommended 10.0.4 requires drupal/core 10.0.4 -> found drupal/core[10.0.4] but these were not loaded, likely because it conflicts with another require.
- drupal/core-recommended 10.0.5 requires drupal/core 10.0.5 -> found drupal/core[10.0.5] but these were not loaded, likely because it conflicts with another require.
- drupal/core-recommended 10.0.6 requires drupal/core 10.0.6 -> found drupal/core[10.0.6] but these were not loaded, likely because it conflicts with another require.
- drupal/core-recommended 10.0.7 requires drupal/core 10.0.7 -> found drupal/core[10.0.7] but these were not loaded, likely because it conflicts with another require.
- drupal/core-recommended 10.0.8 requires drupal/core 10.0.8 -> found drupal/core[10.0.8] but these were not loaded, likely because it conflicts with another require.
- drupal/core-recommended 10.0.9 requires drupal/core 10.0.9 -> found drupal/core[10.0.9] but these were not loaded, likely because it conflicts with another require.
- drupal/core-recommended 10.0.10 requires drupal/core 10.0.10 -> found drupal/core[10.0.10] but these were not loaded, likely because it conflicts with another require.
- drupal/core-recommended 10.0.11 requires drupal/core 10.0.11 -> found drupal/core[10.0.11] but these were not loaded, likely because it conflicts with another require.
- drupal/core-recommended 10.1.0 requires drupal/core 10.1.0 -> found drupal/core[10.1.0] but these were not loaded, likely because it conflicts with another require.
- drupal/core-recommended 10.1.1 requires drupal/core 10.1.1 -> found drupal/core[10.1.1] but these were not loaded, likely because it conflicts with another require.
- drupal/core-recommended 10.1.2 requires drupal/core 10.1.2 -> found drupal/core[10.1.2] but these were not loaded, likely because it conflicts with another require.
- drupal/core-recommended 10.1.3 requires drupal/core 10.1.3 -> found drupal/core[10.1.3] but these were not loaded, likely because it conflicts with another require.
- drupal/core-recommended 10.1.4 requires drupal/core 10.1.4 -> found drupal/core[10.1.4] but these were not loaded, likely because it conflicts with another require.
- drupal/core-recommended 10.1.5 requires drupal/core 10.1.5 -> found drupal/core[10.1.5] but these were not loaded, likely because it conflicts with another require.
- drupal/core-recommended 10.1.6 requires drupal/core 10.1.6 -> found drupal/core[10.1.6] but these were not loaded, likely because it conflicts with another require.
- drupal/core-recommended 10.1.7 requires drupal/core 10.1.7 -> found drupal/core[10.1.7] but these were not loaded, likely because it conflicts with another require.
- drupal/core-recommended 10.2.0 requires drupal/core 10.2.0 -> found drupal/core[10.2.0] but these were not loaded, likely because it conflicts with another require.
- drupal/core-recommended 10.2.1 requires drupal/core 10.2.1 -> found drupal/core[10.2.1] but these were not loaded, likely because it conflicts with another require.
- Root composer.json requires drupal/core-recommended ^10 -> satisfiable by drupal/core-recommended[10.0.0, ..., 10.2.1].