Turns out the routing error was caused by a custom module.
I also have that issue.
Any ideas how to manage this by something that is no ta patch and without losing the data?
Maybe this helps?
https://www.drupal.org/project/search_api_sorts →
Allows sorting by date and some other criterias.
Ok this is related to
💬
Silence the warnings: An overlong word (more than 50 characters) ...
Needs work
Disabling tokenizer solved the problem. So the problem is on search api side.
Maintainers can please close it if it is not important for facet api.
duplicate of 💬 Instructions for clean install on Drupal 10/11 website Active
Hi yan,
thank you for the info.
The D9 version of Sanduhrs will work on D10 with the patches by the update-bot. I already tested that.
This is php only. So you get the php kit.
Done in the latest dev 2.x
Ok i am back on the module.
I will fix that in the next hour and upload the dev. I use the dev in production. You can use it too.
I can confirm that in 6.x. Path works. Thank you for the fix.
Hi castor-designs
Ok, thank you for reporting. I am currently updating my sites to 10/11 too. Will take a look at this in the next days if i find time. Otherwise, i will be back on the projects on january 2nd.
Here are the docs: https://www.drupal.org/node/1913724 →
I think his problem is the new SDC. I currently struggle with that too. SDC makes it heavy complex.
In a subtheme you already have templates/page with two files page.html.twig and page--front.html.twog
Attention: If you delete page--front it will use the starterkits template file
You can edit the page or page--front and add your region there like this:
{% block page_head_right %}
{% if page.page_head_right %}
{{ page.page_head_right }}
{% endif %}
{% endblock %}But be careful that you override the core radix page like this. In my case i have copied over the contents of that file and added my regions, Example:
{#
/**
* @file
* Theme override to display a single page.
*
* The doctype, html, head and body tags are not in this template. Instead they
* can be found in the html.html.twig template in this directory.
*
* Available variables:
*
* General utility variables:
* - base_path: The base URL path of the Drupal installation. Will usually be
* "/" unless you have installed Drupal in a sub-directory.
* - is_front: A flag indicating if the current page is the front page.
* - logged_in: A flag indicating if the user is registered and signed in.
* - is_admin: A flag indicating if the user has permission to access
* administration pages.
*
* Site identity:
* - front_page: The URL of the front page. Use this instead of base_path when
* linking to the front page. This includes the language domain or prefix.
*
* Page content (in order of occurrence in the default page.html.twig):
* - node: Fully loaded node, if there is an automatically-loaded node
* associated with the page and the node ID is the second argument in the
* page's path (e.g. node/12345 and node/12345/revisions, but not
* comment/reply/12345).
*
* Regions:
* - page.header: Items for the header region.
* - page.primary_menu: Items for the primary menu region.
* - page.secondary_menu: Items for the secondary menu region.
* - page.highlighted: Items for the highlighted content region.
* - page.help: Dynamic help text, mostly for admin pages.
* - page.content: The main content of the current page.
* - page.sidebar_first: Items for the first sidebar.
* - page.sidebar_second: Items for the second sidebar.
* - page.footer: Items for the footer region.
* - page.breadcrumb: Items for the breadcrumb region.
*
* @see template_preprocess_page()
* @see html.html.twig
*/
#}
<h1>page html twig front my radix</h1>
{#{% include 'radix:page' %}#}
{#
/**
* @file
* Template for the main page.
*/
#}
{% set page_attributes = attributes ?: create_attribute() %}
{% set
page_classes = [
'page',
]|merge(page_utility_classes ?: [])
%}
<div {{ page_attributes.addClass(page_classes) }}>
<div class="page-header">
<div class="container">
<div class="row">
<div class="col-sm-6 col-md-6 col-lg-6 col">
{% block page_head_left %}
{% if page.page_head_left %}
{{ page.page_head_left }}
{% endif %}
{% endblock %}
</div>
<div class="col-sm-6 col-md-6 col-lg-6 col">
{% block page_head_right %}
{% if page.page_head_right %}
{{ page.page_head_right }}
{% endif %}
{% endblock %}
</div>
</div>
</div>
</div>
{% block page_navigation %}
{% include 'radix:page-navigation' %}
{% endblock %}
{% block page_content %}
{% include 'radix:page-content' with {
page_main_utility_classes: ['py-5'],
page_header_container_utility_classes: ['mb-3'],
}%}
{% endblock %}
{% block page_footer %}
{% include 'radix:page-footer' %}
{% endblock %}
</div>
Works in this case. What i have not achieved so far is adding stuff to the html sdc because just copying that over will not work.
Ok the answer to this is simple.
- The options must be defined in the schema file - i did that
- But i had a typo elf_nofollow instead of elif_nofollow
Info about the type: filter
https://www.drupal.org/node/3419181 →
You can try to rearrange the filter sorting on the text format page.
Thank you.
I added the following in my FilteElif.php file
I get the same error "elif_nofollow elif_nooperner and elif_norfeferrer is not a supported key"
/**
* Default config. Otherwise 'xyz is not a supported key' will be thrown
* @return array
*/
public function defaultConfiguration() {
return [
'elif_nofollow' => FALSE,
'elif_noopener' => FALSE,
'elif_noreferrer' => FALSE
];
}Use full HTML and allow html tags.
That still does not work on 8.x-2.3 and as far as i can see that part of the dev version is in there. i checked the code manually.
Ok, i think it is best to check out they /layouts folder inside barrio. There you can see how you can create own layouts in your subtheme.
In that way you can also reproduce radix layouts.
Hi,
Amazon store?
This module allows including amazon asins using tokens that then get transformed to a shop-design, like the screenshots show.
Same here, that is they way to do it.
Ok i tried that. I may have missed something important here, maybe.
- Added my taxonomy category field to the search api index and also indexed the hirarchy. Set it to fulltext.
- Added a search api view with an exposed form.
- Form is configured to search through all fields
- But there are no results when i search that form using autocomplete or just hitting enter.
I also inject banners like that i use full html for that. It works.
Thank you very much Thomas.
I can not exactly follow here. Can you describe that in detail please?
The module injects a block. If you disable html and the block has html...it may not work because it gets filtered.
marcoka → created an issue. See original summary → .
Ok actually i have no idea because i run the dev with the SDK from wirecutter.
Install the dev version please and test again. I use DEV in production.
Thank you Rik.
I will open a new branch in the next week and also publish a release for the current module i use on my pages.
i can confirm this. patch is not sufficient and causes a new problem with stray
tags.
Update with drupal 10.2 and Radix 5.0.11
This code will ad all classes in a second class tag.
{% if html_tag %}
<{{ html_tag }}{{ attributes|without('id').addClass(classes)}}{{ attributes.setAttribute('id', clean_id) }}>
{% endif %}
Correct code:
{% if html_tag %}
<{{ html_tag }} {{ attributes|without('id').addClass(classes).setAttribute('id', clean_id) }}>
{% endif %}
Thank you, fixed.
I can confirm #21 works here too with Drupal 10.2.4
Hi, thank you.
Hi no complicated workflow necessary. If this is only simple small api stuff we can discuss it here without patches and stuff. Saves a lot of time.
So you added that locally and that fixes the issue?
That memory error normally is because php has not enough memory. What do you use in your php config for memeory_size?
Yes, i think we can close this issue.
It works so far for me.
I can confirm this with
facets 2.0.7
pretty facet paths: 1.7
Thank you. has been pushed and i add it to the new 1.2.x
What is meant wit hattributes 0?
Don´t put so much work and effort in a readme of a beta module. The docs are not even solid yet.
I can not tell because i disabled the module. I am now on D10 with ckeditor 5.
I had around 10.000 words.
Yes i have. My solution also works and you can customize the code to be valid with the schema.org gallery template
I started working on a D10 only version.
Token block 2 is required for that to work
Testing it currently and will report back.
Renamed to *.md.
As this is in development and changing the rest has to be postphoned until everything is stable and solid to document.
i am back. will check this in the next few days.
Hi. Thats a bit complex. I rewrote the image fields and added a custom textfield.
Also activate global script include in the settings and added a class to the view. "photoswipe-gallery"
image
<a class="photoswipe" href= "{{ field_media_image }}" itemprop="contentUrl" data-pswp-width="{{ field_media_image__width }}" data-pswp-height="{{ field_media_image__height }}" title="{{ field_media_image__title }}" alt="{{ field_media_image__title }}" data-overlay-title="{{ field_media_image__title }}">
custom textfield
<figure itemprop="associatedMedia" itemscope itemtype="https://schema.org/ImageObject">
{{ field_media_image_1 }}{{ field_media_image }}{{ field_media_image_2 }}{{ field_media_image_3 }}</a>
<figcaption itemprop="caption description pswp-caption-content">{{ field_media_image_4 }}{{ field_media_image_5 }}</figcaption>
</figure>
That results in the following on my site:
https://www.kopfhoerer-berater.de/test/sony-wf-1000xm5-im-test#image-gal...
@h1nds1ght did you only download the module put it into modules/custom an enabled it on the modules page?
I did use views "custom rewrite field" to build the markup myself. That works.
Just wanted to say that i am not really maintaining this module. Just no time. The second maintainer may take a look.
I think i found the solution.
At first we need event delegation. So we add the eventlistener on the container that always exists. The once is not applied to the listener but to the check of the length.
This way i can add or remove items of a list that are beeing added by a button add/delete
if (once('flagonce', '#produkt-vergleich', context).length) {
flgContainer = document.getElementById("produkt-vergleich");
flgContainer.addEventListener("click",function(e) {
// e.target was the clicked element
console.log("woo");
console.log(e.target.closest("li"));
if(e.target.closest("li")) {
var closestli = e.target.closest("li");
e.target.closest("li").remove();
var clicked_id = closestli.getAttribute('data-nid');
var node_name = closestli.getAttribute('data-nodename');
var data = clicked_id + '::' + node_name;
console.log("clicked icon " + data);
//set class of the add link to unflagged
$(".jqflag[data-nid='" + clicked_id + "']").removeClass('flagged').addClass('unflagged');
$(".jqflag[data-nid='" + clicked_id + "']").removeClass('flagged').addClass('unflagged');
$(".jqflag[data-nid='" + clicked_id + "']").text("Hinzufügen");
$(".jqflag[data-nid='" + clicked_id + "']").prepend(toggleIconAdd);
flagList.remove(data);
loadBlock();
}
});
}Just to be sure the views code "$data['node_field_data']['computed_float']"
"computed_float" is not the name of the computed_field field you added using the ui?
When i add my field to views i get an error. I also have not achived to make my formatter avaliable in views. Its just avaliable when i add the field using layoit builder.
It is a plugin for computed field. Also pay attention to the hardcoded fieldname!
[#3344764#comment-15335022]
I think i already fixed the problems in code. The float problem, was my bad code. The tokens work using hook_token.
I will publish it in a second to a sandbox module.
Thank you all for the infos so far. I am working on an example where i add multiple int fields that will result in a float value.
The code works so far, but one thing confuses me. I don´t get it.
If i output the value it is always rounded down.
- I generate 5.3, the output is 5.0
<?php
namespace Drupal\computed_ratings\Plugin\ComputedField;
use Drupal\Core\Cache\CacheableMetadata;
use Drupal\Core\Entity\EntityInterface;
use Drupal\Core\Entity\EntityTypeInterface;
use Drupal\computed_field\Field\ComputedFieldDefinitionWithValuePluginInterface;
use Drupal\computed_field\Plugin\ComputedField\ComputedFieldBase;
use Drupal\computed_field\Plugin\ComputedField\SingleValueTrait;
/**
*
*
* @ComputedField(
* id = "computed_ratings_field",
* label = @Translation("Computed Ratings Field"),
* field_type = "float",
* )
*/
class ComputedRatingsField extends ComputedFieldBase {
use SingleValueTrait;
/**
* {@inheritdoc}
*/
public function singleComputeValue(EntityInterface $host_entity, ComputedFieldDefinitionWithValuePluginInterface $computed_field_definition): int {
return (float) 5.3;
}
}