Greetings @berramou,
Thank you very much for taking care of this bug report and also for fixing it in the next release.
In the meantime, I modified line 522 of the leaflet_more_maps.module file and I confirm the bug is fixed.
I am fond of this map provider and your help is more than welcome.
Thank you @naveenvalecha
Greetings Ravi,
The method you suggest is indeed an easy way to spot the differences between various versions of a theme (or a module). Thank you very much!
Best regards,
Gilles
The same situation occurs on another D11.1.0 instance: the OpenTopoMap tiles are not displayed on a mobile device nor on an emulated mobile device.
Greetings Chris,
You may hopefully have a look at a related issue which needs testing and where you expertise is more than welcome:
Add support for enclosure field in Views RssFields row plugin so that posts can include media items
✨
Add support for enclosure field in Views RssFields row plugin so that posts can include media items
Needs work
Best regards,
Gilles
Greetings,
The D10 release of this module has achieved impressive results. Thank you very much.
Do you plan to commit a D11 release?
Best regards,
Gilles
On the original instance in French, the post_max-size in php.ini was set to 40MB. The new instance has upgraded this value to 128MB.
Here is the error on the original D11 instance in French. Afterwards, I created another D11 instance in English, only to fix this error.
The error is likely not from the server but from Drupal. And there are no error in the logs.
Greetings,
@naveenvalecha's blog post begins with an example of a custom meta tag:
<link rel="alternate" type="application/rss+xml" href="https://example.com/rss.xml">
The blog post continues with a custom meta tag added through the metatag_custom_tags module:
<meta name="sitename" content="Custom Meta Tag - Demo Site">
To my understanding, the metatag_custom_tags module currently allows two attributes and not three as mentioned in the first example.
Here is the custom meta tag I would like to create:
<link rel="icon" type="image/svg+xml" href="/favicon.svg" />
Here are the informations implemented in /admin/config/search/metatag/custom-tags/icon:
- Name: icon
- Description: SVG favicon
- HTML element: Link
- Attribute name: Rel
- Value attribute: Href
Adding the value /favicon.svg in the custom tags field, this generates the following custom tag:
<meta rel="icon" href="/favicon.svg" />
How do I add the type="image/svg+xml" attribute in the custom tags field? Not with a comma because this generates two custom tags. Neither with a pipe: I tried numerous possibilities and none worked.
Please tell me how to add the type="image/svg+xml" attribute. Thank you.
Found the solution: you uninstall all the submodules and reinstall them afterwards and then it works. But I notice that /admin/config/search/metatag/add becomes slower the more you add submodules.
The more submodules you add, the slower /admin/config/search/metatag/add is.
gillesbailleux → created an issue.
Greetings Drupalistas,
Full kudos to the persons who made such a fresh and beautiful layout. I am fond of the menu and the content presented is really attractive.
Please allow me a constructive criticism: there are no schema types, few Open Graph tags, no Twitter Cards Markup Tag and the HTML headings are not creative.
This is probably an issue in the pipe.
The metatag → and schema_metatag → modules are among the best assets of Drupal. Let's use these modules to broaden the visibility of the Drupal project.
The leaflet_more_markers 1.1.3 release has been tested on a live Drupal 11 instance and the module works as designed.
Thank you to @itamair for committing this D11 compatible version.
gillesbailleux → created an issue.
The composer update -W command has installed the latest Twig version: v3.14.2.
I notice that nodes and blocks are now editable.
Many thanks to @mradcliffe for the tremendous support on this issue.
Thank you very much @mradcliffe
@mradcliffe: nothing can be done from the Drupal community so I guess the Symfony community will fix this.
The Symfony founder and project lead posted this:
https://github.com/twigphp/Twig/security/advisories/GHSA-6377-hfv9-hqf6
@mradcliffe: the infinite loop you spotted can only by fixed by the twig maintainer, right?
Increasing the PHP APCu memory from 32 to 350 MB does not solve the problem.
@raphaelbertrand: when trying to edit a block which does not use ckeditor5, the same blank page appears.
@raphaelbertrand: any advice to increase PHP memory? If yes, where?
Same blank page appears when updating a block.
Removing the drupal/twig_tweak (3.4.0) module does not solve the problem.
Problem is related only to twig because the very same problem occurs on another website when updating v3.14.0 => v3.14.1
otheruser@otherserver:~/public_html$ composer update -W
Loading composer repositories with package information
Updating dependencies
Lock file operations: 0 installs, 1 update, 0 removals
- Upgrading twig/twig (v3.14.0 => v3.14.1)
Writing lock file
Installing dependencies from lock file (including require-dev)
Package operations: 0 installs, 1 update, 0 removals
- Downloading twig/twig (v3.14.1)
- Upgrading twig/twig (v3.14.0 => v3.14.1): Extracting archive
Generating autoload files
47 packages you are using are looking for funding.
Use the `composer fund` command to find out more!
gillesbailleux → created an issue.
@anybody: sorry for my late answer. I am not sure to understand what I have to do.
D10.3.5 solves the isssue I raised.
"This release reverts
🐛
Fix null $cid in CacheCollector classes
RTBC
, released in 10.3.4, which conflicted with Menu Trail by Path, Entity Manager and Gin Toolbar modules."
Thank you such much for this fixed issue!
As mentioned by smustgrave on Slack, there is no relation between the Book breadcrumb cacheability issue and the Bootstrap menu issue because the website does not have the Book module activated.
Hello,
Since updating from D10.3.3 to D10.3.4, the nav-item active
class of the menu is only active on the homepage. I looked in the changes of the release and found this book breadcrumb related issue. The website uses the bootstrap_barrio 5.5.17 theme and the menu was working just fine before the update.
Regards,
Gilles
Greetings agnesliu,
After each new release of the Barrio Bootstrap 5 theme, I use an Open Source software called Kompare in order to see if there are any changes in the subtheme. As you can see in the attachment, there are no changes in the update from 5.5.16 to 5.5.17.
If you see that your custom subtheme still uses 5.5.16, this is normal because your custom subtheme was created from the 5.5.16 release. As mentioned in the documentation → , it is recommended to delete the information added by the Drupal.org packaging script in the yourtheme.info.yml file. This will prevent the issue you have raised here.
If an upcoming release of Barrio offers enhancements in the subtheme because you spotted them with Kompare, it might be useful to update your subtheme.
Finally, if you want to keep an eye on all the requests addressed to the maintainer of this theme, please visit this page.
Best regards,
Gilles
Please pardon me to reopen this issue but the very same problem is back when creating an event with a free entrance fee. When trying to put a zero for the price, the value does not appear in the source code.
The D10.3.1 website uses PHP 8.3.9 and it is equipped with the schema_metatag 3.0.2 release.
Patch #8 does not fix the problem
gilloteaux@ct822-drupal:~/public_html/web/modules/contrib/schema_metatag$ wget
https://www.drupal.org/files/issues/2024-07-16/schema_metatag-n3461565-8... →
--2024-07-16 16:29:17--
https://www.drupal.org/files/issues/2024-07-16/schema_metatag-n3461565-8... →
Resolving www.drupal.org (www.drupal.org)... 151.101.38.217
Connecting to www.drupal.org (www.drupal.org)|151.101.38.217|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1445 (1.4K) [text/plain]
Saving to: ‘schema_metatag-n3461565-8.patch’
schema_metatag-n3461565-8.patch 100%[================================================================================================================>] 1.41K --.-KB/s in 0s
2024-07-16 16:29:17 (34.5 MB/s) - ‘schema_metatag-n3461565-8.patch’ saved [1445/1445]
gilloteaux@ct822-drupal:~/public_html/web/modules/contrib/schema_metatag$
Working on a live site, which patch do I have to apply?
Hi,
Because all my nodes use the schema_metatag module, I have the same problem sitewide. On this D10.3.1 website, the PHP version is 8.3.9.
TypeError: Cannot access offset of type string on string in Drupal\Core\Render\Renderer->doRender() (line 318 of /home/gilloteaux/public_html/web/core/lib/Drupal/Core/Render/Renderer.php).
#0 /home/gilloteaux/public_html/web/core/lib/Drupal/Core/Render/Renderer.php(248): Drupal\Core\Render\Renderer->doRender()
#1 /home/gilloteaux/public_html/web/core/lib/Drupal/Core/Render/Renderer.php(165): Drupal\Core\Render\Renderer->render()
#2 /home/gilloteaux/public_html/web/core/lib/Drupal/Core/Render/Renderer.php(638): Drupal\Core\Render\Renderer->Drupal\Core\Render\{closure}()
#3 /home/gilloteaux/public_html/web/core/lib/Drupal/Core/Render/Renderer.php(164): Drupal\Core\Render\Renderer->executeInRenderContext()
#4 /home/gilloteaux/public_html/web/core/lib/Drupal/Core/Render/Renderer.php(174): Drupal\Core\Render\Renderer->renderInIsolation()
#5 /home/gilloteaux/public_html/web/modules/contrib/schema_metatag/src/Plugin/schema_metatag/PropertyType/BreadcrumbList.php(125): Drupal\Core\Render\Renderer->renderPlain()
#6 /home/gilloteaux/public_html/web/modules/contrib/schema_metatag/src/Plugin/schema_metatag/PropertyType/ItemListElement.php(48): Drupal\schema_metatag\Plugin\schema_metatag\PropertyType\BreadcrumbList->getItems()
#7 /home/gilloteaux/public_html/web/modules/contrib/schema_metatag/src/Plugin/schema_metatag/PropertyType/BreadcrumbList.php(94): Drupal\schema_metatag\Plugin\schema_metatag\PropertyType\ItemListElement->outputValue()
#8 /home/gilloteaux/public_html/web/modules/contrib/schema_metatag/src/Plugin/metatag/Tag/SchemaNameBase.php(206): Drupal\schema_metatag\Plugin\schema_metatag\PropertyType\BreadcrumbList->outputValue()
#9 /home/gilloteaux/public_html/web/modules/contrib/schema_metatag/src/Plugin/metatag/Tag/SchemaNameBase.php(179): Drupal\schema_metatag\Plugin\metatag\Tag\SchemaNameBase->outputValue()
#10 /home/gilloteaux/public_html/web/modules/contrib/metatag/src/MetatagManager.php(634): Drupal\schema_metatag\Plugin\metatag\Tag\SchemaNameBase->output()
#11 /home/gilloteaux/public_html/web/modules/contrib/metatag/src/MetatagManager.php(564): Drupal\metatag\MetatagManager->generateRawElements()
#12 /home/gilloteaux/public_html/web/modules/contrib/metatag/metatag.module(504): Drupal\metatag\MetatagManager->generateElements()
#13 /home/gilloteaux/public_html/web/modules/contrib/metatag/metatag.module(131): metatag_get_tags_from_route()
#14 /home/gilloteaux/public_html/web/core/lib/Drupal/Core/Render/MainContent/HtmlRenderer.php(311): metatag_page_attachments()
#15 /home/gilloteaux/public_html/web/core/lib/Drupal/Core/Extension/ModuleHandler.php(395): Drupal\Core\Render\MainContent\HtmlRenderer->Drupal\Core\Render\MainContent\{closure}()
#16 /home/gilloteaux/public_html/web/core/lib/Drupal/Core/Render/MainContent/HtmlRenderer.php(308): Drupal\Core\Extension\ModuleHandler->invokeAllWith()
#17 /home/gilloteaux/public_html/web/core/lib/Drupal/Core/Render/MainContent/HtmlRenderer.php(285): Drupal\Core\Render\MainContent\HtmlRenderer->invokePageAttachmentHooks()
#18 /home/gilloteaux/public_html/web/core/lib/Drupal/Core/Render/Renderer.php(638): Drupal\Core\Render\MainContent\HtmlRenderer->Drupal\Core\Render\MainContent\{closure}()
#19 /home/gilloteaux/public_html/web/core/lib/Drupal/Core/Render/MainContent/HtmlRenderer.php(284): Drupal\Core\Render\Renderer->executeInRenderContext()
#20 /home/gilloteaux/public_html/web/core/lib/Drupal/Core/Render/MainContent/HtmlRenderer.php(128): Drupal\Core\Render\MainContent\HtmlRenderer->prepare()
#21 /home/gilloteaux/public_html/web/core/lib/Drupal/Core/EventSubscriber/MainContentViewSubscriber.php(90): Drupal\Core\Render\MainContent\HtmlRenderer->renderResponse()
#22 [internal function]: Drupal\Core\EventSubscriber\MainContentViewSubscriber->onViewRenderArray()
#23 /home/gilloteaux/public_html/web/core/lib/Drupal/Component/EventDispatcher/ContainerAwareEventDispatcher.php(111): call_user_func()
#24 /home/gilloteaux/public_html/vendor/symfony/http-kernel/HttpKernel.php(186): Drupal\Component\EventDispatcher\ContainerAwareEventDispatcher->dispatch()
#25 /home/gilloteaux/public_html/vendor/symfony/http-kernel/HttpKernel.php(76): Symfony\Component\HttpKernel\HttpKernel->handleRaw()
#26 /home/gilloteaux/public_html/web/core/lib/Drupal/Core/StackMiddleware/Session.php(53): Symfony\Component\HttpKernel\HttpKernel->handle()
#27 /home/gilloteaux/public_html/web/core/lib/Drupal/Core/StackMiddleware/KernelPreHandle.php(48): Drupal\Core\StackMiddleware\Session->handle()
#28 /home/gilloteaux/public_html/web/core/lib/Drupal/Core/StackMiddleware/ContentLength.php(28): Drupal\Core\StackMiddleware\KernelPreHandle->handle()
#29 /home/gilloteaux/public_html/web/core/modules/big_pipe/src/StackMiddleware/ContentLength.php(32): Drupal\Core\StackMiddleware\ContentLength->handle()
#30 /home/gilloteaux/public_html/web/core/modules/page_cache/src/StackMiddleware/PageCache.php(191): Drupal\big_pipe\StackMiddleware\ContentLength->handle()
#31 /home/gilloteaux/public_html/web/core/modules/page_cache/src/StackMiddleware/PageCache.php(128): Drupal\page_cache\StackMiddleware\PageCache->fetch()
#32 /home/gilloteaux/public_html/web/core/modules/page_cache/src/StackMiddleware/PageCache.php(82): Drupal\page_cache\StackMiddleware\PageCache->lookup()
#33 /home/gilloteaux/public_html/web/core/lib/Drupal/Core/StackMiddleware/ReverseProxyMiddleware.php(48): Drupal\page_cache\StackMiddleware\PageCache->handle()
#34 /home/gilloteaux/public_html/web/core/lib/Drupal/Core/StackMiddleware/NegotiationMiddleware.php(51): Drupal\Core\StackMiddleware\ReverseProxyMiddleware->handle()
#35 /home/gilloteaux/public_html/web/core/lib/Drupal/Core/StackMiddleware/AjaxPageState.php(36): Drupal\Core\StackMiddleware\NegotiationMiddleware->handle()
#36 /home/gilloteaux/public_html/web/core/lib/Drupal/Core/StackMiddleware/StackedHttpKernel.php(51): Drupal\Core\StackMiddleware\AjaxPageState->handle()
#37 /home/gilloteaux/public_html/web/core/lib/Drupal/Core/DrupalKernel.php(741): Drupal\Core\StackMiddleware\StackedHttpKernel->handle()
#38 /home/gilloteaux/public_html/web/index.php(19): Drupal\Core\DrupalKernel->handle()
#39 {main}
@Anybody: the patch has been successfully applied on two websites through two manners. It has been programmatically applied on a live site thanks to the help of Didier Misson → and manually applied by me on a test website.
Two comma separated values have been added to the "See also" field and the two values are in the source code.
Thank you very much and greetings from Belgium.
In the related content, a sentence is unfinished:
"This is a Barrio → subtheme that simp"
Greetings,
Allowing multiple comma separated values to the og:see_also
tag would be a nice feature for the upcoming metatag 2.x release.
Thank you once again for this module.
@stevieb: because of the complexity of this issue, the maintainers need support from Drupalistas contributing on Drupal core. I think in particular about Mike Herchel → to fix this issue. Joris (@borisson_), who contributed to this issue, knows him personally and could hopefully get in touch with him and ask for help.
Using simple_sitemap 4.1.8 on a D10.2.3 instance equipped with PHP 8.3.2, a similar error appears:
TypeError : Drupal\simple_sitemap\Plugin\simple_sitemap\UrlGenerator\EntityUrlGeneratorBase::getEntityImageData(): Argument #1 ($entity) must be of type Drupal\Core\Entity\ContentEntityInterface, Drupal\webform\Entity\Webform given, called in /home/dev-website/public_html/web/modules/contrib/simple_sitemap/src/Plugin/simple_sitemap/UrlGenerator/EntityMenuLinkContentUrlGenerator.php on line 232 in Drupal\simple_sitemap\Plugin\simple_sitemap\UrlGenerator\EntityUrlGeneratorBase->getEntityImageData() (/home/dev-website/public_html/web/modules/contrib/simple_sitemap/src/Plugin/simple_sitemap/UrlGenerator/EntityUrlGeneratorBase.php line 274)
Please pardon me to reopen this issue but the Lighthouse accessibility warning is back using a subtheme powered by bootstrap_barrio 5.5.16. More
@DrupalBubb: awaiting an answser from @TR and @ipwa to give @rajab-natshah co-maintainer credentials.
https://www.drupal.org/project/votingapi_widgets/issues/3414710
📌
Offering to co-maintain Voting API Widgets
Needs review
@TR: the #42 patch has been reviewed & tested by the community. Please commit a release with it.
This project is no more supported. Can the maintainers explain why?
@TR: please commit a release with patch #42. Thank you very much.
John Cook → credited gillesbailleux → .
@erdm: let's hope a D10 release will soon be available
@erdm: please pardon me for asking but are you sure you tested the patch with Drupal 10? Just asking because there is no Drupal 10 release of this module.
I did not see you renamed the issue, Damien. This is very kind of you, thank you very much.
No doubt you can add up to 4 URLs; if needed, I currently add them via a twig file.
gillesbailleux → created an issue.
Thank you to the contributors. Please @TR have a look at the patches a commit a D10 compatible release.
@TR could you please consider to validate patch #11 to commit a D10 compatible release?
@klemendev: it would be indeed very nice to have a 2.0.0-alpha2 release with your working patch. Hopefully @mikeohara will commit it, or another maintainer. Much respect for your time maintaining this very useful module.
Thank you very much to Tim Rohaly for the 8.x-3.0-beta4 release which is D10 compatible.
Thank you very much, Mike!