silva-general — General discussion on Silva.

Re: [Silva-general] Pay per View... and extended meta data

[<tom...@vi...>]

Thank-you both for your replys, they have really helped me out and I am 
now 'almost' convinced that Zope/Silva is the way to go. I have never had 
any experience with Python, although I started to read the online manual 
last night and seing as how I know PHP/Perl etc, it shouldn't be too hard 
to master yet another set of syntax.

> Indeed, both Zope and Silva are quite large APIs that aren't very easy
> to learn. Hopefully this will change somewhat in the future (e.g. when
> we port Silva to Zope 3).

Any ideas when is Zope 3 is due to be released and when the Silva port 
happen?

> I'm not sure if Clemens' understands this correctly, or perhaps I
> misunderstand you, but it sounds to me like you want to see history of
> the price of a certain article rather than just the current price of a
> set of articles, right?

This is correct.

> If so, that would not be possible using the metadata system, and you
> would indeed need either an external system or have to adjust Silva. I
> would probably recommend the latter, by the way, it should be quite easy
> to have some data structure on each object that maintains such a 
history.

You reccomend adjusting Silva in some way to accomplish this, however my 
gut fealing is that I would be better off storing this data externally in 
a MySQL database. This will allow me to do all kinds of fancy 
reporting/cross referencing using my existing SQL knowledge.

> Another option (and perhaps better) than assigning a proxy role to a
> script would be to use so-called Product code, code which is located on
> the filesystem, that is executed without checking permissions.

Are there examples somwhere of this 'Product-code'?

> Indeed ZODB objects should have some id, and indeed that is not
> available (easily at least) from Zope or Silva code.

so it's not accessable 'easily' but is is accessable right? Surely it's 
going to be simpler to access and use this unique id, than to try to build 
ny own tracking system, after all a tracking system has already been 
built... The whole reason I am looking into options such as Silva is to 
avoid re-inventing the wheel (or tracking system in this case) where 
possible.

> ...or use e.g. MySQLMembership (should be in CVS too) as example code.

I've had a little look through this in the CVS, but there seems to be no 
readme doc explaing what it actually is/does... Any chance of a little 
briefing or a link to some documentation?

What I really want is a) somwhere to store detailed information about 
users (personal details, home address, shipping address, billing address, 
company info, website preferences etc.), and b) a way for members to 
update their details via the kopu interface (just to keep things nice and 
consistant). If I opt for storing the user information in an external 
database, is that going to deny me the ability to use kpou in this way? Or 
would that be impossible anyway? (I assume the other option apart from an 
external database is to develop a metadata set to store this information).


On a side note...
can you reccomend a good book for learning the inner details of Zope?


many many many thanks... you've been really helpful :)


-- 
Tom David Kirkpatrick
Virus Bulletin Web Developer, Virus Bulletin

Tel: +44 1235 555139
Web: www.virusbtn.com

Re: [Silva-general] SilvaNews get_intro, other issues/suggestions/improvements

[Guido W. <gu...@in...>]

Tuomas Tonteri wrote:

>SilvaNews shows an intro to news items, where it includes content up to the first paragraph if it fits within the defined maxsize "1024". I would need it to show content up to a defined maxsize without any limits on number on paragraphs. 
>
Actually I had already decided the 'break on first paragraph' wasn't a 
good idea, and turned it off. It will display the first X items up to a 
text size of 1024 no matter what the type of items is in the next 
SilvaNews release (1.3?).

>Even better would be if the maxsize would be user definable in SilvaArticle.
>
I've thought about that but wasn't sure where to make this configurable, 
I don't think the article is the best place because that would put the 
way items are displayed into the hands of authors and would sort of 
surpass editors for this matter. My guess is that allowing authors to 
determine how much of their article is shown would lead to *very* long 
intros and such... ;) On the other hand, the author is the one that sees 
what the intro would look like first, it would probably not be nice for 
editors to have to preview all items in a news viewer to see whether the 
intro looks good or not.

Not sure about this, if you have suggestions please let me know. 
Ignoring the issue until a decision has been made.

> Also crucial would be to not have the "see more" button appear at all, if all the content fits within the intro.
>
>  
>
Good idea, I'll apply it.

>Some reasoning behind this, is for example when a large floating image is in the start of the article, then there will be ugly looking large white space when the first paragraph is not sufficiently long.
>
>  
>
(Sidenote: images will be handled differently in the next SilvaNews 
release, they will at least be scaled down and perhaps not shown at all 
in favour of a dedicated image per item.)

>Second, I reported this earlier also, SilvaArticle can not be edited with Kupu editor at all whereas SilvaDocument can be. Is this fixable?
>
>  
>
The problem is that it's a *lot* of work to do that properly and I just 
don't have time to do so. I hope to have it at some point, but can at 
the moment really not tell when...

>Also having the ability to make folders inside Silva NewsSource is a pretty important feature and has been reported before on this list.
>
>  
>
Yes, and that's just a broken feature that needs to be fixed. 
Unfortunately I'm not entirely sure what the best way to solve this 
would be: we chose to allow 'plain' Silva folders in SilvaNews 
publications before, but there are several issues with those so I think 
it may be better to allow only other SilvaNews publications. However, 
since I'm still not entirely sure (and never really had the time to 
investigate it) I decided to ignore the issue for the last release, I 
hope I get the chance to fix it in the upcoming one.

Cheers,

Guido

Re: [Silva-general] Pay per View... and extended meta data

[Guido W. <gu...@in...>]

Hi!

Since I reckon Clemens' reply may be a bit technical, and because I 
wanted to make some additional remarks, I decided to reply on this:

