I just noticed that Drupal logotype in the header is different from the logotype in the D7 front page.
BEFORE
AFTER
After a little research, I found the following Drupal Brand Guidelines (which I was not aware of):
https://drupal.widencollective.com/portals/gfvztttq/BrandPortal
These guidelines explain most (if not all) choices made for the design of this new front page. The new logotype, the background patterns, the boxes, the (wierd) design elements, etc., all is defined here.
Being that the case, it seems as if there is no room for much change or improvement to the design itself... sigh...
Anyways, posting for those (who like me) where not aware of these guidelines.
Thatโs how it was before. The new UI was announced at DrupalCon Barcelona and was actually staged already a few weeks before that on new.drupal.org. Everyone was invited to test and post their constructive comments here.
I understand. However, I can't help but wonder why this moved from staging to live in its current state when people are still reporting issues. It's difficult to reconcile the drive to market Drupal to marketers, designers, and content creators with what seems to be a less-than-ideal redesign process and such lenient criteria for going live.
But I digress...
Howdy,
I think we all want to be positive and help here, but this front page with undeniably unfinished design and content is clearly not ready for prime time.
I think we can all agree that doing a redesign exercise on a live site is not recommended good practice.
For the sake of avoiding further damage to the Drupal brand, please consider reverting to the original front page and moving this redesign exercise to a staging page where only those people who want to help make it better can access it.
PC menu updated for enhanced readability: links are in standard case and thus spaced for better clarity.
ilfelice โ created an issue.
Howdy,
This has been changed to "Needs review". Is there a patch that I can test?
Howdy,
Awesome module!
Is this fix included in the latest release (3.0.4/28 August 2024)?
@gbyte
Thank you for the response.
I can see how using views would allow monitoring sitemap settings, and also using ECA to automate inclusion/exclusion in the sitemap upon publishing/unpublishing.
Not a developer, but I am available for testing, so let me know if there is anything I can do to get this going.
Howdy,
Thank you for a great module!
I have a quick question: am I) right to assume that this feature would allow exposing sitemap settings in views?
ilfelice โ created an issue.
Howdy,
Apologies for jumping in here, but is there a version of this module that works with Drupal 10?
Howdy,
Thank you for such an awesome module!
Since patch #19 seems to be working, it would be nice to have a new release. ;)
Thank you!
Howdy,
Even after installing Configuration Translation and related modules in Drupal 10.2.5 or 10.2.6, no webforms are accessible. There was no issue with webform configuration, just when viewing the form equals wsod.
Running Webform 6.2.2 on recently update Drupal core 10.2.5 here, and webforms are working OK.
This is a Japanese site, with more than 7 very different webforms, and none of them show the problem reported here.
Reporting this FWIW.
Howdy,
I have a similar problem where 'drush updb' throws the following error message:
[error] /public://asset_injector/ should have write access.
(Currently using Asset Injector Directory not writableI have verified that the 'asset_injector' directory is in fact writable.
I have moved the public files directory using "$settings['file_public_path']" in settings.php.
I have also configured the assets directory using "$settings['file_assets_path']" in settings.php[1], but this module does not seem to respect this setting.
I wonder if these directory related configurations in settings.php have anything to do with this error message being displayed.
Sharing just in case somebody else is in the same situation.
Howdy,
Just wondering: has this issue been addressed?
Howdy,
Having same error with cache after uninstall.
I uninstalled this module, and am getting the following error message in the content type edit pages:
User warning: The following theme is missing from the file system: node_type_class in Drupal\Core\Extension\ExtensionPathResolver->getPathname() (line 63 of core/lib/Drupal/Core/Extension/ExtensionPathResolver.php).
Is this related or should I report separately?
Howdy,
First of all, thank you very much for this very useful module.
I am getting a similar error message (shown below) when I try save a view to which I am trying to add an exposed filter for a webform Entity select field.
InvalidArgumentException: The configuration property display.block_2.display_options.filters.webform_submission_value.value.all doesn't exist. in Drupal\Core\Config\Schema\ArrayElement->get() (line 76 of core/lib/Drupal/Core/Config/Schema/ArrayElement.php).
I can provide any additional information that may be needed to look into this issue.
Regards,
Howdy,
Thank you for this great module!
Just wanted to let you know that adding the license URL line to tiny_slider.libraries.yml as noted here did in fact make the warning message go away.
Since this fix is working, it would be nice if a new version of the module with this change to tiny_slider.libraries.yml would be released, so that sites can update. ;)
Cheers!
ilfelice โ created an issue.
Hello @viren18febs!
Thank you for the fast response.
I don't have my dev PC at hand, so have not actually tried the patch.
But looking at it, and being as simple as it is, I think it patch is good to go.
Have a happy new year!
Howdy,
I realize this is a very old ticket, but just wanted to say that this issue also exists when using this module in Drupal 10.
FWIW, when using the Viewfield module ( https://www.drupal.org/project/viewfield โ ), the contextual links are displayed as expected, so it does not seem to be permissions-related issue.
Should I file a separate ticket for Drupal 10? Please advise.
ilfelice โ created an issue.
Howdy,
Quick follow up on this issue.
After updating my Drupal installation to 10.1.5, the rename link disappeared from the form widget.
Since I am using a Bootstrap 3 subtheme, I resorted to modifying the Boostrap 3 image-widget.html.twig template in the subtheme.
Specifically, I changed the line
{{ data|without('preview') }}
to
{{ element|without('preview') }}
Now the rename link is back, not in the ideal position (above the file link), but otherwise working fine, as in, serving its purpose.
Thought I would share in case it helps anyone else.
Howdy,
FWIW, patch #2 works here too. Drupal 10.1.5 here.
Would be really nice to have a release with this patch. ;)
ilfelice โ created an issue.
Howdy,
Just wanted to let you all know that I upgraded 3 sites from Drupal 9.5 to 10, and Webform 6.2 is working like a charm in all of them.
Great work! Many thanks!
Thank you so much for this awesome module!
I would like to add my vote for a D10 compatible release.
Thank you!
douggreen, thank you for the fix!
Howdy,
Applied #3 patch, and error is gone.
Howdy,
Patch from #26 applied cleanly on a Drupal 10.1 install with newly installed viewsreference 2.0-beta6.
After applying the patch, the error is gone.
@taggartj
Awesome! Thank you so much!
Howdy,
First and foremost, thank you for this great module!
FWIW, I tested the patch in a D10 installation, and it worked as expected.
Would be nice to have a new release. ;)
Howdy,
Tested on Drupal 10.1.0 installation. Patch works. Would be nice to have a new release. ;)
ilfelice โ created an issue.
Howdy,
I tested the solution (workaround?) proposed by @jdhildeb, and it worked, as in, the "Rename" button was displayed.
This was on a Drupal 10 installation using the Bootstrap 3 theme.
FWYW
Howdy,
I tried the workaround noted in #12, but it did not work. I still get the following error when CSS/JS aggregation is enabled:
Error: Class "Drupal\bootstrap\Bootstrap" not found in include_once() (line 31 of /var/www/html/web/themes/contrib/bootstrap/bootstrap.theme).
The theme does work fine when CSS/JS aggregation is disabled. FWIW, my running environment is as follows:
- Drupal 10.1.0
- Ubuntu 22.04 server
- Apache/2.4.52
- PHP version 8.1.20
- Bootstrap 3 theme + sub-theme
Howdy,
After applying the patch in #2, the module installs and works as expected in Drupal 10.
Hi douggreen,
Thank you so much for the clarification.
I will look into the Perimeter module. Thanks for the info.
Drupal 7 EoL Extended by 14 Months; Announcement at DrupalCon Pittsburgh
https://www.thedroptimes.com/31878/drupal-7-end-life-date-extended
Howdy,
FWIW, I am using the dev version in a Drupal 10 installation, and it works fine.
ilfelice โ created an issue.
ilfelice โ created an issue.
Howdy,
Please ignore messages #11 and #12.
It turns out the problem was being caused by the twig debug mode which was on (true). If I turn off the twig debug mode, all is well.
Sorry for the noise!
Howdy,
After updating Drupal to version 10.0.9, now I am seeing the following error message in the log every time I load a page with a flipped table view.
Warning: Drupal\views\Plugin\ViewsHandlerManager->getHandler() ๅ
Undefined array key "id" (/var/www/html/web/core/modules/views/src/Plugin/ViewsHandlerManager.php ใฎ 104 ่ก็ฎ)
#0 /var/www/html/web/core/includes/bootstrap.inc(158): _drupal_error_handler_real()
#1 /var/www/html/web/core/modules/views/src/Plugin/ViewsHandlerManager.php(104): _drupal_error_handler()
#2 /var/www/html/web/core/modules/views/src/Plugin/views/display/DisplayPluginBase.php(898): Drupal\views\Plugin\ViewsHandlerManager->getHandler()
#3 /var/www/html/web/core/modules/views/src/ViewExecutable.php(1055): Drupal\views\Plugin\views\display\DisplayPluginBase->getHandlers()
#4 /var/www/html/web/core/modules/views/src/ViewExecutable.php(913): Drupal\views\ViewExecutable->_initHandler()
#5 /var/www/html/web/core/modules/views/src/Plugin/views/display/DisplayPluginBase.php(2328): Drupal\views\ViewExecutable->initHandlers()
#6 /var/www/html/web/core/modules/views/src/ViewExecutable.php(1707): Drupal\views\Plugin\views\display\DisplayPluginBase->preExecute()
#7 /var/www/html/web/core/modules/views/src/ViewExecutable.php(1642): Drupal\views\ViewExecutable->preExecute()
#8 /var/www/html/web/core/modules/views/src/Element/View.php(81): Drupal\views\ViewExecutable->executeDisplay()
#9 /var/www/html/web/core/modules/views/src/Plugin/Block/ViewsBlock.php(59): Drupal\views\Element\View::preRenderViewElement()
#10 /var/www/html/web/core/modules/block/src/BlockViewBuilder.php(171): Drupal\views\Plugin\Block\ViewsBlock->build()
#11 [internal function]: Drupal\block\BlockViewBuilder::preRender()
#12 /var/www/html/web/core/lib/Drupal/Core/Security/DoTrustedCallbackTrait.php(101): call_user_func_array()
#13 /var/www/html/web/core/lib/Drupal/Core/Render/Renderer.php(788): Drupal\Core\Render\Renderer->doTrustedCallback()
#14 /var/www/html/web/core/lib/Drupal/Core/Render/Renderer.php(374): Drupal\Core\Render\Renderer->doCallback()
#15 /var/www/html/web/core/lib/Drupal/Core/Render/Renderer.php(446): Drupal\Core\Render\Renderer->doRender()
#16 /var/www/html/web/core/lib/Drupal/Core/Render/Renderer.php(204): Drupal\Core\Render\Renderer->doRender()
#17 /var/www/html/web/core/lib/Drupal/Core/Template/TwigExtension.php(477): Drupal\Core\Render\Renderer->render()
#18 /var/www/html/web/sites/default/files/php/twig/6466be4b1ebc9_page--components_manufact_T0Ace7Zkaf5L0NKUCfYUqp3Zt/kxKrdOEsTg6kOn5cPGHLnnVYaGb_H_hVTaBo4F3H8fE.php(472): Drupal\Core\Template\TwigExtension->escapeFilter()
#19 /var/www/html/vendor/twig/twig/src/Template.php(171): __TwigTemplate_bc1f41ca18894907eeb05d98e2dc92ec->block_content()
#20 /var/www/html/web/sites/default/files/php/twig/6466be4b1ebc9_page--components_manufact_T0Ace7Zkaf5L0NKUCfYUqp3Zt/kxKrdOEsTg6kOn5cPGHLnnVYaGb_H_hVTaBo4F3H8fE.php(367): Twig\Template->displayBlock()
#21 /var/www/html/vendor/twig/twig/src/Template.php(171): __TwigTemplate_bc1f41ca18894907eeb05d98e2dc92ec->block_main()
#22 /var/www/html/web/sites/default/files/php/twig/6466be4b1ebc9_page--components_manufact_T0Ace7Zkaf5L0NKUCfYUqp3Zt/kxKrdOEsTg6kOn5cPGHLnnVYaGb_H_hVTaBo4F3H8fE.php(110): Twig\Template->displayBlock()
#23 /var/www/html/vendor/twig/twig/src/Template.php(394): __TwigTemplate_bc1f41ca18894907eeb05d98e2dc92ec->doDisplay()
#24 /var/www/html/vendor/twig/twig/src/Template.php(367): Twig\Template->displayWithErrorHandling()
#25 /var/www/html/vendor/twig/twig/src/Template.php(379): Twig\Template->display()
#26 /var/www/html/vendor/twig/twig/src/TemplateWrapper.php(40): Twig\Template->render()
#27 /var/www/html/web/core/themes/engines/twig/twig.engine(53): Twig\TemplateWrapper->render()
#28 /var/www/html/web/core/lib/Drupal/Core/Theme/ThemeManager.php(372): twig_render_template()
#29 /var/www/html/web/core/lib/Drupal/Core/Render/Renderer.php(433): Drupal\Core\Theme\ThemeManager->render()
#30 /var/www/html/web/core/lib/Drupal/Core/Render/Renderer.php(204): Drupal\Core\Render\Renderer->doRender()
#31 /var/www/html/web/core/lib/Drupal/Core/Template/TwigExtension.php(477): Drupal\Core\Render\Renderer->render()
#32 /var/www/html/web/sites/default/files/php/twig/6466be4b1ebc9_html.html.twig_Ka2CKnUuRjIWvq8m1_Z34FfnV/STr8220A83s7AN-wFG46ESNJfH0O-I-RtGhaxdhf55o.php(86): Drupal\Core\Template\TwigExtension->escapeFilter()
#33 /var/www/html/vendor/twig/twig/src/Template.php(394): __TwigTemplate_4c4cef7beb6adcb805587690c974adbd->doDisplay()
#34 /var/www/html/vendor/twig/twig/src/Template.php(367): Twig\Template->displayWithErrorHandling()
#35 /var/www/html/vendor/twig/twig/src/Template.php(379): Twig\Template->display()
#36 /var/www/html/vendor/twig/twig/src/TemplateWrapper.php(40): Twig\Template->render()
#37 /var/www/html/web/core/themes/engines/twig/twig.engine(53): Twig\TemplateWrapper->render()
#38 /var/www/html/web/core/lib/Drupal/Core/Theme/ThemeManager.php(372): twig_render_template()
#39 /var/www/html/web/core/lib/Drupal/Core/Render/Renderer.php(433): Drupal\Core\Theme\ThemeManager->render()
#40 /var/www/html/web/core/lib/Drupal/Core/Render/Renderer.php(204): Drupal\Core\Render\Renderer->doRender()
#41 /var/www/html/web/core/lib/Drupal/Core/Render/MainContent/HtmlRenderer.php(158): Drupal\Core\Render\Renderer->render()
#42 /var/www/html/web/core/lib/Drupal/Core/Render/Renderer.php(580): Drupal\Core\Render\MainContent\HtmlRenderer->Drupal\Core\Render\MainContent\{closure}()
#43 /var/www/html/web/core/lib/Drupal/Core/Render/MainContent/HtmlRenderer.php(159): Drupal\Core\Render\Renderer->executeInRenderContext()
#44 /var/www/html/web/core/lib/Drupal/Core/EventSubscriber/MainContentViewSubscriber.php(90): Drupal\Core\Render\MainContent\HtmlRenderer->renderResponse()
#45 [internal function]: Drupal\Core\EventSubscriber\MainContentViewSubscriber->onViewRenderArray()
#46 /var/www/html/web/core/lib/Drupal/Component/EventDispatcher/ContainerAwareEventDispatcher.php(111): call_user_func()
#47 /var/www/html/vendor/symfony/http-kernel/HttpKernel.php(168): Drupal\Component\EventDispatcher\ContainerAwareEventDispatcher->dispatch()
#48 /var/www/html/vendor/symfony/http-kernel/HttpKernel.php(74): Symfony\Component\HttpKernel\HttpKernel->handleRaw()
#49 /var/www/html/web/core/lib/Drupal/Core/StackMiddleware/Session.php(58): Symfony\Component\HttpKernel\HttpKernel->handle()
#50 /var/www/html/web/core/lib/Drupal/Core/StackMiddleware/KernelPreHandle.php(48): Drupal\Core\StackMiddleware\Session->handle()
#51 /var/www/html/web/core/modules/page_cache/src/StackMiddleware/PageCache.php(106): Drupal\Core\StackMiddleware\KernelPreHandle->handle()
#52 /var/www/html/web/core/modules/page_cache/src/StackMiddleware/PageCache.php(85): Drupal\page_cache\StackMiddleware\PageCache->pass()
#53 /var/www/html/web/core/modules/ban/src/BanMiddleware.php(50): Drupal\page_cache\StackMiddleware\PageCache->handle()
#54 /var/www/html/web/core/lib/Drupal/Core/StackMiddleware/ReverseProxyMiddleware.php(48): Drupal\ban\BanMiddleware->handle()
#55 /var/www/html/web/core/lib/Drupal/Core/StackMiddleware/NegotiationMiddleware.php(51): Drupal\Core\StackMiddleware\ReverseProxyMiddleware->handle()
#56 /var/www/html/web/core/lib/Drupal/Core/StackMiddleware/StackedHttpKernel.php(51): Drupal\Core\StackMiddleware\NegotiationMiddleware->handle()
#57 /var/www/html/web/core/lib/Drupal/Core/DrupalKernel.php(686): Drupal\Core\StackMiddleware\StackedHttpKernel->handle()
#58 /var/www/html/web/index.php(19): Drupal\Core\DrupalKernel->handle()
#59 {main}Should I file a separate bug report?
Howdy,
Sorry to bring this issue back, but I have upgraded the site I am developing to Drupal 10, and even with the same settings ("Hide Empty Column" in the Flipped Table formatter settings, and "Hide if empty" in the field's setting) the empty rows are now shown.
I have made sure that the cache is flushed, even turned off the cache in the view itself, but the problem persists. Attaching screenshot for reference.
By the way, there is nothing of interest in the Drupal log.
Any ideas of what may be causing this?
Thank you in advance!
Howdy,
After applying the patch in #7, I can install the module in Drupal 10, and confirm that it works as expected.
Howdy,
The module patched with #4 works. I was able to add the block and use the popup as intended by the module.
Thank you for such a fast response!
jorgemare โ created an issue.
Howdy,
For what it's worth, after applying the patch in #99 to a Drupal 10.0.8 installation, the errors are gone and the (file) relationships work as expected in my views.
Thank you @KarlShea!
Howdy,
I was able to install the patched module in Drupal 10.0.8, and can confirm that it works as expected.
It would be nice to have a new release so that it can be installed properly using composer. ;)
Howdy,
I can confirm that the patched module installs and works as expected in Drupal 10.
@apadermo,
Thank you for the reply and clarification.
Feel free to close this issues if deemed appropriate.
Hi @mparker!
Thank you so much for the detailed explanation. I totally understand!
If/when at some point you make progress and need testing, here I am to give a hand. ;)
Howdy,
I tried to install 2.0.x-dev in a Drupal 9.5 test setup running on PHP 8.1, with the following results:
Your requirements could not be resolved to an installable set of packages.
Problem 1
- drupal/blocked_ips_expire dev-2.0.x requires drupal/core ^10 -> found drupal/core[10.0.0, 10.0.1, 10.0.2, 10.0.3] but the package is fixed to 9.5.3 (lock file version) by a partial update and that version does not match. Make sure you list it as an a rgument for the update command.
- drupal/blocked_ips_expire 2.0.x-dev is an alias of drupal/blocked_ips_expire dev-2.0.x and thus requires it to be installe d too.
- Root composer.json requires drupal/blocked_ips_expire 2.0.x-dev@dev -> satisfiable by drupal/blocked_ips_expire[2.0.x-dev (alias of dev-2.0.x)].
I can do more testing if necessary, so just let me know via reply.
jorgemare โ created an issue.