Updated Mosaic to 2.2.1... installed on existing site, now can't edit pages

Hi @espenmn thanks again for your tips!
I've got recaptcha working now, and installed easyform, all good.
I also updated Mosaic in the buildout.
Unfortunately, I then installed Mosaic on the site, which had not been there before!
(the button just took advantage of me, somehow I thought I was updating Mosaic, rather than installing it)
Now I can't edit my existing pages. I get a generic "properties" edit, but no content field (no TinyMCE, in specifc) .
Just wondering where to poke it so I can edit pages again?
Thx.

############################################
#
# Buildout Configuration File for Plone
# -------------------------------------
#
# ALWAYS back up all Plone/Zope data and components
# before changing configuration.
#
# Running "bin/buildout" will update your installation,
# installing missing components as necessary.
#
# This will update the add-on products you've added in the eggs= lines.
# This will not, however, upgrade Plone itself (or anything else you've
# pinned with a version specification). To upgrade Plone itself, see the
# comments in "Plone Component Versions".
#
# Tutorial instructions for using zc.buildout for
# configuration management are available at:
# http://plone.org/documentation/tutorial/buildout
# Full details at http://pypi.python.org/pypi/zc.buildout
#
############################################

[buildout]
############################################
# Plone Component Versions
# ------------------------
# This version of the Unified Installer has the components of Plone 5
# preloaded so that it can install without an Internet connection.
# If you want to update, uncomment the "http://..." line below,
# edit it to point to the current version URL, comment out the
# "versions.cfg" line and run "bin/buildout" while attached to the
# Internet. Generally, you only want to do that as part of a planned migration.
# Note that if you are updating components, you should also check the versions
# section at the end of this file, since recipes or components other than
# those of Zope and Plone may need updating at the same time.
#
extends =
    base.cfg
#    versions.cfg
    http://dist.plone.org/release/5.1-latest/versions.cfg
    https://raw.githubusercontent.com/plone/plone.app.mosaic/master/versions.cfg
# If you change your Plone version, you'll also need to update
# the repository link below.
find-links +=
    http://dist.plone.org/release/5.1-latest/
    
index =https://pypi.python.org/simple/

# If you try to start Zope as root, it will change user id to run as
# the effective user specified here. This user id must own the var directory
# of your buildout.
effective-user = plone_daemon
# This user will own the rest of the installation, and should be used to
# run buildout.
buildout-user = plone_buildout
# A flag to tell the Unified Installer whether or not to document sudo use.
need-sudo = yes

############################################
# Eggs
# ----
# Add an indented line to the eggs section for any Python
# eggs or packages you wish to include in your Plone instance.
#
# Note that versions may be specified here or in the [versions]
# section below. You should always specify versions that you know
# are compatible with the Plone release and at an acceptable
# development level.
#
# If you update to a later version of Plone, remove the hotfix.
#
eggs =
    Plone
    Pillow
    Products.RedirectionTool
#    Products.PloneFormGen
    collective.easyform [recaptcha]
    plone.app.mosaic
    plone.app.imagecropping

    collective.recaptcha
    collective.recaptchacontactform

    plone.formwidget.recaptcha
#    collective.plonetruegallery
#    collective.ptg.unitegallery
#    collective.ptg.carousel
#    collective.ptg.highslide
#    collective.ptg.contactsheet
#    collective.ptg.presentation
#    collective.ptg.fancybox
#    collective.ptg.supersized    

#    plonetheme.booster
#    plonetheme.business_casual

############################################
# ZCML Slugs
# ----------
# Some eggs need ZCML slugs to tell Zope to
# use them. This is increasingly rare.
zcml =
    collective.recaptcha

############################################
# Development Eggs
# ----------------
# You can use paster to create "development eggs" to
# develop new products/themes. Put these in the src/
# directory.
# You will also need to add the egg names in the
# eggs section above, and may also need to add them
# to the zcml section.
#
# Provide the *paths* to the eggs you are developing here:
develop =
#    src/my.package

############################################
# var Directory
# -------------
# Sets the target directory for the "var" components of the install such as
# database and log files.
#
var-dir=${buildout:directory}/var

############################################
# Backup Directory
# ----------------
# Sets the target directory for the bin/backup and bin/snapshotbackup
# commands. Default is inside this project's var directory, but ideally
# this should be on a separate volume or backup server.
#
backups-dir=${buildout:var-dir}

############################################
# Initial User
# ------------
# This is the user id and password that will be used to create the initial
# user id that will allow you to log in and create a Plone site. This only
# sets the initial password; it will not allow you to change an already
# existing password. If you change the admin password via the web interface,
# the one below will no longer be valid.
# If you find yourself locked out of your Zope/Python installation, you may
# add an emergency user via "bin/plonectl adduser".
user=admin:12349876

