First Featured Page can't be edited

make 3 pages with 3 different page images, assign each page to one favourite in the customizr menue, work with WP4 and with customizr 3.2.x. Be sure about ereasing all possible caches, (browser, server etc.)

The question that comes to mind is: Why would you want 3 FPs on the front-page that ALL point at the same Page?

@rdellconsulting Of course I wouldn’t have them pointing to the same page in the final product. I pointed them that way to eliminate one potential source of unknown. Had I pointed them to three different pages, then I’m sure the first response I would have gotten would be, “obviously, the first page is broken somehow.” But to address your objection, and that of @gomill, the same problem exists when pointing to three different pages.

I understand your logic, but you’ve added a risk of creating a different root cause by doing that!

Can we see a site link?

And set up a Child Theme, it’s the best way forward.

Did you try the Plugin Test yet? Deactivate all plugins
Test if OK
If OK, reactivate plugins one-by-one to find the culprit

@rdellconsulting The site is only on my localhost and I don’t have public hosting set up yet. How would a child theme help me with this? Would that allow me to define the three Featured Pages in a different way than through the customize panel?

No it wouldn’t but any other customisation will be safe when Czr is updated.

I added Plugin Test to #5 when you published #6 so that’s the next step

I’m happy to report that I’ve solved the problem. I switched to a different theme, deleted Customizr, reinstalled Customizr (same version), and reactivated. Then I was able to edit the first Featured Page. Thanks to everyone for suggestions!

Yay, that was Stage 2 after the Plugin Test.

Could you mark as [resolved] please

I’ve marked it as resolved, but it’s really only resolved in the sense that I managed to work around the problem. The fact that I could get into that state means the core issue is not really resolved; the problem is still there to bite the next poor fellow who stumbles upon it! I hope the developers will continue to hunt down the bug.