Clemens Klein-Robbenhaar wrote:

>> But also confused (and I get the impression that most people new to 
>> Zope/Silva etc also are similarly confused).
>>
>
>  Yup, Zope, especially Zope2 Silva currently is build on, has some
> steep learing curve. That the price for getting a complex and powerful
> tool ...
>
Indeed, both Zope and Silva are quite large APIs that aren't very easy 
to learn. Hopefully this will change somewhat in the future (e.g. when 
we port Silva to Zope 3).

>> I can't really see any way to implement the Pay-per-view feature I am 
>> after. How can I assign a price to each Publication or article?
>
>
>  Check with the "service_metadata" in the "Services" tab of
> the Silva root. You can add extra metadata sets here. I guess it should
> be possible to add an extra set containing the pricing informations.
>
Let me explain this in a little more detail: Silva's metadata system is 
extensible using either the ZMI or XML from the filesystem (the latter 
is recommended of course), you can defined 'metadata sets' that contain 
certain fields. Such a metadata should be quite easy to create, and 
would indeed allow you to store the price, although it wouldn't allow 
you to do very fancy things with the data (see below).

>> And how can I store a history of all the prices that were ever 
>> applied to each article or publication? Would I have to use an 
>> external 'price' database?
>
>
>  Uh, this is much more trickier ... If You look at the "lastauthor" 
> element
> of the "silva-extra" metadata set, You can figure out how to calculate
> metadata values from other data sources. (Hint: the "Field" tab and 
> then the
> "TALES" tab ... the calculation is in the field for the "default".
> You maybe want to read the "doc/silva-extra.xml"  the metadata set is 
> derived
> from on install instead ...)
>
I'm not sure if Clemens' understands this correctly, or perhaps I 
misunderstand you, but it sounds to me like you want to see history of 
the price of a certain article rather than just the current price of a 
set of articles, right?

If so, that would not be possible using the metadata system, and you 
would indeed need either an external system or have to adjust Silva. I 
would probably recommend the latter, by the way, it should be quite easy 
to have some data structure on each object that maintains such a history.

>> If so, how can I use this external database if each object in silva 
>> doesn't have a persistant uniuqe identifier (as far as I can tell, 
>> the unique id of an object in Zope/Silva is its location in the 
>> database. So what if I move the item? Its unique id has now changed 
>> and I have to update my 'price' database???)
>>
>
>  Uh, good question. Actually there is also an OID used internally in 
> the ZODB,
> but I do not know how to access that unique id from Zope or Silva.
>
Indeed ZODB objects should have some id, and indeed that is not 
available (easily at least) from Zope or Silva code. I think the best 
thing to do would be to generate and keep track of site-wide unique ids 
yourself, which shouldn't be too hard (although not trivial: consider 
issues like importing objects from another site and such!).

