This release is a pre-release and may not be stable for production use.
QUICK INSTALL
- Setup requirements for remember and membrane
e.g. latest Five @ http://codespeak.net/z3/five/release/Five-1.4.2.tgz
Add remember and membrane products to your zope Products folder
Add sampleremember
QUICK STEPS TO MAKING YOUR OWN PRODUCT BASED ON sampleremember
Search and replace all “sampleremember” to “name-of-your-product” (CASE is important)
Search and replace all “SampleRemember” to “NameOfYourProduct” (CASE is important)
Rename files that are named sampleremember or SampleRemember [list which ones]
MORE INFO:
- See “docs/tutorial” for Tutorial documentation. THIS TUTORIAL IS A BIT DATED and may not include
all the steps needed. The ‘sampleremember’ code is the most up-to-date.
See “examples/sampleremember” for the sample remember product.
See “examples/sampleremember/TODO.txt” for suggested list of items that need work.
HISTORIC
3/9/07 Tutorial originally created by:
Andrew Burkhalter <andrewb@onenw.org> Brian Gershon <briang@ragingweb.com>
HISTORIC ISSUE (only relates to code based on SampleRemember version 1.0)
If you based your code on an earlier version of SampleRemember (v 1.0) you may have an incorrectly registered GenericSetup “Import Step” that is stuck in your site, which might be preventing other GenericSetup profiles from running.
I posted a How-To on plone.org called “GenericSetup: Uninstalling Import Steps” (which also details doing this manually in Clouseau), but if you’re anxious:
- NOTE: The bad step may be called “remember-useraddr” or
“sampleremember-defaultmember” or it may be called “YourProductNameHere-default”. The correct one is “remember-useradder”, so don’t delete that one.
Instructions for removing this step are to create an External Method that calls the following code:
from Products.GenericSetup import profile_registry, EXTENSION
from Products.CMFPlone.interfaces import IPloneSiteRoot
from Products.CMFCore.utils import getToolByName
setup = getToolByName(self, 'portal_setup')
setup.setImportContext('profile-myproduct:default')
ir = setup.getImportStepRegistry()
#print ir.listSteps() # for debugging and seeing what steps are available
# delete the offending step
try:
del ir._registered['myproduct-badstep']
except KeyError:
pass
# commit the changes to the zodb
import transaction
txn = transaction.get()
txn.commit()
Changelog
[Mar 23 2009] Fix git based release problem, now using setuptools-git (hannosch)
[Mar 20 2009] Fix bug where SampleMember wasn’t allowed in MemberDataContainer
[Jul 30 2007] portal_type changed. The version in sampleremember.py now matches same case as GenericSetup’s archetype_tool.xml
Metadata
Release files for Products.sampleremember 1.1b2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| Products.sampleremember-1.1b2.tar.gz | 10.5 kB | Without provenance | Details |
Release files / Products.sampleremember-1.1b2.tar.gz
| Download URL | Products.sampleremember-1.1b2.tar.gz |
|---|---|
| Size | 10.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d7191e4a2c99c99d135aeb8eeecfc49f678cba264f8480294ab82b25f695cfe8
|
|
BLAKE2b-256 checksum How to use checksums |
dabf683422d55048b4046c3e00e543060ee86004459f5ec01cf7d0081bd6a1c0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for Products.sampleremember 1.1b2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.