Pete

CTRL + F5 a few times - fixed it earlier today.

It doesn't, but that's not a problem. You can build any structure you like - everything is based around custom fields and it only takes a short space of time, so the beauty of it is that you end up with exactly what you want rather than what a module (assuming you mean like modules with other CMS's) might force you to have. This means you can add any addtional fields you might like and so on. Can you describe what you want to achieve or point us to an example elsewhere and we can give you a few pointers.

The aims seem to be: One site folder One templates folder (which is where it gets messy) One admin interface Potential to share information across sites by calling something like $pages->context('sitename')->find('selector'); - This is the best way I can think of making it work anyway I'm trying to do this without the time to draw a diagram, but the way I would see a new module working would be something like this: Have a single wire folder Have a /site/contexts/ folder, each site has its own folder within containing templates for that context (that way you could ignore the original templates folder) Write some API code to do something like $pages->context('sitename')->find('selector'); DON'T show all the sites in one tree in the admin - no need, just have a drop-down at the top-right somewhere to switch between contexts Give them the option NOT to share the same database if desired. This then caters for marketing mini-sites to share the same DB but larger sites to be separate, as well as allowing for complete separation of templates and fields if desired (useful for creative studios with many sites) This addresses all the requirements I think. There are a few compromises, but this ticks off the main aims I listed and doesn't over-complicate matters. What do you guys think? MODx contexts made my brain hurt so I'm throwing this idea out as something that's hopefully simpler to setup, understand and manage Other considerations are: You need some way of having single sign-on to switch between contexts (let's just call them sites hey? I'm getting confused every time I type that ) if you use the separate databases approach Someone needs to add some functions into the API to make this work the way I described above, but I think that's possible Also the selectors could just be like $site->get('sitename')->pages->find('selector') but I like my first idea better Maybe $pages->site('sitename')->find('selector') though since I've totally gone off the term "contexts" now. Of course if you don't specify the site() part then it will default to the site that the template file is in.# And anything else you can think of...

Amazing, I'll have a look at this later today

A lot of us do this and have a Tools template with just the title field that are used to populate Page fields for selects, autocompletes and ASMselects etc. It's perfectly normal to do this in ProcessWire bit yes it does feel strange to begin with. One advantage is that using ASMseldct (or others) is that you cam tick the option to add more values on the fly when adding pages. Give it a try

I'm saying noooooooooothing

Done, and tagged as a module request

I'm up for this.

Just building on what Luis said, the thing about ProcessWire is that it doesn't make any assumptions about your templates on the front-end, so you couldn't package it as a working part of the core anyway as the first thing most people do is implement their own templates which would strip out the necessary tags to make this work. I think it could certainly be a module (just so it gets bundled with one or more of those editors) that can be downloaded and installed with simple instructions for the developer to implement the necessary tags into their template though, so that's certainly worthwhile someone pursuing. There are some considerations though, such as the way images are handled in ProcessWire, that require further thought as well (hence why I'm thinking a module again). As with most things in PW though, it's certainly possible to implement

ALT+TAB breaks it

Fixed another issue with not being able to see quotes or code blocks when editing - now you can see them which makes it easier to edit them. Note for all: Use the quote or code buttons in the editor as they're the best way of adding either reliably. They've improved them in this version. Heck, even code indents work with them EDIT: Nico - I fixed the nav colour to match the site too.

Willy needs this hat: http://www.loveitsomuch.com/stores/yoda-hat-crochet-pattern-newborn-toddler,260842.html

Luis - can you refresh again? I think there's a caching issue but I might have solved it this end (the JS cache now has a different hash in it). Oddly though I didn't see the problem in same version of Opera on Windows 8 here. Nico - yep - that's on my list. My local copy was a bit older than the current theme so I'll match that at some point.

I'm sure there's a module somewhere that actually added its own API functions - can anyone remember which one it was though?

Thanks - looking forward to trying out the alternative config

I'm all over this like a bad rash

Same to you with bells on Luis & Tina - might be a cache issue? Try a few CTRL & F5's to see if it sorts it please as there was an issue yesterday briefly when a lot of people were online that I fixed.