>  If You cannot find any better way but update the external data base
> on moving documents (I don't know one), You maybe want to add something
> the the "manage_afterAdd" and "manage_beforeDelete" hooks. These hooks
> are called by Zope after it add a new object or before it deletes one.
>
Yes, keep those in mind: you will need to register stuff there for sure. 
See the Silva core code for examples.

>> I am thinking that the assignment of user permissions would probably 
>> be implemented outside of silva. So I'd have a 'buy it now' button 
>> next to each article preview. This would take them to a form asking 
>> for the required details.  Submitting the form would cause a script 
>> to be run, which would then store details of the transaction in 
>> either a mysql database or in the zodb. I also have to get this 
>> script to interact with Silva in order to add the user to the access 
>> settings on the required document (or publication). Is it possible to 
>> apply permissions via a script or does it have to be done through the 
>> admin interface?
>>
>
>  You can define a python script which calls the
> sec_assign(userid, role) on the object You want to grant rights on.
> Note that You should give the script a "Manager" proxy role
> so it is allowed to call the method even if executed by some user
> not having management rights.
>
Another option (and perhaps better) than assigning a proxy role to a 
script would be to use so-called Product code, code which is located on 
the filesystem, that is executed without checking permissions. Apart 
from that I think hooking in some code to register the user to a MySQL 
database (or the ZODB for that matter, depending on the amount of 
expected transactions, since the ZODB can become somewhat bloated if a 
lot of registrations happen) shouldn't be too hard. This code would also 
indeed be allowed to e.g. add users to Zope's user management machinery 
and set roles for those users (e.g. Authorized, which sounds like a good 
role for your usecase).

>> Also, The information stored about each user seems to be very 
>> limited. I can only see a way to set a name and email address. What 
>> if I also want to store other details about the user? Am I right in 
>> thinking that the user data is controlled by zope and only the users 
>> object permissions are controlled by silva? So perhaps this is more 
>> of a zope question, but how can I associate more data with each user?
>>
>
> You can install a different Silva Membership implementation. An example
> code is in the public CVS at infrae:
>
>   http://cvs.infrae.com/SilvaDemoMembership/
>
> (I cannot find a link to download this demo product as a package,
> but its not that big anyway.)
>
Mind that that is probably out-of-date, but it should still be quite a 
good example. If you run into trouble, either check the Silva core to 
see if the API has changed or use e.g. MySQLMembership (should be in CVS 
too) as example code.

>
>> Also. If two authors are working on an article. Does Silva store this 
>> information? So when I display the article, will I be able to list 
>> all authors who worked on it, and also the editor who approved it?
>>
>
>  No, sorry, that information currently not stored, only the last author.
>
Indeed, you would have to store such information yourself. I think the 
feature doesn't sound bad, so who knows it might end up in core Silva 
some day, but right now indeed only the last author is stored.

I hope it's somewhat clear what needs to be done now, if you still have 
questions please let us know...

Cheers,

Guido

Re: [Silva-general] Checkboxes in metadata not unsettable

[Jan-Wijbrand K. <jw...@in...>]

Clemens Klein-Robbenhaar wrote:
> Hi Joachim,
> 
>> another bug that has hit me, that supposedly is fixed in CVS and for that
>> I'd like to have a fix if the bugfix release will be too far away: 
>> CheckBoxes in metadata sets are not un-settable.
> 
> This has been solved for Fomulator a while ago, but the necessary adjustments
> for the metadae fields have not ben made, it seems.

The 'unsettable' checkbox problem is solved for upcomming Silva-1.3 - and the
new versions of Formulator and SilvaMetadata (the fix is largely in here) that
go with it.

> Could You please add an issue to the issue tracker?
> http://issues.infrae.com/silva/

Was an issue created? If so, I can't find it... maybe anyone has a number, so I
can comment on it?


kind regards,
jw

-- 
Jan-Wijbrand Kolman
jw...@in...

[Silva-general] Mailing list migration rescheduled

[Eric C. <er...@in...>]

Silva-general will be migrated later today (after 17:00 CET) and all 
existing members will be moved along with it, since noone objected. When 
this is done, I shall send a mail, but you will see one before that 
asking for confirmation of your subscription. I apologize for any 
inconvenience, and I hope we can keep it to an absolute minimum.

eric casteleijn

Re: [Silva-general] AttributeError when upgrading from 1.1 to 1.2

[Jose A. P. A. <an...@am...>]

I just installed the latest libxml(2.6.19-1)/libxslt(1.1.9-1) libraries and
set my sites to use the XSLT renderer.

No problems so far.

I'm running on Zope 2.7.4, Python 2.3.3 on REHL3.

--
Angelo


> From: "Jose Angelo P. Abarentos" <an...@am...>
> Date: Mon, 04 Apr 2005 10:40:28 +0800
> To: Clemens Klein-Robbenhaar <cro...@we...>
> Cc: "sil...@li..."
> <sil...@li...>
> Subject: Re: [Silva-general] AttributeError when upgrading from 1.1 to 1.2
> 
> After re-reading the INSTALL.txt file, I found out that I have to have Zope
> 2.7.4. 
> 
> It worked after I upgraded Zope but now I got bitten by the Unicode bug
> again. Going through the list archives, it looks like I need to use the new
> XSLT renderer so I'm installing libxml2 and libxslt.
> 
> I will keep you posted.
> 
> Thanks!
> 
> --
> Angelo
> 
> 
>> From: Clemens Klein-Robbenhaar <cro...@we...>
>> Date: Sun, 03 Apr 2005 01:26:31 +0200
>> To: "Jose Angelo P. Abarentos" <an...@am...>
>> Cc: "sil...@li..."
>> <sil...@li...>
>> Subject: Re: [Silva-general] AttributeError when upgrading from 1.1 to 1.2
>> 
>> 
>> Hi Angelo,
>> 
>>> 
>>> I'm trying to upgrade the content on my site from 1.1 to 1.2 and I keep
>>> getting an AttributeError. Below is the traceback:
>>> 
>>> Traceback (innermost last):
>>>   Module ZPublisher.Publish, line 100, in publish
>>>   Module ZPublisher.mapply, line 88, in mapply
>>>   Module ZPublisher.Publish, line 40, in call_object
>>>   Module Products.Silva.ExtensionService, line 92, in upgrade_all
>>>   Module Products.Silva.Root, line 210, in upgrade_silva
>>>   Module Products.Silva.upgrade, line 159, in upgrade
>>>   Module Products.Silva.upgrade, line 114, in upgradeTree
>>>   Module Products.Silva.upgrade, line 92, in upgradeObject
>>>   Module Products.Silva.upgrade_120, line 43, in upgrade
>>>   Module Products.ZCatalog.ZCatalog, line 454, in reindexIndex
>>>   Module Products.ZCatalog.ZCatalog, line 793, in resolve_url
>>> AttributeError: 'NoneType' object has no attribute 'script'
>>> 
>> 
>>   Uh, oh, errors in the catalog :-/
>> 
>>   Which Zope version are You running ?
>> 
>> Clemens
>> 
>> 
>> -------------------------------------------------------
>> SF email is sponsored by - The IT Product Guide
>> Read honest & candid reviews on hundreds of IT Products from real users.
>> Discover which products truly live up to the hype. Start reading now.
>> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
>> _______________________________________________
>> Silva-general mailing list
>> Sil...@li...
>> https://lists.sourceforge.net/lists/listinfo/silva-general
> 
> 
> 
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Silva-general mailing list
> Sil...@li...
> https://lists.sourceforge.net/lists/listinfo/silva-general

Re: [Silva-general] AttributeError when upgrading from 1.1 to 1.2

[Jose A. P. A. <an...@am...>]

After re-reading the INSTALL.txt file, I found out that I have to have Zope
2.7.4. 

It worked after I upgraded Zope but now I got bitten by the Unicode bug
again. Going through the list archives, it looks like I need to use the new
XSLT renderer so I'm installing libxml2 and libxslt.

I will keep you posted.

Thanks!

--
Angelo


> From: Clemens Klein-Robbenhaar <cro...@we...>
> Date: Sun, 03 Apr 2005 01:26:31 +0200
> To: "Jose Angelo P. Abarentos" <an...@am...>
> Cc: "sil...@li..."
> <sil...@li...>
> Subject: Re: [Silva-general] AttributeError when upgrading from 1.1 to 1.2
> 
> 
> Hi Angelo,
> 
>> 
>> I'm trying to upgrade the content on my site from 1.1 to 1.2 and I keep
>> getting an AttributeError. Below is the traceback:
>> 
>> Traceback (innermost last):
>>   Module ZPublisher.Publish, line 100, in publish
>>   Module ZPublisher.mapply, line 88, in mapply
>>   Module ZPublisher.Publish, line 40, in call_object
>>   Module Products.Silva.ExtensionService, line 92, in upgrade_all
>>   Module Products.Silva.Root, line 210, in upgrade_silva
>>   Module Products.Silva.upgrade, line 159, in upgrade
>>   Module Products.Silva.upgrade, line 114, in upgradeTree
>>   Module Products.Silva.upgrade, line 92, in upgradeObject
>>   Module Products.Silva.upgrade_120, line 43, in upgrade
>>   Module Products.ZCatalog.ZCatalog, line 454, in reindexIndex
>>   Module Products.ZCatalog.ZCatalog, line 793, in resolve_url
>> AttributeError: 'NoneType' object has no attribute 'script'
>> 
> 
>   Uh, oh, errors in the catalog :-/
> 
>   Which Zope version are You running ?
> 
> Clemens
> 
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Silva-general mailing list
> Sil...@li...
> https://lists.sourceforge.net/lists/listinfo/silva-general

[Silva-general] Some Unicodeerrors with scands in ?wrong? places

[Tuomas T. <tuo...@he...>]

By scands I mean =E4,=F6 and =E5.

Putting a scand inside the title of a SilvaImage inside SilvaNewsArticle re=
sults in UnicodeDecodeError, when trying to publish the article. This is a =
problem, since that text appears as the tooltip and I needs scands in there=
 occasionally.

Well, I've had also other similar UnicodeDecodeErrors because of scands, bu=
t can't just now remember what were the wrong places. I'l reply to this thr=
ead if I run into another one.

--=20
Tuomas Tonteri
My public PGP key: http://www.physics.helsinki.fi/~tatonter/tt.asc

[Silva-general] SilvaNews get_intro, other issues/suggestions/improvements

[Tuomas T. <tuo...@he...>]

SilvaNews shows an intro to news items, where it includes content up to the first paragraph if it fits within the defined maxsize "1024". I would need it to show content up to a defined maxsize without any limits on number on paragraphs. Even better would be if the maxsize would be user definable in SilvaArticle. Also crucial would be to not have the "see more" button appear at all, if all the content fits within the intro.

Some reasoning behind this, is for example when a large floating image is in the start of the article, then there will be ugly looking large white space when the first paragraph is not sufficiently long.

Second, I reported this earlier also, SilvaArticle can not be edited with Kupu editor at all whereas SilvaDocument can be. Is this fixable?

Also having the ability to make folders inside Silva NewsSource is a pretty important feature and has been reported before on this list.

-- 
Tuomas Tonteri
My public PGP key: http://www.physics.helsinki.fi/~tatonter/tt.asc

[Silva-general] Checkboxes in metadata not unsettable; was: Problems with Umlauts

[Clemens Klein-R. <cro...@we...>]

Hi Joachim,

> another bug that has hit me, that supposedly is fixed in CVS and for
> that I'd like to have a fix if the bugfix release will be too far away:
> CheckBoxes in metadata sets are not un-settable.

[...]

This has been solved for Fomulator a while ago, but the necessary
adjustments for the metadae fields have not ben made, it seems.

  Could You please add an issue to the issue tracker?
http://issues.infrae.com/silva/

  It would be nice if You can attach an example metadata set
with a checkbox there for easier reproducing the issue.

Clemens

Re: [Silva-general] passing values to formulator

[Clemens Klein-R. <cro...@we...>]

Kenneth Gonsalves wrote:
> hi
> i want to use formulator to edit/update data. for this i get the data 
> from the database, and want to insert the values in the formulator 
> form fields. How do i do this?

Most probably via a TALS expession in the corresponding fields.
Read the "formulator-general" mailinglist archives on sourceforge;
its a FAQ there ...

Clemens

Re: [Silva-general] Problems with Umlauts

[Clemens Klein-R. <cro...@we...>]

Joachim Breitner wrote:
> 
> Indeed, that bug it seems to be. Will it be in the 1.2.1 release? Any
> estimates when the release is due (if it is within 2 or 3 weeks, I'll
> just wait, otherwise I need a fix for what I got). Can I get a fix in
> that case somehow?

I do not know about the release scedule but I can send You a patch
if You need tha fix nd do not want to run from the CVS HEAD. Note that the patch 
may be incomplete and otherwiese buggy ...

Clemens

Re: [Silva-general] Pay per View... and extended meta data

[Clemens Klein-R. <cro...@we...>]

Hi Tom,

  [...]
> But also confused (and I get the impression that most people new to 
> Zope/Silva etc also are similarly confused).
> 

  Yup, Zope, especially Zope2 Silva currently is build on, has some
steep learing curve. That the price for getting a complex and powerful
tool ...

> I can't really see any way to implement the Pay-per-view feature I am 
> after. How can I assign a price to each Publication or article?

  Check with the "service_metadata" in the "Services" tab of
the Silva root. You can add extra metadata sets here. I guess it should
be possible to add an extra set containing the pricing informations.

> And how 
> can I store a history of all the prices that were ever applied to each 
> article or publication? Would I have to use an external 'price' database?

  Uh, this is much more trickier ... If You look at the "lastauthor" element
of the "silva-extra" metadata set, You can figure out how to calculate
metadata values from other data sources. (Hint: the "Field" tab and then the
"TALES" tab ... the calculation is in the field for the "default".
You maybe want to read the "doc/silva-extra.xml"  the metadata set is derived
from on install instead ...)

> If so, how can I use this external database if each object in silva 
> doesn't have a persistant uniuqe identifier (as far as I can tell, the 
> unique id of an object in Zope/Silva is its location in the database. So 
> what if I move the item? Its unique id has now changed and I have to 
> update my 'price' database???)
> 

  Uh, good question. Actually there is also an OID used internally in the ZODB,
