[Plone-docs] PHC 4.0a1 is released

Discussion:

Israel Saeta Pérez

2010-12-07 11:19:50 UTC

Hi folks,

I've recently released PHC 4.0a1. This release works on Plone 4 and
includes numerous bug fixes.

One of the most important ones was to refactor the workflow definitions
to make the @@sharing page work as expected. This will hopefully allow
the Collective Commiters group in plone.org to edit the articles in the
KB freely (it was not working previously).

Thanks to everyone who contributed to this release, either with bug
reports or patches. I'm looking forward for new releases already. :)

-- israel

Full changelog:

PloneHelpCenter 4.0a1 (2010-12-07)

- Use lxml to turn image relative links into absolute for the
one-page version of manuals. This introduces a new install
dependency on lxml.
Fixes http://plone.org/products/plonehelpcenter/issues/136.
[dukebody]

- Include numbering in the section title.
Fixes http://plone.org/products/plonehelpcenter/issues/137.
[dukebody]

- Rename type titles: "Page" to "Tutorial Page" and "Link" to
"Help Center Link".
Fixes http://plone.org/products/plonehelpcenter/issues/140.
[dukebody]

- Made it possible to query contentIds via XML-RPC for
collective.developermanual uploads [miohtama]

- Use the aq_parent function instead of the attribute to avoid
AttributeErrors when not using an acquisition wrapper (newer
Zope versions).
[dukebody]

- Fix next/previous custom adapter to visit the same items as appear in
the navigation dropdown. Also make sure this adapter is used for
legacy
ReferenceManuals. This fixes
http://plone.org/products/plonehelpcenter/issues/152/.
[dukebody, davisagli]

- Don't fail when trying to acquire getCurrentVersions if not in
a container that includes currentVersions in its schema. [davisagli]

- Fix the imports to use always Zope 3 style interfaces, making
the code work both in Plone 3 and 4 simultaneuslly.
[dukebody, thanks davisagli]

- Merge relevant changes from the Plone 4 migration branch from
Fabio Rizzo. [dukebody]

- Reverted obsolete code from the referencemanual_view.pt fix. [acsr]

- Updated INSTALL.txt with step by step upgrade guide related to
issue #142 "upgrade steps order unclear" and issue #132 "errata
mentioning Ploneboard". [acsr]

- Fixed an issue with failure to display referencemanual_view when
files are present in the reference manual. [acsr, thanks dukebody]

- Update the whole product to work with Plone 4.0a2. [dukebody]

- Removed "global allow" for Reference Manual. This closes
http://plone.org/products/plonehelpcenter/issues/150.
[keul]

- updated INSTALL.txt with step by step upgrade guide related to
issue #142 "upgrade steps order unclear" and issue #132 "errata
mentioning Ploneboard". [acsr]

- Respect exclude_from_nav setting in the reference manual
table of contents generation [miohtama]

Alex Clark

2010-12-09 05:06:08 UTC

Permalink

Nice! Does that mean it's safe to run a1 on Plone.org? Or should we wait
for 4.0 (right now we are running trunk).

Post by Israel Saeta PÃ©rez
Hi folks,
I've recently released PHC 4.0a1. This release works on Plone 4 and
includes numerous bug fixes.
One of the most important ones was to refactor the workflow definitions
the Collective Commiters group in plone.org to edit the articles in the
KB freely (it was not working previously).
Thanks to everyone who contributed to this release, either with bug
reports or patches. I'm looking forward for new releases already. :)
-- israel
PloneHelpCenter 4.0a1 (2010-12-07)
- Use lxml to turn image relative links into absolute for the
one-page version of manuals. This introduces a new install
dependency on lxml.
Fixes http://plone.org/products/plonehelpcenter/issues/136.
[dukebody]
- Include numbering in the section title.
Fixes http://plone.org/products/plonehelpcenter/issues/137.
[dukebody]
- Rename type titles: "Page" to "Tutorial Page" and "Link" to
"Help Center Link".
Fixes http://plone.org/products/plonehelpcenter/issues/140.
[dukebody]
- Made it possible to query contentIds via XML-RPC for
collective.developermanual uploads [miohtama]
- Use the aq_parent function instead of the attribute to avoid
AttributeErrors when not using an acquisition wrapper (newer
Zope versions).
[dukebody]
- Fix next/previous custom adapter to visit the same items as appear in
the navigation dropdown. Also make sure this adapter is used for
legacy
ReferenceManuals. This fixes
http://plone.org/products/plonehelpcenter/issues/152/.
[dukebody, davisagli]
- Don't fail when trying to acquire getCurrentVersions if not in
a container that includes currentVersions in its schema. [davisagli]
- Fix the imports to use always Zope 3 style interfaces, making
the code work both in Plone 3 and 4 simultaneuslly.
[dukebody, thanks davisagli]
- Merge relevant changes from the Plone 4 migration branch from
Fabio Rizzo. [dukebody]
- Reverted obsolete code from the referencemanual_view.pt fix. [acsr]
- Updated INSTALL.txt with step by step upgrade guide related to
issue #142 "upgrade steps order unclear" and issue #132 "errata
mentioning Ploneboard". [acsr]
- Fixed an issue with failure to display referencemanual_view when
files are present in the reference manual. [acsr, thanks dukebody]
- Update the whole product to work with Plone 4.0a2. [dukebody]
- Removed "global allow" for Reference Manual. This closes
http://plone.org/products/plonehelpcenter/issues/150.
[keul]
- updated INSTALL.txt with step by step upgrade guide related to
issue #142 "upgrade steps order unclear" and issue #132 "errata
mentioning Ploneboard". [acsr]
- Respect exclude_from_nav setting in the reference manual
table of contents generation [miohtama]
------------------------------------------------------------------------------
What happens now with your Lotus Notes apps - do you make another costly
upgrade, or settle for being marooned without product support? Time to move
off Lotus Notes and onto the cloud with Force.com, apps are easier to build,
use, and manage than apps on traditional platforms. Sign up for the Lotus
Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d

--
Alex Clark · http://aclark.net
Author · http://aclark.net/admin

Israel Saeta Pérez

2010-12-09 10:02:25 UTC

Permalink

Hi Alex,

I'm still working on some issues and I want to write tests for the workflow
definitions modified, so we'd better wait for a while more.

Also, I'd like to have a staging sever with the same Data.fs as Plone.org,
and same installed packages, to test the new release there and ensure
nothing blows up in a bad way. Could you get that for me (and everyone)?

-- israel

Post by Alex Clark
Nice! Does that mean it's safe to run a1 on Plone.org? Or should we wait
for 4.0 (right now we are running trunk).

appear in

Post by Israel Saeta PÃ©rez
the navigation dropdown. Also make sure this adapter is used for
legacy
ReferenceManuals. This fixes
http://plone.org/products/plonehelpcenter/issues/152/.
[dukebody, davisagli]
- Don't fail when trying to acquire getCurrentVersions if not in
a container that includes currentVersions in its schema.

[davisagli]

Post by Israel Saeta PÃ©rez
- Fix the imports to use always Zope 3 style interfaces, making
the code work both in Plone 3 and 4 simultaneuslly.
[dukebody, thanks davisagli]
- Merge relevant changes from the Plone 4 migration branch from
Fabio Rizzo. [dukebody]
- Reverted obsolete code from the referencemanual_view.pt fix.

[acsr]

Post by Israel Saeta PÃ©rez
- Updated INSTALL.txt with step by step upgrade guide related to
issue #142 "upgrade steps order unclear" and issue #132 "errata
mentioning Ploneboard". [acsr]
- Fixed an issue with failure to display referencemanual_view when
files are present in the reference manual. [acsr, thanks

dukebody]

Post by Israel Saeta PÃ©rez
- Update the whole product to work with Plone 4.0a2. [dukebody]
- Removed "global allow" for Reference Manual. This closes
http://plone.org/products/plonehelpcenter/issues/150.
[keul]
- updated INSTALL.txt with step by step upgrade guide related to
issue #142 "upgrade steps order unclear" and issue #132 "errata
mentioning Ploneboard". [acsr]
- Respect exclude_from_nav setting in the reference manual
table of contents generation [miohtama]

------------------------------------------------------------------------------

Post by Israel Saeta PÃ©rez
What happens now with your Lotus Notes apps - do you make another costly
upgrade, or settle for being marooned without product support? Time to

move

Post by Israel Saeta PÃ©rez
off Lotus Notes and onto the cloud with Force.com, apps are easier to

build,

Post by Israel Saeta PÃ©rez
use, and manage than apps on traditional platforms. Sign up for the Lotus
Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d

Alex Clark

2010-12-09 14:34:46 UTC

Permalink

Post by Israel Saeta PÃ©rez
Hi Alex,
I'm still working on some issues and I want to write tests for the
workflow definitions modified, so we'd better wait for a while more.

OK, it doesn't have to be perfect, and if the alpha is a "cut" of trunk
we're running that code anyway. I just want to start making the move
from svn to packages.

Post by Israel Saeta PÃ©rez
Also, I'd like to have a staging sever with the same Data.fs as
Plone.org, and same installed packages, to test the new release there
and ensure nothing blows up in a bad way. Could you get that for me (and
everyone)?

Not easily (we've done it before, and it usually ends up being just one
more thing to maintain), but it's fairly trivial to run a local copy of
plone.org these days: 1.) Get a plone.org acct. 2.) Check out the
buildout. 3.) Run bin/buildout -c database.cfg.

Alex

Post by Israel Saeta PÃ©rez
-- israel
Nice! Does that mean it's safe to run a1 on Plone.org? Or should we wait
for 4.0 (right now we are running trunk).

Post by Israel Saeta PÃ©rez
Hi folks,
I've recently released PHC 4.0a1. This release works on Plone 4 and
includes numerous bug fixes.
One of the most important ones was to refactor the workflow

definitions
allow

Post by Israel Saeta PÃ©rez
the Collective Commiters group in plone.org <http://plone.org> to

edit the articles in the

Post by Israel Saeta PÃ©rez
KB freely (it was not working previously).
Thanks to everyone who contributed to this release, either with bug
reports or patches. I'm looking forward for new releases already. :)
-- israel
PloneHelpCenter 4.0a1 (2010-12-07)
- Use lxml to turn image relative links into absolute for the
one-page version of manuals. This introduces a new install
dependency on lxml.
Fixes http://plone.org/products/plonehelpcenter/issues/136.
[dukebody]
- Include numbering in the section title.
Fixes http://plone.org/products/plonehelpcenter/issues/137.
[dukebody]
- Rename type titles: "Page" to "Tutorial Page" and "Link" to
"Help Center Link".
Fixes http://plone.org/products/plonehelpcenter/issues/140.
[dukebody]
- Made it possible to query contentIds via XML-RPC for
collective.developermanual uploads [miohtama]
- Use the aq_parent function instead of the attribute to avoid
AttributeErrors when not using an acquisition wrapper (newer
Zope versions).
[dukebody]
- Fix next/previous custom adapter to visit the same items

as appear in

Post by Israel Saeta PÃ©rez
the navigation dropdown. Also make sure this adapter is

used for

Post by Israel Saeta PÃ©rez
legacy
ReferenceManuals. This fixes
http://plone.org/products/plonehelpcenter/issues/152/.
[dukebody, davisagli]
- Don't fail when trying to acquire getCurrentVersions if

not in

Post by Israel Saeta PÃ©rez
a container that includes currentVersions in its schema.

[davisagli]

<http://referencemanual_view.pt> fix. [acsr]

Post by Israel Saeta PÃ©rez
- Updated INSTALL.txt with step by step upgrade guide

related to

Post by Israel Saeta PÃ©rez
issue #142 "upgrade steps order unclear" and issue #132 "errata
mentioning Ploneboard". [acsr]
- Fixed an issue with failure to display

referencemanual_view when

Post by Israel Saeta PÃ©rez
files are present in the reference manual. [acsr, thanks

dukebody]

related to

Post by Israel Saeta PÃ©rez
issue #142 "upgrade steps order unclear" and issue #132

"errata

Post by Israel Saeta PÃ©rez
mentioning Ploneboard". [acsr]
- Respect exclude_from_nav setting in the reference manual
table of contents generation [miohtama]

------------------------------------------------------------------------------

Post by Israel Saeta PÃ©rez
What happens now with your Lotus Notes apps - do you make another

costly

Post by Israel Saeta PÃ©rez
upgrade, or settle for being marooned without product support?

Time to move

Post by Israel Saeta PÃ©rez
off Lotus Notes and onto the cloud with Force.com, apps are

easier to build,

Post by Israel Saeta PÃ©rez
use, and manage than apps on traditional platforms. Sign up for

the Lotus

Post by Israel Saeta PÃ©rez
Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d

--
Alex Clark · http://aclark.net
Author · http://aclark.net/admin
------------------------------------------------------------------------------
WikiLeaks The End of the Free Internet
http://p.sf.net/sfu/therealnews-com
_______________________________________________
Plone-docs mailing list
https://lists.sourceforge.net/lists/listinfo/plone-docs
------------------------------------------------------------------------------
WikiLeaks The End of the Free Internet
http://p.sf.net/sfu/therealnews-com
_______________________________________________
Plone-docs mailing list
https://lists.sourceforge.net/lists/listinfo/plone-docs

--
Alex Clark · http://aclark.net
Author · http://aclark.net/admin

Israel Saeta Pérez

2010-12-09 15:05:52 UTC

Permalink

Hi,

Post by Alex Clark

Post by Israel Saeta PÃ©rez
Hi Alex,
I'm still working on some issues and I want to write tests for the
workflow definitions modified, so we'd better wait for a while more.

OK, it doesn't have to be perfect, and if the alpha is a "cut" of trunk
we're running that code anyway. I just want to start making the move
from svn to packages.

Yes it is, but includes important changes that can make the whole Help
Center unusable, so I need to test first.

Post by Alex Clark

My only problem is that the plone.org Data.fs is huge and my connection to
the server is not so good, so I'd take hours to get it downloaded, but I'll
try.

-- israel

Alex Clark

2010-12-09 15:17:15 UTC

Permalink

Post by Alex Clark
Hi,

Post by Israel Saeta PÃ©rez
Hi Alex,
I'm still working on some issues and I want to write tests for the
workflow definitions modified, so we'd better wait for a while more.

OK, it doesn't have to be perfect, and if the alpha is a "cut" of trunk
we're running that code anyway. I just want to start making the move
from svn to packages.
Yes it is, but includes important changes that can make the whole Help
Center unusable, so I need to test first.

Ah! Well, in general with any plone.org package (at this moment) we are
counting on trunk being more or less stable, FWIW. So, if you've done
the work for the alpha in trunk, it may end up getting deployed
inadvertently.

Post by Alex Clark

me (and

Not easily (we've done it before, and it usually ends up being just one
more thing to maintain), but it's fairly trivial to run a local copy of
plone.org <http://plone.org> these days: 1.) Get a plone.org
<http://plone.org> acct. 2.) Check out the
buildout. 3.) Run bin/buildout -c database.cfg.
My only problem is that the plone.org <http://plone.org> Data.fs is huge
and my connection to the server is not so good, so I'd take hours to get
it downloaded, but I'll try.

It's not off the table, and as always a ticket on
dev.plone.org/plone.org is the best way to make sure it gets considered.

Post by Alex Clark
-- israel
------------------------------------------------------------------------------
WikiLeaks The End of the Free Internet
http://p.sf.net/sfu/therealnews-com
_______________________________________________
Plone-docs mailing list
https://lists.sourceforge.net/lists/listinfo/plone-docs

--
Alex Clark · http://aclark.net
Author · http://aclark.net/admin

Israel Saeta Pérez

2010-12-09 19:54:35 UTC

Permalink

Post by Alex Clark
Ah! Well, in general with any plone.org package (at this moment) we are
counting on trunk being more or less stable, FWIW. So, if you've done
the work for the alpha in trunk, it may end up getting deployed
inadvertently.

I've just released PHC 4.0b1. I felt it really wasn't alpha.

It includes automated tests for the new workflow definiton and more (see
below). This means we need to run the workflow permission remapping, at
least for the documentation section, for the new workflow policies to take
effect. Should I code up a migration step?

-- israel

PloneHelpCenter 4.0b1 (2010-12-09)

- Use ordering adapters in Plone 4 to sort items in sections.
[dukebody]

- Make the default view for PHC folders obey the items ordering
set using the Contents tab. Formerly, they were sorted
alphabetically by title.
Fixes http://plone.org/products/plonehelpcenter/issues/121.
[dukebody]

- Allow all site-enabled markup types for PHC content, instead of
a fixed list.
Fixes http://plone.org/products/plonehelpcenter/issues/117.
[dukebody]

- Modify workflow definitions to disallow Anonymous users to see
content inside hidden Help Centers.
Fixes http://plone.org/products/plonehelpcenter/issues/118.
[dukebody]

- Remove the "Properties" tab for content-types, that was
duplicating the Metadata schemata already present in the edit
view in Plone 3.
Fixes http://plone.org/products/plonehelpcenter/issues/119.
[dukebody]

- Make mail sending code compatible with Plone 3. PHC 4 is now
compatible with both Plone 3 and 4.
[dukebody]