plone-docs — Discussion about the Plone documentation

[Plone-docs] Suggesting change of web page describing favicon files

[Gunnar P. V. <po...@gu...>]

Now Windows 7 accepts Windows Icon files that are 64x64 pixels. These 
large icons are used in the user interface of Windows 7, by Pinning, 
among other uses.

So any web master may choose to provide such favicon.ico in 64x64 
pixels. When viewed in a browser next to the address bar, such icons are 
typically scaled to a smaller size.

So I suggest that you update the page
http://plone.org/documentation/kb/setting-the-site-icon-favicon-for-your-plone-site

to let the page reflect the capability of 64x64 pixels in Windows Icon 
files.

Gunnar Vestergaard

Re: [Plone-docs] Broken ResolveUID

[Myroslav O. <myr...@qu...>]

Hi,

It look like
http://plone.org/documentation/manual/plone-4-user-manual/portlet-management/portlet-typeshad
broken resolveuid links:

   - resolveuid/eb8800b7a664b35d069ddbcae7e4c837 in Collection section can
   lead to http://plone.org/documentation/kb/collection-portlets
   - resolveuid/3698a06fc5f57d6f9bd6eaf1824f5cc8 in Static Text section can
   lead to http://plone.org/documentation/kb/static-text-portlets

Regards,

m.
-- 
.....................................................................................................
Myroslav Opyr   ▪   CTO   ▪    Quintagroup   ▪   http://quintagroup.com
˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙

Re: [Plone-docs] Developer manual "tutorials" section?

[Clayton P. <cl...@si...>]

On Feb 17, 2011, at 6:06 AM, Mikko Ohtamaa wrote:

> <snip>
> 
> The conversion process is already little fragile, so I suggest let's not try
> to make it more complicate and we'll just rely on Plone's automatic "Page
> not found - suggestions" feature :)


That will just complicate the lives of everyone else, we really shouldn't make it harder for people to find documentation that is already scattered. Big -1 on just leaving a Not Found and letting the user figure it out!

Clayton
-- 
Six Feet Up, Inc. | Where sophisticated web projects thrive
Direct Line: +1 (317) 861-5948 x603
Email: cl...@si...
Try Plone 4 Today at: http://plone4demo.com

Re: [Plone-docs] Developer manual "tutorials" section?

[Dylan J. <dy...@dy...>]

On 17/02/2011, at 10:06 PM, Mikko Ohtamaa wrote:

>
>
> Dylan Jay-4 wrote:
>>
>>
>>> On Feb 16, 2011, at 2:47 AM, Dylan Jay wrote:
>>>> Is it just me or does the "tutorials" section of the community
>>>> developer manual feel out of place?
>>
>
> It is no planned very well, so putting things to proper places is  
> maybe a
> topic for upcoming sprints.

fair enough. Along with merging the two manuals + deleting any KB  
articles with content already covered in the manual.

>
> I'd suggest the section is renamed to "Tools, technologies and  
> processes".

Isn't the whole document about tools, technologies and processes?
Are you trying to say that things like ArchGenXML and buildout are  
external to Plone so should be in it's own section?
If so I disagree. I think it's more helpful to organise things by how  
it helps the developers. ArchGenXML helps you create content types.  
Buildout helps you configure plone. Paster is about creating plugins/ 
packages.

>
>> I've been thinking hard on how to do this but no answers yet.
>> For those not aware the community manual on plone.org is actually the
>> result of a conversion process from svn -> sphinx -> funnelweb ->
>> plone. The information on where items used to be isn't available to
>> sphinx from svn so it's not possible automate this yet so any  
>> renaming
>> in svn won't result in redirects in plone :( Unless someone can think
>> of a clever way to get svn to produce a list of previous paths for
>> each piece of content.
>> The only solution would be to manually reproduce the moves in plone
>> first and then reupload the content overtop.
>>
>
> The conversion process is already little fragile, so I suggest let's  
> not try
> to make it more complicate and we'll just rely on Plone's automatic  
> "Page
> not found - suggestions" feature :)

