[solved] HELP! I upgraded to 2.2.9 and parseChunk isn't replacing the placeholders

I upgraded from 2.2.6 to 2.2.9 and before the upgrade everything worked great. After upgrading NO content is being shown on the site. The containers are there, but, links to pages, product images, ect aren't loading at all. All the placeholders aren't processing.

Any input would be VERY welcome. THANKS! [ed. note: greyskymedia last edited this post 13 years ago.]

Did you check the MODX and/or PHP and/or http.access error logs? I've done some wacky things in my time, and there's always been something in one of those files which provides some kind of clue.

If everything looks ok from the log file, try duplicating a resource and take out all of the items which aren't static (i.e. snippets, chunks, placeholders, resource/tvs, etc.) and see if you can get a plain page (even without template) to show. Once you get a hello world page, add in the items one at a time to see if they fail.

an example of a parseChunk call that isn't working would be helpful. I've tried a simple one on a 2.2.9 installation and it's working fine. [ed. note: sottwell last edited this post 13 years ago.]

We changed from parseChunk to getChunk and all was well again. So, not a fix, but working now thanks folks!!! [ed. note: greyskymedia last edited this post 13 years ago.]

Just to share that Grey is not crazy. I just experienced the same issue (still trying to resolve) as well as others. I will try to follow up with anything more I find out.

THANK YOU!

I can now also confirm that changing it from parseChunk to getChunk has made the problem go away. Of course this still does not answer what is up with parseChunk

I will see if I can find the diff between parseChunk (2.2.6 and 2.2.9)

And, unfortunately, for those of us who need parse Chunk, getChunk won't always be a solution.

I reviewed the code back to 2.2.6 and parseChunk and getChunk are untouched. Also parseChunk is logically the same things and getChunk with default prefix and suffix. Calling the parseChunk method as default in fact is a waste of time as it bypasses the getChunk processor and then processes it itself. In effect this is double the work.

Grey , was this failing on you with custom prefix and suffix too.

yeah, that's what we were using... failing there too