Yes, I know, I'm a grammar pedant. I've accepted this.

Anyway, when you've got a site set up with separate dev and live sites, the message letting you know you're on the dev site should read "CHANGES WILL NOT AFFECT LIVE SITE!". When used as a verb as it is here, you need to use "affect", as "effect" is the noun, eg "Changes will not have any effect on the live site".

So I'm not sure if this should go into the bug report forum or not, but here goes.

I'm building a site at the moment on BigTree that employs self-hosted videos (with HTML5 <video> on the front-end). For a couple of days, I could not, no matter what I tried, make the videos play on iOS devices.

For reference, my videos were stored in /site/files/dictionary/videos/1.mp4. But on the front-end, I was referencing them simply via /files/dictionary/videos/1.mp4 because I know that normally the .htaccess rewrites will transparently send the file through correctly. And on desktop browsers, that's what was happening. But for some reason iOS browsers simply refused to play ball: they'd recognise that I was trying to look at a video file, and bring up the video playback UI, but would completely fail to load it.

Eventually, I discovered the problem: if I went into my unix terminal and tried to access the video file via curl, the output would be the BigTree 404 page template, not the video itself. I just thought that maybe curl somehow doesn't respect mod_rewrite, but it did get me thinking about what the iOS browsers were doing. So on my iPad I tried to access the file with the /site/ part of the URL included and - hey presto - it worked.

So this is a long-winded way of saying that BigTree's default .htaccess rewriting seems to interfere with certain operations on iOS browsers

I love the admin bar, certainly makes it a lot quicker and easier for users to update their content in a dead-simple environment.

But something I noticed, and was very confused by, when I first tested out the demo site (specifically the tree pages) is that it's possible to have "pages" that are actually routed pages showing module content, but when you try to edit the page using the admin bar, you only get the resources attached to that page's template - most likely just a page_header variable. When I was testing out the demo, I didn't yet understand the module system so this was utterly confusing to me, I didn't get why some pages let me edit the content from the admin bar but some didn't.

Now that I understand modules, I understand why the content for a "module page" isn't available from the admin bar. But it occurs to me that my users will still be just as confused. I'm building a site that has modules for a staff directory and a news blog. I'd very much like to be able to have the users edit the content from both of those modules from the pages to which they apply.

(I'm assuming here that there isn't already a way to do this that I've just missed )

So what I'd suggest is this (keeping in mind that I'm largely unfamiliar with the PHP behind BigTree itself): create a method in the BigTreeModule class that can be called from within a routed module template that allows you to pass the module and ID of the content you want to edit to the Admin bar, and if that is specified, the "edit content" button shows the edit form from the appropriate module instead.

As BigTree is open source I'll gladly put in the effort to put together such functionality myself, but I'm just looking for an idea from people more familiar with things as to whether it's even feasible before I do so.

So does this sound good?

So the portfolio site I'm building is one of those ones you see a lot these days where all of the content is displayed in large distinct sections all down the one single page - something like this site.

For ease of editing, I've set up the content in the backend using separate pages, some of which are tied to modules for things like case studies and portfolio items etc.

My problem is that while it's easy enough to spit out the content of each page by looping through the pages and using $cms->getPage(), that doesn't work for pages with different templates. I've set up templates to use for each type of content block, but I can't figure out how to render each of those templates and then provide that rendered content into the "master" template I'm using as the home page.

What I'd like to do is process the first part of the template rendering process (as described here), but only the first part, and then insert that into one of the content 'blocks' on the main page.

Is that possible? Am I barking up the wrong tree, and should I be looking into Callouts? I'm still a bit of a noob here and don't understand how the callouts system works so I may be missing something obvious.

I'd really appreciate any help or advice.

Thanks!