Tell me what's going wrong and I'll fix it.

>
>
> -----
>
> http://twitter.com/moo9000 Follow me in Twitter
>
>
>
> mFabrik News – download now for iPhone and Android
>
>
>
> http://bit.ly/mfabrikitunessignaturemoo
> http://blog.mfabrik.com/wp-content/uploads/2011/01/iPhoneFooter.png
>
>
> http://bit.ly/mfabrikandroidsignaturemoo
> http://blog.mfabrik.com/wp-content/uploads/2011/01/AndroidFooter.png
>
>
>
> -- 
> View this message in context: http://plone.293351.n2.nabble.com/Developer-manual-tutorials-section-tp6030918p6035464.html
> Sent from the Documentation Team mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> The ultimate all-in-one performance toolkit: Intel(R) Parallel  
> Studio XE:
> Pinpoint memory and threading errors before they happen.
> Find and fix more than 250 security defects in the development cycle.
> Locate bottlenecks in serial and parallel code that limit performance.
> http://p.sf.net/sfu/intel-dev2devfeb
> _______________________________________________
> Plone-docs mailing list
> Plo...@li...
> https://lists.sourceforge.net/lists/listinfo/plone-docs

Re: [Plone-docs] Developer manual "tutorials" section?

[Dylan J. <dy...@dy...>]

On 17/02/2011, at 10:31 PM, Raphael Ritz wrote:

> On 2/17/11 12:06 PM, Mikko Ohtamaa wrote:
>
> [..]
>
>>
>>> I've been thinking hard on how to do this but no answers yet.
>>> For those not aware the community manual on plone.org is actually  
>>> the
>>> result of a conversion process from svn ->  sphinx ->  funnelweb ->
>>> plone. The information on where items used to be isn't available to
>>> sphinx from svn so it's not possible automate this yet so any  
>>> renaming
>>> in svn won't result in redirects in plone :( Unless someone can  
>>> think
>>> of a clever way to get svn to produce a list of previous paths for
>>> each piece of content.
>>> The only solution would be to manually reproduce the moves in plone
>>> first and then reupload the content overtop.
>>>
>>
>> The conversion process is already little fragile, so I suggest  
>> let's not try
>> to make it more complicate and we'll just rely on Plone's automatic  
>> "Page
>> not found - suggestions" feature :)
>
> If the change consists of "only" moving some subtree to a different
> location (without changing the structure within the tree) you can
> maintain the old links by defining a Python Script (TTW in ZMI in
> the parent folder of the moved one) like so:
>
> base = container.absolute_url()
> subpath = '/'.join(traverse_subpath)
> url = base + <relative path to new location> + subpath
> context.REQUEST.RESPONSE.redirect(url)
>
> The script needs to have the same id as the folder that
> moved elsewhere. Guess you get the idea.
> More of a hack or work-around but functional.

