![Announcement icon Announcement icon](https://www.drupal.org/files/styles/grid-2-2x-square/public/announcements/drupal-evergreen-logo-280X280px%20%281%29_0.jpg?itok=PHpn6rCb)
Problem/Motivation
Hello project maintainers,
This is an automated issue to help make this module compatible with Drupal 10.
To read more about this effort by the Drupal Association, please read: The project update bot is being refreshed to support Drupal 10 readiness of contributed projects
Patches will periodically be added to this issue that remove Drupal 10 deprecated API uses. To stop further patches from being posted, change the status to anything other than Active, Needs review, Needs work or Reviewed and tested by the community. Alternatively, you can remove the "ProjectUpdateBotD10" tag from the issue to stop the bot from posting updates.
The patches will be posted by the Project Update Bot official user account. This account will not receive any issue credit contributions for itself or any company.
Proposed resolution
You have a few options for how to use this issue:
- Accept automated patches until this issue is closed
If this issue is left open (status of Active, Needs review, Needs work or Reviewed and tested by the community) and the "ProjectUpdateBotD10" tag is left on this issue, new patches will be posted periodically if new deprecation fixes are needed.
As the Drupal Rector project improves and is able to fix more deprecated API uses, the patches posted here will cover more of the deprecated API uses in the module.
Patches and/or merge requests posted by others are ignored by the bot, and general human interactions in the issue do not stop the bot from posting updates, so feel free to use this issue to refine bot patches. The bot will still post new patches then if there is a change in the new generated patch compared to the patch that the bot posted last. Those changes are then up to humans to integrate.
- Leave open but stop new automated patches.
If you want to use this issue as a starting point to remove deprecated API uses but then don't want new automated patches, remove the "ProjectUpdateBotD10" tag from the issue and use it like any other issue (the status does not matter then). If you want to receive automated patches again, add back the "ProjectUpdateBotD10" tag.
- Close it and don't use it
If the maintainers of this project don't find this issue useful, they can close this issue (any status besides Active, Needs review, Needs work and Reviewed and tested by the community) and no more automated patches will be posted here.
If the issue is reopened, then new automated patches will be posted.
If you are using another issue(s) to work on Drupal 10 compatibility it would be very useful to other contributors to add those issues as "Related issues" when closing this issue.
Remaining tasks
Using the patches
- Apply the latest patch in the comments by Project Update Bot or human contributors that made it better.
- Thoroughly test the patch. These patches are automatically generated so they haven't been tested manually or automatically.
- Provide feedback about how the testing went. If you can improve the patch, post an updated patch here.
Providing feedback
If there are problems with one of the patches posted by the Project Update Bot, such as it does not correctly replace a deprecation, you can file an issue in the Drupal Rector issue queue. For other issues with the bot, for instance if the issue summary created by the bot is unclear, use the Project analysis issue queue.
Comment | File | Size | Author |
---|---|---|---|
#72 | fivestar-3287600-72.patch | 2.7 KB | ivnish |
| |||
#34 | d10_combined_3287600-34.patch | 4.3 KB | AbhinavK |
| |||
#31 | 3287600-31-d10-trial.patch | 736 bytes | TR |
#27 | 3287600-27.patch | 9.43 KB | heddn |
Issue fork fivestar-3287600
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
![Tag1 logo](/files/ads/tag1-issue-sponsorship.png)
Comments
Comment #2
Project Update Bot CreditAttribution: Project Update Bot commentedThis is an automated patch generated by Drupal Rector. Please see the issue summary for more details.
It is important that any automated tests available are run with this patch and that you manually test this patch.
Drupal 10 Compatibility
According to the Upgrade Status module, even with this patch, this module is not yet compatible with Drupal 10.
Currently Drupal Rector, version 0.12.0, cannot fix all Drupal 10 compatibility problems.
This patch does not update the
info.yml
file for Drupal 10 compatibility.Leaving this issue open, even after committing the current patch, will allow the Project Update Bot to post additional Drupal 10 compatibility fixes as they become available in Drupal Rector.
Debug info
This patch was created using these packages:
Comment #3
dancbatista CreditAttribution: dancbatista at CI&T commentedI will work on it!
Comment #4
Kristen Pol@dancbatista If you are unable to work on this, please un-assign.
Comment #5
dancbatista CreditAttribution: dancbatista at CI&T commentedI'm working on this @Kristen Pol!
Comment #6
Kristen Pol@dancbatista Thanks for the update!
Comment #7
dancbatista CreditAttribution: dancbatista at CI&T commentedI found another patch that can fix the problem with the Fivestar preview theme function. It's here: https://www.drupal.org/project/fivestar/issues/3273701. All other problems with compatibility with Drupal 10 were fixed.
Comment #8
TR CreditAttribution: TR commentedThank you for working on this. This whole automated patch thing is a bit of a mess because it is incomplete and does things that are really not Drupal 10 related.
What I would like to do here is have more than one issue so these changes aren't all mixed up. You've added a bunch of extra changes without discussion and without explaining what you were doing or why - those things should be done in separate issues. For example:
This also requires changes to fivestar.js, which you haven't done in this patch. Similarly,
If there is a bug in this statement, there should be an issue explaining the problem where we can discuss it and present a patch. You are making this line do the opposite of what it used to do, which is way out of scope for D10 compatibility. There are also other changes you've made without explanation - those should all have their own issues if you think there is a bug or if you want to add a new feature. This current issue is not the place to do either.
The only D10 compatibility problems with this module are the theme functions, which already have an issue, and the one line in the tests that uses assertRaw() which is no longer available in D10. Nothing else. The return type declarations are nice to have now that the minimum PHP of Drupal core supports this, but ALL the test functions should have them, and all of those should be changed together in one patch IMO. Likewise, we should begin to add return type declarations to Fivestar API functions, not just the tests, but the tests are a place where this can be done without breaking backwards compatibility so we should do it in the tests first.
The theme function meta issue is really the blocking issue for D10, and until that is fixed I don't want to change the .info.yml or composer.json to say that the module is D10 compatible, because it isn't until that is fixed.
So what I suggest is to re-roll the patch for just the assertRaw() change so we can fix that here. Then open new issues for 1) the return type declarations in the tests, 2) The jquery.once changes, 3) your new display settings feature, 4) any bugs you have found like empty($vote_ids), 5) etc.
Comment #9
dancbatista CreditAttribution: dancbatista at CI&T commentedThanks for the feedback @TR I will work on this!
Comment #10
heddnYes, the
once
changes are definitely needed. https://www.drupal.org/node/3158256 has some guidance on how to rectify.Comment #11
dancbatista CreditAttribution: dancbatista at CI&T commentedHi, @TR I followed your suggestion and re-rolled the patch for just assert raw() change. I will create the other issues separately.
Comment #12
DeepaliJ CreditAttribution: DeepaliJ at Salsa Digital commentedComment #13
DeepaliJ CreditAttribution: DeepaliJ at Salsa Digital commentedVerified the module by applying patch #11.
![upgrade status](/files/issues//2022-09-06/Upgrade%20status.png)
Scanned using Upgrade Status.
The module is incompatible with Drupal 10, although it is not showing any error but showing warnings which seems fixable as shown in the attached screenshots
Upgrade status
Warnings
![Warnings](/files/issues/2022-09-06/Upgrade_status%20warnings.png)
Also, this module cannot be made D10 compatible unless and until votingapi module is not made compatible with D10
Comment #14
DeepaliJ CreditAttribution: DeepaliJ at Salsa Digital commentedComment #15
dancbatista CreditAttribution: dancbatista at CI&T commented@Deepalij following the instruction of @TR in #8 I just to applied assertRaw() change (In the line 145 of FivestarTest.php I'm using the function $this->assertSession()->responseContains() instead). So For the other changes, I will create issues separately. Please just scan the module with Upgrade Status before using the patch and scan again after using it and observe if the warning about assertRaw() is fixed.
Comment #16
vitorbs CreditAttribution: vitorbs at CI&T commentedI'll review this one.
Comment #17
vitorbs CreditAttribution: vitorbs at CI&T commented-
Comment #18
vitorbs CreditAttribution: vitorbs at CI&T commentedAs @dancbatista said, the patch is re-rolled and only change the test function, so the others problems is better to create another issues to work on them. Moving to RTBC, if anyone disagree with me please tell me and i will work on it. Thanks!
Comment #19
vitorbs CreditAttribution: vitorbs at CI&T commentedComment #20
WebbehPlease do not roll a ProjectBot project to RTBC:
Removing screenshots.
Comment #21
WebbehComment #22
WebbehComment #23
WebbehAh, resetting to Needs Review for review by maintainer TR in #8 and work completed in #11.
Comment #24
dancbatista CreditAttribution: dancbatista at CI&T commentedBeing mentored for @TR in #8, I've created the following related issues.:
1) The return type declarations in the tests #3308839: Return type declarations in the tests
2) The jquery.once changes for the module #3309729: The jquery.once changes for the module
Comment #25
Project Update Bot CreditAttribution: Project Update Bot commentedComment #26
mmjvb CreditAttribution: mmjvb as a volunteer commentedWith https://www.drupal.org/project/infrastructure/issues/3309815) fixed, setting RTBC is no longer considered sabotaging the bot.
Attracting attention of maintainer to commit. Suggest to set to Active when committed to receive potential additional fixes from the bot.
Comment #27
heddnThis is a combined patch of #3308839: Return type declarations in the tests and #3309729: The jquery.once changes for the module with the needed drupal 10 .info.yml changes added to show tests pass on the testbot.
Comment #28
edurenye CreditAttribution: edurenye commentedvotingapi supports D10 in the -dev version of the module.
Setting to needs review because there is a new patch and also to get updates from the Project Update Bot.
Comment #29
wxman CreditAttribution: wxman commentedDoes anyone know if there will be a update coming? I added this to a site I'm designing because it does exactly what I need. I'm not a lot of help in fixing problems, though I wish I was.
Comment #30
wxman CreditAttribution: wxman commentedIf it helps anyone, I applied the patch in #27 then ran upgrade status.
web/modules/contrib/fivestar/fivestar.module
Line 82: The module is defining "theme_fivestar_preview" theme function. Theme functions are deprecated. For more info, see https://www.drupal.org/node/2575445.
web/modules/contrib/fivestar/composer.json
Line 0: The drupal/core requirement is not compatible with the next major version of Drupal. Either remove it or update it to be compatible. See https://drupal.org/node/2514612#s-drupal-9-compatibility.
This seemed to work until I went to a page showing the votes. For every book cover with votes under it I had:
Deprecated function: addcslashes(): Passing null to parameter #1 ($string) of type string is deprecated in Drupal\Core\Database\Connection->escapeLike() (line 1525 of core/lib/Drupal/Core/Database/Connection.php).
I couldn't track down what was the cause so I had to go back to my saved backup of fivestar before the patch.
Comment #31
TR CreditAttribution: TR commentedA lot of this has now been done in other patches. To see what problems remain, I'm going to try testing against D10 here.
Comment #32
TR CreditAttribution: TR commentedComment #33
chikePatch #31 in combination with MR !10 at The jquery.once changes for the module and patch #3 at Remove 'fivestar_preview' theme function got the module working.
Comment #34
AbhinavK CreditAttribution: AbhinavK at TATA Consultancy Services for Pfizer, Inc. commentedAs mentioned in #33, the combination of Patch #31 with MR !10 of The jquery.once changes for the module and Patch #3 of Remove 'fivestar_preview' theme function makes the module Drupal 10 compatible.
So changing the status to RTBC.
Also uploading a combined patch of all the changes for anyone who needs it.
Comment #35
TR CreditAttribution: TR commentedPlease comment in those other issues - that is where those problems are being discussed.
Comment #36
Diego_Mow CreditAttribution: Diego_Mow as a volunteer and at CI&T commentedBoth issues are RTBC.
I'd suggest we get them merged ASAP as they are blockers for future of this module.
Comment #37
RgnYLDZ CreditAttribution: RgnYLDZ commentedAny update on RTBC?
Comment #38
Libbna CreditAttribution: Libbna as a volunteer and at QED42 for Drupal India Association commentedAfter updating the site to d10, I am trying to apply the #34 patch using drupal-lenient but after running composer install it throws error "Cannot apply patch". Can anyone tell me the reason for this issue? Thannks.
It got resolved, I had to remove two extra patches that was added for fivestar.
Comment #39
wxman CreditAttribution: wxman commentedI read the comment above, but the only FiveStar patch I have is the d10_combined_3287600-34.patch. Mine won't load either, and FiveStar has stopped working. I'm also back to getting Deprecated function: addcslashes() errors.
Comment #42
O'BriatI made a MR with the latest combined patch from #34, so you could install it with drupal 10 composer.
You have to use a specific version in require section (here's 1.x-dev), then add a new repository (with the same version) before the drupal one (see https://www.computerminds.co.uk/articles/apply-drupal-9-compatibility-pa...).
:
Comment #43
wxman CreditAttribution: wxman commentedI gave #42 a try.
Not sure what's going wrong. I'm running Version: 8.x-1.0-alpha3
Comment #44
O'BriatYou have to edit your repositories section in composer.json, put this custom repo before the https://packages.drupal.org/8 one.
(I will update my comment to be more clear)
See https://www.computerminds.co.uk/articles/apply-drupal-9-compatibility-pa...
Comment #45
wxman CreditAttribution: wxman commentedThat's kind of what I did. Here's my composer.json:
I don't remember why I have the second
"1": {
"type": "composer",
"url": "https://packages.drupal.org/8"
},
My Require is : "drupal/fivestar": "^1.0@alpha",
could that be the problem?
Comment #46
wxman CreditAttribution: wxman commentedI changed the version to match mine "version": "1.x-dev", changed to: "version": "1.0@alpha",
After running update I get no errors there, but I'm still getting "Deprecated function: addcslashes()" errors, and the stars are not working.
Comment #47
O'BriatWhere did you see these errors?
Can you check that the patch is apply to the installed module ?
As far as I know "addcslashes" is not used in the fivestar module, could you check to which file+line this error points?
As for your compose.json
"https://packages.drupal.org/8" is the main drupal repo, so its fine (but it's duplicated in the entry "1", so you could safely remove it).
I think the packagist ones are useless since it's the default composer repo (https://getcomposer.org/doc/04-
Comment #48
O'BriatNote that core requirement should not be places inside a module composer.json requirements, see https://www.drupal.org/docs/develop/creating-modules/add-a-composerjson-...)
I add a commit to this MR that remove it.
Comment #49
wxman CreditAttribution: wxman commentedTo answer #48 I did not change anything like that.
To answer #47. If you see in my response #45, that is what my composer.json looked like. My other question was regarding whether I should change the 'require' on my composer.json which is
"drupal/fivestar": "^1.0@alpha",
to match your version in the repository:"version": "1.x-dev",
?I know it's long but here's the error
Comment #50
O'Briat#48 was a general notice and directed to module maintainer.
#47 the same version should be used in require > "drupal/fivestar": "1.x-dev" and repositories > fivestar > package > "version": "1.x-dev", (I'm not sure if the value matter, but it should be the same in the two spots)
About your error, it seems like a notice about deprecated usage that originated from an entity in src/Element/Fivestar.php(273). That part is not covered by this issue but is tracked in another one: https://www.drupal.org/project/fivestar/issues/3324052.
Could you test this patch?
Could you also describe the steps to reproduce this error, so I can test it myself?
Comment #51
heddn@TR, any direction on porting this and votingapi to D10? I tried to put forward an effort about 6 months ago and it got bogged down on needing tests. Someone tried to write tests, but that got bogged down too. We're now 4-5 months from loosing D9 support and this pair of modules is the lone blocker to upgrading. What is a workable plan to get us to D10?
Unfortunately, the budget and window I had to push the dial on this 6 months has since dried up. So I'm more interested now as an observer rather then a super active participant. I'm happy to do reviews and confirm any work here still is functional on D10. But don't have a lot of extra time right now.
Comment #52
wxman CreditAttribution: wxman commented@O'Briat I probably have a bigger problem then. I just made a D9 test site, installed 8.x-1.x-dev, edited the composer.json as you suggested, and added a Fivestar field to a test content. It's working fine with no errors. There must be something else conflicting with it on the other site that's causing the error.
Comment #53
O'Briat@wsman, if you are not using ad Drupal 10 coren you could just use the patching system (not need to declare a new repository),e.g.:
Comment #54
wxman CreditAttribution: wxman commented@O'Briat My main site will be D10 as soon as I can get this all fixed. Fivestar is the last one I need to get working. My temporary site I just made used the latest D9 version, and 8.x-1.x-dev for Fivestar. It's working great with no errors at all. That seems to mean something else on my main site is causing the error.
As a test on my main D9 site which is using 8.x-1.x-dev, and the edited JSON, I went to the book page it's on and removed the block with the Fivestar rating. The error went away, I added the field back in and the error returned.
I also just tried changing my theme on the main site to the Claro 9.5.10 theme. The error appeared again as soon as I added Fivestar to the page display.
Comment #55
wxman CreditAttribution: wxman commented@O'Briat I think I did it! I just couldn't figure out the reference hash, but I think I got it right.
Ran composer update, the drush cr, and all the errors are gone completely. Now after all of this I'm guessing none of it will work on a D10 site yet?
Comment #56
wxman CreditAttribution: wxman commentedEven after all the MR and patches the D10 testing still shows the FivestarTest.php 'assertRaw()' error.
The other two are connected with web/modules/contrib/fivestar/fivestar.libraries.yml. The 'fivestar.base' library, and 'fivestar.ajax' library depending on the core/jquery.once asset library.
Comment #57
DamienMcKennaI think this is the appropriate status, given it seems a small change is needed for the Once library.
See https://www.drupal.org/node/3158256 for details.
Comment #58
heddnRe #57: is that handled by #3309729: The jquery.once changes for the module?
Comment #59
wxman CreditAttribution: wxman commentedI tried adding the MR in #15 in that topic but mine is still showing those errors for D10 upgrades
Comment #60
O'BriatHere's the drupal-check on the patched module:
Comment #61
O'Briat@wxman, I pretty sure that you could not set more than one source in a repository. I think you should use the repo to get this issue and use the patch section to apply additional patches. Maybe we could continue this discussion on slack to avoid polluting this thread ?
@DamienMcKenna @heddn, as said in #42 the MR (https://git.drupalcode.org/project/fivestar/-/merge_requests/19/diffs) contains the whole combined patch from #34 which contain the "once" correction provided by #3309729 (which is RTBTC), so this problem should not occur.
Comment #62
heddnI took the patch from #34 and applied it to a D10 site w/ the lenient composer plugin. I'm able to vote using fivestar widget. I think this is good to go. As far as the readout from drupal-check, all of that seems to be code standard things un related to drupal 10 upgrade.
Given my manual testing, marking RTBC.
Comment #63
DamienMcKennaAgreed on committing the changes as-is and working on additional fixes as separate issues, e.g. the getForm() method has been that way since at least 8.9: https://api.drupal.org/api/drupal/core%21lib%21Drupal%21Core%21Form%21Fo...
Comment #64
O'BriatI'm concern about the "field_read_fields" function calls in the module file, there are Drupal 7 ones, should I open a separate issue about that ?
Comment #65
O'Briatupgrade_status shows no errors or warning, as for drupal-check, there are two issues about that (I miss them :( ) :
https://www.drupal.org/project/fivestar/issues/3224945 & https://www.drupal.org/project/fivestar/issues/3224943.
As my basic usages are working fine on Drupal 10 without throwing any errors, I think it cold be marked as RTBC
Comment #66
O'Briat@heddn Sorry, but most errors are more than just "code standard things": missing function, removed parameters, ... I regroup them in one issue/MR https://www.drupal.org/project/fivestar/issues/3377377. IMHO, until these issues are fixed, this module should remain as alpha or beta.
Comment #67
DamienMcKenna@O'Briat: Nobody is disputing the stability status of the module, we're just focused on getting this change committed.
Comment #68
markus_cz CreditAttribution: markus_cz commentedHi, I'm trying to get my head around what I need to do to update to Drupal 10, and I'm a bit confused. I'd prefer waiting for a release, or even a dev-build with all the changes applied. However, judging by the commit log, no changes have been commited in a year. If I understand correctly, this hasn't been done yet because we're waiting for the module maintainer but they're not active?
Comment #69
wxman CreditAttribution: wxman commented@markus_cz I've been watching this too for the same reason. I have the whole site ready to upgrade to 10 except for FiveStar. If it's any help to you, Here are parts of my composer.json that I applied patches and MR's:
So far everything is working great, and the errors have all gone. Upgrade Status still says it's not compatible though. It's my only one.
Comment #70
wxman CreditAttribution: wxman commentedI am by no means a PHP expert. I understand some of it, and look up what I don't. Please fogive me if this sounds wrong.
Upgrade Status showed three errors. One was in web/modules/contrib/fivestar/tests/src/Functional/FivestarTest.php line 145:
$this->assertRaw('No votes yet', 'Fivestar field has no votes.');
The test says it need to be changed to:
$this->assertSession()->responseContains('No votes yet', 'Fivestar field has no votes.');
The other two were library's in web/modules/contrib/fivestar/fivestar.libraries.yml for the "Remove jQuery dependency from the once feature":
I read the post regarding that at https://www.drupal.org/node/3158256 and tried this change:
I saved, flushed caches, and checked all my pages with Fivestar. Everything worked perfectly and no errors. This goes along with the MR and patch I posted above that come from the people that really do know what they are doing. Upgrade Status still has two errors left on the web/modules/contrib/fivestar/fivestar.info.yml, and web/modules/contrib/fivestar/composer.json that complain about core_version_requirement and drupal/core requirement but that is just a simple fix. Is what I did wrong, because it seems to work?
Comment #71
ivnish CreditAttribution: ivnish commentedSame question as #51
TR, what is the final blocker of the module release with D10 compatibility? Can you explain?
Comment #72
ivnish CreditAttribution: ivnish commentedI reroll the patch to the latest dev
Comment #73
ivnish CreditAttribution: ivnish commentedComment #74
heddnre #72: what version of the code did you re-roll? There are several patches and even an open MR. What was the source of your changes so it is easy to review?
Comment #75
jonathan_hunt CreditAttribution: jonathan_hunt at Catalyst IT commentedfwiw, applying patch from #72 allows FiveStar to pass the Upgrade Status Drupal 10 readiness checks.
Comment #76
ivnish CreditAttribution: ivnish commentedheddn, I analyzed the patch #34 and the MR. I removed some already committed code so patch is applying to the latest dev version.
As said #75 the patch is successfully applied and passed the Upgrade Status Drupal 10 readiness checks.
Also I manually tested my project and I don't have any problem. Everything works and no any WSOD
Comment #77
wxman CreditAttribution: wxman commentedI just installing the latest DEV but it's showing incompatible again. I did
composer require 'drupal/fivestar:1.x-dev@dev'
.My composer.json still has:
The errors are in the web/modules/contrib/fivestar/fivestar.libraries.yml. It want's fivestar.base and fivestar.ajax removed.
The others are the simple ones in fivestar.info.yml core_version_requirement
Comment #78
jonathan_hunt CreditAttribution: jonathan_hunt at Catalyst IT commented@wxman I simply ran
composer require "drupal/fivestar:dev-1.x"
with no specific references incomposer.json
.composer.patches.json
:Comment #79
wxman CreditAttribution: wxman commented@jonathan_hunt I removed everything and added the patch you said. Reran require and all is well now. Thank you.
Comment #80
heddnI've opened #3386131: Offer to co-maintain Fivestar to hopefully keep the ball rolling here.
Comment #81
ivnish CreditAttribution: ivnish commentedheddn, thanks!
Comment #82
wxman CreditAttribution: wxman commentedHas something changed? I was getting ready to take the plunge to upgrade the site to 10 and even though I have things still set from #78 I'm now back five star not working and a page full of:
Deprecated function: addcslashes(): Passing null to parameter #1 ($string) of type string is deprecated in Drupal\Core\Database\Connection->escapeLike() (line 1525 of core/lib/Drupal/Core/Database/Connection.php).
Did I miss something?
Comment #83
ivnish CreditAttribution: ivnish commentedThe patch #72 doesn't have "addcslashes" function. Try to find it in another modules
Comment #84
wxman CreditAttribution: wxman commented@ivnish I honestly don't know what's going on now. I have gone back to a backup copy from a couple of weeks ago, and the error is there on every page there is a FiveStar field. On the pages that it's not used the error doesn't show up. The only patch I'm using is the one shown in #78.
Comment #86
heddnRe-titling. The changes are not automated.
Comment #88
heddnGiven the latest comments in #3273701: Remove 'fivestar_preview' theme function, I'm leaving the dead code for an eventual conversion, or at least we can keep debating how we want to handle its conversion. I tested leaving the code in the code-base and nothing bad happens. It is dead code. Commented as such and committed. A tagged D10 release should come shortly.
Hopefully I got all the right people who were involved on this issue credited. It ended up that most of the work was done in sub-issues and this one really just changes the supported versions in composer.json and .info.yml.
Comment #89
heddnSee https://www.drupal.org/project/fivestar/releases/8.x-1.0-alpha4
Comment #90
wxman CreditAttribution: wxman commentedWell I made the leap to D10. I installed the latest Fivestar Alpha4. The only error on the the site is Fivestar though. I'm still getting:
Deprecated function: addcslashes(): Passing null to parameter #1 ($string) of type string is deprecated in Drupal\Core\Database\Connection->escapeLike() (line 1525 of core/lib/Drupal/Core/Database/Connection.php).
I also noticed that the stars can no longer be selected, or edited, like I want to give a book a rating. I know it has to be connected to Fivestar because it only occurs on pages with that field on it.
I have no other patches installing. Is there a Fivestar patch I still need that I'm missing?
Comment #91
heddn@wxman can you open a new issue w/ steps to reproduce? Then link it here? Ideally on a fresh/vanilla Drupal 10 install. I'm using this module on a D10 site for several months now and haven't not seen those specific errors in the logs.
Comment #92
wxman CreditAttribution: wxman commented@heddn I did as you asked: https://www.drupal.org/project/fivestar/issues/3391065.