Applied
MR is needed
I am facing the same issue.
Thank you for the fix
Rajab Natshah → created an issue.
Rajab Natshah → made their first commit to this issue’s fork.
I like this proposed section
"Container size"
It requires less effort to change configurations, and it works out of the box for needed cases.
Needs a hook update to enable and auto configure
G4MBINI → credited Rajab Natshah → .
Grimreaper → credited Rajab Natshah → .
Any needed patch can be added to vardot/varbase-patches .
Only file an issue to add the patch to Varbase Patches
Issue
#3437217 →
: Switched to a local patching system using vardot/varbase-patches and cweagans/composer-patches "~2" within Varbase
Try to delete the old composer.lock before composer update -vvv or you may do composer install -vvv
- in Varbase 10.0.0-rc2 - Issue
#3437217 →
: Switched to a local patching system using vardot/varbase-patches and
cweagans/composer-patches"~2"within Varbase
- Issue
#3458615 →
: Updated Drupal Core to
~10.3.0and~11.0.0with support for recipes in Varbase Profile version requirements
Thanks, jjwfcd, for reporting.
What are the file permissions for the files folder?
Are you getting any error logs or warning logs in syslog?
Thanks, Steve, for reporting
Try only for testing to add a static version for Drupal as "drupal/core": "10.3.1", in the root composer.json file.
Only to check on which package is not letting the update, update to the latest Drupal
Could be fixed in the same Webform module
try to update the Webform module first
They had a new release
if they did not commit the fix in webform
we could add a hook to fix this in varbase_webform
only the location is wrong.
- try to fix in webform first ( file an issue for them)
- try to fix this in your custom module ( TEMP ) in the project
- We can add it in Varbase Webform module
✅ Released varbase-9.1.4 →
✅ Released varbase-9.1.4 →
✅ Released varbase-9.1.4 →
✅ Released varbase-9.1.4 →
✅ Released varbase-9.1.4 →
✅ Released varbase-9.1.4 →
✅ Released varbase-9.1.4 →
✅ Released varbase-9.1.4 →
✅ Released varbase-9.1.4 →
✅ Released varbase-9.1.4 →
✅ Released varbase-9.1.4 →
✅ Released varbase-9.1.4 →
✅ Released varbase-9.1.4 →
✅ Released varbase-9.1.4 →
✅ Released varbase-9.1.4 →
✅ Released varbase-9.1.4 →
✅ Released varbase-9.1.4 →
✅ Released varbase-9.1.4 →
✅ Released varbase-9.1.4 →
✅ Released varbase-9.1.4 →
✅ Released varbase-9.1.4 →
✅ Released varbase-9.1.4 →
✅ Released varbase-9.1.4 →
✅ Released varbase-9.1.4 →
✅ Released varbase-9.1.4 →
✅ Released varbase-9.1.4 →
✅ Released varbase-9.1.4 →
✅ Released varbase-9.1.4 →
✅ Released varbase-9.1.4 →
✅ Released varbase-9.1.4 →
✅ Released varbase-9.1.4 →
✅ Released varbase-9.1.4 →
✅ Released varbase-9.1.4 →
✅ Released varbase-9.1.4 →
✅ Released varbase-9.1.4 →
✅ Released varbase-9.1.4 →
✅ Released varbase-9.1.4 →
✅ Released varbase-9.1.4 →
✅ Released varbase-9.1.4 →
✅ Released varbase-9.1.4 →
✅ Released varbase-9.1.4 →
✅ Released varbase-9.1.4 →
✅ Released varbase-9.1.4 →
✅ Released varbase-9.1.4 →
✅ Released varbase-9.1.4 →
✅ Released varbase-9.1.4 →
Listed in the release note as provided by Andy
https://www.drupal.org/project/bootstrap_styles/releases/1.1.6 →
If you're updating from an earlier version, this module no longer requires Media Library Theme Reset → (because it's unsupported). The update might cause the module to be removed entirely from your codebase, in which case you should uninstall Media Library Theme Reset before deploying the update (it can be done manually or in a post update hook). Failure to do so will result in an error message:
The following module is marked as installed in the core.extension configuration, but it is missing:
media_library_theme_reset
If you'd still like the functionality from Media Library Theme Reset you can try
✅ Release varbase-10.0.0 →
✅ Release varbase-10.0.0 →