Interesting hack but unfortunately the problem isn't how to get it to  
redirect (that's already taken care of) but knowing what to redirect  
from.

I did have on idea on this. If there was a convention of putting a  
small section on the bottom of each sphinx page which listed the  
"previous" paths that page was available at. We could then create a  
transmogrifier blueprint which extracted those paths and that could be  
used by transmogrify.ploneremote to set the plone redirector

Re: [Plone-docs] Developer manual "tutorials" section?

[Raphael R. <r....@bi...>]

On 2/17/11 12:06 PM, Mikko Ohtamaa wrote:

[..]

>
>> I've been thinking hard on how to do this but no answers yet.
>> For those not aware the community manual on plone.org is actually the
>> result of a conversion process from svn ->  sphinx ->  funnelweb ->
>> plone. The information on where items used to be isn't available to
>> sphinx from svn so it's not possible automate this yet so any renaming
>> in svn won't result in redirects in plone :( Unless someone can think
>> of a clever way to get svn to produce a list of previous paths for
>> each piece of content.
>> The only solution would be to manually reproduce the moves in plone
>> first and then reupload the content overtop.
>>
>
> The conversion process is already little fragile, so I suggest let's not try
> to make it more complicate and we'll just rely on Plone's automatic "Page
> not found - suggestions" feature :)

If the change consists of "only" moving some subtree to a different
location (without changing the structure within the tree) you can
maintain the old links by defining a Python Script (TTW in ZMI in
the parent folder of the moved one) like so:

base = container.absolute_url()
subpath = '/'.join(traverse_subpath)
url = base + <relative path to new location> + subpath
context.REQUEST.RESPONSE.redirect(url)

The script needs to have the same id as the folder that
moved elsewhere. Guess you get the idea.
More of a hack or work-around but functional.

Raphael


>
>
> -----
>
> http://twitter.com/moo9000 Follow me in Twitter
>
>
>
> mFabrik News&ndash; download now for iPhone and Android
>
>
>
> http://bit.ly/mfabrikitunessignaturemoo
> http://blog.mfabrik.com/wp-content/uploads/2011/01/iPhoneFooter.png
>
>
> http://bit.ly/mfabrikandroidsignaturemoo
> http://blog.mfabrik.com/wp-content/uploads/2011/01/AndroidFooter.png
>
>
>

Re: [Plone-docs] Developer manual "tutorials" section?

[Mikko O. <mik...@re...>]

Dylan Jay-4 wrote:
> 
> 
>> On Feb 16, 2011, at 2:47 AM, Dylan Jay wrote:
>>> Is it just me or does the "tutorials" section of the community
>>> developer manual feel out of place?
> 

It is no planned very well, so putting things to proper places is maybe a
topic for upcoming sprints.

I'd suggest the section is renamed to "Tools, technologies and processes".



> I've been thinking hard on how to do this but no answers yet.
> For those not aware the community manual on plone.org is actually the  
> result of a conversion process from svn -> sphinx -> funnelweb ->  
> plone. The information on where items used to be isn't available to  
> sphinx from svn so it's not possible automate this yet so any renaming  
> in svn won't result in redirects in plone :( Unless someone can think  
> of a clever way to get svn to produce a list of previous paths for  
> each piece of content.
> The only solution would be to manually reproduce the moves in plone  
> first and then reupload the content overtop.
> 

The conversion process is already little fragile, so I suggest let's not try
to make it more complicate and we'll just rely on Plone's automatic "Page
not found - suggestions" feature :)


-----

http://twitter.com/moo9000 Follow me in Twitter 



mFabrik News – download now for iPhone and Android



http://bit.ly/mfabrikitunessignaturemoo 
http://blog.mfabrik.com/wp-content/uploads/2011/01/iPhoneFooter.png 


http://bit.ly/mfabrikandroidsignaturemoo 
http://blog.mfabrik.com/wp-content/uploads/2011/01/AndroidFooter.png 



-- 
View this message in context: http://plone.293351.n2.nabble.com/Developer-manual-tutorials-section-tp6030918p6035464.html
Sent from the Documentation Team mailing list archive at Nabble.com.

Re: [Plone-docs] Developer manual "tutorials" section?

[Dylan J. <dy...@dy...>]

On 17/02/2011, at 6:09 AM, Clayton Parker wrote:

> On Feb 16, 2011, at 2:47 AM, Dylan Jay wrote:
>> Is it just me or does the "tutorials" section of the community
>> developer manual feel out of place?
>>
>> Shouldn't ArchGenXML be filled under Content management > Archetypes?
>> and Buildout tutorial be put under a new section like "Configuring
>> plone"?
>>
>> Anyone have any problem if I make those changes?
>
> If you do this, make sure there are proper redirects in place from  
> the old location.

I've been thinking hard on how to do this but no answers yet.
For those not aware the community manual on plone.org is actually the  
result of a conversion process from svn -> sphinx -> funnelweb ->  
plone. The information on where items used to be isn't available to  
sphinx from svn so it's not possible automate this yet so any renaming  
in svn won't result in redirects in plone :( Unless someone can think  
of a clever way to get svn to produce a list of previous paths for  
each piece of content.
The only solution would be to manually reproduce the moves in plone  
first and then reupload the content overtop.


>
> Clayton
> -- 
> Six Feet Up, Inc. | Where sophisticated web projects thrive
> Direct Line: +1 (317) 861-5948 x603
> Email: cl...@si...
> Try Plone 4 Today at: http://plone4demo.com
>
>
>

Re: [Plone-docs] Developer manual "tutorials" section?

[Clayton P. <cl...@si...>]

On Feb 16, 2011, at 2:47 AM, Dylan Jay wrote:
> Is it just me or does the "tutorials" section of the community  
> developer manual feel out of place?
> 
> Shouldn't ArchGenXML be filled under Content management > Archetypes?
> and Buildout tutorial be put under a new section like "Configuring  
> plone"?
> 
> Anyone have any problem if I make those changes?

If you do this, make sure there are proper redirects in place from the old location.

Clayton
-- 
Six Feet Up, Inc. | Where sophisticated web projects thrive
Direct Line: +1 (317) 861-5948 x603
Email: cl...@si...
Try Plone 4 Today at: http://plone4demo.com

[Plone-docs] Developer manual "tutorials" section?

[Dylan J. <dy...@dy...>]

Hi,

Is it just me or does the "tutorials" section of the community  
developer manual feel out of place?

Shouldn't ArchGenXML be filled under Content management > Archetypes?
and Buildout tutorial be put under a new section like "Configuring  
plone"?

Anyone have any problem if I make those changes?

---
Dylan Jay
Technical Solutions Manager
PretaWeb: reducing duplication in the government web.
P: +612 80819071 | M: +61421477460 | twitter.com/djay75 | linkedin.com/ 
in/djay75

[Plone-docs] Test

[Alex C. <ac...@ac...>]

Test

-- 
Alex Clark · http://aclark.net/help-me-help-plone

[Plone-docs] Install PloneHelpCenter 4.0b1 in plone.org

[Israel S. P. <duk...@gm...>]

Helloes,

I've tested PloneHelpCenter 4.0b1 in a staging server with the
plone.org data and it didn't explode. Can we deploy it to plone.org
over this weekend?

My checklist:
1. Pin Products.PloneHelpCenter 4.0b1.
2. Update buildout.
3. Reinstall PloneHelpCenter in the quickinstaller (sorry, no upgrade profile).
4. Update permissions mapping in the portal_workflow tool.

-- israel

Re: [Plone-docs] collective-docs deserves a prominent link on plone.org

[Israel S. P. <duk...@gm...>]

Hi Alex,

2010/12/14 Alex Clark <ac...@ac...>:
> On 12/14/10 3:18 PM, Israel Saeta Pérez wrote:
>> Hi,
>>
>> 2010/12/14 Alex Clark<ac...@ac...>:
>>> On 12/14/10 12:37 PM, Israel Saeta Pérez wrote:
>>>> We did some work during the conf:
>>>> http://plone.org/documentation/helpcenter_ploneorg2
>>>>
>>>> Does this link fit here?
>>>
>>>
>>> Cool! Can we deploy this?
>>
>>
>> It's live now. :)  It's a template in the "custom" skin layer, but I
>> can move it to some layer in the PloneOrg product. Which one should I
>> place it into?
>
> Well, it should go in PHC, and ideally have an entry in types.xml that
> says the PHC object can select it as a default view.


I don't think so, since this view doesn't make almost any sense
outside of plone.org (it's kind of harcoded). What I can do is to set
a normal phc view as default view in the PHC product, and place a
template with the same name in a skin layer in the PloneOrg product,
overriding this default view if it's higher up in the theme.

-- israel

Re: [Plone-docs] collective-docs deserves a prominent link on plone.org

[Alex C. <ac...@ac...>]

On 12/14/10 3:18 PM, Israel Saeta Pérez wrote:
> Hi,
>
> 2010/12/14 Alex Clark<ac...@ac...>:
>> On 12/14/10 12:37 PM, Israel Saeta Pérez wrote:
>>> We did some work during the conf:
>>> http://plone.org/documentation/helpcenter_ploneorg2
>>>
>>> Does this link fit here?
>>
>>
>> Cool! Can we deploy this?
>
>
> It's live now. :)  It's a template in the "custom" skin layer, but I
> can move it to some layer in the PloneOrg product. Which one should I
> place it into?

Well, it should go in PHC, and ideally have an entry in types.xml that 
says the PHC object can select it as a default view.

Thanks!


>
> -- israel
>
> ------------------------------------------------------------------------------
> Lotusphere 2011
> Register now for Lotusphere 2011 and learn how
> to connect the dots, take your collaborative environment
> to the next level, and enter the era of Social Business.
> http://p.sf.net/sfu/lotusphere-d2d


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

Re: [Plone-docs] collective-docs deserves a prominent link on plone.org

[Israel S. P. <duk...@gm...>]

Hi,

2010/12/14 Alex Clark <ac...@ac...>:
> On 12/14/10 12:37 PM, Israel Saeta Pérez wrote:
>> We did some work during the conf:
>> http://plone.org/documentation/helpcenter_ploneorg2
>>
>> Does this link fit here?
>
>
> Cool! Can we deploy this?


It's live now. :)  It's a template in the "custom" skin layer, but I
can move it to some layer in the PloneOrg product. Which one should I
place it into?

-- israel

[Plone-docs] unsubscribe

[Barry K. <ba...@en...>]

Thank you!

 

Barry Kroeker

Advertising Manager
EnergyCAP, Inc.

phone: 877.327.3702 x37

cell: 814.359-8597

fax: 719.623.0577

 <mailto:Ba...@En...> Ba...@En...  

 

 <http://www.energycap.com/> EnergyCAP: The 30-Year Leader In Energy
Management Software

 

Re: [Plone-docs] collective-docs deserves a prominent link on plone.org

[Alex C. <ac...@ac...>]

On 12/14/10 12:37 PM, Israel Saeta Pérez wrote:
> On 14/12/10 16:12, Alex Clark wrote:
>> On 12/9/10 3:28 PM, Dylan Jay wrote:
>>> I think we need to keep the plone.org copy for a eat our own dog food
>>> stance plus so search works.
>>
>> I think that is debatable, but I see your point. Personally, I'm not
>> going to champion that cause right now because I'm swamped. But you are
>> already doing all the work anyway ;-)
>>
>> In general, I agree it's nice to be able to upload the c.developermanual
>> content to PHC. But I have "maintenance phobia" about a lot of Plone
>> infrastructure these days.
>>
>>
>>> Is it confusing to keep both though?
>>
>>
>> Not IMHO. We have a few cases like this where some community member
>> argues for an alternate presentation of the same data (c.f. Wiggy and
>> the plone theme vs. trac theme debate of 2009).
>>
>> Presentation and UI are important, and Sphinx gets it right IMHO
>> (elegant, simple, just works, does not get in the way, etc.)
>>
>> Anyway, let's not forget the subject of this thread: displaying
>> c.developermanual prominently on http://plone.org/documentation (with a
>> link to
>> http://plone.org/documentation/manual/plone-community-developer-documentation)
>>
>> Who can we get to do this? I nominate Jon Stahl! (Because I believe he
>> was the last one to re-org/cleanup that page).
>>
>
> We did some work during the conf:
> http://plone.org/documentation/helpcenter_ploneorg2
>
> Does this link fit here?


Cool! Can we deploy this?


>
> -- israel
>
>
> ------------------------------------------------------------------------------
> Lotusphere 2011
> Register now for Lotusphere 2011 and learn how
> to connect the dots, take your collaborative environment
> to the next level, and enter the era of Social Business.
> http://p.sf.net/sfu/lotusphere-d2d


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

Re: [Plone-docs] collective-docs deserves a prominent link on plone.org

[Israel S. P. <duk...@gm...>]

On 14/12/10 16:12, Alex Clark wrote:
> On 12/9/10 3:28 PM, Dylan Jay wrote:
>> I think we need to keep the plone.org copy for a eat our own dog food
>> stance plus so search works.
>
> I think that is debatable, but I see your point. Personally, I'm not
> going to champion that cause right now because I'm swamped. But you are
> already doing all the work anyway ;-)
>
> In general, I agree it's nice to be able to upload the c.developermanual
> content to PHC. But I have "maintenance phobia" about a lot of Plone
> infrastructure these days.
>
>
>> Is it confusing to keep both though?
>
>
> Not IMHO. We have a few cases like this where some community member
> argues for an alternate presentation of the same data (c.f. Wiggy and
> the plone theme vs. trac theme debate of 2009).
>
> Presentation and UI are important, and Sphinx gets it right IMHO
> (elegant, simple, just works, does not get in the way, etc.)
>
> Anyway, let's not forget the subject of this thread: displaying
> c.developermanual prominently on http://plone.org/documentation (with a
> link to
> http://plone.org/documentation/manual/plone-community-developer-documentation)
>
> Who can we get to do this? I nominate Jon Stahl! (Because I believe he
> was the last one to re-org/cleanup that page).
>

