Parse Error after 0.9.2.2 patch

Installed the patch and everything was working well, then I tried clicking on the link to my contact form and starting getting this error:

« Execution of a query to the database failed - Unknown column ’sc.link_attributes’ in ’field list’ »

Any ideas?

oops... link_attributes is a new field when editing documents, intended especially for weblinks, that lets you add things like target="blank" that a menu snippet can use when generating the link. But this was added somewhere in the 0.9.5 code.

Ah, I see... this is part of the same problem of version checking mentioned in this post. See line 77 of the wayfinder.inc.php file. You can just comment out those three lines of the "if" block.

Please see the note Jason added to the security notice for a quick fix: http://modxcms.com/forums/index.php/topic,8726.msg61394.html#msg61394

I saw that note and checked Wayfinder, but could not find that line. It is just listed as Beta 3... which I will now assume is beta to 1.0 and perhaps this was before that line was added. With so many of the snippets in constant development, it is challenging to keep up on everything.

Update to the latest version then add that line then.

Since it is a site of my own, I’m more willing to run it with an RC, was thinking that RC2 might be getting ready for delivery, so I’ve been holding off... would rather ugrade once.

If it is near but still far, to quote Sesame Street, I will go ahead and just upgrade Wayfinder... just trying to find the path of least resistance and effort.

RC2 should be out today.

Great, I’ll keep my fingers crossed! Can’t wait.

cheers

I’m running a site with RC1 right now. Everything seems fine so far, no bugs or anything. So... should I upgrade to RC 2? I’m a bit hesitant because it’s a production site and I don’t want to break anything by upgrading... (I apologize if this is a stupid question, but I’m not used to running beta software).

You can run the upgrade with no problem. Just make sure to have a backup of your site and your database "just in case". The error mentioned here only applied to upgrading 0.9.2.1, and has since been fixed.