but I do not know how to access that unique id from Zope or Silva.

  If You cannot find any better way but update the external data base
on moving documents (I don't know one), You maybe want to add something
the the "manage_afterAdd" and "manage_beforeDelete" hooks. These hooks
are called by Zope after it add a new object or before it deletes one.

  Renaming objects is implemented by first deleting them in the old place and
later add them in the new place. Unfortunately in the current implementation
this means You have to modify the Silva (or SilvaDocument) product itself
add some behaviour in these hooks.

> I am thinking that the assignment of user permissions would probably be 
> implemented outside of silva. So I'd have a 'buy it now' button next to 
> each article preview. This would take them to a form asking for the 
> required details.  Submitting the form would cause a script to be run, 
> which would then store details of the transaction in either a mysql 
> database or in the zodb. I also have to get this script to interact with 
> Silva in order to add the user to the access settings on the required 
> document (or publication). Is it possible to apply permissions via a 
> script or does it have to be done through the admin interface?
> 

  You can define a python script which calls the
sec_assign(userid, role) on the object You want to grant rights on.
Note that You should give the script a "Manager" proxy role
so it is allowed to call the method even if executed by some user
not having management rights.

> Also, The information stored about each user seems to be very limited. I 
> can only see a way to set a name and email address. What if I also want to 
> store other details about the user? Am I right in thinking that the user 
> data is controlled by zope and only the users object permissions are 
> controlled by silva? So perhaps this is more of a zope question, but how 
> can I associate more data with each user?
> 

You can install a different Silva Membership implementation. An example
code is in the public CVS at infrae:

   http://cvs.infrae.com/SilvaDemoMembership/

(I cannot find a link to download this demo product as a package,
but its not that big anyway.)


> Also. If two authors are working on an article. Does Silva store this 
> information? So when I display the article, will I be able to list all 
> authors who worked on it, and also the editor who approved it?
> 

  No, sorry, that information currently not stored, only the last author.


Cheers,
Clemens

Re: [Silva-general] custom extension

[Clemens Klein-R. <cro...@we...>]

Hi Somhorst,


> as some already know i'm building a custom extension for Silva. At the
> moment I have some problems. I created an custom form with an custom
> add_form.pt ( lots of css ).=20
> The problem is that when I submit the form with special characters in i=
t (
> like =F3 or =E7 ) I get an ascii error. The system doesnt seem to know =
how to
> handle the special chars. I find=20
> this odd because I specified in the form and in the template files that=
 the
> system should use UTF-8 so there shouldnt be any error involving ASCII =
?=20

  This is not an "ascii" error, but some problem of implicitely convertin=
g
strings to or from unicode strings. If You get form date from
the request, its always a plain python string, and hopefully in
UTF-8 encoding. You should convert it manually to unicode
e.g. via "title =3D unicode(title, 'utf-8')"

  If You are getting Your data from a Formulator form via validation.
You can ask Formulator to do the transformation by setting the
unicode flag of the form (e.g. having  "<unicode>1</unicode>"
in the corresponfind field.)

>=20
> Next problem is after I submitted the form (because without special cha=
rs it
> works ) and want to edit the form I get an error ''str' object has no
> attribute 'get''=20
[...]

  You will have to read the traceback associated with that error
(from the /error_log) and read the corresponding code ... . If You get st=
uck=20
completely You can post the traceback and the corresponding code
snippets to the list and hope someone else has a look at it.
  The more You get to the point, the higher the probability someone will
answer ;-)


