# Quip Comment not posting in Articles **URL:** \ **Category:** Support\ **Tags:** revo-3\ **Created:** [July 22, 2023, 8:17pm UTC](https://community.modx.com/t/quip-comment-not-posting-in-articles/6904 "2023-07-22T20:17:29Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![masakia](https://community.modx.com/letter_avatar_proxy/v4/letter/m/ac91a4/32.png) [@masakia](https://community.modx.com/u/masakia)\ **Post date:** [July 22, 2023, 8:17pm UTC](https://community.modx.com/t/quip-comment-not-posting-in-articles/6904/1 "2023-07-22T20:17:29Z")
### Summary I installed Articles 2.00 Beta for Modx 3, (my installation is 3.03) When trying to post comment, Modx jumps to blank page and comment not posted. In modx error log, I think it says modResClient class is not loading. ```auto [2023-07-22 13:59:52] (ERROR @ /var/www/clients/client1/web6/web/core/vendor/xpdo/xpdo/src/xPDO/xPDO.php : 666) Could not load class: modRestClient from rest.modrestclient [2023-07-22 13:59:52] (ERROR @ /var/www/clients/client1/web6/web/core/vendor/xpdo/xpdo/src/xPDO/xPDO.php : 1272) Problem getting service rest, instance of class rest.modRestClient, from path ``` Corresponding server error log says null value call in stopforumspam class. ```auto 2023/07/22 13:59:52 [error] 2268444#2268444: *21813 FastCGI sent in stderr: "PHP message: PHP Fatal error: Uncaught Error: Call to a member function getConnection() on null in /var/www/clients/client1/web6/web/core/components/quip/model/stopforumspam/stopforumspam.class.php:76 Stack trace: #0 /var/www/clients/client1/web6/web/core/components/quip/model/stopforumspam/stopforumspam.class.php(56): StopForumSpam->_getClient() #1 /var/www/clients/client1/web6/web/core/components/quip/model/stopforumspam/stopforumspam.class.php(36): StopForumSpam->request() #2 /var/www/clients/client1/web6/web/core/components/quip/processors/web/comment/create.php(71): StopForumSpam->check() #3 /var/www/clients/client1/web6/web/core/components/quip/model/quip/request/quipcontroller.class.php(130): include('/var/www/client...') #4 /var/www/clients/client1/web6/web/core/components/quip/controllers/web/ThreadReply.php(261): QuipController->runProcessor() #5 /var/www/clients/client1/web6/web/core/components/quip/controllers/web/Thr2023/07/22 13:59:52 [error] 2268444#2268444: *21813 FastCGI sent in stderr: "PHP message: PHP Fatal error: Uncaught Error: Call to a member function getConnection() on null in /var/www/clients/client1/web6/web/core/components/quip/model/stopforumspam/stopforumspam.class.php:76 ``` Any suggestion where I should be looking into from here? Articles - version 2.00 Beta Quip - version 2.3.5-pl ---
**Author:** ![halftrainedharry](https://community.modx.com/user_avatar/community.modx.com/halftrainedharry/32/1063_2.png) [@halftrainedharry](https://community.modx.com/u/halftrainedharry)\ **Post date:** [July 22, 2023, 8:48pm UTC](https://community.modx.com/t/quip-comment-not-posting-in-articles/6904/2 "2023-07-22T20:48:42Z")
Quip is not compatible with MODX 3. > > > \## Feature request > \### Summary > Quick summary what's this feature request about…. > > \### Why is it needed? > A clear and concise description of what the problem is. Ex. I'm always frustrated when \[...\] > > \### Suggested solution(s) > A clear and concise description of what you want to happen. > > \### Related issue(s)/PR(s) > Let us know if this is related to any issue/pull request. > > > Perhaps modernising Quip would be a good first use of the \[OpenCollective funds\]…(https://opencollective.com/modx), though I have no idea how much work Quip would need. Probably better to discuss \[in the right repository\](https://github.com/modxcms/Quip/issues) too. > > \_Originally posted by @Mark-H in https://github.com/modxcms/Articles/issues/152#issuecomment-1325241736\_ > > I took this comment from the Articles repository. A few thoughts of mine: > > I think making Quip MODX3 compatible does not require many changes. However, the current version has a few bugs and fixing them requires more work. Quip also generates many PHP warnings and may not be compatible with the latest PHP versions. > > Even more work is needed if Quip will be changed to ajax-based. > > I don't know how widely Quip is being used. I am using it on a website and it is a great extra. However, I have started replacing Quip with Hashover to be able to upgrade to MODX3. I am not sure if there is a real need for a MODX-based commenting component. The OpenCollective funds seem to be quite limited so maybe they should be targeted to something else? ---
**Author:** ![masakia](https://community.modx.com/letter_avatar_proxy/v4/letter/m/ac91a4/32.png) [@masakia](https://community.modx.com/u/masakia)\ **Post date:** [July 22, 2023, 9:58pm UTC](https://community.modx.com/t/quip-comment-not-posting-in-articles/6904/3 "2023-07-22T21:58:36Z")
Thank you! I started to think so. (lol) Quip in Extra menu is also broken. The menu points to Core 1. After I manually correct it to point to quip home, I see threw of error (simplified for brevity) ```auto Unable to load processor for action "mgr/thread/getList", it does not exist as an autoloadable class that extends \MODX\Revolution\Processors\Processor, and also not as a file in "/var/www/clients/client1/web6/web/core/components/quip/processors/mgr/thread/getList.class.php" Unable to load processor for action "mgr/comment/getUnapproved", it does not exist as an autoloadable class that extends \MODX\Revolution\Processors\Processor, and also not as a file in "/var/www/clients/client1/web6/web/core/components/quip/processors/mgr/comment/ getUnapproved.class.php" Unable to load processor for action "mgr/comment/getList", it does not exist as an autoloadable class that extends \MODX\Revolution\Processors\Processor, and also not as a file in "/var/www/clients/client1/web6/web/core/components/quip/processors/mgr/comment/getList.class.php" Unable to load processor for action "mgr/comment/getUnapproved", it does not exist as an autoloadable class that extends \MODX\Revolution\Processors\Processor, and also not as a file in "/var/www/clients/client1/web6/web/core/components/quip/processors/mgr/comment/ getUnapproved.class.php" 1788) Unable to load processor for action "mgr/comment/getList", it does not exist as an autoloadable class that extends \MODX\Revolution\Processors\Processor, and also not as a file in "/var/www/clients/client1/web6/web/core/components/quip/processors/mgr/comment/getList.class.php" ``` So these error says the code is looking for camelCase.class.php and actual class files are all in lowercase. For the sake of it, I renamed class files and now backends are showing but this cant be a fix. Alright I will hold off the implementation. ---
**Author:** ![halftrainedharry](https://community.modx.com/user_avatar/community.modx.com/halftrainedharry/32/1063_2.png) [@halftrainedharry](https://community.modx.com/u/halftrainedharry)\ **Post date:** [July 22, 2023, 10:08pm UTC](https://community.modx.com/t/quip-comment-not-posting-in-articles/6904/4 "2023-07-22T22:08:11Z")
If you have some programming skills, maybe you can take a look at this commit someone made to a fork of the _Quip_ repository. > I haven’t looked at it and can’t verify that it works. ---
**Author:** ![masakia](https://community.modx.com/letter_avatar_proxy/v4/letter/m/ac91a4/32.png) [@masakia](https://community.modx.com/u/masakia)\ **Post date:** [July 24, 2023, 7:05pm UTC](https://community.modx.com/t/quip-comment-not-posting-in-articles/6904/5 "2023-07-24T19:05:57Z")
Thank you,. Using the commit above, I made a good progress. After editing those files, a lot of error message went away and Quip backend is correctly showing (using newly added ‘index’ at namespace quip) There is still a strange behavior going on. When I set up Article container settings and try viewing it first time, the comment form is displayed. However, it disappears when I try to view it the second time. Modx logs the following error. ```auto [2023-07-24 11:10:30] (ERROR @ /var/www/clients/client1/web6/web/core/vendor/xpdo/xpdo/src/xPDO/xPDO.php : 666) Could not load class: modAction from mysql.modaction [2023-07-24 11:10:30] (ERROR @ /var/www/clients/client1/web6/web/core/vendor/xpdo/xpdo/src/xPDO/xPDO.php : 786) modAction::load() is not a valid static method. ``` Now, If I place Quip and QuipReply snippet directly on a page resource outside Article Container, The form and comments are consistently displayed. I can add comment and it will be displayed when posted. So the Quip itself seems to be working. In Article Resource, on Second refresh of the page, where +comments and +comments\_form placeholders should be are blank. (looking at it with developper console) When I go to Article container settings and change any settings and save, and then view the page the form will show up in the first render. I can add a comment and comment will show up. Refresh the Browser and all comment section is gone. ---
**Author:** ![masakia](https://community.modx.com/letter_avatar_proxy/v4/letter/m/ac91a4/32.png) [@masakia](https://community.modx.com/u/masakia)\ **Post date:** [June 19, 2025, 3:24am UTC](https://community.modx.com/t/quip-comment-not-posting-in-articles/6904/6 "2025-06-19T03:24:42Z")
I maybe beating the dead horse here, but I had a chance to look little further at this combined use of modified version of Quip and Article 2.0.0 on modx3 install this week, after two years of break. The patch mentioned above, [GitHub - zahlenhexe/Quip: A commenting component for MODX Revolution](http://github.com/zahlenhexe/Quip) does seem to work. However, It was applied to Quip 2.3.4pl, so I created a version in [my github based on 2.3.5pl](https://github.com/a2life/modx3_quip) (and created [a transport package](https://github.com/a2life/modx3_quip/releases) so other people can try it out ) Now with Articles, this time I noticed that sample.articleTemplate uses [[!+article\_property]] (un-cached tags) version of properties. If I change all those properties to [[+article\_property]], (cached tag) then the page works fine with Quip. With un-cached tags, the page renders every first time the resource was altered but subsequent rendering of the page will not produce properties values and therefore any snippets based on those un-cached properties do not work, so naturally no outputs from Quip snippets are shown. At this time, I inclined to think this is more of Articles peculiarity rather than Quip’s issue. I am going to test it further but since I use WordPress (:P) for blog part of my site, and most of the summer will be used on repairing backyard patio, it will be a slow progress.