I had a similar issue and discovered, as I was trying things, that setting the default value to a fixed value (which I did just for testing) and then setting it back to Content ID from URL seemed to get it working again.
Kristi Wachter → created an issue.
THANK YOU, No Sssweat - that is extremely helpful information!
Kristi Wachter → created an issue.
Same here - I'm not using Skeleton, but patch #6 fixed this error for me.
Is this something that could be committed?
Thank you!
Kristi Wachter → created an issue.
zim - THAT WORKED! Thank you so much. Now that I've created a Public Client Key and used that on my Accept.js config page, my transactions are going through.
Thank you SO MUCH for answering my question and sharing that! I hope this thread will be helpful to anyone else who runs into a similar problem.
Kristi Wachter → created an issue.
Kristi Wachter → created an issue.
That's extremely helpful, John - thanks so much for sharing your experience and for listing those patches. I really appreciate it!
Hi @TomTech,
Thanks so much for the very helpful reply!
That pointed me in the right direction - I'm not using a custom entity, I just somehow managed to create my Order Type Item without assigning a Purchasable Entity Type.
Is there publicly-editable documentation for these steps that I could contribute to? I don't always find time to help out with documentation, but I'd love to contribute if I can.
Thanks again for your quick assistance!
Kristi
Kristi Wachter → created an issue.
In some cases, clearing the cache may help. I did
- Flush all caches
- Flush plugins cache
- Flush all caches
just for good measure, and the problem went away for me.
Just confirming another site where rolling back to 4.20 fixes the problem, and urging a reroll of the patch and getting this committed to the next release if possible. Thanks!
Kristi Wachter → created an issue.
Thanks to everyone for reporting your experiences.
robotjox, did you find an exit plan, and if so, could you share what you had to do to uninstall it, and what system you substituted instead?
Thanks!
Hi TR,
Thanks for the reply!
I was mostly thinking an adjustment to the Rules composer requirements might be helpful for folks who are new to Drupal. I know I could adjust my minimum-stability settings, but out of the box, starting up Drupal with the recommended
composer create-project drupal/recommended-project projectname
gets you relatively strict minimum-stability.
So, for newer users, trying to do
composer create-project drupal/recommended-project projectname
and then
composer require -W 'drupal/rules:^3.0@alpha'
throws an error that may just make them give up - whereas, if typed-data beta is an acceptable requirement for rules, I wondered whether adjusting the composer requirements for Rules (to reflect that beta version of typed-data) might allow the commands to run seamlessly for new users.
If it doesn't make sense to make any changes, I understand and thank you for at least reading this, and maybe the existence of this issue will at least help newer users find a quick solution to the error message:
they can either use composer to install typed-data before installing rules, or they can, as you say, install both rules and typed-data in the same composer command.
Thanks!
Kristi Wachter → created an issue.