-
Notifications
You must be signed in to change notification settings - Fork 31
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
Articles cannot find Quip 2.3.5 on install #161
Comments
This issue has been mentioned on MODX Community. There might be relevant details there: https://community.modx.com/t/articles-container-just-shows-blank-page/5393/5 |
Any idea why that might happen @muzzwood? I just checked the listing and that seems fine to me. |
Older versions where still active, I've disabled them for now to see if that helps. |
Not sure, I'm afraid. 😕 I just tested it again:
|
@rthrash is it possible to describe all older releases of Quip? All of them appear to be active and causing some issues since they all come up in the response of the API. |
Interesting, as it seemed to work for me (see my latest post in mentioned thread above). I completely uninstalled and (force) removed Articles and all dependencies, purged old packages and removed the core/cache folder manually before I tried to download and install Articles again. It did work for me though, after all. |
Can someone else test if this issue is now solved? |
Bug report
Summary
Quip 2.3.5 is not found by the resolver when installing Articles
Some quick testing showed that changing the resolver to install Quip 2.3.3 works. Odd!
Step to reproduce
Try installing Articles 1.8.0 on MODX 2.8.4 while Quip is not installed.
Observed behavior
Reported by @VibeDesign https://community.modx.com/t/articles-container-just-shows-blank-page/5393
Install completes fine but has the error message:
Manually installing Quip first allows Articles to function.
Expected behavior
Find Quip and install it! 👏🏻
Environment
Articles 1.8.0 on MODX 2.8.4
The text was updated successfully, but these errors were encountered: