Re: Moving Plone sites | Tipps & Docs
Wolfgang Jeltsch <wls580ii-u9ERN231N2QZkvjqreKGLti2O/[email protected]>
| Newsgroups | gmane.comp.web.zope.plone.user |
|---|---|
| Message-ID | <1422889011.5436.92.camel@idefix> |
Am Montag, den 02.02.2015, 15:21 +0100 schrieb Armin Stroß-Radschinski: > Take a look at > https://plone.org/documentation/manual/upgrade-guide/ I think this only discusses upgrading an existing Plone installation, not moving sites to a new Plone installation. > Better than your idea: Change the Plone version in the old buildout > (the staging copy!) and rerun buildout to upgrade Plone This is not really appropriate for my case. My server might have been hacked. So I want to get rid of any code, because it could be modified. As a result, I have to do a fresh install. > Tipp: Copy over the var/filestorage/Data.fs file and the whole > var/blobstorage directory including the invisible .layout file I guess this would copy over a lot of Python code, which could be modified by an attacker. How can I only copy non-code data like web pages and user databases? All the best, Wolfgang ------------------------------------------------------------------------------ Dive into the World of Parallel Programming. The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ Plone-Users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/plone-users