############################################
# Debug Options
# -------------
# Start Zope/Plone instances in "fg" mode to turn on debug mode;
# this will dramatically slow Plone.
#
# Add-on developers should turn deprecation warnings on
deprecation-warnings = off
# change verbose-security to "on" for useful security errors while developing
verbose-security = off

############################################
# Parts Specification
#--------------------
# Specifies the components that should be included in the buildout.
# Most are defined in the base.cfg extension; you may add your
# own if you need them at the end of this file.
parts =
    zeoserver
    client1
    backup
    zopepy
    unifiedinstaller
    precompiler
    setpermissions

############################################
# Major Parts
# ----------------------
# These common parts make use of sane base settings from
# base.cfg. To customize a part, just add whatever options
# you need. Read base.cfg for common settings.

[zeoserver]
<= zeoserver_base
recipe = plone.recipe.zeoserver
zeo-address = 127.0.0.1:8100

[client1]
<= client_base
recipe = plone.recipe.zope2instance
zeo-address = ${zeoserver:zeo-address}
http-address = 8080

############################################
# Versions Specification
# ----------------------
# Version information supplied here will "pin" Python packages to a particular
# version number, even when you use the "newest" flag running buildout.
# Specifying versions for all packages is a good idea and can prevent
# accidental changes when you add new packages to your buildout.
# Note that versions specified here will override those specified earlier
# in the configuration, including those from the Plone and Zope version
# config files.
#
[versions]
# Use the setuptools and zc.buildout versions that are
# available in our Python environment.
setuptools =
zc.buildout =


# prevents zope startup crash
plone.protect = 3.1.2

##
#collective.recaptcha = 2.1.0
plone.formwidget.recaptcha = 2.2.0

Products.DocFinderTab = 1.0.5
bobtemplates.plone = 1.0.3
buildout.sanitycheck = 1.0.2
collective.checkdocs = 0.2
collective.recipe.backup = 3.0.0
mr.bob = 0.1.2
pkginfo = 1.3.2
plone.recipe.unifiedinstaller = 4.3.2
requests-toolbelt = 0.6.2
twine = 1.7.2
zest.pocompile = 1.4
zest.releaser = 6.6.4

# Required by:
# Jinja2==2.8
MarkupSafe = 0.23

# Required by:
# clint==0.5.1
args = 0.1.0

# Required by:
# twine==1.7.2
clint = 0.5.1

# Required by:
# zest.releaser==6.6.4
colorama = 0.3.7

It sounds like you might have a javascript error.
If so, you might see it other places (for example when you click 'add content' you can not click on the content type, but you are taken to another page where you can choose which content type to add.

You can try to go to http://yoursite/@@resourceregistry-controlpanel

and enable debug mode.

If it still does not help; Try removing most of you add ons (except Mosaic and see if that helps).

If it still does not help: Try adding another plone site in the same instance and see if that works

Well, I've just copied the text from the un-editable page, and rebuilt it as a Mosaic page.
Trivial in my case, but for a larger site it is a worrisome thing to install a product (Mosaic) which then renders existing pages uneditable, and seems to be irreversible.

More specifically—
When I added Mosaic (actually by accident, I thought I was updating the install, but in fact it had not been used on this site previously), the existing "page" layout would display the page, but regardless of the display setting, when I tried to edit the page — a standard Plone Page, apparently it tries to load it as a Mosaic page, and no content editor is loaded, only the properties tabs.

Attempting to display as Mosaic, the page title shows, but none of the existing content.
Editing shows only the Title and Summary tiles.

It seems that the data is there on the original page, of course, but once Mosaic code is in the render path, the content can't be edited...

Thanks, as always for your thoughts. I don't have an urgent need for a fix at this point, a lesson learned, that if you want to use Mosaic, be sure to start out with Mosaic!

Best
PF

That's odd that the edit screen was immediately taken over by mosaic for your types.

Normally there is an additional step, you have to choose "Display -> Mosaic Layout" before the editor kicks in.

If you want to 'unmosaic' a piece of content and go back to regular plone behavior, choosing "Display->view" should do the trick.

This is intended behavior in Mosaic when it is installed and activated for a content type, as the 'main text' field of your content type is the main content and will be replaced by the mosaic layout. In the mosaic editor there's a properties button which will open up the original 'edit' view in a modal, but with the text and version notes disabled.

See:

and:

Sorry, perhaps I'm not explaining fully.
When I go back to Display --> View Document, I do see the original content. However, I still can't edit it, which is what I'm complaining about.
When I choose 'edit' only the header fields show up.
The original edit view has the TinyMCE content pane, which is now missing.

Thanks!

Hi Fred, Thanks very much, I'll have a look at this.

Plone Foundation Code of Conduct