We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 15558
    • 108 Posts
    thanks for your answers

    I'd like to follow those steps, Bob, unfortunately it seems to be messed up, whatever the package I try to uninstall, I get lots of

    "xPDO->toCache() could not cache object with signature"

    and the uninstall script breaks up before its end. Can someone remember me what Articles does about the add-ons it contains ? Can I install Articles, and then just remove one of its add-ons ? I guess no ? My greatest wish would be to erase everything about Articles, Quip, getResource/Page, TagLister, everything that concerns Articles, and then install fresh stuff. Can I do that easily in the database ?
      Sorry for that ⇧ , I'm no dev but I wanna try
      • 3749
      • 24,544 Posts
      I've been there. A while back I had to clean out some quip/articles/taglister/archivist references from the DB. I searched for those strings in the DB and removed the records. I think this had to do with an older version of the Articles package not having a proper package signature. I believe it's been corrected in later versions but I'm not sure.

      BTW, the errors you saw on installation are normal if the package has been installed before. They don't necessarily indicate trouble. This is also true of many of the errors you see when uninstalling if PHP is set to report E_NOTICE errors and display_errors() is on. This often becomes an issue when the host upgrades PHP (they almost never tell you that they're doing it). Recent versions often have E_NOTICE on by default.

      MODX doesn't mess with the error reporting settings because you might want them on in a development environment, but they should always be off on a production site.



        Did I help you? Buy me a beer
        Get my Book: MODX:The Official Guide
        MODX info for everyone: http://bobsguides.com/modx.html
        My MODX Extras
        Bob's Guides is now hosted at A2 MODX Hosting
        • 15558
        • 108 Posts
        Thank you Bob.

        At this point, i cleaned the database and deactivated the cache so I get installs/uninstalls/removals that seem to be proper.

        And comments still don't work. (For reminder, they used to work on that website, so eveything about Quip calls and associated templates shall be okay because I didn't modify any of them...)


        What if I told you people "Hi, my commenting system is down, this is my error log, what does that mean ?"

        and here comes the log :

        [2013-02-07 23:08:04] (ERROR @ /index.php) [Quip] Thread not found for comment: Array
        (
        [id] => 2
        [thread] => Leila-UI-thread
        [parent] => 0
        [rank] => 0000000002
        [author] => 1
        [body] => dummy test comment
        [createdon] => 2013-02-07 23:08:04
        [editedon] =>
        [approved] => 1
        [approvedon] =>
        [approvedby] => 0
        [name] => kehezen
        [email] => [email protected]
        [website] =>
        [ip] => xx.xxx.xxx.xxx
        [deleted] =>
        [deletedon] =>
        [deletedby] => 0
        [resource] => 95
        [idprefix] => qcom
        [existing_params] => Array
        (
        [a] => 47
        )

        [nospam] =>
        [auth_nonce] =>
        [preview_mode] =>
        [comment] => dummy test comment
        [quip-post] => 1
        )





        More info :

        A new entry is created in the modx_quip_threads table as I visit a published ressource for the first time, that is normal isn't it ?
        For example :

        - I visit http://swqw.fr/chroniques/musiques-electroniques/kane-ikin-sublunar.html
        - the new entry in modx_quip_threads has for "name" the value "Kane Ikin - Sublunar-thread". This is because I'm asking for this :

        [[!QuipReply?
        &thread=`[[*pagetitle]]-thread`
        &tplAddComment=`tplAddComment`
        &closeAfter=`0`
        ]]

        and it's okay for me.

        - Then I post a comment on that ressource. The comment doesn't show up. Backend shows the following :



        and



        No other entry is created in threads table in the database.

        But if I check the modx_quip_comments table, the posted comment exists, and has for "thread" the value "KaneIkin-Sublunar-thread". Please notice the absence of spaces.


        That's it.
        I may sound gross by assuming that this isn't a big issue to solve but unfortunately I can't get through this. Can somebody here ? I'd be grateful. (I just typed graceful at first). Thanks for reading [ed. note: kehezen last edited this post 13 years, 8 months ago.]
          Sorry for that ⇧ , I'm no dev but I wanna try
          • 42261
          • 3 Posts
          Since I upgraded to Quip 2.3.3 I've been getting the same error as you kehezen.

          It looks like Quip strips all the spacing in the thread title. I have a resource with the title "Document Test 1" and the quip call:
          [[!Quip? &thread=`Doc: [[*pagetitle]]` &threading=`0`]]
          [[!QuipReply? &thread=`Doc: [[*pagetitle]]`]]

          This should create a thread called "Doc: Document Test 1" and so it does but no matter how many comments I submit, the front-end and the Quip Threads Manager won't display a thing. And this is what the error log reports:

          [2013-03-03 23:10:08] (ERROR @ /events/index.php) [Quip] Thread not found for comment: Array
          (
          [id] => 9
          [thread] => DocDocumentTest1
          [parent] => 0
          [rank] => 0000000009
          [author] => 1
          [body] => testinggg
          [createdon] => 2013-03-03 23:10:08
          [editedon] =>
          [approved] => 1
          [approvedon] =>
          [approvedby] => 0
          [name] => Default Admin User
          [email] => [email protected]
          [website] =>
          [ip] => ::1
          [deleted] =>
          [deletedon] =>
          [deletedby] => 0
          [resource] => 12
          [idprefix] => qcom
          [existing_params] => Array
          (
          )

          [nospam] =>
          [auth_nonce] =>
          [preview_mode] =>
          [comment] => testinggg
          [quip-post] => 1
          )

          I checked the Db and the comments were submitted in a thread called DocDocumentTest1. Bug? Everything was fine with Quip 2.3.2, never had any problems with thread titles that include spacing.