warning: modxss will f*ck up your site

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

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.

Actually, that’s possible. I hadn’t thought of doing it that way, but it would only put the subpackages in the grid and you’d have to install them all one by one. You’d have to uninstall them one by one and you’d still lose any resources you modified or created as children of the SS pages. I’m not sure that would be an improvement overall.

I stand corrected on Evo. I forgot that there’s no built-in generic package uninstall.

Quote from: Peter at May 02, 2011, 05:45 PM

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.

I understand your frustration.

In the meantiume, I think that one guy is just not enough to actually handle most of the more popular modx 3rd party addons, and the update of sample sites, and maintaining the core, and answer on the forum, and twitter, and... the list goes on.

So, i understand your concern, but i can’t blame the guy behind it too...

Maybe, you should report it on github directly so it can be fixed for future users ?

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

Actually, that’s possible. I hadn’t thought of doing it that way, but it would only put the subpackages in the grid and you’d have to install them all one by one. You’d have to uninstall them one by one and you’d still lose any resources you modified or created as children of the SS pages. I’m not sure that would be an improvement overall.

Definitively not improvement, i agree.
PB need an "uninstall-options" file.

It should come with a warning or it should install the contents into its own context.

But then uninstalling it shouldn’t delete all the resources that came with it.

Would Version X help resolve this?

I won’t be filing a github report. When I tried to do that a month ago it said I would have to pay $7.95 a month to do so. I’d rather pay MODx team for support.

Something definitively gone wrong when you tried.

Filling a bug report is free on github.

Maybe you tried to use pro features for private git repositories ?

Nope. I was told to file a report and the link given directed me to open an account at GitHub for $7.95 a month. Hmph!

Since i use a free github account and i’ve alse entered some bug reports, i can assure you that git is free as long as you stay in the open source valley.

Sounds better than the valley of death.

The link I got before was different than the one I just got before. I’m set with a Valley of Open Source github account.

I’m rebuilding the site but man oh man, this is a major bummer having to remember all the chunks!

Sigh. :’(

I have most of the content on my computer, but I have to go dig up some old spreadsheet to find the correct menuindex/order of containers and files. Property sets are great and I think they’re all intact. But it’s still extra work.

Okay, I’m done moaning about this. It will be great if PM can load a sample site and "let it go" without having it so tightly tied to itself.

I think this may be after the fact, but could you not just have downloaded your nightly site files snapshot (most hosting companies provide this to my knowledge) to restore the previous day’s version of your MODx installation?