On Mon, Dec 5, 2011 at 6:29 AM, Jean-Michel FRANCOIS tou...@gmail.comwrote:
I have asking this to be sure your upgradestep was working, it is a
requirement to get the button.
As I've said, repeatedly, I can perform the upgrade through the
portal_setup tool. What I wanted to know is what else
On Dec 2, 12:29 pm, Jean-Michel FRANCOIS tou...@gmail.com wrote:
You have to know this version has nothing to do with the version of the
setup.py. It is just a version of install and used to know if we have to
migrate data.
Of COURSE I know that. Isn't it clear that I DO know how to make a
I was under the impression that Plone would show an Upgrade button
for any product whose installed metadata version was the metadata
version on the filesystem, and for which there was a Generic Setup
upgrade step whose source and destination tags matched: ie,
upgrade steps that would be shown
I think this depends on what version of Plone you're running. What are you
working with?
On Fri, Dec 2, 2011 at 8:40 AM, derek aus...@pointerstop.ca wrote:
I was under the impression that Plone would show an Upgrade button
for any product whose installed metadata version was the metadata
I _have_ an upgrade step - obviously, I have to if I'm able to run the
upgrade through the portal_setup tool
Perhaps the integer profile version is the issue. I admit to having been
curious about why exactly the Plone version numbers were integers. Why does
it need to be an integer?
