-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot install plugin in Craft 5.2 #42
Comments
I'm experiencing the same issue. In craft repositories changelog for 5.0.0: |
The plugin has not been updated to support Craft 5 - our apologies. We are working on the updates now, and will let you know when a version is ready for testing and release. |
I'm currently testing a version that works with Craft CMS 5 (v5.3.4). This includes modifications that support Craft Commerce products (https://github.com/brilliancenw/craft-algolia-sync/releases/tag/5.0.0-alpha) |
Any updates? Craft 5 CMS plugin store is showing this plugin as available for Craft 5. Thank you! |
Hello @npegman - were you able to test the latest version? (5.0.3-alpha), we have that running on Craft 5.5.10. If that's working for you, we can bring that into the stable build. In your composer file, adjust the version:
|
I was not able to get 5.0.3 installed. I get the same error about composer requiring craft 4 after running:
ddev composer require "brilliance/algolia-sync:^5.0.3-alpha" -w && ddev craft plugin/install algolia-sync
brilliance/algolia-sync v5.x-dev requires craftcms/cms ^4 -> found craftcms/cms[4.0.0-alpha.1, ..., 4.x-dev] but it conflicts with your root composer.json require (^5.5.5)
Thank you Mark
…-Nate
[cid:emlLogo_d78dfc7d-3f3d-48da-8249-26f4654c9f08.jpg]<https://unist.com> Nate Pegman Sr. Marketing Communications
***@***.*** unist.com<https://unist.com>
Phone: 616.588.2237
Fax: 616.949.9503
Unist, Inc. | 4134 36th St SE | Grand Rapids, MI 49512 | United States
The information transmitted, including attachments, is intended only for the person(s) or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of or taking of any action in reliance upon this information by person(s) or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and destroy any copies of this information.
From: Mark Middleton ***@***.***>
Date: Thursday, January 23, 2025 at 4:13 PM
To: brilliancenw/craft-algolia-sync ***@***.***>
Cc: Nate Pegman ***@***.***>, Mention ***@***.***>
Subject: Re: [brilliancenw/craft-algolia-sync] Cannot install plugin in Craft 5.2 (Issue #42)
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
Hello @npegman<https://github.com/npegman> - were you able to test the latest version? (5.0.3-alpha), we have that running on Craft 5.5.10. If that's working for you, we can bring that into the stable build. Thank you
—
Reply to this email directly, view it on GitHub<#42 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AGEZ25HXH66ZWR4BAKT6IIL2MFLNTAVCNFSM6AAAAABVYIQNZ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMJRGAZDOOJZG4>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
@npegman - I was able to perform a clean install on ddev without issue. I see the error mentions "v5.x-dev" - is it possible that is already in your composer.json instead of the 5.0.3-alpha? Can we hop on a screenshare to work through any issues the plugin may be causing? Drop me a note in the Craft Discord (username: whirledweb) or at [email protected]. I'm confident we can get it resolved - I apologize for the frustration. |
When trying to install the plugin, there's an undefined error. When cheking the logs, I get the following.
..."exception":"[object] (Error(code: 0): Undefined constant craft\\services\\Utilities::EVENT_REGISTER_UTILITY_TYPES at /var/www/html/vendor/brilliance/algolia-sync/src/AlgoliaSync.php:137)"...
The text was updated successfully, but these errors were encountered: