With regards the hosting - the server is pretty okay - the current site has the same number of documents running off a custom-built CMS and the load-time is rapid:
http://tinyurl.com/248lzc
--------------------------------
Contents of Ditto index page:
--------------------------------
[[ReflectAmended? &parents=`350` &display=`10` &summarize=`10000` &removeChunk=`Comments` &tpl=`ditto_blog_amended` &paginate=`1` &extenders=`summary,dateFilter` &paginateAlwaysShowLinks=`0` &tagData=`documentTags` &sortBy=`display-date` &dateSource=`display-date` &tplAlt=`blogFirstItem` &id=`archive` &dateFormat=`%d %B %Y` &noResults=`<br /><br /><p>No articles were written in the time period specified.</p>`]]
<p id="blogShow">Showing <strong>[+archive_start+]</strong> - <strong>[+archive_stop+]</strong> of <strong>[+archive_total+]</strong> Articles</p>
<div id="ditto_pages"> [+archive_previous+] [+archive_pages+] [+archive_next+] </div>
***Explantion
"The custom Reflect version actually outputs a complete Ditto call including the filters needed to show only the month/year selected. Thus, there’s no need to use Ditto after the Reflect call in this instance."
You can see the custom Reflect snippet here:
http://tinyurl.com/26lwco
To confirm - I have debugged by installing the latest Ditto/Reflect versions and using the calls:
[[ditto-test? &parents=`350` &display=`10` &summarize=`10` &removeChunk=`Comments` &tpl=`ditto_blog_amended` &paginate=`1` &extenders=`summary,dateFilter` &paginateAlwaysShowLinks=`0` &tagData=`documentTags` &sortBy=`display-date` &dateSource=`display-date` &tplAlt=`blogFirstItem` &dateFormat=`%d %B %Y`]]
[[reflect-test? &dittoSnippetParameters=`startID:350` &groupByYears=`0` &showItems=0` &tplMonth=`reflect_month_tpl`]]
I get the very same error 500 issues.
--------------------------------
Templates
--------------------------------
template: ditto_blog_amended
<div class="news-box-content">
<div class="home-txt">
<div class="icons">[!chunkListParser?chunks=`[+tviconChunks+]`!]</div>
<div class="news-title"><h2><a href="[~[+id+]~]" title="[+title+]">[+title+]</a></h2></div>
<div class="news-txt-pic-box">
<div id="indexImage"><a href="[~[+id+]~]" title="[+title+]">[+tvindexImage+]</a></div>
<strong>[+date+]</strong> <br /><br />
<p>[+summary+]</p>
<p class="ditto_link"><a href="[~[+id+]~]" title="[+title+]">Read more about [+title+] »</a></p>
</div>
</div>
</div>
template: blogFirstItem
<div class="news-box-content2">
<div class="home-txt">
<div class="icons">[!chunkListParser?chunks=`[+tviconChunks+]`!]</div>
<div class="news-title"><h2><a href="[~[+id+]~]" title="[+title+]">[+title+]</a></h2></div>
<div class="news-txt-pic-box">
<div id="indexImage"><a href="[~[+id+]~]" title="[+title+]">[+tvindexImage+]</a></div>
<strong>[+date+]</strong> <br /><br />
<p>[+summary+]</p>
<p class="ditto_link"><a href="[~[+id+]~]" title="[+title+]">Read more about [+title+] »</a></p>
</div>
</div>
</div>
***Explantion
The snippet call to chunkListParser is the TV-Based Chunks code found in the Wiki:
http://wiki.modxcms.com/index.php/Create_TV-Based_Chunks it basically draws in icons that indicate the type of media that each item has attached.
- For debugging - I have removed these calls from the Ditto templates though the problem persisted.
MODX Staff
