hi
i tested the MR15 which effectively hide/show the "Additional settings" section.
However, is there anyway to extend this feature so that it (only or also) depends on permission/ role assigned to a user ?
Some content editor with specific role may be allowed to change the icon settings when adding entity item to which the iconify field is attached.
As now it's going to be possible to hid/show the Additional settings, I am also thinking (if possible) to :
- either completely move the "Additional settings" from "default field value" to the form display settings, so that configuration be made there and overridden when editing a content that has the iconify field (with enabled => Enable inconify icons Advanced settings + permission / role feature)
- or keep as it is in default value settings for only when no value is set and and overridden by form display settings or user when editing a content item
Thanks
hi
thanks for this quick reactions.
I will test an let you know
Thanks
delacosta456 → created an issue.
hi
There is an ongoing work about the Readme
here
📌
Add a README file
Needs work
You can open the latest patch or Interdiff file there to read some descriptions
delacosta456 → created an issue.
delacosta456 → created an issue.
hi
ok thanks for replying and having this already planned. it's may also be the best moment to start planning joining/merging force/module with @Dobefu.
I have feature request about field settings that i would post on a specific issue.
Thanks
hi
Thanks for both maintainers for this issue that clarify the confusion and the nice work you people have done each other in your module.
However does is mean that iconify_icons will also provide an icon-picker widget ?
Thanks
hi
i also confirm this issue with D10.2.5 php8.2
Thanks for the patch
i set this issue back to a support request because i just realize that after saving the form even if new value set on the form a not retain, running drush cex
warn about those changes.
The strange part of this issue for me i please need help from anyone to understand is why is it behaving so on UI only with VarthemeBS4 or generated sub-theme of Vartheme Bs4
Thanks
delacosta456 → created an issue.
hi @sime
Not **AUTOMATICALLY** but be here (Drush comand to export all items from entity with defined criteria) ✨ Drush comand to export all items from entity with defined criteria Needs review may be a start point of export by entity type that i am using.
and then re-enabling the custom-default-content-module
(in CI/CD) will do the remaining task.
For more export option this (Add `drush dcer --bundles` option to limit export) ✨ Add `drush dcer --bundles` option to limit export Needs review may help but I haven't tested.
hi
Any update please about this.It is still the case with default Vartheme4 of Varbase 9.1.2
hi all
@andypost
@lammensj
@eelkeblok
@kalpaitch
@nedjo
@pfrenssen
@jomsy
Can somebody please help me know how to use the $update_existing
variable (setting it to true ) when re-enabling DC-custom-module to fire entities update?
Thanks
hi @eduardo-morales-alberti
I was looking for something like this.
The patch applied correctly but looks to have breaks another patch
Drush comand to export all items from entity with defined criteria
✨
Drush comand to export all items from entity with defined criteria
Needs review
that i was using to export at once node+references to folder .
Example : drush dcer node 34 --folder=modules/custom/mycustom_default_content/content
after the merge request 45.patch
the above command doesn't work and send the following error
In LegacyServiceInstantiator.php line 282: You have requested a non-existent parameter "default_content.deleter".
Can you help
Thanks
delacosta456 → created an issue.
hi @unstatu
thanks for the patch that applied correctly on D10.2 +php8.2
However on my own side when updating the node's section (in layout builder), changes will not be reflected in another env until i delete the node and import again by enabling the custom module.
This looks to be also the case for other entities like menu_link_content.(Ex have menu link X in both environment Adev and Bprod. on Adev, change the label and disable the menu link, and finally export. there will be no change )
it' looks like #175 approach is the only one that is successfully uptating an entity
delacosta456 → created an issue.
delacosta456 → created an issue.
hi
i was also having Nid constantly changing on import and would like to know if this issue and
https://www.drupal.org/project/default_content/issues/3277477 →
are related
hi
i was also having this issue with permission related to devel module.
Patch #11 also worked for me on 10.2.5 + php.8.2
Thanks
hi
i am on D10.2 +php8.2 and none of patch in #9 applied
Only the the patch in #9 applied . Can somebody help please
Thanks
hi
thanks for the logic of this patch. while this patch is correctly being applied on D10.2+php8.2
the on on
this issue →
doesn't apply
can someone please help for this
Thanks
hi
i am trying to aplly the MR24 on D10.2 with php 8.2 without success can somebody help with this
Thanks
hi @flyke
Thanks for your clarification.
However following your suggestion returned an error of too many argument
Below is the drush command i try to use :
drush dcer menu_link_content menu_name main --folder=modules/custom/brains_mtcb_default_content/content
and this return the error message below
Too many arguments to "dcer" command, expected arguments "entity_type_id" "entity_id".
i am i missing something ?
Thanks
delacosta456 → created an issue.
hi
thanks for replying
i agreed with your suggestion.
By the way i that will be if people follow a workflow that exclude using composer on prod environment which (for most blog's i had read) is not usually the case as you can also see in that documentation.
So in addition to your suggestion does it make sense to suggest :
Before deploying to the production site always use <strong>in your test or preprod environment</strong> composer install --no-dev, so that unnecessary
Thanks
delacosta456 → created an issue.
hi @flyke
i was reading this discussion to find a solution for my case and started being confuse when i read your comment.
Please what did you exactly mean by the below
UPDATE: never mind, figured it out:
drush dcer menu_link_content menu_name main --folder=modules/custom/my_custom_module/content
I have this patch applied but not really sure on how to make your command work.
Thanks
delacosta456 → changed the visibility of the branch 2916876-10.1.x to active.
hi
thanks for replying
i am alrady using the configuration you describe.
- on local i did everything with Lando (composer install, export config etc)
- and when everything is ok i pushed to Gitlab with a configured CI/CD that deploy per branch after some test tasks and merges requests on each of them (BchDev=>to Dev, Bchstg=>to Stg and BchMain=>to Prod)
However i haven't see any clear simple and easy way to deploy to PROD than the composer method with gitlab by first taking the site to maintenance mode.
Did have any suggestion ? is it what could be in Deploy Varbase on Platform.sh ? if yes please check the link because it's not clickable .
i have already noticed
The composer build may faile at anypoint, and you will end up with the production site as down
which is why i requested for a support
Thanks
delacosta456 → created an issue.
hi
also thanks for #175 .. it's working on D10.2.5 with php8.2
hi
as mentioned by @cosmin-hodis-mindras after applying patch on my own side too the error message changed to exactly message reported (
#3
🐛
Deprecated function: Use of "self" in callables
Needs review
) . i am on D10.2.5 and php8.2.17
Thanks
hi
thanks for the suggestion .
It worked.
hi
is it still possible to use this functionality with 8 version?
delacosta456 → created an issue.
hi @
theodorosploumis Your workflow posted saved me from some trouble i was having with some distro By the way, dear all, i would like to know if there is a particular reason@
theodorosploumis mentionned:drush updb --no-cache-clear
and later rundrush cr
? (a simple drush updb does it not combine the two line?)
Thanks
hi
i am already using config_split in the scenario you describe . but it means that you must know exactly what you are doing after investigating on each module implication
As you can see at admin/module page with module_filter enabled you can filter by Enabled, disable, Unavailable .
My request about "Not required" module because i have seen that for each module listed at admin/module page there is an info (**Required by:**) saying if it's actually required by another module . So i was expecting with my feature request there could be a **Not required** filter that will exclude from the list modules **actually required**
The https://www.drupal.org/project/unused_modules → looks to be doing something similar but there is a lot of confusion there
delacosta456 → created an issue.
delacosta456 → created an issue.
hi
Can you please elaborate how you "Upgrade" to D10 ? For example what was the your previous Varbase version before you begin upgrade?
hi all
i was facing this issue too until i realize that node's that have block_content, does not export the block content when runing "drush dcer ...
" command . below are the applied patches that resolve it for me (exporting the entity with reference)
"patches": {
"drupal/default_content": {
"1 - Add a Normalizer and Denormalizer to support Layout Builder - https://www.drupal.org/project/default_content/issues/3160146#comment-14814050": "https://www.drupal.org/files/issues/2022-12-06/default_content-3160146-53.patch",
"2 - Do not reimport existing entities": "https://www.drupal.org/files/issues/2022-07-29/default_content-fix-uuid-duplicate-entry-2698425.patch",
"3 - Update inline block usage on import - https://www.drupal.org/project/default_content/issues/3359137#comment-15042582": "https://www.drupal.org/files/issues/2023-05-09/default_content-3359137-3.patch"
},
hi
finally i was able to solve this with default_content module 2.0.x-dev in combination with patches below
"patches": {
"drupal/default_content": {
"1 - Add a Normalizer and Denormalizer to support Layout Builder - https://www.drupal.org/project/default_content/issues/3160146#comment-14814050": "https://www.drupal.org/files/issues/2022-12-06/default_content-3160146-53.patch",
"2 - Do not reimport existing entities": "https://www.drupal.org/files/issues/2022-07-29/default_content-fix-uuid-duplicate-entry-2698425.patch",
"3 - Update inline block usage on import - https://www.drupal.org/project/default_content/issues/3359137#comment-15042582": "https://www.drupal.org/files/issues/2023-05-09/default_content-3359137-3.patch"
}
},
"patches-ignore": {
"drupal/varbase_core": {
"drupal/default_content": {
"Issue #3160146: Add Layout Builder Normalizer and Denormalize": "https://www.drupal.org/files/issues/2021-04-07/3160146-37.patch"
}
}
}
}
}
Please note that to be able to successfully export node related inline block_content (with dcer
) and get i correctly imported when enabling module all above patches( 3160146-53.patch replacing 3160146-37.patch) where needed.
Now am still looking for how to figure "updating changed made without the need to delete node and re-import"
Thanks
hi
if it may help the workaround for me without patching (until stable patch) is
- n database run
select * from key_value where name = "field.field.deleted" or name = "field.storage.deleted";
- in terminal run
drush cr
- Navigate to admin/config/system/cron and run cron or navigate to admin/config/system/cron/jobs scroll down and at row
Purges deleted Field API data
click Run
hope it's help
Thanks
hi
ok thanks .. Update run successfully now
delacosta456 → created an issue.
hi
i just notice line are missing ..
let me retry and get back to you please
hi
sorry forgot to add my composer.json before update
{
"name": "vardot/varbase-project",
"description": "Project template for Varbase distribution.",
"type": "project",
"license": "GPL-2.0-or-later",
"authors": [
{
"name": "Vardot",
"homepage": "https://github.com/vardot",
"role": "Maintainer"
}
],
"support": {
"issues": "http://drupal.org/project/issues/varbase",
"source": "http://cgit.drupalcode.org/varbase"
},
"repositories": {
"drupal": {
"type": "composer",
"url": "https://packages.drupal.org/8"
},
"assets": {
"type": "composer",
"url": "https://asset-packagist.org"
}
},
"require": {
"composer/installers": "~2.0",
"oomphinc/composer-installers-extender": "~2.0",
"cweagans/composer-patches": "~1.0",
"drupal/core-composer-scaffold": "~10",
"drupal/core-project-message": "~10",
"webflo/drupal-finder": "~1.0",
"drupal/core": "~10.1.0",
"vardot/varbase": "~9.0.0",
"vardot/varbase-updater": "~2.0",
"drupal/module_filter": "^4.0",
"drupal/config_split": "^2.0@RC",
"drupal/default_content_deploy": "2.0.x-dev@dev",
"bower-asset/jquery": "^1.6",
"drupal/jquery_ui": "^1.6",
"drupal/robotstxt": "^1.5",
"drupal/unused_modules": "^1.5",
"drupal/varbase_media_demo": "^10.0",
"drupal/easy_install_d10": "10.x-dev@dev",
"drupal/config_import_de": "^1.0",
"drupal/varbase_media_header": "^9.1",
"drupal/better_normalizers": "^2.0@beta",
"drupal/recreate_block_content": "^3.0"
},
"require-dev": {
"drupal/core-dev": "~10",
"drush/drush": "~12.0",
"phpstan/phpstan": "~1.10.0",
"phpstan/extension-installer": "~1.3.0",
"mglaman/phpstan-drupal": "~1.1.0",
"phpstan/phpstan-deprecation-rules": "~1.1.0"
},
"config": {
"bin-dir": "bin/",
"secure-http": false,
"optimize-autoloader": true,
"preferred-install": {
"drupal/core": "dist"
},
"allow-plugins": {
"composer/installers": true,
"cweagans/composer-patches": true,
"oomphinc/composer-installers-extender": true,
"drupal/core-composer-scaffold": true,
"drupal/core-project-message": true,
"dealerdirect/phpcodesniffer-composer-installer": true,
"phpstan/extension-installer": true,
"vardot/varbase-updater": true
}
},
"scripts": {
"post-install-cmd": [
"Varbase\\composer\\ScriptHandler::createRequiredFiles",
"Varbase\\composer\\ScriptHandler::removeGitDirectories"
],
"post-update-cmd": [
"Varbase\\composer\\ScriptHandler::createRequiredFiles",
"Varbase\\composer\\ScriptHandler::removeGitDirectories"
],
"post-drupal-scaffold-cmd": ["Varbase\\composer\\ScriptHandler::postDrupalScaffoldProcedure"]
},
"minimum-stability": "dev",
"prefer-stable": true,
"conflict": {
"drupal/drupal": "*"
},
"extra": {
"branch-alias": {
"dev-9.0.x": "9.0.x-dev"
},
"drupal-core-project-message": {
"include-keys": ["homepage", "support"],
"post-create-project-cmd-message": [
"<bg=blue;fg=white> </>",
"<bg=blue;fg=white> Congratulations, you have installed the Varbase codebase </>",
"<bg=blue;fg=white> from the vardot/varbase-project template! </>",
"<bg=blue;fg=white> </>",
"",
"<bg=yellow;fg=black>Next steps</>:",
" * Install the site: https://www.drupal.org/docs/installing-drupal",
" * Read the user guide: https://docs.varbase.vardot.com",
" * Get support: https://www.vardot.com/en/form/get-support-varbase",
" * Join Our Slack Team for Feedback and Support:",
" http://slack.varbase.vardot.com",
" * Remove the plugin that prints this message:",
" composer remove drupal/core-project-message"
]
},
"drupal-scaffold": {
"allowed-packages": [
"drupal/core",
"vardot/varbase"
],
"gitignore": true,
"locations": {
"web-root": "./docroot"
},
"file-mapping": {
"[web-root]/sites/default/default.services.yml": {
"mode": "replace",
"overwrite": false,
"path": "docroot/core/assets/scaffold/files/default.services.yml"
},
"[web-root]/sites/default/default.settings.php": {
"mode": "replace",
"overwrite": false,
"path": "docroot/core/assets/scaffold/files/default.settings.php"
}
}
},
"installer-paths": {
"docroot/core": ["type:drupal-core"],
"docroot/profiles/{$name}": ["type:drupal-profile"],
"docroot/modules/contrib/{$name}": ["type:drupal-module"],
"docroot/themes/contrib/{$name}": ["type:drupal-theme"],
"docroot/libraries/slick": ["npm-asset/slick-carousel"],
"docroot/libraries/ace": ["npm-asset/ace-builds"],
"docroot/libraries/jquery-ui-touch-punch": ["bower-asset/jqueryui-touch-punch"],
"docroot/libraries/swagger-ui/dist": ["npm-asset/swagger-ui-dist"],
"docroot/libraries/{$name}": [
"type:drupal-library",
"type:bower-asset",
"type:npm-asset"
],
"docroot/modules/custom/{$name}": ["type:drupal-custom-module"],
"docroot/themes/custom/{$name}": ["type:drupal-custom-theme"],
"drush/contrib/{$name}": ["type:drupal-drush"]
},
"installer-types": [
"bower-asset",
"npm-asset"
],
"drupal-libraries": {
"library-directory": "docroot/libraries",
"libraries": [
{"name": "objectfitpolyfill", "package": "bower-asset/objectfitpolyfill"},
{"name": "chartjs", "package": "bower-asset/chartjs"},
{"name": "c3","package": "bower-asset/c3"},
{"name": "d3", "package": "bower-asset/d3"},
{"name": "dropzone","package": "npm-asset/dropzone"},
{"name": "blazy", "package": "npm-asset/blazy"},
{"name": "slick", "package": "npm-asset/slick-carousel"},
{"name": "ace", "package": "npm-asset/ace-builds"},
{"name": "jquery-ui-touch-punch", "package": "bower-asset/jqueryui-touch-punch"},
{"name": "imagesloaded", "package": "npm-asset/imagesloaded"},
{"name": "swagger-ui", "package": "npm-asset/swagger-ui-dist"}
]
},
"enable-patching": true,
"composer-exit-on-patch-failure": true,
"patchLevel": {
"drupal/core": "-p2"
},
"patches": {
"drupal/core":{
"(Serge for DCD)[PP-1] Expose Layout Builder data to REST and JSON:API": "https://www.drupal.org/files/issues/2023-12-11/2942975-252_revised_239.patch"
},
"drupal/hal": {
"(Serge for DCD) Translated field denormalization creates duplicate values":"https://www.drupal.org/files/issues/2023-04-05/2904423-90.patch"
},
"drupal/easy_install": {
"PHP warning on": "https://www.drupal.org/files/issues/2020-07-25/Solution.patch"
},
"drupal/default_content": {
"2 - Don't add translation, if exist - https://www.drupal.org/project/default_content/issues/3176839#comment-13859359": "https://www.drupal.org/files/issues/2020-10-14/default_content-3176839-2.patch",
"3 - Add a Normalizer and Denormalizer to support Layout Builder - https://www.drupal.org/project/default_content/issues/3160146#comment-14814050": "https://www.drupal.org/files/issues/2022-12-06/default_content-3160146-53.patch",
"4 - Update inline block usage on import - https://www.drupal.org/project/default_content/issues/3359137#comment-15042582": "https://www.drupal.org/files/issues/2023-05-09/default_content-3359137-3.patch"
}
},
"patches-ignore": {
"drupal/varbase_core": {
"drupal/default_content": {
"Issue #3160146: Add Layout Builder Normalizer and Denormalize": "https://www.drupal.org/files/issues/2021-04-07/3160146-37.patch"
}
}
}
}
}
hi
ok thanks i will expect it
delacosta456 → created an issue.
hi
thanks for replying
what could be the simple and best patch combination because i am for have been trying a lot of things i am a little bit confused.
- Should i Simple go with the default_content module + the patch you suggested
without
any other extra export module ? For info please know that immediately after reading your reply i tried the latest patch #53 ✨ Add a Normalizer and Denormalizer to support Layout Builder Needs work that applied correctly but followed by an error message saying that #37 → could not be applied. This sound logic but make my Gitlab CI/CD stucks. i tried the "patches-ignore" method recommended i here in Varbase Documentation but still getting the error
- Should i use the the patch together with those one i mentioned in my first post
Thanks
delacosta456 → created an issue.
hi
i am also facing this issue on D10.1.6
have tried that at time of writing was impossible for D9 and D10 as i said... Now it's ok for D10 ,
hi
i just change the status of this issue because it is still the case for 2.00.. for example If a node was deleted the JSON file is still present
hi
please is there any update for this?
delacosta456 → created an issue.
hi
many thanks for replying
My request was more about something that could "also" be configurable from UI
An illustration could be what this d7 module offer https://www.drupal.org/project/link_onclick →
Thanks
delacosta456 → created an issue.
delacosta456 → created an issue.
delacosta456 → created an issue.
hi
Never mind
Updating from 10.0.44 to 10.0.45 solve the issue
Thanks
delacosta456 → created an issue.
delacosta456 → created an issue.
hi
Many thanks quick reply and for solving this.
delacosta456 → created an issue.
delacosta456 → created an issue.
hi all
switching from pdo_mysql to nd_pdo_mysql under PHP settings
also worked for me .
for infos i diddnt have Cpanel on my hosting but a custom php settings board. Which mean that this solutions should work with most hosting .
Thanks
hi
ook i see. and yes i am using coffee.
I was just looking for the logic provided by Admin search input : pssibility to filter / search from toolbar inside long/deep display menu tree
Thanks
delacosta456 → created an issue.
delacosta456 → created an issue.
delacosta456 → created an issue.
delacosta456 → created an issue.
hi
any update about this please
i am also facing this issue
Thanks
delacosta456 → created an issue.
hi
this was because i reuse an old custom included shared.settings.php that has $settings['hash_salt']
of old site.
The best way is to finish installing new site and now carefully merge differences of new installed settings, php to custom included shared.settings.php
Thanks
delacosta456 → created an issue.
Hi
Try doing it Inside your web panel manager (where you configured the site's domain to.[the subfolder])
So as said above the if the sub-folder(where you see composer.json and composer.lock) is "mysite",
(instead of /mysite/admin/content that could still send error ) from the web panel manager (where you can configure domain to point to other thing than public_html)
write /mysite/web or /mysite/docroot (this last part depend on where drupal's index.php file is located)
Hope it's help
hi sorry
but this is still a real issue
- The module is not providing any more a default media Type.
- According to above, configuration steps are very complicated and difficult to save the media after inserting to Media library
@nginex thanks for following and the upcoming release
hi @rajab-natshah thanks for your reply.shall we still keep this issue here tied to Varbase?