warning: modxss will f*ck up your site

If you decide to do away with modxss package you will lose any content that it installed. Gone. Goodbye forever. Well, kinda. You can login to the server’s database and get some of it back via phpMyAdmin.

This ties in with my issue with SimpleSearch that never got a reply. It came with modxss, which I installed to learn Revo. What an education.

Ugh! Go ahead and ban me from this forum. I really don’t care anymore. Back to Evo and it’s fail safe ways.

Why would someone ban you for noting a problem? Granted additional information would be nice so the issue could be resolved to help others....

Sorry your stuff got trashed. That sounds really frustrating.

Any package will uninstall the elements and resources it installed when you uninstall it. The purpose of the sample site is to provide a sandbox for playing around with MODX. It’s not really intended to be the basis for a real site because you’d have a bunch of stuff that you don’t need cluttering up your site.

If you created new resources they should still be there as long as they are not children of any SS pages, but it’s completely expected that all the SS pages and their children would be removed on uninstall. The same thing would happen with the Evo sample site, BTW.

One of the thing i miss with Revo’s package is the ability to control what to uninstall with "setup-options" menu.
it would be useful for some case, where you bundle elements that are still used by other packages.

Quote from: lossendae at May 02, 2011, 05:22 PM

One of the thing i miss with Revo’s package is the ability to control what to uninstall with "setup-options" menu.
it would be useful for some case, where you bundle elements that are still used by other packages.

That would definitely be a good feature, but it would be a job to implement because PM automatically registers everything that’s installed for deletion in the uninstall. You’d have to install everything with a script rather than as part of the main package, then have an uninstall script give you the options.

The same thing would happen with the Evo sample site, BTW.

How?

Quote from: BobRay at May 02, 2011, 05:17 PM

The same thing would happen with the Evo sample site, BTW.

Technically this is really not possible since the Evo sample site is not something you can uninstall, unlike the Revo one which is a package.

Quote from: BobRay at May 02, 2011, 05:23 PM

That would definitely be a good feature, but it would be a job to implement because PM automatically registers everything that’s installed for deletion in the uninstall. You’d have to install everything with a script rather than as part of the main package, then have an uninstall script give you the options.

If PM could handle mumtiple package installation at once, it would have been wonderful.
Installing a blog package containing getResouce, getPage,Quip, etc... each their own namespace, and single uninstallation or udpate.

Installing a blog package containing getResouce, getPage,Quip, etc... each their own namespace, and single uninstallation or udpate.

That’s exactly what I thought modxss would do, but as I learned, the PM treats as one resource regardless of its package contents.

Furthermore, the resources that modxss installs can be updateable in the PM but don’t expect them to actually function correctly, at least that was my experience with SimpleSearch. modxss originally had SS 1.0 and it was some version after that that simply didn’t work.