We did some work during the conf:
http://plone.org/documentation/helpcenter_ploneorg2

Does this link fit here?

-- israel

Re: [Plone-docs] PHC 4.0a1 is released

[Israel S. P. <duk...@gm...>]

2010/12/9 Alex Clark <ac...@ac...>

>
> 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]

Re: [Plone-docs] PHC 4.0a1 is released

[Alex C. <ac...@ac...>]

On 12/9/10 10:05 AM, Israel Saeta Pérez wrote:
> Hi,
>
> 2010/12/9 Alex Clark <ac...@ac...
> <mailto:ac...@ac...>>
>
>     On 12/9/10 5:02 AM, Israel Saeta Pérez wrote:
>      > 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.

>
>      >
>      > 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 <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.



>
> -- israel
>
>
>
> ------------------------------------------------------------------------------
> This SF Dev2Dev email is sponsored by:
>
> WikiLeaks The End of the Free Internet
> http://p.sf.net/sfu/therealnews-com
>
>
>
> _______________________________________________
> Plone-docs mailing list
> Plo...@li...
> https://lists.sourceforge.net/lists/listinfo/plone-docs


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

Re: [Plone-docs] PHC 4.0a1 is released

[Israel S. P. <duk...@gm...>]

Hi,

2010/12/9 Alex Clark <ac...@ac...>