Cheers,
Clemens

Re: [Silva-general] AttributeError when upgrading from 1.1 to 1.2

[Clemens Klein-R. <cro...@we...>]

Hi Angelo,

> 
> I'm trying to upgrade the content on my site from 1.1 to 1.2 and I keep
> getting an AttributeError. Below is the traceback:
> 
> Traceback (innermost last):
>   Module ZPublisher.Publish, line 100, in publish
>   Module ZPublisher.mapply, line 88, in mapply
>   Module ZPublisher.Publish, line 40, in call_object
>   Module Products.Silva.ExtensionService, line 92, in upgrade_all
>   Module Products.Silva.Root, line 210, in upgrade_silva
>   Module Products.Silva.upgrade, line 159, in upgrade
>   Module Products.Silva.upgrade, line 114, in upgradeTree
>   Module Products.Silva.upgrade, line 92, in upgradeObject
>   Module Products.Silva.upgrade_120, line 43, in upgrade
>   Module Products.ZCatalog.ZCatalog, line 454, in reindexIndex
>   Module Products.ZCatalog.ZCatalog, line 793, in resolve_url
> AttributeError: 'NoneType' object has no attribute 'script'
> 

  Uh, oh, errors in the catalog :-/

  Which Zope version are You running ?

Clemens

[Silva-general] AttributeError when upgrading from 1.1 to 1.2

[Jose A. P. A. <an...@am...>]

Hello All,

I'm trying to upgrade the content on my site from 1.1 to 1.2 and I keep
getting an AttributeError. Below is the traceback:

