Joss

Something I regularly add is this to Additional Settings: paste_text_sticky: true paste_text_sticky_default:true This automatically removes formatting from anything pasted into the editor - this can save a lot of mess! And if you want to turn the context menu on, add contextmenu to the plugins field.

You can customise TinyMCE exactly the way you would normally, just using the field configuration. Go to the field (body, for instance) go to the Input tab and click on TinyMCE advanced configuration In the valid elements add -sub,-sup, to the end of the list (probably after pre so it ends code,pre,-sub,-sup,) In the theme_advanced_buttons_1 field, add ,sub,sup somewhere. And that should do it. Check on the TinyMCE wiki for other stuff you can add.

Try using a more defined selector. $news = $pages->find("template=news-item, limit=5, sort=-date, parent=/newsparentpage/"); You might not even need the parent if the template is enough.

http://www.bbc.co.uk/news/technology-21697704 Looks like you are much safer sticking to using a nice little Cray then.

Oh I got a couple of things up there already. (and I used to have a ton of things on Source Forge about 12 years ago - and on Fresh Meat) Though this one was a hassell. The first version Uploaded fine, then I went to update it and it complained about a Detached Head and then a bunch of other errors .... So, tried again. But I did add categories in the gap between the two!

I look at it like a line of obedient hounds following a trail of tasty morsels. When they get to where you are currently standing, they all sit there looking at you with big, expectant, eyes, waiting for you to drop something.

He means footy.

