Upgrading from 2.0.x to 2.2

Hi,

Quick question: I gathered it's possible to update from MODx 2.1.x to 2.2.
But is it possible to update from 2.0.x? 2.0.8, to be more precise. Or should I first update from 2.0.8 to 2.1.something, then to 2.2?

I couldn't find this information on the Upgrading to 2.2.x page.

Thanks.

I wonder too, did anyone tried to update 2.0.8pl to 2.2?

Worked fine for me (2.08 -> 2.2pl2).

Just upgraded from 2.0.8 to 2.2. Seems to work fine, except my navigation menu (WayFinder) no longer works. It does not appear at all. I then checked out my WayFinder version, and updated it from 2.1.3 to 2.3.3. Even so, the menu doesn't show up.

This is my code, nothing fancy:



Any ideas? Thanks.

Edit: hmm, I removed the last exclamation mark, and it worked. Not sure why it was there in the first place... typo? Or did it have a use I forgot about? *shrugs* [ed. note: Stifu last edited this post 14 years, 8 months ago.]

That final exclamation point is definitely wrong. It may have been left over from an Evolution tag and may have been ignored by earlier version of the Revo parser.


---------------------------------------------------------------------------------------------------------------
PLEASE, PLEASE specify the version of MODX you are using . . . PLEASE!
MODx info for everyone: http://bobsguides.com/MODx.html

Alright, thanks for the confirmation.

I actually have another last problem since the update to 2.2. I have a snippet that used the MODx DB API ($modx->db) which doesn't work anymore. Until I find why it doesn't work, I simply replaced the $modx->db lines with regular PHP.

This line (first line in the snippet; $type is a snippet parameter):


Triggers this error: "Fatal error: Call to a member function select() on a non-object in (blabla)/www/core/cache/includes/elements/modsnippet/1.include.cache.php on line 7"


The ironic thing is that when I googled this error, the first result I found was an old topic of mine about the same error (in French). What I say in that topic is that I just reverted to regular PHP as I couldn't find the root cause.

Does anyone have an idea? [ed. note: Stifu last edited this post 14 years, 8 months ago.]

The DBAPI was deprecated in the original 2.0.x Revolution releases and removed in 2.1.x. You can install this plugin to add it back until you understand how to refactor your code against the proper Revolution API's. Some hints on migrating to the Revolution API here.

Thanks guys! I'll manage now.

Just performed 2.0.8 -> 2.2.7 well done modx!!

had to manually set these system_settings because my manager wasnt showing correct
compress_js = 0
compress_css = 0

Delete system_config cache and done…

I will report if any other problems will occur.
- update: well I had an old doc_manager plugin that caused problems in components menu. So im reverting to 2.0.8 so i can delete it and then update again.
- update: actually I just had to remove docmanager_desc from the db in the _menu table [ed. note: sjeijk last edited this post 13 years, 5 months ago.]