The module is not usable in Drupal 11 even with the patches here. I could not apply these patches with composer nor patch command so I downloaded from the fork here. When I installed from the fork, the module wasn't configurable as the edit form was in a bad shape.
#6 also helps.
While the module worked when I created custom links directly on the menu edit page, when I created a basic page I didn't see menu_per_role settings until I followed the tip in #6. I remembered I didn't have to do this in my Drupal 9 sites so I checked those sites and found the setting for 'Show fields on menu items that point to content' had none of the options selected, while in the D10 site I am working on now, the setting for 'Show fields on menu items that point to content' had 'Never' selected by default. This turned off menu_per_role for the basic pages I created until I set 'Show fields on menu items that point to content' to 'Always' as said in #6. Note that this didn't make menu_per_role to work for links generate by other modules as said in #7.
I am really sorry for messing up this issue. It is all my fault. I wasn't seeing classes to add to trainings because I created classes but didn't add members to the classes. Now I added two members to one of the classes and boom, it showed up and I was able to add the class to a training.
So in my case, this issue does not exist. I can add users and classes to trainings without any issues and without needing any patches.
Sorry again for the mix up.
Thank you.
I think the issue here is trying to use this module on links generated by other modules like the User module or Views module. The module is not active for such links and I tested similar modules including the one mentioned in #5 and it is the same behaviour. None of the similar modules I tested set permissions for links generated by other modules.
I just installed on Drupal 10.3.10 and it won't uninstall. Luckily I took a db dump before installing so I have to roll back the site.
I am thinking that the fact I had no users on the site when I got to the 'Member's page is getting me confused about what is working and what is not.
Now I took off patch #4 and created two users from 'People > Add user' and when I got back to 'Members' page and clicked on 'Add members' I was able to see the two users I created and I could add them to the training. So I think there is no issue about discovering users and adding them to trainings, at least for sites not having too many users count as is my case. What I still find not working is adding classes to trainings. I created a class and when I got to 'Add members' page and clicked on 'Classes' tab, I didn't see any classes loaded.
So I don't see what issue patch #4 solves, maybe it addresses sites with large volume of users, but I have taken it off and I could add users to trainings.
In my case, I installed the latest version of Opigno and while setting up and applying patches along the way I got to the stage of adding members to the training then I found out users and classes were not loading on the page. When I click on 'Add members', an existing class will flash and then go away and there will then be no classes nor users displayed. When I got to this stage I had only one admin user account on the site and on the 'Add members' I was able to create two users and a Class. Whether they were added on the training I couldn't tell as the users and classes were not loading on the page.
No way to add a user or class on the training.
Then I applied patch #4 here and, just like the author said in #4, the patch swaps out Opigno's handling of the feature to rely on the Group module, so the interface looked different from the default Opigno system. And then I am able to only add users to training and can't add classes.
Here is what I found on the console before I applied this patch,
The first error I found:
A form field element should have an id or name attribute
A form field element has neither an id nor a name attribute. This might prevent the browser from correctly autofilling the form.
To fix this issue, add a unique id or name attribute to a form field. This is not strictly needed, but still recommended even if you have an autocomplete attribute on the same element.
Affected resource is this markup
<div class="input-group"><input placeholder="Filter by users" class="form-control"></div>
rendered from this file, modules\contrib\opigno_learning_path\modules\opigno_user_selection\templates\entity-selector.html.twig
The second error I found is:
Incorrect use of < label for=FORM_ELEMENT >
The label's for attribute doesn't match any element id. This might prevent the browser from correctly autofilling the form and accessibility tools from working correctly.
To fix this issue, make sure the label's for attribute references the correct id of a form field
Affected resource is this markup,
<label for="edit-training-users">Find existing users or groups</label>
rendered from this file, themes\contrib\aristotle\templates\form\form-element.html.twig
I attempted fixing these errors but couldn't so I am relying on this patch which I will consider it a workaround until there is a fix.
On the site is "drupal/opigno_learning_path": "~3.2.0"
The patch is working, thank you.
Using 1.0.x-dev, I couldn't get past this error with free tier. I tried with OpenAI and Anthropic.
The workaround at #12 is working for me on Drupal 10.3.5.
I wrote a patch to add breadcrumb in the block, in the referenced issue.
The MR solves the issue.
When I uninstalled big_pipe module I could see the slider as an admin.
I encountered this issue. I was working with WAMP on localhost and the slider was showing while I was logged in as admin but when I moved the site to remote server, the slider stopped loading while I was logged in as admin and was loading only when I viewed as anonymous.
The patch works and module works well in Drupal 10.
A Drupal 10 release will be appreciated.
@weseze when I used the module I needed this feature, https://www.drupal.org/project/redirect_after_registration/issues/3163523 → Don't know if the module now has it.
It means myself have been abusing this module. I check it everywhere I add an image. I don't like the stress of entering alt texts and I have heard many say that to me.
I get. Thanks.
Or "Check to skip adding an alt text."
I think "Check to skip adding alt text." will suffice. The technical angle of screen readers and image being 'decorative' will throw off a larger number of users. E.g. we have this issue on our forum and most forum members don't know screen readers, never heard of 'decorative' and don't even know what alt text means and so when they see "This image ..should be hidden'' they get alarmed like their image will not show to some people.
This works for Drupal 10, https://www.drupal.org/project/commerce_quick_node_clone →
Both with 2.0.9 and 2.0.x-dev is-less is not existent both in the main stage and the navigation slide. is-less is not found anywhere.
This is still an issue with the latest 2.x releases.
Really my bad.
Adding the image styles fixed the issue.
I usually would add the image styles but I was quickly setting up the page to fine tune later.
Sorry about the trouble and thanks for helping out.
Do you know because of this issue I had to use Colorbox on a different site I had this issue some weeks ago. That was nodes and not product but this issue appeared and to move on I installed Colorbox and used it.
Screenshot of formatter form:
Backtrace (when trying to view a product):
The website encountered an unexpected error. Try again later.
Error: Call to a member function transformDimensions() on null in Drupal\blazy\Media\BlazyImage::transformDimensions() (line 444 of modules/contrib/blazy/src/Media/BlazyImage.php).
Drupal\blazy\Blazy::transformDimensions() (Line: 81)
elevatezoomplus_build() (Line: 42)
template_preprocess_elevatezoomplus()
call_user_func_array() (Line: 261)
Drupal\Core\Theme\ThemeManager->render() (Line: 491)
Drupal\Core\Render\Renderer->doRender() (Line: 248)
Drupal\Core\Render\Renderer->render() (Line: 475)
Drupal\Core\Template\TwigExtension->escapeFilter() (Line: 61)
__TwigTemplate_ff4c80800399fc79d4ccb6c3cb72253b->doDisplay() (Line: 360)
Twig\Template->yield() (Line: 335)
Twig\Template->render() (Line: 38)
Twig\TemplateWrapper->render() (Line: 33)
twig_render_template() (Line: 348)
Drupal\Core\Theme\ThemeManager->render() (Line: 491)
Drupal\Core\Render\Renderer->doRender() (Line: 248)
Drupal\Core\Render\Renderer->render() (Line: 238)
Drupal\Core\Render\MainContent\HtmlRenderer->Drupal\Core\Render\MainContent\{closure}() (Line: 638)
Drupal\Core\Render\Renderer->executeInRenderContext() (Line: 231)
Drupal\Core\Render\MainContent\HtmlRenderer->prepare() (Line: 128)
Drupal\Core\Render\MainContent\HtmlRenderer->renderResponse() (Line: 90)
Drupal\Core\EventSubscriber\MainContentViewSubscriber->onViewRenderArray()
call_user_func() (Line: 111)
Drupal\Component\EventDispatcher\ContainerAwareEventDispatcher->dispatch() (Line: 186)
Symfony\Component\HttpKernel\HttpKernel->handleRaw() (Line: 76)
Symfony\Component\HttpKernel\HttpKernel->handle() (Line: 53)
Drupal\Core\StackMiddleware\Session->handle() (Line: 48)
Drupal\Core\StackMiddleware\KernelPreHandle->handle() (Line: 28)
Drupal\Core\StackMiddleware\ContentLength->handle() (Line: 32)
Drupal\big_pipe\StackMiddleware\ContentLength->handle() (Line: 106)
Drupal\page_cache\StackMiddleware\PageCache->pass() (Line: 85)
Drupal\page_cache\StackMiddleware\PageCache->handle() (Line: 48)
Drupal\Core\StackMiddleware\ReverseProxyMiddleware->handle() (Line: 51)
Drupal\Core\StackMiddleware\NegotiationMiddleware->handle() (Line: 36)
Drupal\Core\StackMiddleware\AjaxPageState->handle() (Line: 51)
Drupal\Core\StackMiddleware\StackedHttpKernel->handle() (Line: 741)
Drupal\Core\DrupalKernel->handle() (Line: 19)Using Drupal core 10.3.1 and Barrio B5 theme install Drupal commerce, add images field on a product or product variation, format the field to display with Splide Image, use Grid Foundation for Skin main, X Grid for Optionset main, choose an image style, then add Media switcher "Image to Elevatezoomplus" with Default optionset.
Trying viewing a product you will see the error.
I have also seen this with a different theme based on Bootstrap 4 and running Drupal 9.
chike → created an issue.
I encountered this issue in Drupal 10.3.1. Patch #3 got me over it. There seems to be other opinions about the patch on this page.
Also not sure if it is related to this issue, but the module still had other problems after I got over the first issue. I then opened this issue 🐛 LogicException: A stray renderRoot() invocation is causing bubbling of attached assets to break. Active .
chike → created an issue.
chike → created an issue.
This is Drupal 10.3.1 and I could not get past Uncaught TypeError: $(...).once is not a function. When I managed to get past it I can't tell why the code is not working either the changes I made or the code itself. I guess .slick--field-slider should be okay for .your-carousel-class?
I can remove all the animation classes I added on the carousel so this code can add the classes afresh without having to remove and append to existing classes.
Thank you.
For anyone else looking to override this text, you can put this on a custom module or .theme file,
/**
* Implements hook_form_alter().
*/
function custommodule_form_alter(&$form, \Drupal\Core\Form\FormStateInterface $form_state, $form_id) {
//Override 'Proceed as guest' text
$form['login']['guest']['text']['#markup'] = t('<p>Proceed to checkout, an account will be created for you at the end. You will be notified via email about your new account.</p><p>You can also proceed as guest if you have an existing account and your new order will be added to your account.</p>');
}
I too am wondering what is 'optional' about an account that will surely be created without the user doing anything about it.
I have been searching through the variables on the form and don't seem to see a way to override the text. Is there a way please? I want to set "Proceed to checkout, an account will be created for you at the end. You will be notified via email about your new account."
Using the 'Calculated' formatter solved the issue I was talking about in #12.
Thank you and apologies for the trouble.
Using the 'Calculated' formatter solved this issue.
Thank you and apologies for the trouble.
Please how does this issue relate to this one I raised here, https://www.drupal.org/project/commerce_exchanger/issues/3449136 💬 Converted price not showing on product page until product is added to cart Active
Thank you.
Hello @BR0kEN, talking about multiple parents, do you see any case in the issue I posted here, https://drupal.stackexchange.com/questions/320139/hierarchical-select-mo...
Is the scenario I described the way things are designed or is there an issue in my scenario?
I am using the latest version of cshs.
Thank you!
You know the best way to do it, I am not a programmer as you know.
Will be good if the breakpoint is made configurable so someone can choose the breakpoint they want zoom turned off.
Thank you for the clarification. I would have written a patch if I had enough knowledge 🥺.
@facine Does the mentioned commerce issue being fixed make any difference now?
Oh I got it working now. Formerly on the handler I mapped 'Amount' to the computed twig field but now I tried by using the 'Other' option and adding a webform token of the field. This got the computed twig value working as the product price. Thanks.
I am having a similar issue, all attempts to pass a computed token or computed twig value to the price field is failing. If I try a value field with a number explicitly written it will will work but a token value or computed twig value will fail to pass. I have tried all types of Twig filters and all types of ways to cast the value to make sure it is a number and yet it wouldn't pass over to the price field.
Patch #7 is working. Thanks.
I can't see any error logs.
Yes I have field_formatter installed, the latest version 3.0.0-rc3
The MR worked for me. I didn't test any of the other patches.
I got the same issue, the comments here encouraged me to try regardless so I saved the page and everything worked!
Yes this works.
Thank you!
It didn't work.
I want to target the submit button, should be the last step I guess. What can I adjust in my code to target the button and change the text?
hook_form_alter() didn't work I guess for the same reason given by FrankDesign in the comment here, https://drupal.stackexchange.com/questions/308223/drupal-9-commerce-chan...
Here is the code I used,
function mymodule_alters_form_alter(&$form, \Drupal\Core\Form\FormStateInterface $form_state, $form_id) {
if ($form_id == "commerce-checkout-flow-multistep-default") {
$form['actions']['submit']['#value'] = t('Complete checkout');
}
}This does not work.
Tried again and sure the patch is working for me now.
I completely agree with this.
I am using media_thumbnails_video which like you said needs ffmpeg.
Per my check most (if not all) host companies will not offer ffmpeg on their shared plans because it is resource-intensive. A user attempting to install it will also need root level access on the server which a shared hosting plan will not offer.
I spoke with my host company now and they said,
... ffmpeg is not supported on any of our hosting plans due to security considerations and resource intensiveness.
So like I feared, there seems to be no luck for sites on shared servers.
As said on #6 admin-level permissions is required for a user to be adding views headers and footers so I am not sure site owners would be giving untrusted users admin roles. For the possible security risks with Twig templates, a warning message could be left on the field.
There is a legitimate and very powerful use case for allowing Twig syntax on views headers and footers just as they add so much power to views when one uses 'Custom text' field to play around with fields using Twig. It indeed gives so much power to Views, and so also will there be such power added to headers and footers if full Twig syntax is allowed.
Yesterday I wanted to use Twig if elseif condition to conditionally display a message on the views footer depending on the value of a field, that's when I noticed this wasn't possible. Now I did make a Custom text field and write the Twig conditions on it and then added the field on the footer which ended up achieving the same goal. So if I could still add the condition there somehow why not then allow us do it directly on the footer?
Weighing the security risks against the use case of the feature, it sure will win to have it enabled and a warning message left on the field to tell people to write Twig with care.
My issue wasn't solved. What happened in my case was somehow 'media' module did not install completely or something cos I found the media types were not available on the site and visiting 'admin/content/media' threw an error. So I rolled back the site till I uninstalled 'media' module. I removed patch #57 and re-installed the media module and it was now properly installed. I re-installed back all the other modules and site came back normal.
The thing is, without patch #57 I wouldn't have been able to access the Uninstall page to uninstall the media module and the other modules that required it.
I installed Drupal 10.2.4 and started building the site, just regular site building stuff - enabling contrib modules and creating pages. Then I decided to uninstall the 'contact' module and clicking /admin/modules/uninstall threw this error,
Drupal\Core\Database\DatabaseExceptionWrapper: SQLSTATE[42S02]: Base table or view not found: 1146 Table 'custom_theme.media' doesn't exist: SELECT "base_table"."vid" AS "vid", "base_table"."mid" AS "mid" FROM "media" "base_table" GROUP BY "base_table"."vid", "base_table"."mid" LIMIT 1 OFFSET 0; Array ( ) in Drupal\Core\Entity\Query\Sql\Query->result() (line 271 of C:\wamp64\www\custom-theme\public_html\core\lib\Drupal\Core\Entity\Query\Sql\Query.php).
The 'media' module was auto-installed as a dependency for 'bootstrap_layout_builder' module. I have not added a media item yet.
Anyways patch #57 got me back to the Uninstall page and I was able to uninstall the 'contact' module.
Thanks @_utsavsharma
I equally can't find a way to do this.
It looks like it's either one uses this formatter or use Colorbox and the two will not work together.
See how Conditions in Webform handles this,
None of the patches is applying on the latest version.
I just experienced what @jjpost said at #23.
Okay. I will try it out. Thanks.
Thanks @dqd for all your work. When I tried the patches and they didn't work I reached out to a friend and he did this on the site: he made 3 conditions to solve the issue. Let me explain.
The control field is 'field_type_of_event'. If the value is 'Physical' then the target field 'field_venue' should be visible and if the value is 'Virtual' then the target field should be hidden. I had another condition to show another field 'field_online_event_platform' when 'field_type_of_event' has value 'Virtual'.
Initially I set one condition for 'visible' then I noticed that when it is hidden it was still required (the field was required) so the form won't submit. That was where the frustration started.
But I found out one other thing, if control field is set to 'Physical' and the target field showed up and I entered a value in 'field_venue' let's say 'Lagos' and then I switched the control field to 'Virtual' and 'field_online_event_platform' becomes visible and I entered a value 'Google Meet' and saved the form; then both 'Lagos' and 'Google Meet' are displayed on the page. So not only did I need to make the hidden field not-required, I also needed to make it empty cos user could have populated it with values before changing his mind to hide it.
So my friend made these three conditions on the site:
First he made 'field_venue' not required on the site and then he made the conditions.
1) If 'field_type_of_event' has value 'Physical' make 'field_venue' visible.
2) If 'field_type_of_event' has value 'Physical' make 'field_venue' required.
3) If 'field_type_of_event' has value 'Virtual' make 'field_venue' empty.
This is working perfectly.
I am not sure if this will help in the decision making for the way forward.
It does render the Header or Footer area of the configured View but I had wanted to show the term description and an image field I added to the terms on the term pages.
I am using X Grid for 'Optionset main' and X Splide nav for 'Optionset nav' and when there is one image, is-less class is added on the navigation slide and none added on the main slide. If slider type is set to 'Loop' on any of the slides the arrows show up. If slider type is set to 'Slide' on the navigation slide, the arrows are hidden and if slider type is set to 'Slide' on the main slide the right arrow shows up.
Summary: is-less is only added on the navigation slide (in my case) and only hides the arrows with slider type set to 'Slide' or 'Fade' and does not hide the arrow when slider type is set to 'Loop', when slide has only one image. is-less is never added on the main slide and the arrows stay visible.
Unfortunately I am not able to make a patch.
Thanks.
base on module Elevate Image Zoom
but this module is no longer under maintenance and too many errors, I decided to redo it all with new library jQuery ElevateZoom Plus Plugin
View demo
The above message on the project page suggests one should not use the other module if starting a new project.
@dac_ca I thought about this two days when I installed a new site using steps at #33 then I found layout_builder_iframe_modal wasn't showing a good UI so I tried to remove it but found out I couldn't cos the method at #33 made bootstrap_layout_builder require it so I had to unstall bootstrap_layout_builder before I would be able to uninstall layout_builder_iframe_modal.
I then realized the implication of one using his own methods, if the module finally makes an update to remove the dependency on media_library_theme_reset and the way the modules goes does not play with your custom way, you have to roll back to follow the module and if you have built a heavy site, it wouldn't be easy rolling back. E.g. before I could uninstall layout_builder_iframe_modal I had to disable all layouts made with bootstrap_layout_builder and then uninstall bootstrap_layout_builder. I could do that because it was still a new site, if I had gone far with the project it won't be that easy removing layout_builder_iframe_modal. Perhaps there could be some type of way of requiring all the projects independently in localhost and overwriting in production. But to be safer I would suggest waiting for the module to make an update so you are not left to fight your fires alone.
MR !24 didn't work for me neither did the patch on the referenced issue.
I am using shs for a select field and when I enter a value and save, if I edit the node the field will appear twice it two levels and thrice if 3 levels. It's messy.
I can't make a patch so I can only report.
Using Drupal 10.2.3 and Commerce 8.x-2.38 I am still not able to let users see only orders on their own products.
But Twig Tweak might be an overkill for a site that is not already using it.
It would be more handy having a configuration option for it on the block. How I wish I have the expertise to make a patch for it, but not yet.
This works nicely, thanks.
Putting it in a submodule will be an excellent idea but I am not sure the maintainer will commit the patch. A better way will be to make a separate dependent module for it.
This is not working for me. Term lineage is not saved after applying the patches above.
The maintainer of this module said repeatedly this module will NEVER save term lineage as a feature.
I will suggest using https://www.drupal.org/project/taxonomy_set_lineage → together with shs to save the lineage.
As per #8 yes you can create one but it works fine as long as you use Layout Builder or remain in-cms. If you make a template override for the view mode your template will be ignored and commerce-product--default.html will always be used, but will respect your custom view mode as to the fields you enable or disable in Manage display.
None of the patches here is working for me in Drupal 10.2.0.
#4 worked for me (Drupal 10.2.0)
Thanks for your work. I later found out this was due to changes → in Twig 2.10.0.
Also is there a way for this module not to depend on Lightning Media cos having core Media module turned on and this module again requiring one to install Lightning Media kind of clutters the site with Media solutions.
I can use Layout Builder in the 'PDF' display to add and remove fields but layouts and styles made with LB are not respected in the generated PDF files.