MODX 2.2.8 Upgrade - Working for you?

So far, I have successfully updated 4 MODX sites from 2.2.7 (and a few 2.2.6) up to the latest 2.2.8 without any issues.
I have not seen anything out of the ordinary so far but again, our sites are relatively basic.

This upgrade couldn't have gone any smoother from what I see. [ed. note: adagency last edited this post 13 years, 3 months ago.]

Same here. I also upgraded a site from 2.2.4 to 2.2.8 and that went smoothly as well.

~Upgraded from 2.2.6 to 2.2.8 and everything went smoothly apart from my dashboard having the defaults back ( IE News feed, config check etc ), originally built this site on the revo beta version and only ever had 1 problem on upgrades which was my own fault lol.

Indeed, mine have all gone well. I've even done a remote upgrade via wget and documented the process http://sottwell.com/links/upgrade-modx.pdf

An issue has cropped up for me related to contexts. On a site where there are two contexts and were working great, they now fail unexpectedly. I can get the context back briefly after clearing the cache, but then it gets lost again.

For example, I have a http://site-a.com/products/ and that page is symlinked on http://site-b.com/products/, but on site-b the context starts to fail after clearing the cache and then I just get site-a's homepage when trying to go to http://site-b.com/products/

I am using the ContextRouter plugin.

I just implemented that plugin. Just make sure you have all of the Context settings per the documentation.

I would also make sure the admin on the server didn't change settings in the hosting environment.

Additionally, I made the default landing page for each context open to 9999 Anonymous Member. Make sure your ACLs aren't causing a roll back.

Shawn,

Thanks for the response. I feel good about the first two suggestions (http_host is set) and I'm the only one in the hosting env, but how do I set a particular page to that Anonymous Member (9999)? Do I create an anonymous resource group then apply with that setting and add the page to it? I tried that but I'm getting the same results.

It truly is weird. After I clear the cache the context will work fine for a while then it will lose context--typically on the second visit.

Matt

I read a post from someone else who had trouble with multiple contexts in 2.2.8 who fixed it by manually deleting all files in the core/cache directory and clearing the browser cache and cookies.

Tried that but no luck, Bob. Thanks for the suggestion, though. Any other ideas?

Is the site_url tag in the base href tag in your template uncached? If not, try that, and be sure you have a site_url Context Setting for every front-end context.