Traceback (innermost last):
  Module ZPublisher.Publish, line 100, in publish
  Module ZPublisher.mapply, line 88, in mapply
  Module ZPublisher.Publish, line 40, in call_object
  Module Products.Silva.ExtensionService, line 92, in upgrade_all
  Module Products.Silva.Root, line 210, in upgrade_silva
  Module Products.Silva.upgrade, line 159, in upgrade
  Module Products.Silva.upgrade, line 114, in upgradeTree
  Module Products.Silva.upgrade, line 92, in upgradeObject
  Module Products.Silva.upgrade_120, line 43, in upgrade
  Module Products.ZCatalog.ZCatalog, line 454, in reindexIndex
  Module Products.ZCatalog.ZCatalog, line 793, in resolve_url
AttributeError: 'NoneType' object has no attribute 'script'


Anyone have idea where this is happening?

--
Angelo

[Silva-general] Pay per View... and extended meta data

[<tom...@vi...>]

I've spent some weeks now designing a relational database that will act as 
a kind of document publishing system, and also store details about the 
users who use it (address details, personal details etc.) allowing them to 
subscribe to specific articles or publicationseither a pay-per-view basis, 
an anual basis or to just outright buy the right to view the article or 
publication at any time.

I then stumble accross Zope and Silva....
Wow, I'm impressed!

I think the way Silva lets you create documents/publications etc is great. 
The way you can set permissions to individual items or entire publications 
is great. The way it stores multiple versions of documents is great. And 
from what I can tell, the front end (ie. the view the public sees) is very 
customiseable, and that is great too!

But also confused (and I get the impression that most people new to 
Zope/Silva etc also are similarly confused).

I can't really see any way to implement the Pay-per-view feature I am 
after. How can I assign a price to each Publication or article? And how 
can I store a history of all the prices that were ever applied to each 
article or publication? Would I have to use an external 'price' database? 
If so, how can I use this external database if each object in silva 
doesn't have a persistant uniuqe identifier (as far as I can tell, the 
unique id of an object in Zope/Silva is its location in the database. So 
what if I move the item? Its unique id has now changed and I have to 
update my 'price' database???)

I am thinking that the assignment of user permissions would probably be 
implemented outside of silva. So I'd have a 'buy it now' button next to 
each article preview. This would take them to a form asking for the 
required details.  Submitting the form would cause a script to be run, 
which would then store details of the transaction in either a mysql 
database or in the zodb. I also have to get this script to interact with 
Silva in order to add the user to the access settings on the required 
document (or publication). Is it possible to apply permissions via a 
script or does it have to be done through the admin interface?

Also, The information stored about each user seems to be very limited. I 
can only see a way to set a name and email address. What if I also want to 
store other details about the user? Am I right in thinking that the user 
data is controlled by zope and only the users object permissions are 
controlled by silva? So perhaps this is more of a zope question, but how 
can I associate more data with each user?

Also. If two authors are working on an article. Does Silva store this 
information? So when I display the article, will I be able to list all 
authors who worked on it, and also the editor who approved it?

A bombardment of questions I know... But hey!

-- 
Tom David Kirkpatrick
Virus Bulletin Web Developer, Virus Bulletin

Tel: +44 1235 555139
Web: www.virusbtn.com

[Silva-general] custom extension

[Somhorst J. <qs...@oc...>]

Hi all,

as some already know i'm building a custom extension for Silva. At the
moment I have some problems. I created an custom form with an custom
add_form.pt ( lots of css ).=20
The problem is that when I submit the form with special characters in =
it (
like =F3 or =E7 ) I get an ascii error. The system doesnt seem to know =
how to
handle the special chars. I find=20
this odd because I specified in the form and in the template files that =
the
system should use UTF-8 so there shouldnt be any error involving ASCII =
?=20

Next problem is after I submitted the form (because without special =
chars it
works ) and want to edit the form I get an error ''str' object has no
attribute 'get'' a few weeks ago I did also get this
error when i tried to use a python script to fill a multilistbox. For =
some
reason I suspect that the problem is caused by one of the fields I =
specified
in the form but I cant seem to find which one.

The base extension I uses was EPTALK and worked fine, ofcourse I looked =
@
other extensions and scripts in the products folder. Could someon help =
me
with the problem?

Yours sincerely,

J.somhorst

Re: [Silva-general] Questions about SilvaNews

[Bengt G. <ben...@id...>]

Tuomas Tonteri wrote:

> 2) How do I customize Silva News output? Basically I could edit 
> the Product at the Zope dir and install the modified Silva
> News product, but can I not edit the Silva News files from
> ZMI? For example if I would like to have <hr> after each news 
> item from Silva News Viewer, how should I do it the proper way?

Today, to modify presentation, the proper way has moved to CSS. Perhaps
you can add a bottom border to the CSS section formatting the rows of
the news table?

Regards

Bengt

Re: [Silva-general] Questions about SilvaNews

[Andy <aal...@be...>]

Hi Toumas,

> 1) There is no KUPU editor avaible for editing Silva Article, that Silva
> News uses. Is there some reason Silva Document and Silva Article are
> separate?
I can't answer this one...perhaps Guido? (I'm interested in an answer two ;-)
>
> 2) How do I customize Silva News output? Basically I could edit the Product
> at the Zope dir and install the modified Silva News product, but can I not
> edit the Silva News files from ZMI? For example if I would like to have
> <hr> after each news item from Silva News Viewer, how should I do it the
> proper way?

There are two ways you can do this.  The first way is as you mentioned: modify 
the NewsViewer code that renders news headlines.  You'll find it here:
${ZOPE_HOME}/Products/SilvaNews/views/public/NewsViewer/

There are three '.pt' files (Zope Page Templates) that render the three public 
uses of a news viewer (viewing most recent news, archives, and searching).  
These are view_news.pt, view_archive.pt and search_news.pt, respectively.

