We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 28100
    • 66 Posts
    I had Jot, Newspublisher and Ditto all set up and working.  Yay!  The next day (I didn’t change a thing) it all turned to custard and now none of the articles I posted will show as anything except a blank page and if I post a new article I get directed to the ’error’ page.  Safari activity window shows a Internal Server error(500), I’ve checked MODx logs and there’s nothing showing there.  I’ve checked the CGI logs (GoDaddy) and there’s nothing there either.  All other pages and functions work OK. 

    I’ve stripped everything on the site back to only personalize, wayfarer, WebLoginPE, Jot, Newspublisher and Ditto.  I’ve even tried using the default template ... nada.

    I started off using the basic blog in wiki to set things up, then customised it to suit my needs.  This is what I now have:

    CommentsBlog:
    [[Jot? &subscribe=`0` &pagination=`10`]]

    (yes I’ve tried using it uncached)

    BlogTemplate:
    <div class="ditto_item" id="ditto_item_[+id+]">
            <h3 class="ditto_pageTitle"><a href="[~[+id+]~]">[+pagetitle+]</a></h3>
            <div class="ditto_documentInfo">by <strong>[+author+]</strong> on [+date+]</div>
            <div class="ditto_introText">[+introtext+]</div>
    </div>


    The SHOW_BLOG page:
    [!Ditto? &parent=`14` &summarize=`6` &total=`20` &commentsChunk=`CommentsBlog` &tpl=`BlogTemplate`!]


    The INPUT_BLOG page:
    [!NewsPublisher? &folder=`14` &footertpl=`CommentsBlog` &makefolder=`1` &rtcontent=`tvblogContent`!]


    Newpublisher Snippet edit - I removed the content line and replaced it with:
    [*blogContent*]


    And had my TV set up for it - with correct document group selected.


    Now when I go to clear the site cache I always have this message no matter how many times I click the clear cache button:
      Cache: Found 4 files in cache directory and deleted 1 cache files.
      New cache files will be created when pages are requested.
      The following files were deleted:
          * docid_2.pageCache.php
    Page id 2 is the site unavailable page I’d created - but no one would be accessing it so I don’t know why it won’t clear.

    From the admin panel, if I edit an article page and remove the {{CommentsBlog}} from the end of the article then I can access the page again - put it back and I get the blank page error.


    I’ve been trying to get this worked out for days now, I need to get it online but I’m at a total loss as to what to try next to fix things.  Any help would be most appreciated.  huh huh huh
      • 7231
      • 4,205 Posts
      Usually a blank page means a bad snippet. This may simply be a conflict between the sniipets. But you may be having issues with commands from a previous version of Ditto. For example &commentsChunk=`CommentsBlog` is not a valid command (as far as I know) for the current Ditto. I think it should be &removeChunk and to use &summarize you need to load the summary extender &extenders=`summary`.

      Change the Ditto call to:
      [!Ditto? &parents=`14` &summarize=`6` &total=`20` &removeChunk=`CommentsBlog` &tpl=`BlogTemplate` &extenders=`summary`!]
      Not sure if this will make a difference with your problem but could eliminate some possible issues.

      I am not familiar enough with either Jot or NewsPublisher to spot any compatibility issues there.
        [font=Verdana]Shane Sponagle | [wiki] Snippet Call Anatomy | MODx Developer Blog | [nettuts] Working With a Content Management Framework: MODx

        Something is happening here, but you don&#39;t know what it is.
        Do you, Mr. Jones? - [bob dylan]
        • 28100
        • 66 Posts
        Thanks dev_cw. I didn’t know that Ditto had been updated so thanks for that info ( I think). I’ve now updated to Ditto 2.1 and then tried your call there but get this error:

        PHP error debug
          Error: 	Missing argument 18 for ditto::determineIDs(), called in /home/content/s/a/l/html/www/domain name/manager/includes/document.parser.class.inc.php(769) : eval()'d code on line 793 and defined	 
          Error type/ Nr.: 	Warning - 2	 
          File: 	/home/content/s/a/l/html/www/domain name/assets/snippets/ditto/classes/ditto.class.inc.php	 
          Line: 	571	 
          Line 571 source: 	function determineIDs($IDs, $IDType, $TVs, $orderBy, $depth, $showPublishedOnly, $seeThruUnpub, $hideFolders, $hidePrivate, $showInMenuOnly, $myWhere, $keywords, $dateSource, $limit, $summarize, $filter, $paginate, $randomize) {


        Somethings broken. huh

          • 7231
          • 4,205 Posts
          Humm, did you update the snippet in the manager and the /assets/snippet/ditto folder? My only guess is that a required parameter is not making it to the ditto class.

            [font=Verdana]Shane Sponagle | [wiki] Snippet Call Anatomy | MODx Developer Blog | [nettuts] Working With a Content Management Framework: MODx

            Something is happening here, but you don&#39;t know what it is.
            Do you, Mr. Jones? - [bob dylan]
            • 28100
            • 66 Posts
            Yes, updated both manager and ditto folder. I think I need to look into this new ditto a bit more ...
              • 28100
              • 66 Posts
              Well where I’m at now is, since modx installed so well on my Mac and I had no errors with any snippets/chunks or anything, and because these errors all came from out of the blue on the live server (even though I hadn’t changed anything on that domain or it’s modx) I began to wonder if my Hosting (GoDaddy) had anything to do with it ... especially after reading some of the topics here.

              I’ve just installed on a new server (borrowed some space), it all went as it says it should on the packet, I’ve got Newspublisher, Ditto and Jot waltzing between the sunflowers singing happy ... dittos. smiley There’s no errors, no problems, no stress ... and no countless hours of wasted time.

              I’ve literally spent the last month trying to get modx to work at GoDaddy and run into nothing but trouble from day one. I put it down to n00bieness but when I made that first post above, I couldn’t fathom how the same code on 2 servers could give such drastically different results. It might be early days on this different server, but after reading peoples feedback about the oddities of Godaddy hosting I’ve really gotta say that after all the trials and errors of the last month I have way more faith in Modx than I do in GoDaddy! kiss
                • 25663 MODX Staff
                • 12,272 Posts
                Great feedback spacefish. Could you post a link to this in the hosting experiences forum topic?
                  Ryan Thrash, MODX Co-Founder
                  Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
                  • 28100
                  • 66 Posts
                  Thanks rthrash - new topic created in hosting.

                  BTW dev_cw, that Ditto call you posted for me above works on the different server. Thanks! smiley