Thread

I need content pages like About, Biography, Terms of Service - how do you do this?

I created a Pages channel and added headline and text fields, but these pages must not be ‘publishable’.
The CMS user must be presented with a fixed set of pages, of course, and no way to add new pages to it.

Pretty simple task - but finding answers or how-to’s for even the simplest questions seems to be in vain more often than not.
Really frustrating.

Thanks for your time.

Also, while we’re at it: 😉

Is there any documentation about “the thumbs directory” thing?

Why do I have to pay $30-60 for basic navigation features?
Or internationalization? :long:

Michael Boyink is a genius at doing everything in ee without add-ons, so check out http://www.train-ee.com/  Good luck!

Giraffentoast,

To restrict users ability to additional content to a channel you’ll want to check out Zoo Flexible Admin - this will allow you to set up a navigation menu in the CP for your content adminstrators user group.

I second the recommendation that you look at Mike Boyink’s training materials on train-ee.com - that’s where i got started and it was invaluable.  In particular, have a look at the “building a small business site” tutorial.  It goes through every step of an example site build - he’s updated the book to EE2, but perhaps not the online version - but all you have to do is think “channel” wherever you see the word “weblog” and the rest is basically the same.

There’s a lot of different ways to handle navigation in EE - on the upside it allows you to custom-craft an experience you think best matches your client’s way of thinking (and yours) - the downside is actually the same - you have a lot of different options, so you may have to experiment a little before you settle on an approach you and your client likes the best.  Don’t feel you have to resort to add-ons - they’re a convenience to be sure, but many native options are also worth looking at.

Best of luck!

Thanks, guys. Unfortunately, even Train-ee doesnt seem to list a way to get this done.

About, Home, Terms of Service pages that only consist of TITLE and BODY are no biggie, right.
But I dont want the later admins to be able to delete those pages or add new ones, of course.

If EE member group management didnt read

Can post and edit entries in:  Pages

but let people enable and disable editing/posting seperately, then yeah, you’d just enable editing pages and disable publishing…

Any ideas?

In a round about way, you can prevent them from deleting - but it depends on your administrator model.  Within the member group settings, you have controls for “can delete own entries” and “Can delete channel entries authored by others” so you can prevent them from deleting if it was authored by someone else (you, a master administrator, etc).  SO as long as they have their own login account, you can at least prevent deletion.  Unfortunately posting and editing are tied together in EE, so you can’t deny one without denying the other, except in the case of editing entries authored by someone else, which you can block separately (i.e. then they could only edit their own).

Thats a pity. Truth is, I’m still trying to sell EE to our client here, because I think it’s really got potential. But I’m coming across an increasing number of fundamental weak points that I didnt expect a commercial product to have.

So yeah, if any suggestions come up (or any info on the thumbs directory thing…) please leave a post. I’ll check back every now and then.

Thanks again.

What’s your question about the thumbs directory? It’s just an automatic thing when you upload an image via the file field so that when you go back to edit the entry, EE can show you a tiny little preview of the image inline with the file field.

What’s your question about the thumbs directory? It’s just an automatic thing when you upload an image via the file field so that when you go back to edit the entry, EE can show you a tiny little preview of the image inline with the file field.

The thumbnails are created for the backend only?
No tags to make use of them in the frontend?

So if you want to actually use thumbnails you end up with two thumbnail folders (_thumbs and _thumbnails) in each upload directory?
With potentially identical thumbnails in them?

That’s right - they’re just an automatic thing for use on the back end - i suspect you COULD use them somehow, but it wouldn’t be typical.  Normally you’d want some control over that - which is what the image manipulation setting are - then you can setup your own preferences for automatic on-load sizing - scale or contain, set a width and height, watermark them, etc. And that’s not limited to thumbs - it could be virtually any size, within reason.  Not as many options for on-upload resizing as there are in a full-features front-end resizing add-on like CE Image, but it’s decent enough.