In view_news.pt, there is a line containing:
   <br /><br />
You prob. want to add your <hr /> before or after it.

The down side of doing this is that you have to remember to modify the package 
every time you upgrade SilvaNews.

The other way is to use zope page templates and python scripts through the 
ZMI.  Using this method, you would retrieve the news items from the news 
viewer.  I don't think SilvaNews has a public API document, so you'll have to 
inspect the source of NewsViewer and possibly other modules.  Here's an 
example using page templates:

<div id="newsblock" tal:define="items here/newsviewer/get_items">
<tal:rep repeat="item items">
 <div tal:define="news_item item/getObject">
  <h1 tal:content="news_item/get_title" />
  <h2 tal:content="news_item/subheader" tal:condition="news_item/subheader" />
  <p tal:content="obj/lead" tal:condition="obj/lead" />
 </div>
</tal:rep>
</div>

I think the latest (and unreleased) version of SilvaNews changes the above 
NewsItem API a bit, but this will work for SilvaNews-1.0.  Since it sounds 
like you're new to Zope, let me walk you through this:

The first <div> tag retrieves the news items from the news viewer.  The items 
returned are not the actual news items yet, it is a resultset retrieved from 
the zope catalog.  The next line, tal:rep sets up a loop over the items.  
Using tal:name tags for looping and defines, conditions, etc. is nice because 
they are automatically removed from the rendered content.  The next div tag 
retrieves the NewsItem from the catalog result, and defines it as news_item.  
Inside this div tag the summary of the news item is rendered.  The method 
get_title is defined in the Silva product, subheader and lead are defined in 
NewsItem.py.

I hope this helps point you in the right direction.

cheers,
Andy

Re: [Silva-general] Problems with Umlauts

[Joachim B. <ma...@jo...>]

Hi again,

another bug that has hit me, that supposedly is fixed in CVS and for
that I'd like to have a fix if the bugfix release will be too far away:
CheckBoxes in metadata sets are not un-settable.

This is BTW how I solved my problem WRT hiding stuff from the
navigation: Adding my own metadata set and adding a
"hide-from-metadata"-field, that is checked in my layout template. My
other problem (hiding not accessible stuff) I solved digging around in
Zope-API-Documents. Though I'd say that these two options should be
included in regular Silva, e.g. a dropdown list in the silva-general
metaset "Show in Navigation? Always, Never, If Content is Readable by
current user" or the like. Just a suggestion though.

Thanks and Greetings, and I hope you don't mind my many posts

Joachim
--=20
Joachim Breitner
  e-Mail: ma...@jo...
  Homepage: http://www.joachim-breitner.de
  ICQ#: 74513189
Bitte senden Sie mir keine Word- oder PowerPoint-Anh=E4nge.
Siehe http://www.fsf.org/philosophy/no-word-attachments.de.html

Re: [Silva-general] Problems with Umlauts

[Joachim B. <ma...@jo...>]

Hi Clemens and List,

Am Freitag, den 25.03.2005, 20:45 +0100 schrieb Clemens
Klein-Robbenhaar:
>   This smells much like issue 1270:http://issues.infrae.com/silva/issue12=
70
>=20
>   A tentative fix is in the CVS version, but I do not think we have caugh=
t
> all cases where the problem can occure. In my opinion its a Zope bug in t=
he
> first place, but I am no very confortable with the i18n-stuff of Zope to
> be sure about this ...

Indeed, that bug it seems to be. Will it be in the 1.2.1 release? Any
estimates when the release is due (if it is within 2 or 3 weeks, I'll
just wait, otherwise I need a fix for what I got). Can I get a fix in
that case somehow?

Greetings,
Joachim
--=20
Joachim Breitner
  e-Mail: ma...@jo...
  Homepage: http://www.joachim-breitner.de
  ICQ#: 74513189
Bitte senden Sie mir keine Word- oder PowerPoint-Anh=E4nge.
Siehe http://www.fsf.org/philosophy/no-word-attachments.de.html

Re: [Silva-general] Problems with Umlauts

[Clemens Klein-R. <cro...@we...>]

Hi Joachim,

> Hi,
>=20
> I got a Problem with umlauts here (Zope 2.7.3 - now :), Silva 1.2).
>=20
> I have a SilvaDocument that has a special Character (=FC, applies also =
to
> =E9, most likely to others too) in the Title I gave it on creation, whi=
ch
> worked fine. I can publish and view the Document, but trying to use the=

> "Properties"-Tab gives me an Error:
>=20

  This smells much like issue 1270:http://issues.infrae.com/silva/issue12=
70

  A tentative fix is in the CVS version, but I do not think we have caugh=
t
all cases where the problem can occure. In my opinion its a Zope bug in t=
he
first place, but I am no very confortable with the i18n-stuff of Zope to
be sure about this ...

Cheers
clemens

[Silva-general] More intelligent Navigation

[Joachim B. <ma...@jo...>]

Hi,

while I'm at it:

Is there a way to make the navigation hide elements that the current
user may not see anyways?=20

And is there a way to hide certain entries from the navigation
alltogether? For example, the sitemap (Silva Auto TOC Object) in my
Silva Root needs no Navigational entry, as the link is put somewhere
else on the page.

Thanks,

Joachim

PS: For those interested, I'm working on a German high school's website,
http://www.schickhardt-gymnasium-herrenberg.de/
--=20
Joachim Breitner
  e-Mail: ma...@jo...
  Homepage: http://www.joachim-breitner.de
  ICQ#: 74513189
