Stefane,
Logging out and back in should fix your access rights, but Eventframe is no longer maintained (apart from occasional bugfixes to keep our own sites running).
I ran into a few problems with the architecture that necessitated a rewrite:
1. I assumed one level of folder hierarchy would be sufficient (so we have event sites at /2014, /2015, etc), but we've frequently wished for having nested folders for sub-sites. This required a new database pattern.
2. Eventframe was written in a hurry in basically a two week sprint in 2012. It never had tests or database migrations and after a while #1 seemed a bigger thing to fix than adding tests.
I've written a new framework called
Nodular that supports hierarchical paths and can load sub-paths in a single database request instead of doing recursive calls. The goal was 100% test coverage from the beginning (it's currently at 96%). However, I haven't gotten around to rewriting Eventframe atop Nodular because of #3 and #4.
3. One of Eventframe's goals was to let websites be updated by non-technical users via a web interface. HTML and CSS is too involved to be done over simple web forms, so Eventframe uses site "themes" -- reusable skins -- that control layout and appearance but have no content.
In practice, event websites are mostly marketing brochures and the design and content teams have to work closely together, and event website designs are almost always updated for newer events. We have never re-used a skin as is.
We use Git for version control of HTML/CSS, and Eventframe provides database-backed versioning for text content, but working across two version control systems is hard, so our crew has tended to hardcode content into the templates and manage all of it in Git. Eventframe more or less serves static templates in production for us.
4. Finally, our main goal with web-managed content was to turn it over to users, making fully interactive websites. This proved to be a bad business decision. Users have definitively moved away from brand-driven experiences to app-driven experiences. We've decided to stop investing in brand experiences and focus on activity-driven apps -- the funnel app, which is now an independent website at Talkfunnel.com.
I'm therefore not putting any more effort into Eventframe.
However, I'd love it if you want to pick up Nodular and build with it. I'm building a little asset management app with it in my spare time (named
Packman).
Best,
Kiran