I did something similar in 2011. The good thing was it was a personal project, the bad thing was it was a few months' worth of evenings that I'd lost Some evenings were more productive than others of course so I probably only lost 2 weeks of work in real terms, but it still hurts. The end result was that, since it was a ProcessWire site, I came back to it a bit later on to re-do the bits I'd lost and not only was I quicker at it the second time around I actually did a better job of it too in about 3 weeks worth of evenings. So yes, I try to backup often nowadays

It's really easy to do the path stuff - you can split out that information by running a PHP explode() function on the path name and then picking out the year, month and day and then have whatever structure you like in PW. The main thing I keep asking though is more important and harder work - do you have an example of one of the articles so I can see the contents and suggest how you would parse all that? Basically if I could see that, I can pretty much give you the code to do it as I've got a converter script on my PC here Another question I asked earlier was how images are stored for each article (when they have images)? Are images just in the folder with the file that contains the text? The paths can stay the same as the text versions if you like - /issues/2013/Jan/08/ for example, but then have a more meaningful title on the end, like "news-story-title" if you like. You could also do away with the date in the path altogether and just have /issues/news-story-title and people can use an archive page to go through the days/months/years. But I'll rewind a bit as the harder part will be importing the articles. Iterating through your current directories, assuming the path you have for the files is consistent back through the months and years is easy, but I'm itching to see the content of one of the text files to see how hard that side of things might be

It's ProcessWire API code, which is basically PHP functions for the most part. Best thing to do is if you can share an example news post like I mentioned and one of us can probably give you a better idea.

Any topic like this is bound to get negative at some point, whether it be people like me balking at the price of things or others with different dislikes. All that aside, what would we achieve from more hands on deck? Well let's see - the majority of people here help each other out. Many people contribute ny way of modules (which are simple to write compared to other systems). Others spread the word because they like the project so much. It's not a case of bums on seats - we've got a growing commmunity of active users who help each other and enrich the project going forwards. We've been lucky enough to attract a lot of talented people who used to work with other well-developed systems who now prefer ProcessWire because it genuinely saves them time and stress and makes building websites fun and quick. It's not for everyone though - you can use it to build pretty much everything you might need in a website but you might want to take a step back if you were thinking of building a specific web application or other project that requires complex relationships in the database (although some folks here are managing to build those in ProcessWire too). We're no Wordpress/Joomla rival in terms of numbers, but all I see with those platforms is clunkyness and bloat personally. Modules for both are hit and miss as most here are aware, and clients will often push one of those systems for the sole reason that they've heard of them before and trust the name. I'm glad we're not that big yet because we're at a stage where we have some quality modules and can keep an eye on them and suggest improvements to them. It's not imposed quality control, it's helping each other out. Not sure where my train of thought is rolling off to, but I think the bit about what we would achieve by people coming here from other systems is that we often then have the skills as a community to help others who come from those systems. We often see questions like "I do this in my old CMS, how would I do it in PW?" which is great as the more experience we have in the community the quicker we can help those people out. As for any perceived plagiarism with any of the admin themes (I've not used EE so don't know which theme you're referring to, hence my choice of wording), if there is an issue then please inform ryan and I'm sure he will look into it. If nobody makes a complaint then we can't take action. I hope none of that has come across as negative. I'm not the best at being impartial on forums and I'm just trying to get my own points across. EDIT: @Antti - fixed, there are a few styling issues left I think.

From memory the XML sitemap class doesn't check for multisite needs, though I seem to recall someone asking this before and maybe even posting some altered code (I might have dreamed that bit thouugh!).

At least indenting seems to work. What is infuriating though is that the new code button does indent stuff fine, but it's hard to see what's code and what isn't when you go to edit a post. Still, I just checked and you can add to code when editing a post and it seems fine - you just have to realise that the stuff in Courier font is code. It's like they changed the system so it works, but at the same time gave more margin for error

Well I did fix the JS issue so that's probably it Soma Tina - not sure which links you mean? They should all be up top if we're talking the links in the light-blue section, or other links are at the very top on the dark bar above that. I just checked the old template against the new one and don't see any missing links.

EDIT: arjen beat me to it