With this patch I got this module working in Drupal 11. I added the fixes by @Project Update Bot here to the patch then I made extra fixes. If you apply this patch you need to download this file jquery-migrate-3.5.2.min.js from https://github.com/jquery/jquery-migrate into \md_slider\assets\js\libraries folder and delete the old version jquery-migrate-1.2.1.min.js.
If you applied the patch at issue Fix the errors/warnings reported by PHP_CodeSniffer 📌 Fix the issues reported by phpcs Active you may have to take if off as this patch conflicts with it.
I finally am able to get this module to work in Drupal 11. It took many more deprecation fixes than is covered in the patches here and also it took upgrading this library, \modules\contrib\md_slider\assets\js\libraries\jquery-migrate-1.2.1.min.js to a more recent version like jquery-migrate-3.5.2.min.js which you can download here, https://github.com/jquery/jquery-migrate
Perhaps I will submit the fixes I made as a MR later on.
I found the problem.
The image was actually rendering. The image is certificate borders so is transparent in the middle. It is larger in size than the certificate so when it rendered, the borders weren't showing so it was basically showing the middle part which is transparent.
I adjusted this portion of the CSS in the template,
.page-bg img {
min-height: 600px;
min-width: 600px;
}to this,
.page-bg img {
min-height: 600px;
min-width: 600px;
width: 100%;
height: auto;
}and the background image was brought into view.
Thanks.
chike → created an issue.
My client scheduled a call with Moxo and he said during the call he explained he has an Opigno website and wants to use Moxo on it as Opigno requires. He said the representative at Moxo didn't know what he meant by Opigno and when he asked for the cost, he was told he needs to shell out $4,000 to get started with a subscription.
He is just trying to launch the website for a new business idea and now he needs $4k for live meetings when he is not sure yet how many people will find his service interesting enough to sign up on the website.
Isn't this outrageous?
We have a critical need to use BigBlueButton in Opigno. The cost of Moxo is outrageous for us. Does anyone have a glue code or a tested configuration to use BBB in Opigno?
Any help will be appreciated.
I downloaded the library from this link you placed on the page, https://www.dropbox.com/scl/fi/h7ca8cpa8m5p3dhyxnnag/gridstack.zip?rlkey... Would that be the correct version?
Here is a patch that works with the latest version.
This patch will add the following features to the module:
1) Make possible to show image fields on products, taxonomy terms and users. Without this patch you can't show image fields of products, users and taxonomy terms, you can only show image fields of nodes.
2) Make possible to add the site breadcrumb inside the block. With a checkbox you can choose to add the breadcrumb or not.
3) Make possible to choose overlay colors. You can choose two colors for the overlay color gradient, choose the gradient direction and choose overlay opacity, all in the UI.
4) Make possible to choose to show or hide the image title of the image field or the alternative text for the "Default background image" if image field is not used.
As I said earlier, AI helped me write these features so perhaps I (sorry, 'we') could have missed one or two Drupal coding standards.
I think it will be better to have it enabled because from the Block layout one can click through to create and place a content block in a region. I think this will be a smoother experience especially for a new user who doesn't know about content blocks.
After the release of Drupal 11 version, the MR here which I use in my sites became unmergeable and thus the patch wasn't applying anymore. I tried to rebase the MR but seems I mistakenly committed to the main branch. I am sorry about that. I am not a programmer hence the mistake.
@hatuhay please discard the changes I made if not okay by you. I will henceforth be manually patching my sites as I really need those features in the MR.
Thanks.
On installing Views UI by default, it is difficult to decide. I think it is better not to.
I am not sure new users will know what to do with it so better someone that knows turn it on.
On the other hand it can be made more intuitive and the power handed to new users. It definitely will blow them apart. (Making it more intuitive shouldn't involve taking off anything that is available right now to advanced users).
Enabling it by default also will help for people evaluating what is possible out of the box.
So I think again it is better to install.
Thank you sir.
The module solves the problem. I think the module should be bundled into Drupal CMS. It is absolutely essential.
I am sorry my issue is not really what this issue is all about - only related.
I tried to place a copy of composer.phar on my host server but that didn't work. This is what I did.
I navigated to the root of my host account where I have vendor folder then I ran the following commands:
curl -sS https://getcomposer.org/installer | php
chmod +x composer.phar
Then I added this in settings.php,
$settings['composer_executable'] = '/home/username/composer.phar';
This doesn't work.
Same issue here.
I installed Drupal CMS on a shared hosting server and visiting 'Browse' shows the error,
Unable to download modules via the UI: The composer executable cannot be found. Make sure it's installed and in the $PATH
I didn't check but I can bet if you make a clean install of Drupal, you won't see the issue in Olivero.
This most likely is a theme issue. I have only encountered it with this theme and have not seen it working with many other themes.
I can't find any patch like that in composer.json. I am not sure Opigno shipped with that. Probably someone in your team added the patch.
Was the patch added to Drupal core or Aristotle theme or some other place in Opigno? How can I remove the patch?
Hi, do you mean you applied this patch and the issue was solved? Did you write this patch or on which issue was it posted?
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.