[Quick Manager+] QM+ Breaks Snippets and Friendly URLs?

Would anyone know why QM+ would break a website? I just upgraded the development copy of the website I manage from 0.9.6.3 to 1.0, and before I logged in to the manager the website appeared as it should. However, clicking any link on the home page took the browser back to the home page. I fixed this temporarily by turning off Friendly URLs, but I really need Friendly URLs to work on the production copy of the site seeing as those are the addresses other websites use to link to our content.

After logging in to the manager, I viewed the site - only to see it with its guts spilled. No snippets were working correctly; the wayfinder nav bar was permanently expanded, and the custom snippets we made were expanded as well. I did notice the QM+ bar at the top of the page, so I went into the manager and disabled QM+ and BAM site functionality restored. It’s a shame cause QM+ was one of the 1.0 features I was looking forward to. My guess is something doesn’t run right with the CSS, but I can’t say for sure. Any ideas?

Without seeing the site could only guess but I’ve upgraded over 30 and never had a problem.

Do you have and mootools or jquery running on the site other than the QM ??if so thry running them in non-conflict mode but that’s just a guess

I do use jquery, but it is already running in non-conflict mode...

Well as I say can only guess as can’t see the site, have you updated the paths in the manager, are the paths to the javascript files correct, what javascript do you have running on there, perhaps turn QM back on and add the links to other javascript stuff back in 1 at a time and see if there a conflict

What paths in the manager would I have to update? I assumed it would remain untouched after the upgrade. Paths also have not changed. I use minify and colorbox for javascript, and use jquery to cache css files. I’ll work on this more tomorrow, but I have to head out for the night. Thanks for the help so far, paulp!

What paths in the manager would I have to update? I assumed it would remain untouched after the upgrade.

Sorry I thought you had installed a development copy of your live site to test the upgrade on so if not ignore that bit.

I use minify and colorbox for javascript, and use jquery to cache css files.

Never used any of them but if you turn QM off and everything works I would defiantly say there is a conflict, if you can work out which one is causing it it will be a lot easier to find a fix for it plus the development team may want to know about it.

Post back when you have tested them one at a time and worked out which one is causing it., also make sure all the files for the QM were copied over correctly ;o)