PyroCMS v0.9.7.4 - an open-source modular general purpose CMS

[eluser]Phil Sturgeon[/eluser]
[quote author="Rick Jolly" date="1258587683"]Great work on the new interface![/quote]

Props to Colin Williams on the design, we all know I suck at graphics. He has done an amazing job so far and is working on not just the GUI but the pyrocms.com design AND the default theme for PyroCMS. The project would be pretty screwed without him now we have slightly nicer looking competition.

[quote author="hugle" date="1258605366"]About features... maybe it would be good to generate sitemaps for Google
SO it would ping Google after something is inserted/updated/deleted to/from database,
or maybe posibility do it manually by clicking some link in specific section[/quote]

I dont think "pinging" Google would work so well, but I have been fleshing out some ideas for a modular sitemap system for quote a while. Each module could (optionally) have its own sitemap controller which would build a index for that module alone. Then that would be picked up by a main sitemapindex controller, and pull them together. This should be in v1.0 or shortly after.

[eluser]wiredesignz[/eluser]
The new admin interface looks very cool, good work Colin.

[eluser]Phil Sturgeon[/eluser]
Here is a recent talking point for v0.9.8 which I posted on our internal collaboration board. This will require users with custom themes and custom modules to make some changes, but in the long run it enables us to do a LOT of cool new things.

I will put together a set of "find & replace" rules and general upgrade instructions on a article/wiki page somewhere for people this effects.

I realised that there were too many words knocking around that didn't quite cover what they were meant to, so I am in the process of re-naming stuff to make v0.9.8 a neater, more logical build for theme developers.

Templates

I have renamed the Layout library to Template. That library was an archaic mess anyway, with things tacked on over 3 years, so its time I had a serious recode.

Template suggests more of a wireframe, and should incorporate everything. A template is the entire built page and contains the logic to pull themes and layouts together.

Themes

These can stay as they are. I considered renaming to skins, but... effort!

Wrapper

Killed! This was the method name that handled old layouts, $this->layout->wrapper('admin/layout'); = ridiculous. It is now: $this->template->layout('admin/layout');

Layout

The word layout has been freed up by renaming the Layout library to Template, but I am still not sure about what it should mean.

We clearly need layouts, but what level should they be. We cannot have a generic database of layouts as at the moment a layout (default.php or default-wide.php) contains the header, content and footer, meaning lots of theme specific stuff is in there.

Perhaps we can split this into 2 different things.

A) Page layouts

A database GUI for essentially wrapping a page. This would mean we can have a dropdown instead of the text-box on the pages "Advanced" tab, and it would be independant of the general layout. It would let pages have grouped layouts, section navigation bars, etc. We could even add a helper to load in navigation groups, so the navigation bars were dynamic via Navigation module.

B) Module layouts

Perhaps we could have a way for modules to specify their own layouts, so the main layouts have no sidebar at all. A module could contain any number of layouts, and just like view files at the moment these can be over-written in the theme.

This is all confusing stuff, but I think having two kinds of layout would make life easier. It means users can just add pages and faf around with a 5 page site, or they can add a bigger sub-set of pages and control a 100+ page site without them all looking identical. It also means the entire site wont have the EXACT same sidebar, etc on all pages.

Anyway guys, let me know what you think!

That goes just as much for you guys, the community, who have helped this project a huge amount so far.

[eluser]Colin Williams[/eluser]
Haven't been following this thread. Thanks for the compliments on the interface, guys.

[eluser]bdegier[/eluser]
How do I make some pages and navigation options for logged in users only?

[eluser]Phil Sturgeon[/eluser]
This is not yet a feature. I have been trying to think up the best implementation for this, without making the user interface too complicated or having to entirely re-develop how permissions work.

Any suggestions?

[eluser]bdegier[/eluser]
I'm a complete idiot, so not exactly

Best way for providing this to users is to include a few lines of code on the top of their documents which checks the permissions.

Can't you add something like permission level 0, which means logged out. Level 1 means Users, level 2 admin etc?

Just a thought, i'm a noob.

[eluser]bdegier[/eluser]
Another question (I keep em coming ):
I've written a basic shoppingcart using the CI shoppingcart library which i'd like to integrate into my PyroCMS install.

What is the "right" (best/easiest) way of doing this? I used a clean CI install when writing this a while back using 1 controller and a couple of views.

This is related to my above question because i want this to be only accessible for logged in users.

Thanks,

Bento

[eluser]Phil Sturgeon[/eluser]
Make a new module called shop and put all your controllers, models and views in there. To make sure users are logged in, use $this->user_lib->logged_in().

[eluser]bdegier[/eluser]
I see an XML file in the existing modules. Do i need to make one?
I'll take it there aren't any docs on this yet (even in beta stages? ).