moving to 3.x line as this is one of the goals in to make the Bid form more available.
2.2.2 release. have recently fixed a 'logger' bug in the cron task -- this was blocking status changes.
moving to needs review even though is released.
bid have a 'relist' id, are you sure the Bid you deleted belongs to the current active relist. this could be one side of the UI.
the view for the list seen on Auction Nodes (public) would be found on View admin/structure/views/view/bids_relist_group -- this is set with a cache tag. you may need to adjust that setting.
have moved to hook_install/uninstall of order item and some related config cleanup on 2.2.2 release
won't fix. this is glitch of 'Upgrade Status' and how it processes versions. As COMPOSER is actually the perfered way to 'load all the things' this is the only concern (and works as expected).
see previous related (closed) ticket,
3.0.x is still set as dev line only release for now final Commerce Core 3.
cheers. have released 2.2
I've actually determined that because Commerce Core is cutting off at 10.3 is causing the build problem this way. I'll need to shift it over on the 3.x line anyway.. I'll set up a 2.2.0 release for THIS ticket.
https://www.drupal.org/about/core/policies/core-release-cycles/release-p... →
Honestly, as this project is not funded by Users in any way I am not looking to maintain what CORE is doing with maintaining such ''long term" majors (2 Drupals at once). Core has too much consistency. in NOT being a true base. this is why I already have several releases version. as that proof.
note: this bug sounds like something that was known with order items.. (if memory servers me).
moving to dev3 line.
Assuming you have your composer.json setup to use Patch, you can apply the "plain diff" of this patch from the dev line of the projects repo
noted. thanks.
Seems like it would be a good time to include Drupal 11 in the modules .info.yml. I'm not sure if tests are running here..
joevagyok → credited skaught → .
duplicate of #3420902
certainly, lots of open tickets around this in core..
Drupal issues search | "text=not+compatible&component=update.module" →
this is how this module is currently set for release status:
it seems like core isn't figuring out that what's recommended isn't geared per core release.
As per #50 and #48. I'll move to RTBC logo is aligned with the rest of items below, matching overall design mocks.
#48 notes. " But there should be some space between logo and slider." I would agree the width of the entire item might ought to be wider but that scope that might pushing this ticket IMO. Also, as we know various browsers use different widths.
to be clear, I was staffed by Optasy for work on the estore project.
thanks for confirming your hosting platform. Indeed, this module IS NOT STABLE!!
this module is not maintained!
umm.. I see you have scrollbars being displayed. Do you have your setup to always show them?
preview with flex-shrink attached, shows both of our toggles between breakpoints.
local demo image was just 71*83 pixel grab (then autosized as expected to 34x40).
have reviewed patch. yes oversight in original name spacing for file usage.
will also probably need an update hook to check if any update any existing entries to be updated to 'file' (as $new_logo_managed->getEntityTypeId() will equal 'file').
also was using drupal 11 (a new site, not an updated project). I had come across several other bug/error notices. this is the only one that was fatal/wsod.
the_g_bomb → credited skaught → .
on 3.x dev I am now converting to a custom field. time to rebuild this tool.
opening as 2.1.x dev line. I do still want to rebuild this (to SDC, general modernize). but time, as always....
overall, 'allowing empty' this is not a operation I want this model to have.
second note, patch does not have need tests.
pameeela → credited SKAUGHT → .
would you be able to outline the advantage of this hook? simply, what is your use-case that you need to alter the like that you can not 'use custom title' not be useful??
also: needs tests.
[#3344141]. ScrollTopCommand is now a core command.
have added composer file and adjusted module info for 10.1. -> 11. have tested on d11 locally
see: https://www.drupal.org/project/auctions/issues/3460496#comment-15718255 🐛 Use IEF ^1.0 || ^3.0 Closed: works as designed
@d11 and forward
https://www.drupal.org/project/auctions/releases/3.0.x-dev →
this is resolved on the 3.x line, in that we will use v3 future forward. thanks!
hestenet → credited SKAUGHT → .
most generally, We should account for more space then just 2 active languages. As often sites can have 4-7. this would make the desktop design (to show as inline items) not as 'ready out of the box' considering the 'head width' available.
-Put a button in that block with the hidden attribute on it, so it's not visible on the page
-Use JS to remove that hidden attribute so we can see the button
-Use JS to add a hidden attribute to the languages so they are now invisible
A. are you concerned with JS degrade, or just the breakpoint hide/showing.
B. a reminder of projects like
https://www.drupal.org/project/dropdown_language →
(which i maintain) to remind that Unami Profile can provide a block plugin that is the block to be placed with whatever Accessible Ready UI (button and links) with the true language paths and SEO readhy hreflang's.
#28. "YML plugin declaration of icons sets to be added to modules and icons..."
nice. "a standardized way across Drupal"
@ahsannazir thanks for the followup. hiding old branch to reduce confusion.
SKAUGHT → changed the visibility of the branch 3444391-center-small-navigation to hidden.
re-started from up to date clean branch
re: Say there is a design change to increase the image size to 45*45 pixels,
✨
Center small navigation logo on collapsed state
Needs review
would be the fallback to address images that are too small.
@siliconmeadow
Can you set the default branch to 2.1.0 now. I do not have perm in gitlab.
Am releasing 2.1.x line for Drupal 11 (PHP 8.3+) only. will also allow Stats page to be more useful ( emptyparagraphkiller Usage Stats → )
#18 Crop module 8.x-2.4 has now been released!!!!
no, it required by, nor first. it would be a different set of tests at well.
💬 Update module erroneously recommends conflicting update to 6.1.x for sites on Drupal 10.0.x or lower Closed: works as designed is using an update hook of Update Module to 'short-cut' this.
if the problem is still (untill d11 is actually out, and if core themselves need to update Update module around this in a wider way across conbrib -- i will continue to wait to see that result.
"{my D}rupal installation in an outdated state." outdated -- i assuming your site is running fine otherwise and this is only an notice to a dev/admin and can be explained at this time.again, i blame update manager: this is confusing that the 4.1 line is indeed not with 10.3 (as it was in 10.2). i can not guess at the 'Requires Drupal core:" is blank off hand. again, this is internal to update manager.
low concern.
core_version_requirement is correctly set by {dropdown language} for both these releases, and follows my long-term tagging strategy. as does my composer setup to keep major core version apart with my release cycles.
-> I have no control over Update Manager messaging. this bug seems like theres, not mine.
otherwise, Dropdown Language is operating normally correct? (:
I would have to assume you have been using v4.0.3 through your entire Drupal 10 life cycle?
patch 404 applies as expected on Drupal 11.0.x.
There is something wrong with gitlab. I can not start a new branch or pull in current dev head to get this patch into. This is probably why 404 is a file.
benjifisher → credited SKAUGHT → .
logo is not aligned with rest of first items.
benjifisher → credited SKAUGHT → .
If you are looking to begin this work, of course -- please feel fee to. I'll be happy to consider at the time a patch exists.
linking