I believe it is a Search API problem, not Search API SOLR.
Sorry for the delay in feedback. It sounds like you didn't create the same environment as mine. I have to do this from memory as I solved the immedate problem by creating essentially a suplicate field for both CT's...
I Create 2 different CT's. I creadted a Term Ref field I would use for both CT's. I used CF to control a field based on certain Taxonomy ID's. Each CT uses different Terms (Tax ID's) from the same Taxonomy.
I found that after i created the CF on the first CT, the second CT already had CF applied to it without me having configured any. The applied CF was identical on the second CT but because it used the Terms the first CT needed I needed to adjust it for the Terms the second CT needed. If I adjusted it on CT2 the adjustments broke the CF on CT1. Likewise if I deleted it from CT2 it was deleted from CT1.
GuyManDude → created an issue.
GuyManDude → created an issue.
GuyManDude → created an issue.
GuyManDude → created an issue.
GuyManDude → created an issue.
I happened to have another 10.2.2 box around do I decided to test Beta3 on it. It worked fine but there are differences between my boxes that might be helpful for you to know.
This working 10.2.2 server was upgraded from 10.0.9
When adding Serial Field to a Content Type on this box, the Serial Field was listed in the 'Number' section.
When adding Serial Field to a Content Type on the other box, the Serial Field was listed in the 'Serial' section.
Wow, do I feel like a tool Wim. I can't believe I didn't catch those CSS errors. You were right, they were the problem.
just tried creating a whole new content type just to test Serial in a vanilla setting and same problems happened. I cannot delete that new content type either, it generates a wsod.
Last time I was able to fix the site using this suggestion from another thread:
Export site config: drush cex
Find the config name for the broke field in the exported directory on the server. In my case it was: field.field.node.invoice.field_invoice_number
run the delete config command (replace my config name with yours): drush config-delete field.field.node.invoice.field_invoice_number
Clear cache
I just tried doing it again but the content type still generates a wsod when trying to edit it.
Just tried it and got wsod when adding it to a Content Type. I selected Serial from the list if available fields and as soon as I click Add the wsod appears. Here's some log info:
Drupal\Core\Field\FieldException: Attempted to create an instance of field with name field_asset_id on entity type node when the field storage does not exist. in Drupal\field\Entity\FieldConfig->getFieldStorageDefinition() (line 316 of /var/www/html/drupal10/web/core/modules/field/src/Entity/FieldConfig.php).
Thanks for following-up. The server I was using for the original post is long-gone, but I should make you aware I tried using this module on a vanilla 10.2 install just a few days ago and had problems with it. Other people had the same problem apparently. If you posted this without actuallly testing it on 10.2, you might want to conduct some more tests...
My apologies, I should have been more clear. I have only ever removed the entire comment. What you see in that screenshot is what happens. The formatting goes haywire.
I'm not sure if I even have that test box around any more to troubleshoot further.
GuyManDude → created an issue.
Looking at the summary of log error 2 looks like it might identify the culprit:
Summary:
Drupal\Core\Field\FieldException: Attempted to create an instance of field with name field_ct_project_id on entity type node when the field storage does not exist. in Drupal\field\Entity\FieldConfig->getFieldStorageDefinition() (line 316 of /var/www/html/drupal10/web/core/modules/field/src/Entity/FieldConfig.php).
I cannot get back into the Content Type to remove the field. It WSOD as soon as I click on the edit button.
Here is 2 of 3 log messages:
Summary:
Drupal\Core\Field\FieldException: Attempted to create an instance of field with name field_ct_project_id on entity type node when the field storage does not exist. in Drupal\field\Entity\FieldConfig->getFieldStorageDefinition() (line 316 of /var/www/html/drupal10/web/core/modules/field/src/Entity/FieldConfig.php).
#0 /var/www/html/drupal10/web/core/lib/Drupal/Core/Field/FieldConfigBase.php(370): Drupal\field\Entity\FieldConfig->getFieldStorageDefinition()
#1 /var/www/html/drupal10/web/core/lib/Drupal/Core/Field/FieldConfigBase.php(549): Drupal\Core\Field\FieldConfigBase->getSettings()
#2 /var/www/html/drupal10/web/core/lib/Drupal/Core/TypedData/Plugin/DataType/ItemList.php(230): Drupal\Core\Field\FieldConfigBase->getItemDefinition()
#3 /var/www/html/drupal10/web/core/lib/Drupal/Core/TypedData/TypedDataManager.php(190): Drupal\Core\TypedData\Plugin\DataType\ItemList->getItemDefinition()
#4 /var/www/html/drupal10/web/core/lib/Drupal/Core/Field/FieldTypePluginManager.php(91): Drupal\Core\TypedData\TypedDataManager->getPropertyInstance()
#5 /var/www/html/drupal10/web/core/lib/Drupal/Core/Field/FieldItemList.php(41): Drupal\Core\Field\FieldTypePluginManager->createFieldItem()
#6 /var/www/html/drupal10/web/core/lib/Drupal/Core/TypedData/Plugin/DataType/ItemList.php(212): Drupal\Core\Field\FieldItemList->createItem()
#7 /var/www/html/drupal10/web/core/lib/Drupal/Core/Field/FieldItemList.php(177): Drupal\Core\TypedData\Plugin\DataType\ItemList->appendItem()
#8 /var/www/html/drupal10/web/core/lib/Drupal/Core/Entity/ContentEntityStorageBase.php(271): Drupal\Core\Field\FieldItemList->applyDefaultValue()
#9 /var/www/html/drupal10/web/core/lib/Drupal/Core/Entity/ContentEntityStorageBase.php(129): Drupal\Core\Entity\ContentEntityStorageBase->initFieldValues()
#10 /var/www/html/drupal10/web/core/lib/Drupal/Core/Entity/ContentEntityStorageBase.php(94): Drupal\Core\Entity\ContentEntityStorageBase->doCreate()
#11 /var/www/html/drupal10/web/core/modules/field/field.module(288): Drupal\Core\Entity\ContentEntityStorageBase->create()
#12 /var/www/html/drupal10/web/core/modules/field_ui/src/Form/FieldStorageConfigEditForm.php(114): _field_create_entity_from_ids()
#13 /var/www/html/drupal10/web/core/lib/Drupal/Core/Entity/EntityForm.php(107): Drupal\field_ui\Form\FieldStorageConfigEditForm->form()
#14 /var/www/html/drupal10/web/core/modules/field_ui/src/Form/FieldStorageConfigEditForm.php(85): Drupal\Core\Entity\EntityForm->buildForm()
#15 /var/www/html/drupal10/web/core/modules/field_ui/src/Form/FieldConfigEditForm.php(199): Drupal\field_ui\Form\FieldStorageConfigEditForm->buildForm()
#16 /var/www/html/drupal10/web/core/lib/Drupal/Core/Entity/EntityForm.php(107): Drupal\field_ui\Form\FieldConfigEditForm->form()
#17 [internal function]: Drupal\Core\Entity\EntityForm->buildForm()
#18 /var/www/html/drupal10/web/core/lib/Drupal/Core/Form/FormBuilder.php(536): call_user_func_array()
#19 /var/www/html/drupal10/web/core/lib/Drupal/Core/Form/FormBuilder.php(283): Drupal\Core\Form\FormBuilder->retrieveForm()
#20 /var/www/html/drupal10/web/core/lib/Drupal/Core/Entity/EntityFormBuilder.php(48): Drupal\Core\Form\FormBuilder->buildForm()
#21 /var/www/html/drupal10/web/core/modules/field_ui/src/Controller/FieldConfigAddController.php(62): Drupal\Core\Entity\EntityFormBuilder->getForm()
#22 [internal function]: Drupal\field_ui\Controller\FieldConfigAddController->fieldConfigAddConfigureForm()
#23 /var/www/html/drupal10/web/core/lib/Drupal/Core/EventSubscriber/EarlyRenderingControllerWrapperSubscriber.php(123): call_user_func_array()
#24 /var/www/html/drupal10/web/core/lib/Drupal/Core/Render/Renderer.php(627): Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->Drupal\Core\EventSubscriber\{closure}()
#25 /var/www/html/drupal10/web/core/lib/Drupal/Core/EventSubscriber/EarlyRenderingControllerWrapperSubscriber.php(121): Drupal\Core\Render\Renderer->executeInRenderContext()
#26 /var/www/html/drupal10/web/core/lib/Drupal/Core/EventSubscriber/EarlyRenderingControllerWrapperSubscriber.php(97): Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->wrapControllerExecutionInRenderContext()
#27 /var/www/html/drupal10/vendor/symfony/http-kernel/HttpKernel.php(181): Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->Drupal\Core\EventSubscriber\{closure}()
#28 /var/www/html/drupal10/vendor/symfony/http-kernel/HttpKernel.php(76): Symfony\Component\HttpKernel\HttpKernel->handleRaw()
#29 /var/www/html/drupal10/web/core/lib/Drupal/Core/StackMiddleware/Session.php(58): Symfony\Component\HttpKernel\HttpKernel->handle()
#30 /var/www/html/drupal10/web/core/lib/Drupal/Core/StackMiddleware/KernelPreHandle.php(48): Drupal\Core\StackMiddleware\Session->handle()
#31 /var/www/html/drupal10/web/core/modules/page_cache/src/StackMiddleware/PageCache.php(106): Drupal\Core\StackMiddleware\KernelPreHandle->handle()
#32 /var/www/html/drupal10/web/core/modules/page_cache/src/StackMiddleware/PageCache.php(85): Drupal\page_cache\StackMiddleware\PageCache->pass()
#33 /var/www/html/drupal10/web/core/lib/Drupal/Core/StackMiddleware/ReverseProxyMiddleware.php(48): Drupal\page_cache\StackMiddleware\PageCache->handle()
#34 /var/www/html/drupal10/web/core/lib/Drupal/Core/StackMiddleware/NegotiationMiddleware.php(51): Drupal\Core\StackMiddleware\ReverseProxyMiddleware->handle()
#35 /var/www/html/drupal10/web/core/lib/Drupal/Core/StackMiddleware/AjaxPageState.php(36): Drupal\Core\StackMiddleware\NegotiationMiddleware->handle()
#36 /var/www/html/drupal10/web/core/lib/Drupal/Core/StackMiddleware/StackedHttpKernel.php(51): Drupal\Core\StackMiddleware\AjaxPageState->handle()
#37 /var/www/html/drupal10/web/core/lib/Drupal/Core/DrupalKernel.php(704): Drupal\Core\StackMiddleware\StackedHttpKernel->handle()
#38 /var/www/html/drupal10/web/index.php(19): Drupal\Core\DrupalKernel->handle()
#39 {main}
Here is 1 of 3 log messages
Deprecated function: Creation of dynamic property Drupal\smart_date\Plugin\views\filter\Date::$dateFormatter is deprecated in Drupal\smart_date\Plugin\views\filter\Date->__construct() (line 53 of /var/www/html/drupal10/web/modules/contrib/smart_date/src/Plugin/views/filter/Date.php)
#0 /var/www/html/drupal10/web/core/includes/bootstrap.inc(164): _drupal_error_handler_real()
#1 /var/www/html/drupal10/web/modules/contrib/smart_date/src/Plugin/views/filter/Date.php(53): _drupal_error_handler()
#2 /var/www/html/drupal10/web/modules/contrib/smart_date/src/Plugin/views/filter/Date.php(61): Drupal\smart_date\Plugin\views\filter\Date->__construct()
#3 /var/www/html/drupal10/web/core/lib/Drupal/Core/Plugin/Factory/ContainerFactory.php(21): Drupal\smart_date\Plugin\views\filter\Date::create()
#4 /var/www/html/drupal10/web/core/lib/Drupal/Component/Plugin/PluginManagerBase.php(76): Drupal\Core\Plugin\Factory\ContainerFactory->createInstance()
#5 /var/www/html/drupal10/web/core/modules/views/src/Plugin/ViewsHandlerManager.php(121): Drupal\Component\Plugin\PluginManagerBase->createInstance()
#6 /var/www/html/drupal10/web/core/modules/views/src/Plugin/ViewsHandlerManager.php(106): Drupal\views\Plugin\ViewsHandlerManager->createInstance()
#7 /var/www/html/drupal10/web/core/modules/views/src/Plugin/views/display/DisplayPluginBase.php(893): Drupal\views\Plugin\ViewsHandlerManager->getHandler()
#8 /var/www/html/drupal10/web/core/modules/views/src/ViewExecutable.php(1055): Drupal\views\Plugin\views\display\DisplayPluginBase->getHandlers()
#9 /var/www/html/drupal10/web/core/modules/views/src/ViewExecutable.php(913): Drupal\views\ViewExecutable->_initHandler()
#10 /var/www/html/drupal10/web/core/modules/views/src/Plugin/views/display/DisplayPluginBase.php(2323): Drupal\views\ViewExecutable->initHandlers()
#11 /var/www/html/drupal10/web/core/modules/views/src/ViewExecutable.php(1707): Drupal\views\Plugin\views\display\DisplayPluginBase->preExecute()
#12 /var/www/html/drupal10/web/core/modules/views/src/ViewExecutable.php(1642): Drupal\views\ViewExecutable->preExecute()
#13 /var/www/html/drupal10/web/core/modules/views/src/Element/View.php(81): Drupal\views\ViewExecutable->executeDisplay()
#14 /var/www/html/drupal10/web/core/modules/views/src/Plugin/Block/ViewsBlock.php(61): Drupal\views\Element\View::preRenderViewElement()
#15 /var/www/html/drupal10/web/core/modules/block/src/BlockViewBuilder.php(171): Drupal\views\Plugin\Block\ViewsBlock->build()
#16 [internal function]: Drupal\block\BlockViewBuilder::preRender()
#17 /var/www/html/drupal10/web/core/lib/Drupal/Core/Security/DoTrustedCallbackTrait.php(111): call_user_func_array()
#18 /var/www/html/drupal10/web/core/lib/Drupal/Core/Render/Renderer.php(858): Drupal\Core\Render\Renderer->doTrustedCallback()
#19 /var/www/html/drupal10/web/core/lib/Drupal/Core/Render/Renderer.php(421): Drupal\Core\Render\Renderer->doCallback()
#20 /var/www/html/drupal10/web/core/lib/Drupal/Core/Render/Renderer.php(493): Drupal\Core\Render\Renderer->doRender()
#21 /var/www/html/drupal10/web/core/lib/Drupal/Core/Render/Renderer.php(240): Drupal\Core\Render\Renderer->doRender()
#22 /var/www/html/drupal10/web/core/lib/Drupal/Core/Template/TwigExtension.php(475): Drupal\Core\Render\Renderer->render()
#23 /var/www/html/drupal10/web/sites/default/files/php/twig/65d13ebededbc_page.html.twig_JscyU9j3wel2jWyL9z74dSYY7/z7fCI8sTMpHFCtI8Cud5mgPXpnvmOamvu59Rgv6MKZs.php(173): Drupal\Core\Template\TwigExtension->escapeFilter()
#24 /var/www/html/drupal10/vendor/twig/twig/src/Template.php(394): __TwigTemplate_ccbaf97de9a6ca7b312e17748107d5ea->doDisplay()
#25 /var/www/html/drupal10/vendor/twig/twig/src/Template.php(367): Twig\Template->displayWithErrorHandling()
#26 /var/www/html/drupal10/vendor/twig/twig/src/Template.php(379): Twig\Template->display()
#27 /var/www/html/drupal10/vendor/twig/twig/src/TemplateWrapper.php(38): Twig\Template->render()
#28 /var/www/html/drupal10/web/core/themes/engines/twig/twig.engine(39): Twig\TemplateWrapper->render()
#29 /var/www/html/drupal10/web/core/lib/Drupal/Core/Theme/ThemeManager.php(348): twig_render_template()
#30 /var/www/html/drupal10/web/core/lib/Drupal/Core/Render/Renderer.php(480): Drupal\Core\Theme\ThemeManager->render()
#31 /var/www/html/drupal10/web/core/lib/Drupal/Core/Render/Renderer.php(240): Drupal\Core\Render\Renderer->doRender()
#32 /var/www/html/drupal10/web/core/lib/Drupal/Core/Template/TwigExtension.php(475): Drupal\Core\Render\Renderer->render()
#33 /var/www/html/drupal10/web/sites/default/files/php/twig/65d13ebededbc_html.html.twig_5xftcACKmjZCoVf1JZjhL_7dI/1DOao2P8brYK_slzGLmH6WL-swG8BUpgVS7BX_HeiP0.php(91): Drupal\Core\Template\TwigExtension->escapeFilter()
#34 /var/www/html/drupal10/vendor/twig/twig/src/Template.php(394): __TwigTemplate_c6b592d32615f32abc94a551b3c137c6->doDisplay()
#35 /var/www/html/drupal10/vendor/twig/twig/src/Template.php(367): Twig\Template->displayWithErrorHandling()
#36 /var/www/html/drupal10/vendor/twig/twig/src/Template.php(379): Twig\Template->display()
#37 /var/www/html/drupal10/vendor/twig/twig/src/TemplateWrapper.php(38): Twig\Template->render()
#38 /var/www/html/drupal10/web/core/themes/engines/twig/twig.engine(39): Twig\TemplateWrapper->render()
#39 /var/www/html/drupal10/web/core/lib/Drupal/Core/Theme/ThemeManager.php(348): twig_render_template()
#40 /var/www/html/drupal10/web/core/lib/Drupal/Core/Render/Renderer.php(480): Drupal\Core\Theme\ThemeManager->render()
#41 /var/www/html/drupal10/web/core/lib/Drupal/Core/Render/Renderer.php(240): Drupal\Core\Render\Renderer->doRender()
#42 /var/www/html/drupal10/web/core/lib/Drupal/Core/Render/MainContent/HtmlRenderer.php(158): Drupal\Core\Render\Renderer->render()
#43 /var/www/html/drupal10/web/core/lib/Drupal/Core/Render/Renderer.php(627): Drupal\Core\Render\MainContent\HtmlRenderer->Drupal\Core\Render\MainContent\{closure}()
#44 /var/www/html/drupal10/web/core/lib/Drupal/Core/Render/MainContent/HtmlRenderer.php(153): Drupal\Core\Render\Renderer->executeInRenderContext()
#45 /var/www/html/drupal10/web/core/lib/Drupal/Core/EventSubscriber/MainContentViewSubscriber.php(90): Drupal\Core\Render\MainContent\HtmlRenderer->renderResponse()
#46 [internal function]: Drupal\Core\EventSubscriber\MainContentViewSubscriber->onViewRenderArray()
#47 /var/www/html/drupal10/web/core/lib/Drupal/Component/EventDispatcher/ContainerAwareEventDispatcher.php(111): call_user_func()
#48 /var/www/html/drupal10/vendor/symfony/http-kernel/HttpKernel.php(186): Drupal\Component\EventDispatcher\ContainerAwareEventDispatcher->dispatch()
#49 /var/www/html/drupal10/vendor/symfony/http-kernel/HttpKernel.php(76): Symfony\Component\HttpKernel\HttpKernel->handleRaw()
#50 /var/www/html/drupal10/web/core/lib/Drupal/Core/StackMiddleware/Session.php(58): Symfony\Component\HttpKernel\HttpKernel->handle()
#51 /var/www/html/drupal10/web/core/lib/Drupal/Core/StackMiddleware/KernelPreHandle.php(48): Drupal\Core\StackMiddleware\Session->handle()
#52 /var/www/html/drupal10/web/core/modules/page_cache/src/StackMiddleware/PageCache.php(106): Drupal\Core\StackMiddleware\KernelPreHandle->handle()
#53 /var/www/html/drupal10/web/core/modules/page_cache/src/StackMiddleware/PageCache.php(85): Drupal\page_cache\StackMiddleware\PageCache->pass()
#54 /var/www/html/drupal10/web/core/lib/Drupal/Core/StackMiddleware/ReverseProxyMiddleware.php(48): Drupal\page_cache\StackMiddleware\PageCache->handle()
#55 /var/www/html/drupal10/web/core/lib/Drupal/Core/StackMiddleware/NegotiationMiddleware.php(51): Drupal\Core\StackMiddleware\ReverseProxyMiddleware->handle()
#56 /var/www/html/drupal10/web/core/lib/Drupal/Core/StackMiddleware/AjaxPageState.php(36): Drupal\Core\StackMiddleware\NegotiationMiddleware->handle()
#57 /var/www/html/drupal10/web/core/lib/Drupal/Core/StackMiddleware/StackedHttpKernel.php(51): Drupal\Core\StackMiddleware\AjaxPageState->handle()
#58 /var/www/html/drupal10/web/core/lib/Drupal/Core/DrupalKernel.php(704): Drupal\Core\StackMiddleware\StackedHttpKernel->handle()
#59 /var/www/html/drupal10/web/index.php(19): Drupal\Core\DrupalKernel->handle()
#60 {main}
GuyManDude → created an issue.
GuyManDude → created an issue.
web/themes/custom/infoseciab/infoseciab.info.yml
web/themes/custom/infoseciab/infoseciab.libraries.yml
web/themes/custom/infoseciab/css/iabck5.css
When I remove the comment the display is a mess. See attached screenshot.
I have not touched the minifile. How would I check it?
GuyManDude → created an issue.
GuyManDude → created an issue.
I found and fixed the problem. In my custom theme's info.yml file I had failed to add my custom css declaration under the ckeditor5-stylesheets library like so:
ckeditor5-stylesheets:
- css/ck5style.css
- css/custom.css
GuyManDude → created an issue.
This sounds like it addresses the problem I have. I am trying to capture the 'Current State' value with a field in Views but I cannot find the correct field. The ony field that sounds like it would work is the Moderation State field but that always shows as Active, not one of the states in the particular Workflow I am looking for.
GuyManDude → created an issue.
GuyManDude → created an issue.
GuyManDude → created an issue.
GuyManDude → created an issue.
GuyManDude → created an issue.
Thanks you for your feedback. This approach works for landing pages with fixed paths, but for content which has a path/ it won't work. We need path/* menu links!
Thanks again. I imported the example you have here and it works as noted. However it's not clear how to find the value of the token name. The example uses "mynode" for that token name, but it does not appear to be an arbitrary name. I tried changing the value to something else and the message no longer appears on screen when viewing an article.
From the Load Route Parameter instructions:
Name of token
The name of the token, the parameter value gets stored into.
I used Devel to see if I could find a token called mynode but I could not. Does mynode have special significance to Drupal or ECA?
GuyManDude → created an issue.
Thanks for the prompt feedback. Can you offer a suggestion for a non-coder please? Are there some canned events that fit the bill by chance?
I'm using a Viewed Content Entity as a trigger.
GuyManDude → created an issue.
GuyManDude → created an issue.
GuyManDude → created an issue.
Thank you! You're right, I'm not thinking about this the right way. I was using Cron just as trigger without realizing it provides context. It's an easy way to quickly test a Rule. I assumed adding the Entity as a bundle provided any necessary context. I'm going to play around with Rules again with this new perspective.
BTW, The objective I am trying to accomplish is having nodes (Contracts) with start and expiration date fields that can be up weeks/months/years apart. I planned to use Scheduler to fire off an email say 90 days before the expiration date. The email would link to that contract where a multi-value field called something like 'next reminder' can set a duration like 7, 14 30 days out. When the node is saved Rules would change the expiration date field using the current time and offset by the selected value (7,14,30 etc), and schedule another email to be sent on the new expiration date. This way the Contract owner can get multiple reminders about the expiration in advance of the actual expiration date.
Does this sound doable?
Thanks for responding TR. I'm still struggling. I have attached a screen recording to show you what's going on. Hopefully it will shed some light.
GuyManDude → created an issue.
GuyManDude → created an issue.
@Abyss. Thanks for your feedback. I use this technique on a D7 site with a Bootstrap 3 theme. I am just trying to recreate something close to it on D9/10.
I have no idea how to use that twig template with my Views block. Can I not simply comment out whatever progress bar oriented css the Bootstrap 5 theme applies and use my own css in my own css file?
Thanks again Ravi. The _progress.css file only contains this css:
.progress {
display: block;
height: unset;
overflow: unset;
font-size: unset;
background-color: unset;
}
I tried commenting it out and restarting Apache but it made no difference.
I also tried commenting out the extensive progress section in the /var/www/html/drupal/web/themes/contrib/bootstrap5/css/style.css file and again it made no difference.
At this point I need a little more detailed help please.
Hi Ravi. Thanks for your help. I have attached some screenshots. The orange colored bars you see on the rendered block are the progress bars.
Here is the Views field rewrite code to make it easy to copy and paste.
<div class="progress"><strong>Left PDU: </strong>
<div class="progress-bar iab-warning" role="progressbar" style="width: {{ field_ct_rack_left_pdu }}%" aria-valuenow="{{ field_ct_rack_left_pdu }}" aria-valuemin="0" aria-valuemax="100">{{ field_ct_rack_left_pdu }}</div>
</div>
I gave the Presave method a shot but it did not make any difference.
I installed Easy mail and created a simple template but that didn't fix problem either!
I have attached 2 different models. Both models have actions to send mail using both core and Easy Mail:
core-presave_email.tar.gz - This model uses Presave function.
core-eca_reminder.tar.gz - This model uses Content Update function.
@VladimirAus It only flashes when I am logged in. That's an interesting find!
GuyManDude → created an issue.
I just came across this as a very recent user to D9/10. I deleted a field from a Content Type and it broke the Views that were using it. Very annoying to say the last, but more importantly it's a recipe for disaster. I also found I cannot simply edit the broken View and remove the same field from it to fix it quickly. The old fields are not visible on the View edit page any more!
The View was disabled which was helpful to understand what had happened, but can you not configure it such that a reference to the broken field is still visible allowing easy removable from the Views edit page?
GuyManDude → created an issue.
You'll have to download it to view it. Link
GuyManDude → created an issue.
I added the menu link using the /admin/structure/menu method. It does it regardless of the user I am logged in with.
I am using it in a Views Block.
I am having what I suspect may be the same problem. My progress bars are not rendering correctly. Everything renders at full width so the progress indicator appears to be full etc.
I see VladimirAus commited some code in #2. Does that code fix the problem, and if so, is it scheduled to be included in the next update?
Thanks for your time and thoughts.
For anyone else struggling with this.
After trying various potential fixes using the CKEDITOR.config.allowedContent = true; method to no avail (i don't know the correct file to edit), I edited my subtheme info.yml file and added my own custom stylesheet like so:
ckeditor_stylesheets:
- css/style.css
- css/custom.css
Edit mode looks like view mode now.
GuyManDude → created an issue.
Sorry for the slow response and thanks for following up. I have used this Bootstrap 5 theme on D9 and D10 and in both cases the navbar flashes white and appears to rapidly slide down into place. So far it seems to only affect Chrome/Brave and Opera. Firefox and Edge did not exhibit the same problem.
Mobilewise I have only tested Chrome and Safari and it's fine on either.
When I first noticed this I was on D10 and had done quite a bit of theme customization so I didn't want to jump to conclusions. Since then I have installed in on more than one D10 server and a D9 server and it exhibited the problem immediately after I had added a menu link to the navbar.
GuyManDude → created an issue.
GuyManDude → created an issue.
Thanks for your thoughts. I did clear the caches. The code above is exactly what he used, so I'm guessing there are some other debug tools features I need to enable.
C3 is the one in the pics.
Thanks for following up. The attached diagram has the current chart on the left and the objective chart on the right. I want to be able to have a fixed value on one side (in this case it is a value of 100) and have the bars grow toward the fixed value. The values of the bars will never go over 100 as it represents percent.
Closing this ticket. I have been unable to recreate the problem. Subsequent block creation worked as expected.
GuyManDude → created an issue.
Thanks again Wombat. I'm surprised I wasn't already aware of the Prepopulate module. That looks like it might just be the ticket!
GuyManDude → created an issue.
GuyManDude → created an issue.
GuyManDude → created an issue.
GuyManDude → created an issue.
The #11 patch is not working for my D10 site. It has also rendered Layout Builder for that content type even after uninstalling both Layout Builder and Layout Builder Tabs and reinstalling Layout Builder.
Prior to patch, got this error when clicking Manage Layout:
Warning: Undefined array key "block_id" in __TwigTemplate_4a3fe46f3c0ba04dfda5c592bf4b89f1->doDisplay() (line 173 of sites/default/files/php/twig/6460750b6f7e8_tabs.html.twig_5sroUazadlcoTpU0Pqk4ZMapg/hfLTqiiT0Z2P2C3pwfsvkun2lluC9YVZyTgo32fTQp8.php).
After patch, got this error when clicking Manage Layout:
The website encountered an unexpected error. Please try again later.
Twig\Error\RuntimeError: The callable passed to the "filter" filter must be a Closure in sandbox mode. in twig_check_arrow_in_sandbox() (line 41 of modules/layout_builder_tabs/templates/tabs.html.twig).
This is a band new D10 test site with very little work done on it. I'm using the Bootstrap 5 theme. I tested the Simple Multi Step Form module by creating a new content type with 3 text fields (one for each step). After playing with it for a short while I uninstalled that module and installed Entity Form Steps. I used the same content type and created a couple of new nodes and played with it for a short while. Unfortunately I got this far before noticing the CSS problem.
I uninstalled the Entity Form Steps module but the problems persist even after clearing cache and restarting Apache.
I would like to get the site functional again so I can test both of those modules again paying closer attention this time. I need to use one of these modules, so I want to avoid the module that created this problem of course.
Thanks for your time and thoughts.
I have narrowed my problem down to the default Full HTML Text Format. I created a new Text Format and unchecked all filters and my code rendered fine. I believe the 'Correct faulty and chopped off HTML' setting was probably what was affecting it although I haven't taken the time to do a thorough investigation.
GuyManDude → created an issue.
GuyManDude → created an issue.
GuyManDude → created an issue.
I'm running D10 with 3.0.0 version CSV Serialization via Ludwig. This was the output from the respective CSV, JSON and XML exports
CSV Export
The website encountered an unexpected error. Please try again later.
Error: Call to undefined function League\Csv\bom_match() in League\Csv\AbstractCsv->getInputBOM() (line 229 of modules/csv_serialization/lib/league-csv/v9.6.2/src/AbstractCsv.php).
JSON error
[{"title":"\u003Ca href=\u0022\/node\/8\u0022 hreflang=\u0022en\u0022\u003EWidget 1\u003C\/a\u003E","field_year":"2003","field_number":"11"}]
XML Export:
This XML file does not appear to have any style information associated with it. The document tree is shown below.
Widget 1 ]]>
2003
11
Thanks for your feedback Wombat. Ideally, editing each one of those categories of data would open the node with just the set of data for that category. We can easily break up the Viewing mode by using a tab per category etc, so having an edit mode per tab might be fantastic?