> On 12/9/10 5:02 AM, Israel Saeta Pérez wrote:
> > 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.



>  >
> > 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.
>
>
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

Re: [Plone-docs] PHC 4.0a1 is released

[Alex C. <ac...@ac...>]

On 12/9/10 5:02 AM, Israel Saeta Pérez wrote:
> 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.

>
> 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

>
> -- israel
>
>
> 2010/12/9 Alex Clark <ac...@ac...
> <mailto:ac...@ac...>>
>
>     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).
>
>
>     On 12/7/10 6:19 AM, Israel Saeta Pérez wrote:
>      > 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 <http://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
>     <http://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
>
>
>     ------------------------------------------------------------------------------
>     This SF Dev2Dev email is sponsored by:
>
>     WikiLeaks The End of the Free Internet
>     http://p.sf.net/sfu/therealnews-com
>     _______________________________________________
>     Plone-docs mailing list
>     Plo...@li...
>     <mailto:Plo...@li...>
>     https://lists.sourceforge.net/lists/listinfo/plone-docs
>
>
>
>
> ------------------------------------------------------------------------------
> This SF Dev2Dev email is sponsored by:
>
> WikiLeaks The End of the Free Internet
> http://p.sf.net/sfu/therealnews-com
>
>
>
> _______________________________________________
> Plone-docs mailing list
> Plo...@li...
> https://lists.sourceforge.net/lists/listinfo/plone-docs


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