Bitte senden Sie mir keine Word- oder PowerPoint-Anh=E4nge.
Siehe http://www.fsf.org/philosophy/no-word-attachments.de.html

[Silva-general] Problems with Umlauts

[Joachim B. <ma...@jo...>]

Hi,

I got a Problem with umlauts here (Zope 2.7.3 - now :), Silva 1.2).

I have a SilvaDocument that has a special Character (=FC, applies also to
=E9, most likely to others too) in the Title I gave it on creation, which
worked fine. I can publish and view the Document, but trying to use the
"Properties"-Tab gives me an Error:

Time
2005/03/25 16:01:15.479 GMT+1
User Name (User Id)
root (root)
Request URL
http://www.schickhardt-gymnasium-herrenberg.de/silva/informationen/praktiku=
m/edit/tab_metadata
Exception Type
UnicodeEncodeError
Exception Value
'ascii' codec can't encode character
u'\xfc' in position 11: ordinal not
in range(128)

Traceback (innermost last):

      * Module ZPublisher.Publish, line 101, in publish
      * Module ZPublisher.mapply, line 88, in mapply
      * Module ZPublisher.Publish, line 39, in call_object
      * Module Shared.DC.Scripts.Bindings, line 306, in __call__
      * Module Shared.DC.Scripts.Bindings, line 343, in _bindAndExec
      * Module Products.FileSystemSite.FSPageTemplate, line 191, in
        _exec
      * Module Products.FileSystemSite.FSPageTemplate, line 124, in
        pt_render
      * Module Products.PageTemplates.PageTemplate, line 96, in
        pt_render
        <FSPageTemplate at /silva/service_views/Silva/edit/tab_metadata
        used
        for /silva/service_views/SilvaDocument/edit/VersionedContent/Docume=
nt>
      * Module TAL.TALInterpreter, line 190, in __call__
      * Module TAL.TALInterpreter, line 234, in interpret
      * Module TAL.TALInterpreter, line 407, in do_optTag_tal
      * Module TAL.TALInterpreter, line 389, in no_tag
      * Module TAL.TALInterpreter, line 234, in interpret
      * Module TAL.TALInterpreter, line 671, in do_useMacro
      * Module TAL.TALInterpreter, line 234, in interpret
      * Module TAL.TALInterpreter, line 694, in do_defineSlot
      * Module TAL.TALInterpreter, line 234, in interpret
      * Module TAL.TALInterpreter, line 409, in do_optTag_tal
      * Module TAL.TALInterpreter, line 394, in do_optTag
      * Module TAL.TALInterpreter, line 389, in no_tag
      * Module TAL.TALInterpreter, line 234, in interpret
      * Module TAL.TALInterpreter, line 637, in do_condition
      * Module TAL.TALInterpreter, line 234, in interpret
      * Module TAL.TALInterpreter, line 409, in do_optTag_tal
      * Module TAL.TALInterpreter, line 394, in do_optTag
      * Module TAL.TALInterpreter, line 389, in no_tag
      * Module TAL.TALInterpreter, line 234, in interpret
      * Module TAL.TALInterpreter, line 637, in do_condition
      * Module TAL.TALInterpreter, line 234, in interpret
      * Module TAL.TALInterpreter, line 409, in do_optTag_tal
      * Module TAL.TALInterpreter, line 394, in do_optTag
      * Module TAL.TALInterpreter, line 389, in no_tag
      * Module TAL.TALInterpreter, line 234, in interpret
      * Module TAL.TALInterpreter, line 671, in do_useMacro
      * Module TAL.TALInterpreter, line 234, in interpret
      * Module TAL.TALInterpreter, line 409, in do_optTag_tal
      * Module TAL.TALInterpreter, line 394, in do_optTag
      * Module TAL.TALInterpreter, line 389, in no_tag
      * Module TAL.TALInterpreter, line 234, in interpret
      * Module TAL.TALInterpreter, line 409, in do_optTag_tal
      * Module TAL.TALInterpreter, line 394, in do_optTag
      * Module TAL.TALInterpreter, line 389, in no_tag
      * Module TAL.TALInterpreter, line 234, in interpret
      * Module TAL.TALInterpreter, line 637, in do_condition
      * Module TAL.TALInterpreter, line 234, in interpret
      * Module TAL.TALInterpreter, line 409, in do_optTag_tal
      * Module TAL.TALInterpreter, line 394, in do_optTag
      * Module TAL.TALInterpreter, line 389, in no_tag
      * Module TAL.TALInterpreter, line 234, in interpret
      * Module TAL.TALInterpreter, line 637, in do_condition
      * Module TAL.TALInterpreter, line 234, in interpret
      * Module TAL.TALInterpreter, line 694, in do_defineSlot
      * Module TAL.TALInterpreter, line 234, in interpret
      * Module TAL.TALInterpreter, line 637, in do_condition
      * Module TAL.TALInterpreter, line 234, in interpret
      * Module TAL.TALInterpreter, line 549, in do_insertTranslation
      * Module TAL.TALInterpreter, line 214, in interpretWithStream
      * Module TAL.TALInterpreter, line 234, in interpret
      * Module TAL.TALInterpreter, line 520, in do_i18nVariable
UnicodeEncodeError: 'ascii' codec can't encode character u'\xfc' in
position 11: ordinal not in range(128)

What's wrong, and how can I fix it?

Thanks,

Joachim Breitner

--=20
Joachim Breitner
  e-Mail: ma...@jo...
  Homepage: http://www.joachim-breitner.de
  ICQ#: 74513189
Bitte senden Sie mir keine Word- oder PowerPoint-Anh=E4nge.
Siehe http://www.fsf.org/philosophy/no-word-attachments.de.html