thetuningspoon

I'm using the in-context editing menubar plug-in, and to avoid confusing my clients, I'd like to be able to remove the little edit button that shows up in the corner of front-end pages by default. What's the best way to go about doing this?

unless they decide to quote some funny code that they have seen on a blog

Point taken

It seems like you should be able to accomplish this by restructuring your pages into something like this:

Home

Top Navigation

Bottom Navigation

404

Admin

Trash

And then looping through the children of each. I guess the problem with this is that you'd end up with ugly URLs like www.yoursite.com/top-navigation/page-1

Is there any way around that?

I have been thoroughly battle testing it on two projects recently and that eureka feeling still hasn't worn off yet. PW is just a dream to work with - especially for designers who like to write their own semantic HTML and not have a CMS generate for you (badly).

Happy to hear the love is more than surface deep! I'm extremely happy with it so far.

In case it helps anyone, you can set TinyMCE to accept ALL tags by entering *[*] in valid_elements

Setup > Fields > (field with TinyMCE on it, i.e. body field) > Input > Tiny MCE Advanced

Replace everything in the valid_elements field with *[*]

This is of course if you trust the editors of your website... which I don't see being a problem most of the time. My clients don't usually want to to sabotage their own websites

Welcome everfreecreative--Thanks for your great feedback.

Hey Ryan, thanks for the welcome. And thank you for all the work you've put and continue to put into this wonderful application!

I appreciate the enthusiasm and it is contagious--makes me want to work on PW all day.

Whatever I can do to help!

I would have to advise against Magento. I used it on a small ecommerce project and it was just a beast. Unnecessarily complex templating and a confusing back end. I had to upgrade my server to a VPS just to get it to run at all, and even then it was slow. 3/4 of the way into the project I made the decision to drop it and look for something else. I found OpenCart. Working with it was like a dream in comparison. So I'll throw my hat in for OpenCart.

Some of my more coding proficient friends have since told me that Magento is very inefficient under the hood. So, unfortunately, my experience with it is not unique.

Thanks for the welcome, guys. I'm pretty solid with the basics of php, so Processwire is good for me in that regard. I've never understood the point of having a separate templating language. It's not much easier for people who don't know php and it just makes it harder for those who do to understand how the app is working behind the scenes. I can't imagine it helps with site performance, either.

I'm going through the documentation and I just keep on thinking "yes! yes! YES!"

OH. MY. GOD.

Tell me I'm not dreaming!

I've been scouring the Internet for weeks looking for a CMS that would allow me to give my clients a decent user experience.

I've developed sites in Joomla, Drupal, Silverstripe, and Wordpress. Joomla was a nightmare of epic proportions. The admin interface is confusing and inconsistent. Drupal had promise in theory, but trying to customize it just caused it to bug out. Silverstripe is nice, but the admin panel is slow and clunky. Wordpress is great for blogs, but feels like you're hacking it if you're trying to use it for more than that.

After my frustrations with the big name CMSs, I decided to try and get a better lay of the land and see what else was out there. Every one of them was either lacking a crucial feature, poor on the usability front, or a buggy mess.

I have some programming knowledge, but mainly I am a designer looking for a CMS that lets me design the client's experience in the same way that I'm able to design the end user's experience. I don't need templates or templating languages. I want something that lets me be the designer and then gives my clients the power to work with what I've developed.

As someone deeply concerned about user experience, I don't understand it. How could so many developers get this so wrong? Were they just throwing these things together without thinking about the use cases? The need for flexibility? What people actually NEED in a CMS? I was beginning to think I'd have to become a PHP developer and build something from scratch.

So far, what I see in ProcessWire is almost exactly the ideal CMS I have been piecing together in my mind's eye. The consistency in the mental design model, the absolutely crucial ability to create your own page types and custom fields for your clients which is utterly lacking or nonexistant in nearly every major CMS, the ability for logged in users to easily update a page they're on by simply hitting an "edit" link from the front end...

Elegant, logical, and flexible. It's obvious that you've put a lot of thought into this. Thank you.

I can't wait to get started.