This ditto problem is killing me!

This is crazy! I’ve been working with another developer on a site and we cannot get a ditto call to work.

The ditto call is simply being output at text rather than being processed. We’ve tried all the usual suspects when this happens without solving it.

Cached/uncached

This is the resulting output. Curiously, the [! is changed to [[ on output.


We turned off Rich Text on the page with the call. No change.

We’ve removed the calls from TinyMCE and placed them in the template via a chunk and finally put the calls directly into the template. No change.

We’ve systematically removed items from the head one at a time to remove potential conflicts, including all scripts and style sheets. No change.

Other snippets work just fine including weblogin, breadcrumbs, ajaxsearch, etc.

We’ve rerun the install/upgrade using a newly downloaded install of 1.0.4 and verified all the files are in the ditto snippet folder. No change.

We installed a new version of Modx 1.0.4 on another domain in the same godaddy hosting environment. The ditto call works just fine on a new installation. Here’s where it gets interesting. When we uploaded the sql db from the first site into the newly installed site and uploaded selected assets folders (css, images, etc), the ditto call doesn’t work.

So it seems there is something in the DB that is conflicting here. But we don’t know what it might be or how to identify the culprit.

One possibility, that we don’t know how to identify or fix is this. Another editor (ckeditor331) was installed and subsequently uninstalled in the original site. Perhaps there are some remnants left over, but how would we find and remove them?

Finally, the original modx installation of 1.0.4 was done using a Godaddy script. None of the snippets were installed with this script so we ran the upgrade to add in all the snippets.

We at the point now where we’re about to just recreate the site from scratch without uploading the db.

Any other ideas?

Try this:



Also spell check the template name to be sure.

Zi

No change, it simply outputs the call as text.

It seems to me the call isn’t even being processed enough to recognize improper syntax if that were the problem. If I use an incorrect tpl name in the call I would get a message that says the tpl chunk is invalid or not found. I don’t think its even getting that far.

Can I have a look at the site myself?

Just so you know, the uncached [!...!] tags are converted by MODx on the first pass through the parser into [[...]] tags. The snippet isn’t evaluated until the post-processing. Pages taken from cache also go through post-processing; it’s at this point that the uncached snippet gets evaluated.

Susan

So that explains why the [! was changed. Thanks for that.

Can you then tell me how the "cacheable" setting on the page affects this?

I’m just curious, I don’t think it’s related to our problem.

Thanks!