There is a hidden parameter which you can use to start a Plone instance, so that every less or javascript file gets recompiled any time you reload the browser.

Just start your instance as follow:

$ FEDEV=true ./bin/instance fg

First of all we need to recover the ZODB with fsrecover.py script which comes with ZODB.

./bin/zopepy ../buildout-cache/eggs/ZODB3-3.10.5-py2.7-linux-x86_64.egg/ZODB/fsrecover.py -P 0 var/filestorage/broken-Data.fs var/filestorage/Data.fs

Then we need to analyze the ZODB to get a list of known PosKeyErrors. To do this we use fsrefs.py script which comes with ZODB.

./bin/zopepy ../buildout-cache/eggs/ZODB3-3.10.5-py2.7-linux-x86_64.egg/ZODB/scripts/fsrefs.py -v var/filestorage/Data.fs > fsrefs-output.txt

Then we run the following script as follows to fix the broken references with fake objects. After that, we should have a working database and can see what data is still alive and can be saved.

./bin/instance run fix-broken-references.py

import re
import os
import transaction as zt
from ZODB.utils import p64
from persistent import Persistent


refs_file = open('fsrefs-output.txt', 'r')
oids = []
for line in refs_file:
    rematch = re.search(r'oid\s+(?P<oid>[\w\W]+?) .*', line)
    if not rematch:
        continue
    oids.append(rematch.group('oid'))

i = 0
for oid in set(oids):
    zt.begin()
    i += 1
    print("create fake obj [%s] for: %s" % (i, str(oid)))
    a = Persistent()
    try:
        oid_int = int(oid, 16)
    except ValueError:
        print("ValueEror on %s, skip!" % oid)
        zt.abort()
        continue
    a._p_oid = p64(oid_int)
    a._p_jar = app._p_jar
    app._p_jar._register(a)
    app._p_jar._added[a._p_oid] = a
    zt.commit()
print("finished!")

Usually you would do something like this, in your upgrade step:

def upgrade_to_1_1(context):
    loadMigrationProfile(
        context,
        'profile-my.example:default'
    )

But if you only need to reload the rolemap config, you can also do:

def to_1200(context):
    loadMigrationProfile(
        context,
        'profile-my.example:default',
        ['rolemap']
    )

First we define two indexers, a dummy indexer and the more specific real indexer for our index we want:

from plone.indexer import indexer


@indexer(IDexterityContent)
def dummy_index(obj):
    """ dummy to prevent indexing child objects
    """
    raise AttributeError("This field should not indexed here!")


@indexer(ILibrary)
def my_parent_index(obj):
    """
    :return: value of field my_parent_field
    """
    return obj.my_parent_field

For these indexers we register two adapters:

<configure
    xmlns="http://namespaces.zope.org/zope">

    <adapter factory=".library.dummy_index" name="my_parent_field" />
    <adapter factory=".library.my_parent_index" name="my_parent_field" />

</configure>

Both adapters have the same name. The catalog now lookup for these adapters and will use the more specific adapter for the current object. So for the parent object with the interface ILibrary it will be the second and it will result the index value. But for a child object the catalog will get the adapter which calls the dummy_index index and this will raise an AttributeError and the catalog will ignore that.

Im einfachen Fall, dass man den Pfad festlegen kann, funktioniert auch folgende Konfiguration des ObjPathSourceBinder:

related_obj = RelationChoice(
    title=_(u"Referenziertes Objekt"),
    source=ObjPathSourceBinder(
        portal_type="MyRelatedObjType",
        navigation_tree_query=dict(
            portal_type=["MyRelatedObjType",],
            path={ "query": '/ub/ub-db' })
    ),
    required=False,
)

Will man aber den Pfad zur Laufzeit ermitteln, dann kann man nicht wie oben beschrieben vorgehen. Wir bauen uns deshalb einen angepassten ObjPathSourceBinder welcher

 from Acquisition import aq_parent, aq_inner
 from plone.formwidget.contenttree import ObjPathSourceBinder
 from plone.formwidget.contenttree.utils import closest_content
 from zope.interface import implementer
 from zope.schema.interfaces import IVocabularyFactory


 def get_librarydb(context):
     """Get the most local 'Library Database'."""
     parent = context
     if not parent:
         return None
     while parent.portal_type != 'LibraryDB':
         parent = aq_parent(aq_inner(parent))
         if getattr(parent, 'portal_type', None) is None:
             return None
     return parent


@implementer(IVocabularyFactory)
class RelatedObjPathSourceBinder(ObjPathSourceBinder):
    """Provide available related objects."""

    def __call__(self, context):
        if 'path' not in self.navigation_tree_query:
            db = get_librarydb(context)
            if db:
                path = '/'.join(db.getPhysicalPath())
                self.navigation_tree_query["path"] = {"query": path}
        return self.path_source(
            closest_content(context),
            selectable_filter=self.selectable_filter,
            navigation_tree_query=self.navigation_tree_query)

RelatedObjPathSourceBinderFactory = RelatedObjPathSourceBinder()

Der neue RelatedObjPathSourceBinder kann wie folgt verwendet werden.

related_obj = RelationChoice(
    title=_(u"Referenziertes Objekt"),
    source=RelatedObjPathSourceBinder(
        portal_type="MyRelatedObjType",
        navigation_tree_query=dict(
            portal_type=["MyRelatedObjType",])
    ),
    required=False,
)

Unter anderem bringt die neue Version folgende Vorteile:

• die neuen Kollektionen enthalten Korrekturen und können nun auch beim Orts-Kriterium die Tiefe berücksichtigen
• plone.portlet.static geht nun besser mit relativen URL's um
• viele JavaScript Bibliotheken wurden aktualisiert um mit jQuery 1.7 bis 1.9 kompatibel zu sein
• verbessertes caching der Bildskalierungen in plone.app.imaging

Es gibt viele Änderungen mehr, nicht alle sind für den Endnutzer sichtbar, bringen aber Verbesserungen für Entwickler mit sich und erhöhen die Stabilität. Ein Update auf die Aktuelle Version sollte von Plone 4.3.x ohne großen Aufwand möglich sein und wird klar empfohlen.

Die vollständigen release notes finden Sie hier: https://plone.org/products/plone/releases/4.3.4

Unter Debian Linux sind folgende Bibliotheken zu installieren

• poppler-utils
• libxslt1-dev
• libxml2-dev
• wv
• xsltproc
• unzip