Re: [Plone-docs] PHC 4.0a1 is released

[Israel S. P. <duk...@gm...>]

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


2010/12/9 Alex Clark <ac...@ac...>

> 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).
>
>
> On 12/7/10 6:19 AM, Israel Saeta Pérez wrote:
> > 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]
> >
> >
> >
> >
> ------------------------------------------------------------------------------
> > 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
>
>
>
> ------------------------------------------------------------------------------
> This SF Dev2Dev email is sponsored by:
>
> WikiLeaks The End of the Free Internet
> http://p.sf.net/sfu/therealnews-com
> _______________________________________________
> Plone-docs mailing list
> Plo...@li...
> https://lists.sourceforge.net/lists/listinfo/plone-docs
>

Re: [Plone-docs] PHC 4.0a1 is released

[Alex C. <ac...@ac...>]

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).


On 12/7/10 6:19 AM, Israel Saeta Pérez wrote:
> 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]
>
>
>
> ------------------------------------------------------------------------------
> 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

Re: [Plone-docs] documentation for plone.app.blob on plone.org needs update

[Kees H. <hi...@gw...>]

Hi Israel,

This looks excellent, thanks for acting so quickly.

Kees

On 12/08/2010 11:37 AM, Israel Saeta Pérez wrote:
> Hi Kees,
> 
> Thanks a lot for reporting this issue. I've updated the Archetypes Developer
> Manual fields reference accordingly. Could you check it out and see if
> everything's ok now?
> 
> -- israel
> 
> 
> 
> 2010/12/8 Kees Hink <hink-JZa/QnC6/z0A...@pu...
> <mailto:hi...@gw...>>
> 
>     I see now that the poster in the mailing list complains about a page in the
>     archetypes developer manual [1], not about the one in the plone 4 blobstorage
>     page [2]. I can't edit the archetypes page.
> 
>     The archetypes page's BlobField information is still sparse, and it doesn't
>     mention import ImageField from plone.app.blob.field. It's also a bit redundant.
>     For the sake of keeping documentation in one place, would it be a good idea to
>     link to [2]?
> 
>     [1]
>     http://plone.org/documentation/manual/developer-manual/archetypes/fields/fields-reference#blob_field
> 
>     [2]
>     http://plone.org/documentation/manual/upgrade-guide/version/upgrading-plone-3-x-to-4.0/updating-add-on-products-for-plone-4.0/use-plone.app.blob-based-blob-storage
> 
>     On 12/08/2010 10:08 AM, Kees Hink wrote:
>     > I just found out that i actually can change the page, so i did.
>     >
>     > On 12/08/2010 10:05 AM, Kees Hink wrote:
>     >> I followed the instructions on plone.org <http://plone.org> about adding
>     blobfields to content
>     >> type [1], but the first example (for ImageField) doesn't work
>     (AttributeError
>     >> for getAvailableSizes). I found the answer in a mailing list [2]. Like
>     someone
>     >> on the list suggested: i think the doc should be updated. I'd do it
>     myself if i
>     >> could.
>     >>
>     >> Kees
>     >>
>     >> [1]
>     >>
>     http://plone.org/documentation/manual/upgrade-guide/version/upgrading-plone-3-x-to-4.0/updating-add-on-products-for-plone-4.0/use-plone.app.blob-based-blob-storage,
>     >>
>     >> [2]
>     >>
>     http://plone.293351.n2.nabble.com/Plone-4b3-ImageWidget-and-AttributeError-getAvailableSizes-td5076850.html
>     >
>     >
>     ------------------------------------------------------------------------------
>     > 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
> 
> 
>     ------------------------------------------------------------------------------
>     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
>     _______________________________________________
>     Plone-docs mailing list
>     Plo...@pu...
>     <mailto:Plo...@pu...>
>     https://lists.sourceforge.net/lists/listinfo/plone-docs
> 
> 
> 
> 
> ------------------------------------------------------------------------------
> 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
> 
> 
> 
> _______________________________________________
> Plone-docs mailing list
> Plo...@pu...
> https://lists.sourceforge.net/lists/listinfo/plone-docs