A short tutorial/help package aimed at new users (Note, a more step by step version of this tutorial is now available on the Wiki as a follow on to the Basic Website Tutorial - http://wiki.processwire.com/index.php/Simple_News_System ) - BE CAREFUL - don't mix the two. Either use the wiki or my files, not both at the same time. To be honest, you will learn more using the wiki version. This is an example script showing how to create a very basic news system with categories in PW. It includes templates and functions and full instructions of how to use it, which fields to create and so on. This is NOT a module or an instant solution, but it will help get you going faster if you have not done this sort of thing before. This example is for when you have a site carefully constructed round the page hierarchy, but want to add a basic news or blog that sits at least partly outside that tree. The system helps you to create a single news page that lists articles that are stored under a hidden parent. The articles are sorted by category - categories are created under another hidden parent and are selected with a page field. Full instructions are in the main newsfunctions.inc script and everything is commented. You can find it all here: https://github.com/jsanglier/Pw-News Joss PS: This is just one way to do a news system and should be taken as an example, not as the best way.

Absolutely, and it is not designed to compete with WordPress either. Having said that, you can create incredible blog applications with ProcessWire - just for fun!

Please do. I had to make some odd changes to it because, of course, I created it with one of my installs which has things in strange places! I think I changed it to fit a standard install, however.

@ Aren One thing you need to remember is that ProcessWire is designed to allow you to develop any sort of website - so doing some sort of a blog is only one of thousands of things you might do. Also, a blog you might want may well be completely different to what another developer wants. However, it is not that complicated - the news system I have just posted for you took me an hour or so from scratch, including writing all the instructions. And I am not a developer! So, while there is no blogging setup in ProcessWire to simplify, little bits of code that can speed up development is never a bad things to have kicking around.

"So someone in your team should be the gatekeeper for these administration resources." Yep, always keep someone around who can take all the blame. My dog has a very rough time in that regard.

I have sort of started the process by accident in answering a different post https://github.com/jsanglier/Pw-News The way I have done these (because it is the way I now tend to work) is to do them as functions that can just be rendered on whatever page.

Right, here you go! This is three files complete with instructions for creating news. You need to do some work, but a lot of it is done already. Full instructions are in the newsfunctions.inc file. Just copy the three files to /site/templates/ and then change as you wish. This does not NOW includes categories - just a simple news posting. But it is enough to get you started. It is for a main news page that lists news articles and links them through to their own template. The news articles are all pages created under a hidden page. The main news index page includes pagination. https://github.com/jsanglier/Pw-News Joss

Okay, I am sort of working on both - give me a day or two.

Interesting review, and I have sympathy with his confusion about pages - which is why I wrote my tongue in cheek post about pages ages ago. However, he has missed the point that pages are a versatile tool and not just lump of text. He also seems to have misunderstood about the relationship between the page list and the site and that you are not limited to the page list structure if you dont want to be. I think he sees it as something that is great for a handful of pages and does not realise that it can be used for vast, resource driven sites and solutions. But that is probably not the reviewers fault, but maybe something that we can all sell better from this end.

I tend to make sure that the parent is Hidden, then there is no automatic link to the kids (whatever state they are in) unless you create one. That way they don't accidentally become visible because someone did the wrong setting. If you want a catch all, you could always give them a template file but don't render any of the fields. You can then redirect that anywhere you wanted. I would think just keeping the parent Hidden will be easier though and means that the children (if published) are still accessible by page fields, if you need that later.

Mine do! If possible I like to surround it with bouncing ball, flashing arrows and a horde of Angels singing "We'll meet again" Oh, and I tend not to have it linked .... This is one for Bootstrap classes. (I have left off the dancing chihuahuas) <ul class='breadcrumb'> <?php echo "<li><a href='{$pages->get("/")->url}'><i class='icon-home'></i></a> </li>"; foreach($page->parents as $parent) { echo "<li><a href='{$parent->url}'>{$parent->title}</a> <span class='divider'>/</span></li>"; } echo "<li class='active'>{$page->title}</li>"; ?> </ul>

Hmmm.. Might be exactly what I need for something

Planning! Hi Luke I am a great believer that what ever system you are working on you should only be creating the fields and so on once you have already decided exactly what is needed. With ProcessWire, since you create the templates and fields directly in the back end (as opposed to the template file which you will use for all your presentation work), this is particularly important, since you will want to make sure that you are not duplicating fields unnecessarily. For instance, if you create a particular textarea/tinymce field, you may want to re-use that on several templates across your site. Once that work is done, then the people involved have a much better idea what template files they will be creating and what they will need them to do, and that work can then be delegated to team members. Joss

I would guess that since you are not doing a specific action of removing the images field, then there is no command to delete the actual files.

I was just messing around with something else, and I realised the term "CMS Framework" as a phrase is a nice compromise.

Sounds like you have a password incompatibility problem - there is a different character length between versions. Have a search on Stack Overflow - there are a lot of posts about this - maybe one will help you.

Part of the trick is defining the target market segment. There is an industry wide problem at the moment where market segments are very poorly defined. There are two reasons for this: Firstly, the majority of marketing is done by non marketing people, and secondly this is all very new and shiny and no one is totally sure what to do with it yet. This even shows with companies like MicroGoopple - with the lack of strict market segments, they have all tended to go for scatter gun marketing in every area all at once. With ProcessWire, the issue is "Is it a CMS or not?" Well, that runs into a problem almost immediately - what on earth is a CMS? Or, more precisely, who is a CMS for? Blogger is a CMS. It is a straightforward system that allows people to manage content in a very precise and defined way. Wordpress is a CMS. It works like blogger, except you can host it locally and make it work not like blogger at all. Joomla is a CMS, except they would like to point out that it is a Framework with a CMS on top of it. Drupal is definitely a CMS - it allows you to manage anything, but it is a hell of a long way off from Blogger where we started. ProcessWire is a CMS - except it is a CMS that allows you to imagine and build your own CMS on top of it. So, it is not a CMS then? Certainly, if all the other CMSs are defined by the fact that they are a central system where you can "theme" and build modularly using modules/plugins/whatever, then ProcessWire is possibly not a CMS - it is too flexible and does not have that same central construction mantra. To a certain extent, it is a misuse of the term CMS that is causing all the problems. Out of the box, Blogger, Wordpress and Joomla are probably not CMSs, but AMS - article management systems. Since, unless you stick all kinds of third party additions to them, managing articles is all they do. Drupal is a bit more flexible out of the box. So, it would help marketing if all those others would go off and re-brand themselves as AMSs and leave the more versatile offerings to use the term CMS a little more correctly. Well, that is not going to happen - and in addition, there is quite a gap between what Drupal and Liferay do on one side and what EE, ModX and PW do on another. We have seen in these forums a couple of newer people posting, with quite genuine reasons, that they are confused that PW does not have a theming system like Wordpress has. It doesn't, of course, because it is not doing what Wordpress does - at least not out of the box. You can build a Wordpress out of it (I am having fun doing one at the moment) and you could even build a theming system to go with that - but that would be what you can DO with ProcessWire, not what it is. To my mind, ProcessWire is, at the end of the day, not a CMS as such, or an AMS, possibly more of a CMF, but not even that totally. ProcessWIre is really, a very strong starting point. If you want to develop a web tool of some description, PW is where you start. It allows you to get your visual interface and core data together very quickly and tidily and then gives you enough tools to develop a fine-grained approach to what you actually want to do with that data. In a funny sort of way, it is, for the new browser orientated development world, what Desktop development tools were to users back in the late nineties. It does a lot of the heavy lifting for you while you get on with the presentation and fabrication. So, back to the market - PW is a professional's tool. It can be used by amateurs like me and even quite effectively, but those with better knowledge are always going to be able to take development with PW far further and faster. As such, I think it should be marketed in the first instance as a tool for developers/designers (I really do not like splitting those groups), while making sure it is accessible for those with less knowledge, but like to learn. In practice this means presenting it to the development community through seminars and user-group meets, as well as making sure that each geographical market area has a common focus point (like the German website this thread is meant to be about) that can be used to gather in and grow local communities. Now, this is where I lift the lid on what the marketing industry really thinks of this sort of product. Basically, promoting open source systems is no different to promoting a rock band - you need fansites, reviews, groupies, and everything that goes with it! I am sorry, but I would be hard pressed to put a Rizzla paper between the marketing brief for a highly regarded Open Source system and one for the newest boy band. And having seen the behaviour of some developers on "other" open source projects, there is little difference there either! Joss

Oh, I love keeping you on your toes! Yeah, I think with these Framework Profiles, there should always be two - one which is basically just the framework ready to go with maybe some helper functions to be used as snippets, and a second (based on the first) which actually gives a starting point. I am putting an identical one together based on Foundation 4, by the way, though I am not going to attempt a Foundation admin!!!