Saravanan666/pypi-org huggingface dataset:
Package: silva.app.redirectlink
Introductionsilva.app.redirectlinkis an extension forSilva3.0 that lets
you use a new a content type, a redirect link, which does a permanent
HTTP redirect to its target.You shouldn’t add these redirect links to your site manually. They
are automatically created when you move or rename content in Silva.This lets you preserve old URLs to access moved or renamed contents,
telling the visitor to permanently update its reference to it. This
means search engines will update their search caches with the new
URL of your moved or renamed content. This prevents having content
disappear from search results when it was easily found before.When you think that visitors and search engines have updated their
references to the moved or renamed contents, you can delete those links
in order to definitively disable all old URLs.You can keep moving and renaming content items as many times you wish.
The redirect link will keep tracking the content each time it moves
using intids.For previous version ofSilva, look at previous version ofsilva.app.redirectlink.Code repositoryYou can find the code for this extension in Git:https://github.com/silvacms/silva.app.redirectlinkChangeLog3.0 (2013/05/23)Mark Silva Redirect Link as not addable in the installer. This
prevent to see it in the add menu.3.0c1 (2012/09/24)Update API to Silva 3.0c1.3.0b1 (2011/11/11)Update code for Zope 2.13 and Python 2.6.Rebuild SMI interface withsilva.ui.1.1 (2010/07/16)Compatibility fixes for Zope 2.12, Python 2.6 and Silva 2.31.0 (2010/02/01)Initial release.
Package: silva.app.shorturl
IntroductionThis extension provides native Short URLs inSilva. It allows users
to manage short hyperlinks to any Silva content item. It’s
particularly useful for Twitter postings.Instead of sending a URL such as:http://www.yoursite.com/department/news/articlename(51 characters)It’s much better to send a URL like:http://yoursite.com/$jUe8eg(27 characters)Additionally, Custom Short URLs can be created, for instance:http://yoursite.com/HappyNewYear(32 characters)These provide a memorable URL that’s better for communication since the
path contains meaning as opposed to gibberish. It’s especially effective
for usage in other mediums like email and print.When the extension is activated aShort URLsentry appears in Silva’s
Settings menu. The screen displays the Short URL for that item and
provides a form for creating Custom Short URLs.This feature can be combined with a short domain name to redirect a site
visitor to the destination content.Code repositorySource code can be found in Git:https://github.com/silvacms/silva.app.shorturlChanges3.0.2 (2013/10/09)Fix bugs when services got deleted by hand.3.0.1 (2013/05/24)Update API for name chooser to prevent to create custom short urls
with id of content.3.0 (2013/03/07)Initial release
Package: silva.app.sitemap
Introductionsilva.app.sitemapis an extension let you generate XML sitemaps
0.9 (seehttp://www.sitemaps.org/protocol.html) forSilva3.A viewsitemap.xmlwill be available on every folder of your site
in order to access the sitemap.A local service will permit you to configure which content you want to
see in the sitemap and configure exceptions.Code repositorySource code can be found in a Git repository at:https://github.com/silvacms/silva.app.sitemapChanges1.0 (2012/12/11)Initial release
Package: silva.app.subscriptions
Introductionsilva.core.subscriptionslet visitors subscribe toSilvacontent in order to receive notification emails on modification. You
can only subscribe to a part of the site or only to a page.Subscription registration can be done by visitors via a form rendered
inside the public layout. If the visitor is not authenticated, the
form is protected with a Captcha. The registration requires a
validation done by email.Site managers can directly administrate subscribed emails (add,
remove) without that validation step.A local service contains some generic settings and all email templates
used. You can be customized them at will.The service provides you with an API usable to develop extensions that
send notification for any wanted action or event using a custom email
template of your choice.Code repositoryYou can find the source code for this extension in Git:https://github.com/silvacms/silva.app.subscriptionsChanges3.0.3 (2013/12/16)Make possible to configure settings in SMI.Improve validation of the parameters in links given to the user.Update icons.3.0.2 (2013/05/24)Modify public form text and actions.3.0.1 (2013/03/05)Add a link in the SMI to the public form to subscribe or unsubscribe.3.0 (2012/12/11)Improve tests.3.0c1 (2012/09/25)Update API to Silva 3.0c1.Fix bugs, verify i18n.Improve tests.3.0b1 (2011/11/11)Update SMI interface to usesilva.ui.Store information in Zope annotations instead of default attributes
on the object.1.1 (2010/12/20)Change widget used for user subscribed list in SMI to a textarea.1.0 (2010/10/20)Initial after split out of Silva.
Package: silva.captcha
This is a captcha support for Silva. It works with the help ofskimpyGimpy.After installing the extension, you can either use azeam.formwidget, a Formulator widget or ask the captcha directly.You can get the captcha image in your template the following way:<tal:captcha tal:define="captcha nocall:here/@@captcha"
             tal:content="structure captcha/image_tag">
</tal:captcha>You can get the captcha as a sound file like this:<div class="captchaAudio"
     tal:define="captcha nocall:here/@@captcha">
   <a href="#" target="_blank"
      tal:attributes="href captcha/audio_url">Audio version</a>
</div>You can validate an captcha entry in Python like this:from zope.component import getMultiAdapter


captcha = getMultiAdapter((self.context, self.request), name='captcha')
if not captcha.verify(input):
    # Bad value
else:
    # Good valueThis extension require at leastSilva2.3 or higher. For previous
version of Silva, you can use previous versions of the extension.Use in Python ScriptIn your Python Script/Code Sources, you can use for example:from silva.captcha import validate

request = context.REQUEST
input = request.form.get('captcha_field', None)
if not validate(context, request, input):
    # Bad value
else:
    # Good valueThis will validate (or not) the input of the captcha.Code repositoryYou can find the code of this extension in Git:https://github.com/silvacms/silva.captcha.Changelog1.3.1 (2013/05/23)Update generatedimgto pass validation.1.3 (2010/10/18)Don’t rely anymore on collective.captcha: the implementation is now
done here. This fix compatibility with Zope 2.12. This
implementation rely on default Silva secret service, and don’t
require anymore any installation task. It requires at least Silva
2.3.Add a Captcha field and a Captcha widget for zeam.form.This extension is now grokked.1.2.1 (2009/11/18)Fix tests if GenericSetup is available in the product folder.1.2 (2009/08/17)Added Formulator field to easily add a captcha to Formulator forms.Fix installation in Silva 2.2.1.1 (2008/11/12)Add avalidatemethod for Python Scripts and Code sources.Don’t make Silva Root become a local site if it’s already the case
(i.e. Silva 2.2).1.0.1 (2008/06/04)Fix broken extension uninstall,Add simple test to test extension install/uninstall.1.0 (2008/05/27)Initial release.
Package: silva.core.cache
PresentationThis package provide a pluggable cache support for Silva related
components, base onBeaker.
By default content will be cached in memory, but you can use a different
storage like files, memcache or an SQL database to store cached content.For a single instance installation we recommand to use memory as
storage. For a ZEO / multi Zope instance installation we recommand to
use memcache as storage.To use memcache recommend to installpylibmc, this can be done via
buildout. Please refer to the installation documentation of Silva for
this.After you can configure in your Zope configuration
(zope.conf) which storage to use for which regions:<product-config silva.core.cache>

    # default region
    default.lock_dir /tmp/memcache
    default.type ext:memcached
    default.url localhost:11211

    # shared region
    shared.lock_dir /tmp/memcache
    shared.type ext:memcached
    shared.url someotherhost:11211

</product-config>APIDevelopers have different tools at their disposal, mainly:silva.core.cache.descriptors.cached_methodDecorator that can be used on a class method to cache its
computation. It can take aregionwhich specify which caching
region to use, akeywhich is a callable, taking as parameter
the class on which the method is called to compute a caching
key. Ifregionis not specified, all other parameters are Beaker
options used to configured the cache manager used.silva.core.cache.descriptors.cached_propertyDecorator that can be used on a class to create a read-only
property where its computation is cached in Beaker. Except forkeyit takes the same parameters thancached_method.silva.core.cache.store.StoreGiving a cache name, it give a dictionnary like access to this
cache.silva.core.cache.store.SessionStoreConstructed out of a request, it is a dictionnary like access to a
unique cache for this user session. The session is identified with
the help of the adapterIClientIdofzope.session. An
implementation of this adapter for Zope 2 is done in this package.silva.core.cache.interfaces.ICacheManagerA global utility provides this interface to give you access to all
cache managers used by this extension.silva.core.cache.memcacheutils.MemcacheSliceStore a list of items in memcache.Code repositoryThe code for this extension can be found in Git at:https://github.com/silvacms/silva.core.cacheChanges3.0.2 (2013/03/06)Session cookie now usesIVirtualSitenew top level path method
instead of root path, ensuring the cookie is set for the whole site.3.0.1 (2012/09/24)Session cookie use the HTTPOnly flag now.Update API to match Silva 3.0c1.3.0 (2011/11/08)Add a memcache slice to store a list of items in memcache. There is
a fallback available if you don’t have memcache.Improve cache descriptors.2.3.2 (2010/10/27)Ensure caching keys are always string. This is required by memcache
implementations.2.3.1 (2010/10/18)Fix cookie path for cookie session in case of virtual host hosting.2.3 (2010/10/06)Initial release.
Package: silva.core.contentlayout
silva.core.contentlayoutis a coreSilvaextension that let users
define content layout (called template or designs) in SMI or on the
filesystem, that can be used as model for pages built with the
extensionsilva.app.page.For more information on how to define you how templates, please refer
to theextension developer documentation.CreditsThanks toUCLfor the port of this extension to Silva 3.0.Code repositoryYou can find the code of this extension in Git:https://github.com/silvacms/silva.core.contentlayoutChangelog3.0.5 (2013/12/18)Make possible to edit settings in SMI3.0.4 (2013/10/08)Update tests to be ran inside a transaction to ensure the last
author is properly set.Update to use new icon API.Improve tests.3.0.3 (2013/08/26)Update tests.3.0.2 (2013/05/23)Fix compatilbility with jQuery 1.9.Fix various Silva XML improt and export issues when the models are
not exported with the content, missing or others settings differs.Prevent to select as design for a model the same model or a model
used by the current model, preventing loops.Improve slot block user interface.Improve tests.3.0.1 (2013/03/06)Fix compatiblity with JQuery 1.8. This is the minimum required
version now.Fix persistence of the block slot (for model). Modifications were not
saved.Update Silva XML import and export API.3.0 (2012/12/12)Improve tests.3.0c1 (2012/09/25)Initial release of the refactored extension for Silva 3.0.
Package: silva.core.editor
IntroductionSupport to edit rich text usingCKEditorwithinSilva3.Code repositoryYou can find the source for this extension in Git:https://github.com/silvacms/silva.core.editorChanges3.0.3 (2013/12/19)Make possible to configure the settings in SMI.Remove linktargetattribute if they are empty.Add support to determine the size of the text.Update interface used to lookup images, to support Silva Ghost Asset
as possible images.Improve tests.3.0.2 (2013/10/09)Extend text API: introduction can be truncated to a given of words
in addition to a number of letters. Support changing the level of
titles (like h1 are converted to h2 and so on).Add a CKEditor plugin to style tables.Improve selection of Silva block elements in CKEditor.Add support for various flavor of broken links, like invalid external URL.Add a per-tag HTML sanitizer for more control on the edition
process. An upgrade is required for it to work.3.0.1 (2013/05/24)Fix xml import and export to work with multiple block of text in the
same content.Update javascript for jQuery 1.9.Don’t include the Silva save plugin when the editor is created as a
form field.Fix CSS that prevent to resize CKEditor dialog.Ensure that link’s URL are never saved withjavascript:void()in
it.3.0 (2013/03/06)Addstriketo the list of default authorized tags,Add support for different resolution on images,Fix anchor in CKEditor (don’t set anhreftag on them),Fixzeam.formwidget cleanup,Update Silva XML import and export support.3.0c2 (2012/12/11)Add a menu and a button to remove an anchor.Only index anchor that do have a title.Bug fixes on IE and Webkit for Silva integration.3.0c1 (2012/09/24)Add support to retrieve text fulltext, and purge it (set it empty).Add support to sanetize HTML.Add support for multiple editor configuration (one per content
type), with built-in fallback.Add azeam.formwidget to edit HTML with the editor.Improve tests.Fix bugs.Update icons, default settings and CSS.3.0b1 (2011/11/11)Initial release.
Package: silva.core.interfaces
silva.core.interfacesdefines Zope interfaces to describe the
defaultSilvaAPIs, theirs contents and functionalities.Those interfaces are used to generate the Developer documentation as
well:http://docs.silvacms.org/latest.Code repositoryYou can find the code of this extension in Git:https://github.com/silvacms/silva.core.interfacesChangelog3.0.4 (2013/12/16)Add an interface for services editable in SMI.Update some of the ghost interfaces.Update some of the quota interfaces.Add a bundle error, composed of multiple sub-errors.3.0.3 (2013/10/08)Improve icon lookup API.Review API to set last author on contents.3.0.2 (2013/05/23)Add an APIIHTTPHeadersSettings.Add arepairmethod toIOrderManager.Fix some interface that were missing methods and attributes.3.0.1 (2013/03/06)Update Silva XML import/export API.RenamedIAssetDatatoIAssetPayload.Introduce an interfaceIReferablefor content that can be
referred to (include ZMI objects).3.0 (2012/12/11)AddISilvaNameChooserto support a pluggable identifier
management.ExtendIAuthorizationto give access to related email.3.0c1 (2012/09/24)More API has been update to match pep8 recommandation.Improve and add more Silva events.Improve and add more Silva exceptions.Add a new base,VersionedNonPublishable, for versioned content
that are not publishable.More API have been improved on images, titled object and security objects.3.0b1 (2011/11/08)Major API refactoring on Silva contents.Add generic exceptions.Improve events.2.3.1 (2010/12/20)Update interface documentation.Remove no longer used interfaces.Update interface inheritance tree to match content one.2.3 (2010-10-07)Subscription interfaces moved to silva.app.subscriptions.Authorization management API have been updated.Content interfaces have been updated and documentation improved.Events have been added for publication actions.2.3b1 (2010-10-15)Remove unused interfaces,Add missing interfaces for contents.2.2 (2010-03-31)Clean some interface that where includingself.2.2b1 (2010-01-22)Initial release after splitting from Silva core.
Package: silva.core.layout
Introductionsilva.core.layouthelps you to create and customize public layouts
forSilva. It’s the base system for new generation filesystem based
layouts.You can have more information on how to use this package in theSilva
developer documentation.Code repositoryYou can find the code in a Git repository at:https://github.com/silvacms/silva.core.layoutChangelog3.0.2 (2013/08/26)Fix an Acquisition bug in the metadata helper for layouts.3.0.1 (2013/03/06)Change doctype of the Porto layout to HTML 5. If you inherit from
this layout, and don’t change the main layout, you can override with
the doctype attribute from the class.3.0 (2012/12/11)Update Zope API calls.Fix a bug on error pages.3.0c1 (2012/09/24)Version are now rendered with a layout if directly called. You need
to have the permissionRead Silva contentto access them.Default Porto templates are now written withgrokcore.chameleon.Various Silva 3.0c1 API updates.Improve tests.3.0b1 (2011/11/08)The default page to render a content now does itself, without
delegating with the content object. This makes things much more
cleaner.request.modelis no longer
supported.request.resourcebaseas well.Use silva.fanstatic to include resources. Now use fanstatic
packaging for jquery and jqueryui.Now use the generic packagegrokcore.viewinstead ofinfrae.layout.Support for the legacy layout is no longer supported and have been
removed.2.3.2 (2010-02-07)Improve legacy stability, specially error pages on non-Silva content.
Add tests.Add a content provider to manage the favicon.2.3.1 (2010-12-20)Add alangattribute on the HTML tag of the Porto layout.Applysilva.core.layoutlayout on all Silva content.Update tests.2.3 (2010-10-07)SMI Maker interface moved tosilva.core.smi.A new content providerheadinsertto extends pages heads.Default Porto template have been improved.Add JQuery and JQueryUI resources. You can use them in your layout
by inheriting fromsilva.core.layout.jquery.interfaces.IJQueryResourcesorsilva.core.layout.jquery.interfaces.IJQueryUIResources.2.3b1 (2010-07-16)Replacez3c.formwithzeam.form.Improve default Porto layout.Add asilva.core.layoutlegacy layout to replace the one of
SilvaLayout, with support for overrides.Move some dependent code from SilvaLayout tosilva.core.layout:
traverser to set skin,IMetadataadapter, skin metadata set.Skin is now only set while traversing to the publish object. This
prevent to get it changed to something else while accessing other
that might have a different skin.SMILayer moved tosilva.core.smi.Update code to be compliant with Zope 2.12 and Python 2.6.2.2b1 (2010-01-25)Porto skin is now not registered by default but only usuable as base
skin for more complicated skins.Add support to render error pages in modern skins.Various bug fixes and improvement in the Porto skin:Set HTTP cache header by default.Improve navigation generation code.Use silva.core.interfaces and silva.translations.2.2a2 (2009-01-12)Improve Porto skin to be extended more easily.2.2a1 (2008-11-18)Initial release
Package: silva.core.messages
Library for flash messages (user feedback), similar toz3c.flashmessage.Code repositoryYou can find the code of this extension in Git:https://github.com/silvacms/silva.core.messagesChangelog2.3 (2010-10-07)Update to use theSessionStoreofsilva.core.cache.2.3b1 (2010-07-14)First release, see README.txt
Package: silva.core.references
Introductionsilva.core.referencesis a coreSilvaextension that defines
directed references between two Silva content: a source and
target. With the help of a central catalog, you have the possibility
to query the references in both direction: who is the target if I am
the source, and who is the source if I am the target.References are tagged with different names, and can be found by
searching on one of those names.Unless you use weak references, you can’t remove an content which is a
target of a reference, you will get an error. If you used a weak
reference, the source will be removed.This extension provides you with a set of fields and widgets that can
be used in forms (zeam.formand Formulator) in SMI.UsageThis extension is used to manage links and relations in Silva
Document, Silva Ghost and Silva Link for instance.Code repositoryThe code for this extension can be found in Git at:https://github.com/silvacms/silva.core.referencesChanges3.0.4 (2013/12/18)Display the list of broken references in SMI as well.Improve a little the performances.Fix the reference lookup widget that could display an invalid edit
link to the original content in complicated virtual host setup.Update icons.3.0.3 (2013/08/26)Fix bugs on service template.Fix scope of the CSS defined for the reference widget.3.0.2 (2013/05/24)Optimize path computation helpers.Update widget’s javascript to be compatible with jQuery 1.9.3.0.1 (2013/03/06)Add a widget forzeam.formand multiple references.Update Formulator to match new Silva XML import / export feature.IntroduceIReferableinterface that must implemented for all
content that can be the target of a reference. This fixes problems
where cleanup wasn’t called if the target wasn’t a Silva content.ReferenceSetobject have been improved performance wise.3.0 (2012/12/11)Small bug fixes when the widget is not used in the SMI.3.0c1 (2012/09/24)Add a new reference type,DeleteSourceReferenceValue, that
automatically delete the source of the reference of the target is
removed (so is the reference).Improve reference selection widget.Improve tests.Fix bugs (non-required values).3.0b1 (2011/11/10)Add a Formulator field for relations, that are used in Code Sources.Fix some Aquisition bug edge-case.Improve widget popup to work withsilva.ui, and have default SMI
feature (such as preview).2.3.3 (2010-02-07)Add a refresh functionality to the JS reference selection popup.Add the possibility to add new content from the JS reference selection
popup.Fix some bugs on content suppression (and add test for this case).Fix various small issues.2.3.2 (2010-12-20)Add a clear fonctionality to the JS reference selection popup.If nothing is selected in the JS reference popup, no link is generated
in the field. An edit link in the field have been added as well.2.3.1 (2010-10-18)Improve references graphs representation.Add aReferenceSet.Fix some bugs in case of duplication of broken references.2.3 (2010-07-16)First official release.
Package: silva.core.services
This package contains default Silva services definition (API) and
implementation of mandatory Silva services.You can have more information on how to use this package in theSilva
developer documentation.Code repositoryThe code for this extension can be found in Git:https://github.com/silvacms/silva.core.servicesChangelog3.0.1 (2013/10/08)Refactor the catalog optimization to use a more generic API to hook
itself in Zope. This API can be used by other optimizations,
reducing the cost of having multiple ones active at the same time.3.0 (2013/05/23)Fix a bug in the catalog optimitization.Fix incomplete interface declaration.3.0c1 (2012/09/24)Improve content walking tree utilities.Implement a content queue for cataloging content inside a
transaction (speed optimization).MoveUnicodeSplitter, used by the catalog from Silva.Update services APIs.Improve tests.3.0b1 (2011/11/08)Update catalog, version_status is renamed to publication_status.Support for automatic service installation when the root is added.Define more services API (Files …).Remove hacks for FilesystemSite.2.3.1 (2010/12/20)Update interface documentation.2.3 (2010/10/18)Interfaces for Members and Groups services have been added/moved here.A new default service is added: Silva Secret Service, that create a
secret out of some strings and validate it.2.3b1 (2010/07/16)Add an utilitywalk_silva_treeto go through all Silva content.Simplify catalog setup code with newsilva.core.confdefault
service factory.Removehaunted_pathindex which now useless.Update code to be compliant with Zope 2.12.2.2b1 (2010/01/25)Initial release.